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 would you design a lead scoring model from scratch?
Model-answer hint
Closed-won analysis, fit plus behaviour, thresholds agreed with sales, score decay, review cadence.
Question 2: MQLs are up but sales says quality is down. What do you do?
Model-answer hint
Lead feedback data, scoring review, source analysis, follow-up SLA, recycling rules.
Question 3: How do you structure lifecycle stages?
Model-answer hint
Clear definitions, entry and exit criteria, ownership, alignment with CRM stages.
Question 4: What does DMARC do and why does it matter?
Model-answer hint
Domain authentication, spoofing protection, mailbox-provider requirements for bulk senders.
Question 5: A contact withdraws consent. How does that reach every system?
Model-answer hint
Central consent record, sync to all tools, suppression lists, audit trail.
Question 6: Design an onboarding journey for a B2B free trial.
Model-answer hint
Behaviour triggers, product data, branching, sales alerts, activation measured.
Question 7: Which attribution model would you recommend and why?
Model-answer hint
Depends on context; multi-touch versus first or last touch; limits; consistency over time.
Question 8: How do you prevent workflow chaos in a large HubSpot instance?
Model-answer hint
Naming conventions, documentation, named owners, audits, retiring unused flows.
Question 9: How do you bring product usage data into marketing?
Model-answer hint
Segment or reverse ETL, event definitions, privacy review, concrete use cases.
Question 10: Tell us about an automation that went wrong.
Model-answer hint
Ownership, root cause, safeguards added afterwards.
Questions 11–20 (Marketing core)
Question 11: How do you connect marketing activity to revenue?
Model-answer hint
tracking plan, CRM integration, known attribution limits, incrementality tests, definitions agreed with sales.
Question 12: How do you design a marketing experiment?
Model-answer hint
hypothesis, primary metric, sample size, duration, stopping rule, documented result.
Question 13: How do you adapt a global campaign for Gulf audiences?
Model-answer hint
cultural review, Arabic-first copy, local platforms such as Snapchat, local moments, regulatory checks.
Question 14: How do you agree with sales on what counts as a qualified lead?
Model-answer hint
shared definitions, follow-up SLAs, feedback loops, joint review of outcomes.
Question 15: When do you write in Khaleeji dialect versus Modern Standard Arabic?
Model-answer hint
channel, audience and formality, guided by a brand voice guide; never translated English.
Question 16: How do you use generative AI in marketing without harming the brand?
Model-answer hint
governance rules, human review, fact-checking, disclosure, no confidential data in tools.
Question 17: Which metrics do you report to a CMO every week?
Model-answer hint
pipeline or revenue contribution, CAC, conversion rates, spend pacing; few vanity metrics.
Question 18: How do you brief a creative or content team?
Model-answer hint
objective, audience insight, one message, mandatory elements, success measure.
Question 19: How do you decide to stop a channel or programme?
Model-answer hint
thresholds agreed in advance, marginal returns, opportunity cost, evidence.
Question 20: Describe a campaign that failed and what you learned.
Model-answer hint
honest diagnosis, the data used, the specific change made afterwards.
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 2 hours. Given an anonymised export of 5,000 CRM contacts with activity and deal outcomes, propose a lead scoring model with weights and thresholds, design a 5-step nurture journey for mid-score leads, and list the consent and data-quality fixes required before launch.
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 scoring without sales input or outcome data.
- Treats consent as a single checkbox on a form.
- Has no documentation habits.
- Measures success by email open rates alone.
- 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.