Interview scorecard template

Identity and Access Management Specialist interview scorecard

Evaluate Identity and Access Management Specialist candidates across 4 weighted areas: technical depth, real incidents and findings, risk judgement, and getting things fixed. Technical depth leads at 35%, so check hands-on command of Okta, Entra ID or SailPoint: SAML and OIDC federation, SCIM provisioning, conditional access policies, PAM vaults, and role mining. Use the rubric to compare role-specific evidence consistently.

See AI scoring
security complianceiamoktaprivileged accesssaml oidc
TL;DR
For technical depth, look for evidence the candidate names specific IdPs and connectors configured, explains token flows and claim mappings precisely, and distinguishes SCIM from JIT provisioning without prompting. For real incidents and findings, look for evidence the candidate describes concrete identity incidents with dates, blast radius, root cause in group nesting or stale entitlements, and the control added afterwards. Apply the written 1–5 anchors to every answer, record the evidence behind each rating, and use the factor weights to reach a consistent overall assessment.
Complete evaluation framework

What to assess and how to score it

Review the evidence signals before interviewing. Then use the anchored descriptions—not instinct alone—to choose the score that best matches each answer.

01
Evaluation factor

Technical depth

35% weight

Check hands-on command of Okta, Entra ID or SailPoint: SAML and OIDC federation, SCIM provisioning, conditional access policies, PAM vaults, and role mining for RBAC models.

Evidence to listen for

  • Command of the specific attack surface, tooling, and controls the role covers
  • Understands how the underlying system works, not just how the tool reports on it
  • Can explain an attack or control chain end to end
  • Distinguishes what they found themselves from what a scanner flagged

Five-point scoring guide

1
Poor

Tool operator only; no understanding of the systems underneath.

2
Needs Improvement

Runs tooling but cannot explain findings or how the attack works.

3
Satisfactory

Solid working knowledge; depth thins outside familiar tooling.

4
Very Good

Strong command of the domain; explains attack and control chains clearly.

5
Excellent

Names specific IdPs and connectors configured, explains token flows and claim mappings precisely, and distinguishes SCIM from JIT provisioning without prompting.

02
Evaluation factor

Real incidents and findings

30% weight

Probe real access incidents: orphaned accounts found during recertification, a broken SSO cutover at 2am, privilege escalation via nested groups, or failed SOX access audit findings.

Evidence to listen for

  • Brings specific incidents, findings, or audits they personally worked
  • States their own role rather than the team's
  • Describes what was actually at risk and what changed afterwards
  • Can talk about a finding that turned out to be wrong

Five-point scoring guide

1
Poor

No hands-on work; knowledge is entirely certification or coursework.

2
Needs Improvement

Limited exposure; cannot describe their contribution to an incident.

3
Satisfactory

Real casework with adequate detail; ownership sometimes vague.

4
Very Good

Specific incidents with clear personal scope and what changed after.

5
Excellent

Describes concrete identity incidents with dates, blast radius, root cause in group nesting or stale entitlements, and the control added afterwards.

03
Evaluation factor

Risk judgement

20% weight

Assess how they weigh standing admin rights against operational friction: joiner-mover-leaver gaps, break-glass accounts, service account sprawl, and least privilege versus helpdesk ticket volume.

Evidence to listen for

  • Prioritises by actual exploitability and business impact, not raw severity scores
  • Can argue for accepting a risk as well as fixing it
  • Knows the difference between a finding and a problem
  • Does not cry wolf or wave things through

Five-point scoring guide

1
Poor

Treats every finding as critical, or waves real risk through.

2
Needs Improvement

Follows severity scores mechanically; no business context.

3
Satisfactory

Reasonable prioritisation; less confident arguing for risk acceptance.

4
Very Good

Prioritises by exploitability and impact; can justify accepting a risk.

5
Excellent

Ranks identity risks by exploitability and audit exposure, defends time-bound elevation, and admits where they accepted residual risk with compensating controls.

04
Evaluation factor

Getting things fixed

15% weight

Test how they drove remediation: access review campaigns with reluctant app owners, deprovisioning SLAs, decommissioning shared logins, and evidence packaged for auditors or ISO 27001 reviewers.

Evidence to listen for

  • Writes findings engineers can act on rather than a wall of output
  • Has persuaded a team to fix something they did not want to fix
  • Explains risk to executives in business terms
  • Works with the org rather than policing it

Five-point scoring guide

1
Poor

Adversarial with engineering; findings never get fixed.

2
Needs Improvement

Reports are unactionable; no influence beyond raising tickets.

3
Satisfactory

Adequate reporting; relies on mandate rather than persuasion.

4
Very Good

Actionable findings and a real record of getting fixes shipped.

5
Excellent

Cites certification completion rates, revoked entitlement counts, and how they got application owners to sign off without escalation to leadership.

Evidence-led prompts

Interview questions for a Identity and Access Management Specialist

Use these prompts to surface evidence for the weighted factors above and compare candidates against the same role-specific criteria.

  1. 01

    What professional experience do you have with IAM systems, and at what scale?

  2. 02

    Are you familiar with implementing Single Sign-On (SSO) solutions?

  3. 03

    Can you describe your experience with two-factor or multi-factor authentication processes?

  4. 04

    Describe your experience with cloud-based IAM solutions.

  5. 05

    Can you explain how you identify potential IAM vulnerabilities, and how you would address them?

See the complete Identity and Access Management Specialist question set
Put this rubric to work

Score every candidate against the same standard

Add these weighted factors to Hirevire and let AI evaluate recorded answers against your rubric.

Explore AI Scorecards