Interview scorecard template

Privacy-by-Design Consultant interview scorecard

Evaluate Privacy-by-Design Consultant candidates across 4 weighted areas: technical depth, real incidents and findings, risk judgement, and getting things fixed. Technical depth leads at 35%, so check command of GDPR Articles 25 and 35, DPIA methodology, data minimisation patterns, pseudonymisation, consent management platforms, ROPA upkeep, and cross-border transfer tools like SCCs. Use the rubric to compare role-specific evidence consistently.

See AI scoring
security compliancedata protectiondpiagdprprivacy engineering
TL;DR
For technical depth, look for evidence the candidate cites specific articles, ISO 27701 or NIST Privacy Framework controls, and explains pseudonymisation versus anonymisation with real system examples. For real incidents and findings, look for evidence the candidate describes named DPIAs, resulting design changes, regulator correspondence, and DSAR volumes handled with dates and outcomes. 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 command of GDPR Articles 25 and 35, DPIA methodology, data minimisation patterns, pseudonymisation, consent management platforms, ROPA upkeep, and cross-border transfer tools like SCCs and TIAs.

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

Cites specific articles, ISO 27701 or NIST Privacy Framework controls, and explains pseudonymisation versus anonymisation with real system examples.

02
Evaluation factor

Real incidents and findings

30% weight

Probe DPIAs they personally authored, privacy reviews on product design sprints, breach notifications filed with a supervisory authority, and data subject access request backlogs they cleared.

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 named DPIAs, resulting design changes, regulator correspondence, and DSAR volumes handled with dates and outcomes.

03
Evaluation factor

Risk judgement

20% weight

Assess how they weigh legitimate interest against intrusiveness, score residual risk after mitigation, and decide when to advise a client to abandon a data use entirely.

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 theoretical from material privacy risk, defends a documented decision to accept residual risk, and names the escalation trigger.

04
Evaluation factor

Getting things fixed

15% weight

Look for evidence they embedded privacy controls into backlogs, retention schedules, and vendor contracts rather than issuing advisory memos engineers quietly ignored.

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

Shows privacy requirements landed as Jira tickets, default retention settings, or DPA clauses, with adoption tracked after handover.

Evidence-led prompts

Interview questions for a Privacy-by-Design Consultant

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

  1. 01

    Can you describe your experience applying privacy by design principles in real projects?

  2. 02

    Can you discuss a challenging privacy issue you resolved?

  3. 03

    Could you describe your experience designing privacy settings and user controls?

  4. 04

    What steps do you take to bring privacy into the early stages of a project?

  5. 05

    Can you describe your approach to privacy impact assessments?

See the complete Privacy-by-Design Consultant 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