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 one control library for several frameworks?
Model-answer hint
unified control set, mapping matrix, one owner and one evidence stream per control.
Question 2: Walk through a risk assessment you ran.
Model-answer hint
scope, assets and threats, likelihood and impact, treatment decisions, owners.
Question 3: What makes evidence audit-quality?
Model-answer hint
complete, timestamped, from the system of record, linked to control and period.
Question 4: How does DORA change third-party risk management?
Model-answer hint
ICT third-party register, contract requirements, exit plans, concentration risk.
Question 5: Design effectiveness versus operating effectiveness: what is the difference?
Model-answer hint
built correctly versus worked consistently over the audit period.
Question 6: A control owner keeps missing remediation deadlines. What do you do?
Model-answer hint
escalate with risk framing, agree interim mitigation, track in the governance forum.
Question 7: How do you scope a SOC 2 Type II report?
Model-answer hint
trust services criteria, systems in scope, audit period, subservice organisations.
Question 8: What does PDPL require when personal data leaves Saudi Arabia?
Model-answer hint
transfer conditions, safeguards, risk assessment and documentation.
Question 9: How do you prepare for a regulator inspection in 2 weeks?
Model-answer hint
scope, evidence index, owner briefings, known gaps with plans, mock walkthroughs.
Question 10: What belongs in a board risk report?
Model-answer hint
top risks and trends, control effectiveness, overdue actions, incidents, risk appetite.
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
Given a 30-control extract from NCA ECC and a short description of a fintech’s environment, produce a gap assessment, map each gap to ISO 27001 Annex A, and propose a 12-week remediation plan with owners and evidence.
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
- Treats compliance as document templates with no link to technical reality.
- Cannot explain how a specific control was tested.
- Is unfamiliar with the frameworks that apply in the target market.
- Avoids challenging control owners or escalating risk.
- 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.