How we assess
Every applicant goes through 5 gates: application, an AI-assisted screen, a live technical assessment scored by a practice lead, a client-fit interview, and reference and credential checks. The questions below come from the live assessment. We score answers on reasoning and trade-offs, not on recalling definitions.
20 technical questions with model-answer hints
Questions 1–10 (role-specific)
Question 1: How do you define opportunity stages?
Model-answer hint
Buyer-verified exit criteria rather than seller activity; consistent across teams.
Question 2: Forecast accuracy is poor. Where do you start?
Model-answer hint
Stage definitions, data hygiene, historical conversion analysis, cadence, accountability.
Question 3: Design lead routing for a 30-person sales team.
Model-answer hint
Territory and segment rules, round-robin, SLAs, fallbacks, monitoring.
Question 4: How do you design balanced territories?
Model-answer hint
Account potential, workload, geography, coverage model, fairness.
Question 5: What goes into compensation plan design?
Model-answer hint
Behaviour alignment, simplicity, accelerators, caps, cost modelling.
Question 6: How do you keep CRM data clean?
Model-answer hint
Validation rules, required fields at the right stage, automation, audits, adoption.
Question 7: Which metrics do you report weekly to the CRO?
Model-answer hint
Pipeline coverage, creation, conversion, velocity, forecast versus actual.
Question 8: How do you align marketing and sales definitions?
Model-answer hint
Shared lifecycle stages, SLAs, joint reporting.
Question 9: When do you build a RevOps tool versus buy one?
Model-answer hint
Cost, maintenance, scale, integration, time to value.
Question 10: Tell us about a system change that failed adoption.
Model-answer hint
Lessons on change management, training and stakeholder buy-in.
Questions 11–20 (Sales core)
Question 11: Walk us through your qualification framework on a live deal.
Model-answer hint
MEDDPICC elements with evidence, gaps identified, next actions.
Question 12: How do you prepare for a first meeting with a C-level buyer?
Model-answer hint
account research, a hypothesis about their priorities, tailored questions, a clear desired outcome.
Question 13: How do you prioritise your time across a large territory or book?
Model-answer hint
account tiering, potential versus effort, pipeline coverage, weekly planning.
Question 14: A buyer goes silent after a strong evaluation. What do you do?
Model-answer hint
diagnose the cause, multi-thread contacts, offer value rather than pressure, re-qualify honestly.
Question 15: How do you work across Arabic- and English-speaking stakeholders in one deal?
Model-answer hint
language choice per audience, consistent bilingual materials, cultural norms, clear written follow-ups.
Question 16: What does good written follow-up after a meeting look like?
Model-answer hint
recap of the buyer’s priorities, next steps with dates and owners, sent within 24 hours.
Question 17: How do you work with technical colleagues in a deal?
Model-answer hint
clear roles, shared discovery, joint planning, no over-promising.
Question 18: How do you expand an existing account?
Model-answer hint
value delivered so far, new stakeholders, adjacent use cases, timing with renewals.
Question 19: How do you use conversation intelligence or AI tools in your sales work?
Model-answer hint
call review, coaching, research and summaries, with human judgement on decisions.
Question 20: Describe a customer relationship you rescued after a service failure.
Model-answer hint
ownership, transparent communication, recovery plan, relationship outcome.
Interviewer tip: Ask for a real example after every answer. Strong candidates describe what they built, what broke and what they changed.
Practical task
Timebox 3 hours. Given an anonymised Salesforce export with 12 months of opportunities, leads and activities, diagnose the 3 biggest data or process problems, propose new stage definitions and routing rules, and build a simple pipeline and forecast dashboard in a tool of your choice.
How to run it Share the brief 24 hours ahead or run it live. Ask the candidate to talk through trade-offs as they work; reasoning matters more than a finished artefact.
Red flags our practice leads watch for
- Builds dashboards without fixing the underlying definitions.
- Over-customises the CRM with no documentation.
- Cannot write basic SQL or reason about data.
- Ignores user adoption when changing processes.
- Universal flag: Vague answers that never reach a concrete system, number or decision the candidate personally owned.
The scorecard we use
Score each dimension 1–4 (1 = no evidence, 2 = partial, 3 = solid, 4 = exceptional):
| Dimension | Weight | What a 4 looks like |
|---|---|---|
| Technical depth, production judgement and security | 40% | Explains how and why, designs for failure and sensitive data, and knows each tool’s limits |
| Practical task and problem solving | 30% | Delivers a working solution with tests and documented decisions |
| Communication and documentation | 20% | Explains clearly to technical and non-technical audiences, in English or Arabic |
| References and regional context | 10% | References confirm the claimed scope; knows the frameworks and data-residency rules that apply |
Pass bar: weighted average of 3.0 out of 4 or higher, with no dimension below 2. The practice lead approves the final result.