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 build a sink-and-source model for a new currency?
Model-answer hint
map every source and sink, rates per segment, simulate over time, check inflation.
Question 2: How do you detect inflation in a live economy?
Model-answer hint
balances by cohort, earn-to-spend ratios, price sensitivity, item value drift.
Question 3: Walk through designing a battle pass.
Model-answer hint
tiers, free versus premium value, progression pacing, price, season length.
Question 4: How do you design a personalised offer system?
Model-answer hint
segmentation, triggers, value ratios, frequency caps, fairness rules.
Question 5: How do you set up a pricing A/B test?
Model-answer hint
hypothesis, randomisation, sample size, primary and guardrail metrics, duration.
Question 6: ARPDAU versus ARPPU: when does each mislead?
Model-answer hint
all users versus payers; mix shifts and conversion changes distort both.
Question 7: How do ads and IAP coexist without cannibalisation?
Model-answer hint
target non-payers, rewarded placements, measure impact on LTV.
Question 8: How do you estimate LTV early in soft launch?
Model-answer hint
cohort curves, retention modelling, early spend signals, confidence ranges.
Question 9: Which regulatory issues affect monetisation design?
Model-answer hint
loot-box disclosure and odds, age rules, consumer protection, platform policy.
Question 10: How do you respond to community backlash on pricing?
Model-answer hint
combine data and sentiment, communicate openly, adjust, compensate where fair.
Questions 11–20 (Game Development core)
Question 11: How do you find and fix a frame-time spike on target hardware?
Model-answer hint
platform profiler, isolate CPU, GPU or I/O, per-system budgets, verify on device.
Question 12: How do you manage memory budgets on mobile?
Model-answer hint
per-category budgets, texture compression, streaming, leak tracking on low-end devices.
Question 13: How do you keep gameplay data-driven for designers?
Model-answer hint
config assets or tables, hot reload, validation, simple tooling.
Question 14: A mechanic “doesn’t feel right”. What do you do?
Model-answer hint
quick prototype, exposed tuning values, playtests, combine feel with telemetry.
Question 15: How do you organise version control for large binary assets?
Model-answer hint
Perforce streams or Git LFS, file locking, branch strategy, CI builds.
Question 16: What makes a build pipeline dependable for a live game?
Model-answer hint
automated builds, smoke tests, versioned content, staged rollout, fast rollback.
Question 17: How do you prepare a title for platform certification?
Model-answer hint
requirements checklist from day one, automated checks, an internal pre-certification pass.
Question 18: How do you use telemetry after soft launch?
Model-answer hint
funnels, D1/D7/D30 retention, cohorts, A/B tests, guardrail metrics.
Question 19: How do you handle Arabic text and RTL layouts in game UI?
Model-answer hint
glyph shaping, mirrored layouts, font fallback, text expansion, culturalisation review.
Question 20: Describe a feature you cut or rescoped to hit a milestone.
Model-answer hint
trade-off logic, stakeholder alignment, effect on the player.
Interviewer tip: Ask for a real example after every answer. Strong candidates describe what they built, what broke and what they changed.
Practical task
Using a spreadsheet of a mid-core game’s soft-launch data, identify the 2 biggest economy or monetisation problems, propose a redesigned starter offer and one new sink, model their expected impact and design the A/B test that would validate them.
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
- Optimises revenue with no guardrail metrics.
- Cannot explain the statistical basics of an A/B test.
- Designs offers without a model of the economy behind them.
- Dismisses player sentiment or regulation.
- 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.