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: SAML or OIDC for a new application?
Model-answer hint
OIDC for modern apps and APIs, SAML for legacy enterprise apps; explain tokens and flows.
Question 2: How do you roll out conditional access without locking people out?
Model-answer hint
report-only mode, break-glass accounts, phased rollout, risk signals.
Question 3: Walk through a passwordless rollout.
Model-answer hint
FIDO2 and passkeys, device readiness, recovery flows, communication, adoption metrics.
Question 4: How do you automate joiner-mover-leaver?
Model-answer hint
HR as source of truth, role models, SCIM provisioning, approval workflows.
Question 5: What is segregation of duties, and how do you enforce it?
Model-answer hint
defined toxic combinations, preventive checks at request, detective reviews.
Question 6: How do you bring service accounts under control?
Model-answer hint
inventory, owners, vaulting, rotation, replacement with workload identity.
Question 7: What should PAM cover beyond password vaulting?
Model-answer hint
session recording, just-in-time access, approvals, endpoint privilege management.
Question 8: How do you give an AI agent access to user data safely?
Model-answer hint
delegated scoped tokens, consent, short lifetimes, per-action audit.
Question 9: What are the main risks in B2B federation?
Model-answer hint
trust scope, partner offboarding, attribute mapping, monitoring.
Question 10: How do you measure an IAM programme?
Model-answer hint
MFA coverage, orphaned accounts, review completion, time to provision.
Questions 11–20 (Cybersecurity core)
Question 11: Map a control you implemented to NCA ECC-2:2024 or ISO 27001.
Model-answer hint
control reference, implementation, evidence produced, how effectiveness was tested.
Question 12: Walk through a ransomware intrusion using MITRE ATT&CK.
Model-answer hint
initial access to impact, with a detection or control at each stage.
Question 13: How do you prioritise 5,000 open vulnerabilities?
Model-answer hint
known exploitation, asset criticality, exposure, compensating controls, SLA tiers.
Question 14: Which logs do you need to investigate a compromised cloud identity?
Model-answer hint
sign-in, token issuance, control-plane audit, resource access and network flow logs.
Question 15: Explain zero trust to a CFO in 2 minutes.
Model-answer hint
no trust by network location; verify identity, device and context per request; frame as business risk.
Question 16: How do you write a detection that is useful, not noisy?
Model-answer hint
clear hypothesis, right data source, baseline tuning, emulation testing, documented triage steps.
Question 17: What do you do in the first hour of a suspected breach?
Model-answer hint
preserve evidence, contain, follow the playbook, start the regulatory clock, control communications.
Question 18: How do you protect secrets across CI/CD, cloud and laptops?
Model-answer hint
central vault, short-lived credentials, OIDC federation, secret scanning, rotation.
Question 19: How does SAMA CSF differ from ISO 27001 in practice?
Model-answer hint
sector regulator and maturity scoring versus a certifiable management system; large control overlap.
Question 20: Describe a security fix you won despite pushback.
Model-answer hint
quantified risk, business framing, agreed compromise, verified closure.
Interviewer tip: Ask for a real example after every answer. Strong candidates describe what they built, what broke and what they changed.
Practical task
Design the target identity architecture for a bank with 6,000 staff and 2 million app users: workforce SSO and MFA, customer login with Nafath, PAM for 300 administrators and service-account remediation, plus a 6-month rollout plan.
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
- Cannot separate authentication flows from authorisation decisions.
- Ignores machine identities entirely.
- Plans an MFA rollout with no recovery or break-glass path.
- Treats access reviews as a spreadsheet exercise.
- 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.