Interview scorecard template

Data Privacy Consultant interview scorecard

Pre-screening scorecard for Data Privacy Consultant candidates.

See AI scoring
security compliancedata mappingdpiagdprprivacy program
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 6, 28 and 30, CCPA/CPRA, DPIA methodology, ROPA upkeep, SCCs and transfer impact assessments, plus tooling such as OneTrust or BigID.

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 and lawful bases fluently, distinguishes controller and processor duties, and names retention and transfer mechanics without hedging.

02
Evaluation factor

Real incidents and findings

30% weight

Probe actual engagements: breach notifications filed within 72 hours, DSAR backlogs cleared, regulator queries answered, vendor DPAs renegotiated, audits or ICO correspondence they personally handled.

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 breach or DSAR cases with dates, volumes, notification decisions, and the regulator or client response afterwards.

03
Evaluation factor

Risk judgement

20% weight

Test how they weigh residual privacy risk: legitimate interest assessments, dark pattern consent flows, secondary use of personal data, and when to advise stopping processing.

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

Separates legal exposure from reputational harm, argues proportionate mitigations, and names the risks they accepted and documented.

04
Evaluation factor

Getting things fixed

15% weight

Assess how remediation actually happened: privacy by design reviews with engineering, records retention schedules enforced, training rollouts, and evidence controls stayed in place after sign-off.

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 closing findings with owners and deadlines, and shows follow-up evidence that controls persisted, not just a report delivered.

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