Test judgment under constraints
An iGaming product manager assessment should show how a candidate trades off revenue, player value, risk, and market rules. Generic interviews let candidates recite retention formulas, roadmaps, and regulatory concepts without showing how they affect decisions.
Use one realistic case, not disconnected questions: define a market, product surface, commercial goal, data excerpt, and constraints. Request a short written response and structured discussion. Test priorities, rejected options, required evidence, and when to involve compliance or responsible-gaming specialists.
Make assumptions visible. A promotion proposal should specify segment, expected player value, cost exposure, eligibility, measurement window, and guardrails. A catalogue change should explain whether it improves discovery, margin, trust, or retention—and what it might damage.
Build a decision packet
Keep preparation to 75–90 minutes. Asking candidates to design an entire sportsbook or casino app rewards presentation speed and interview practice; a constrained packet tests role-relevant work.
Provide a one-page objective, such as improving first-week return among newly verified casino players without increasing bonus cost per retained player. Add compact data on acquisition source, verification, first deposit, first game session, net gaming revenue, bonus use, and return activity. State markets and non-negotiable controls: excluded-player handling, age or identity gates, promotional eligibility, and auditability.
Ask for:
- a problem statement separating the business symptom from the player problem;
- ranked product bets, including one they would not pursue;
- a measurement plan with a primary metric, input metrics, and guardrails;
- a risk log for compliance, fairness, data quality, and operational dependencies.
This creates comparable evidence without treating familiarity with one operator's tooling as product ability.
Catalogue choices expose product judgment
A catalogue is a discovery system, not a grid to fill with maximum inventory. It has commercial, player-experience, supplier, and regulatory consequences. Strong candidates ask what is available and promotable by market, how provider economics differ, which titles fit player intent, and whether merchandising creates repetitive or unsuitable exposure.
Search serves players who know what they want; curated rails support discovery; recently played reduces returning-player effort; promotional placement may lift conversion while crowding out trusted favourites. Candidates reasoning from the mechanics of an iGaming storefront should separate availability, ranking, search relevance, and campaign placement.
Use a scenario: a high-margin provider wants a permanent top rail, while new players abandon the lobby after broad, undifferentiated browsing. Strong answers define an audience and hypothesis—for example, a market-specific starter rail for verified new depositors—while retaining search and category access. They also name a counter-metric: complaint rate, failed search, repeated exposure, deposit-to-first-play delay, or a responsible-gaming signal relevant to operator policy.
| Evidence level | Catalogue response signal |
|---|---|
| Weak | Adds tiles, boosts the provider, and measures clicks only. |
| Sound | Defines player job, segment, placement logic, and funnel from lobby view to meaningful play. |
| Strong | Explains supplier, market, trust, and compliance constraints; proposes an experiment and harmful side effects to monitor. |
Do not reward game-title knowledge. Reward understanding of catalogue rules, fallback states, market controls, and measurement.
Cohort economics tests commercial thinking
Revenue totals can hide whether a change creates durable value or buys short-lived activity. Ask candidates to use cohorts anchored to a meaningful starting event, rather than calendar months of mixed users. For casino, this might be verified players completing a first deposit and eligible game session; the event depends on product and market.
Use definitions that require precision:
Activation rate = users reaching first value / eligible new usersWeek-4 retention = cohort users returning in week 4 / users in the starting cohortBonus cost per retained player = bonus cost for the cohort / retained playersNet contribution per acquired account = expected gross gaming revenue - channel, payment, bonus, and variable service costs
For a fictional cohort of 1,000 verified arrivals, 420 make a first deposit, 230 complete a meaningful game session, and 92 return in week four. Candidates should ask whether week-four return is the right interval and whether excluded or restricted accounts are consistently removed. A deposit-rate increase is not success if bonus cost rises faster than retained contribution.
Look for segmentation by acquisition channel, market, payment method, game category, device, and new-versus-returning status. A paid campaign with cheap depositors but weak week-four retention may be worse than a costlier channel with stable cohorts. Decisions might include changing landing-page promises, revising onboarding, suppressing an unsuitable offer, or pausing channel scale until downstream quality improves.
Strong answers distinguish leading from lagging measures. Verification-to-first-meaningful-session time can guide weekly onboarding work; cohort retention and contribution show whether it improved business health. Both require eligibility rules, a time window, and an owner.
Personalisation needs explicit governance
Personalisation in iGaming is a behavioural system, not a generic conversion layer. Test whether candidates use context to reduce friction without creating pressure around sensitive behaviour. Ask them to choose a surface—catalogue ordering, education, offer visibility, lifecycle messaging, or account prompts—and state needed data, exclusions, and review process.
Include AI personalisation in iGaming as behavioural governance because model quality does not settle the product decision. Candidates should address applicable consent and notice, eligibility and suppression rules, human review, audit trails, model drift, and reversal of harmful rules.
Prompt: a model predicts a group will accept a bonus. What must be true before it appears? Strong candidates begin with eligibility, whether behavioural-data use is permitted by policy and market rules, lifecycle suitability, and protection for excluded or at-risk players—not expected conversion. They define a holdout group and inspect guardrails alongside conversion.
Weak answers treat one-to-one targeting as automatically good. Strong ones recognise that relevance has boundaries designed by product with legal, compliance, data, and responsible-gaming partners.
Compliance changes the product shape
Regulatory constraints belong in discovery, requirements, design, release planning, and measurement. Treating them as final approval causes rework and unsafe flows. Assess whether candidates include constraints in the first problem statement.
Ask them to map a feature across three layers:
- Player flow: screens, messages, deposits, withdrawals, or game-access points that change.
- Control logic: checks, exclusions, limits, records, or approvals in each target market.
- Operational response: who receives alerts, can pause the feature, and documents decisions.
Product managers need not provide legal opinions. They should identify and document uncertainty, then obtain a decision from the accountable legal or compliance owner. Score requests for market-by-market rules, separation of global intent from local configuration, and safe defaults when requirements are unclear.
A revealing error is to call every control conversion friction to remove. Good judgment distinguishes avoidable effort from necessary protection and explains the difference to commercial stakeholders.
Score the reasoning, not polish
Use one rubric and require interviewers to record evidence before discussing the hire. This reduces the influence of charisma, shared career history, and familiar vocabulary.
| Assessment area | Weight | Evidence to score |
|---|---|---|
| Catalogue and merchandising | 25% | Player intent, availability rules, discovery trade-offs, experiment design |
| Cohort economics | 25% | Cohort definition, formulas, segmentation, contribution logic, guardrails |
| Personalisation governance | 20% | Eligibility, suppression, data boundaries, review process, reversibility |
| Compliance as product input | 20% | Market variation, escalation, safe defaults, operational ownership |
| Decision communication | 10% | Clear assumptions, prioritisation, uncertainty, stakeholder reasoning |
A five-point scale needs behavioural anchors: one is unsupported feature output; three links action to evidence and named trade-offs; five anticipates second-order effects, identifies missing data, and creates a practical route to test or safely reject an idea.
Calibrate before interviews. Two assessors should independently score a sample response, compare evidence, and refine vague rubric language. If they cannot explain why one answer is stronger, the rubric measures taste rather than job performance.
False positives that distort hiring
Vocabulary can falsely signal depth. Watch for:
- Metric recital without a decision. Names retention, lifetime value, and net revenue but cannot define cohort, denominator, or the action each metric changes.
- Revenue-first merchandising. Pushes promoted content without player intent, market availability, search access, repetition, or player-protection effects.
- Personalisation as targeting volume. Treats more messages and offers as success without suppression, consent, suitability review, or a control group.
- Compliance handoff. Says legal will handle it but provides no risk register, configuration need, release gate, or accountable owner.
- Experiment theatre. Proposes an A/B test without population, duration logic, primary outcome, or stop condition.
Do not make the opposite error: reject candidates for lacking local jargon or coming from adjacent regulated products. Disciplined questions, user protection, structured uncertainty, and evidence-based choices may predict faster ramp-up than fluent language with weak judgment.
Turn assessment evidence into a hire
Use the live interview to probe written choices rather than reopen the case. Ask what evidence would change the top priority, what would ship behind a feature flag, which stakeholder would disagree, and which control they would refuse to weaken. This shows whether reasoning is genuine or memorised.
Finish with a decision record: category scores, cited evidence, unresolved concern, role-specific risk, and conditions for success. For senior hires, add review by a compliance or responsible-gaming leader. They need not judge product craft, but can test whether the candidate treats player protection as a design responsibility.
This hiring loop selects product managers who can make commercial progress without separating catalogue performance, cohort health, personalisation, and compliance—the judgment required after the interview.