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: Hosted model API or self-hosted open model: how do you decide?
Model-answer hint
residency, cost at volume, latency, quality on real tasks, operational burden.
Question 2: Sketch a reference architecture for an enterprise RAG platform.
Model-answer hint
ingestion, embedding, vector store, retrieval API, LLM gateway, evaluation, observability, access control.
Question 3: What belongs in an LLM gateway?
Model-answer hint
routing, authentication, rate limits, logging, redaction, cost attribution, fallbacks.
Question 4: The best model is only offered outside the country. What now?
Model-answer hint
classify data, keep restricted data in-region, redact, route sensitive classes to in-region models.
Question 5: How do you build a TCO model for a copilot rollout?
Model-answer hint
users × queries × tokens, retrieval and hosting, growth scenarios, people cost.
Question 6: How do you compare 3 vector databases fairly?
Model-answer hint
own data and queries, recall at k, latency under load, filtering, cost, operability.
Question 7: Which identity model do agents use when acting for a user?
Model-answer hint
delegated, scoped tokens, on-behalf-of flows, per-action audit.
Question 8: What does an AI architecture review board check?
Model-answer hint
risk tier, data flows, security, evaluation plan, cost, exit strategy.
Question 9: How do you avoid lock-in to one model provider?
Model-answer hint
gateway abstraction, portable prompts and evals, open formats, contract terms.
Question 10: How would you explain a cost overrun to a steering committee?
Model-answer hint
root cause, evidence, options with trade-offs, a clear recommendation.
Questions 11–20 (AI & Data core)
Question 11: How do you decide between rules, classic ML and an LLM for a problem?
Model-answer hint
start from decision value and error cost; choose the simplest option that meets the metric.
Question 12: How do you detect training-serving skew?
Model-answer hint
shared feature code, logged inference inputs, distribution checks between training and live data.
Question 13: How do you build an evaluation set that predicts production results?
Model-answer hint
representative sampling, slice coverage, leakage checks, labelled with measured agreement, refreshed on a schedule.
Question 14: What goes on a model-health dashboard, and who acts on each signal?
Model-answer hint
quality, drift, latency, cost and the business KPI, each with an owner and threshold.
Question 15: How do you handle personal data in a training pipeline under PDPL or GDPR?
Model-answer hint
minimisation, lawful basis, pseudonymisation, residency, retention limits, DPIA.
Question 16: How do you roll back a model or prompt change that degrades results?
Model-answer hint
versioned registry, canary or shadow release, automated gates, one-step rollback.
Question 17: When does fine-tuning beat retrieval or better prompting?
Model-answer hint
behaviour, format and domain style favour tuning; fresh facts favour retrieval; weigh data and cost.
Question 18: Describe a data-quality incident you caught.
Model-answer hint
how it was detected, root cause, the contract or test added, the alert that now exists.
Question 19: How do you forecast and cap the monthly cost of an AI workload?
Model-answer hint
tokens or GPU hours, caching, batching, model routing, budgets with alerts.
Question 20: Explain a modelling trade-off you made to a non-technical executive.
Model-answer hint
plain language, business impact, the option rejected and why.
Interviewer tip: Ask for a real example after every answer. Strong candidates describe what they built, what broke and what they changed.
Practical task
Produce a 2-page target architecture and cost model for a bilingual customer-service copilot used by 2,000 agents at a Saudi bank, covering data residency, identity, model selection rationale, evaluation approach and a 12-month run-rate under 2 scenarios.
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
- Recommends a favourite vendor without testing on the client’s data.
- Cannot estimate cost per user or per query, even roughly.
- Defers residency and identity to “a later phase”.
- Produces diagrams with no path to a delivery plan.
- 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.