Interview scorecard template

Privacy Engineer interview scorecard

Evaluate Privacy Engineer 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 depth in privacy engineering: pseudonymisation and tokenisation patterns, differential privacy or k-anonymity, consent plumbing, data lineage tooling, retention enforcement in production data stores. Use the rubric to compare role-specific evidence consistently.

See AI scoring
security compliancedata mappingdpiagdprprivacy engineering
TL;DR
For technical depth, look for evidence the candidate names specific techniques and their limits, for example why hashing an email is not anonymisation, and shows code or schema level detail. For real incidents and findings, look for evidence the candidate walks through named assessments and pipelines they built, including record volumes, response times, and findings that changed a product decision. 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 depth in privacy engineering: pseudonymisation and tokenisation patterns, differential privacy or k-anonymity, consent plumbing, data lineage tooling, retention enforcement in production data stores.

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 techniques and their limits, for example why hashing an email is not anonymisation, and shows code or schema level detail.

02
Evaluation factor

Real incidents and findings

30% weight

Probe real deliverables: DPIAs they authored, RoPA build-outs, DSAR and deletion pipelines, cross-border transfer assessments, or a breach they triaged with legal and security.

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

Walks through named assessments and pipelines they built, including record volumes, response times, and findings that changed a product decision.

03
Evaluation factor

Risk judgement

20% weight

Assess how they weigh purpose limitation, lawful basis, and data minimisation against product velocity; ask where they accepted residual risk versus blocked a launch.

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

Distinguishes regulatory exposure from theoretical harm, cites GDPR or CCPA provisions accurately, and explains a defensible trade-off they documented.

04
Evaluation factor

Getting things fixed

15% weight

Test how privacy requirements reach engineers: privacy review gates in the SDLC, OneTrust or internal tooling, automated scanners, and getting retention tickets actually merged.

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

Describes embedded controls and default-safe tooling that removed manual review, with evidence of remediation closure rather than logged recommendations.

Evidence-led prompts

Interview questions for a Privacy Engineer

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

  1. 01

    Can you explain a situation where you identified and mitigated a privacy risk?

  2. 02

    Can you give an example of a complex privacy problem you solved?

  3. 03

    Have you been involved in a data breach investigation, and what was your role?

  4. 04

    What is your experience with privacy by design and by default?

  5. 05

    How do you ensure privacy requirements are met in a development environment?

See the complete Privacy Engineer 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