Join the team

OpsPal freelancer questionnaire

We work with senior operators and builders on real client systems. This form helps us understand how you think, what you have shipped, and where you want to focus. There are no trick questions—answer in your own voice.

Prefer to meet us first? Read about who we are or book a call for client work.

1 · Basic profile

What is your full name? What is your email address? LinkedIn, portfolio, GitHub, or Upwork (links) What time zone are you in? How many hours per week are you available? What type of work are you looking for? What best describes you?

2 · Core skill self-assessment (1–5)

1 = no experience · 2 = basic exposure · 3 = with guidance · 4 = independently · 5 = architect, troubleshoot, teach

CRM setup and administration

Workflow automation

API integrations

Front-end development

Back-end development

Database design

Reporting and dashboards

AI prompting / AI workflow design

QA testing

SOP creation

Client communication

Project scoping

Troubleshooting broken systems

Working with ambiguous requirements

3 · Tools and platforms

Which CRMs have you used? Rate your skill for each (Salesforce, HubSpot, Pipedrive, GoHighLevel, Zoho, Airtable, Close, other). Automation tools (Zapier, Make, n8n, Workato, Pipedream, Google Apps Script, other). Project-management tools (ClickUp, Asana, Monday, Trello, Jira, Linear, Notion, other). Data or dashboard tools (Sheets, Excel, Looker Studio, Power BI, Tableau, Metabase, SQL, BigQuery, other). AI tools you use regularly (ChatGPT, Claude, Gemini, Perplexity, Cursor, Copilot, Replit, other). Programming languages or frameworks you use professionally. Tools or platforms you are genuinely advanced in. Tools you have used but would not feel comfortable owning independently.

4 · CRM / RevOps capability

Describe the most complex CRM or operations system you have worked on. Custom fields, objects, properties, pipelines, or stages—examples. Lead routing, deal routing, task routing, or assignment logic. Validation rules, required fields, or stage-exit criteria. SLA timers, breach alerts, or escalation workflows. Cleaning duplicate, messy, or incomplete CRM data—your process. Dashboards or reports for leadership, sales, marketing, or operations. If a client says, “Our CRM is a mess,” what do you inspect first? CRM mistakes inexperienced operators commonly make.

5 · Automation and integration

Describe an automation you built that saved time, reduced errors, or improved a process. When would you use Zapier or Make versus custom code? Webhooks, APIs, authentication, or middleware—explain your experience. How do you test an automation before making it live? Failed automation steps, duplicate records, or broken workflows—how you handle them. How do you document automations so someone else can maintain them? An automation you would refuse to build because it is too fragile or risky.

6 · Software / technical ability

What is the most complex software or technical project you have built? What parts did you personally own (architecture, frontend, backend, database, deployment, QA, documentation)? Strongest parts of software development for you. Weakest parts of software development for you. Experience with sandbox, staging, or development environments. How you manage environment variables, API keys, passwords, or secrets. How you approach debugging when something breaks. Have you ever broken a live system? What happened, and how did you fix it?

7 · AI workflow capability

How do you use AI in your work today? AI workflows connected to CRMs, calls, emails, forms, tickets, or documents. Prompts for structured outputs (summaries, CRM fields, tags, classifications, next steps). How you make AI outputs more accurate, useful, and consistent. How you handle confidential or sensitive client data when using AI tools.

8 · Project execution and communication

What information do you need before starting a project? How do you handle unclear or incomplete requirements? How do you estimate timelines and communicate delays? How do you push back when a client asks for something that is not a good idea? What should be included in a good weekly project update? SOPs, Loom walkthroughs, changelogs, or handoff documentation—examples. What kind of client, manager, or project environment gets your best work?

9 · Strengths, weaknesses, and fit

Top three technical strengths. Top three operational strengths. Top three weaknesses or areas where you need support. Types of tasks that drain your energy or slow you down. Types of projects that put you in flow. Mistakes you tend to make under pressure. What should OpsPal know before assigning you client-facing work?

10 · Practical case study

A client uses HubSpot, Slack, Google Sheets, Typeform, Zapier, and Gmail. Leads submit a form, but some duplicate, some do not get assigned, Slack alerts fire inconsistently, and dashboard numbers look wrong.

What would you inspect first? What would your first 7 days of fixing that system look like? What would you document, test, and hand off before calling the project complete?

Optional scoring tags

After reviewing answers, tag each person as one or more (optional self-selection).

CRM Admin — fields, pipelines, permissions, cleanup RevOps Builder — routing, SLAs, dashboards, lifecycle Automation Specialist — Zapier, Make, n8n, alerts Technical Ops Generalist — tool stitching, SOPs Software Engineer — apps, portals, APIs Data Analyst — dashboards, KPI definitions, reporting QA AI Workflow Builder — prompts, CRM enrichment QA / Documentation — testing, changelogs, handoffs Client-Facing Operator — discovery, updates, training

By submitting, you confirm the information is accurate to the best of your knowledge. We use this only to evaluate fit for OpsPal delivery work.