Interview scorecard template

AI Legal Analyst interview scorecard

Evaluate AI Legal Analyst 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 the EU AI Act risk tiers, GDPR Article 22, NIST AI RMF and ISO 42001, plus how they read model cards, DPIAs. Use the rubric to compare role-specific evidence consistently.

See AI scoring
security complianceai governanceeu ai actgdprmodel risk
TL;DR
For technical depth, look for evidence the candidate cites specific articles and control frameworks from memory, and distinguishes high risk from limited risk classification with concrete system examples. For real incidents and findings, look for evidence the candidate describes named systems reviewed, the findings logged, and what changed in the deployment or contract as a result. 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 the EU AI Act risk tiers, GDPR Article 22, NIST AI RMF and ISO 42001, plus how they read model cards, DPIAs and vendor training data clauses.

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 control frameworks from memory, and distinguishes high risk from limited risk classification with concrete system examples.

02
Evaluation factor

Real incidents and findings

30% weight

Probe actual reviews they ran: a conformity assessment, an algorithmic impact assessment, a copyright or bias finding raised on a live model before launch.

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 systems reviewed, the findings logged, and what changed in the deployment or contract as a result.

03
Evaluation factor

Risk judgement

20% weight

Assess how they weigh legal exposure against product timelines: hallucination liability, automated decision transparency, IP indemnity gaps in LLM vendor terms.

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 exposures by likelihood and severity, escalates the material few, and accepts documented residual risk rather than blocking everything.

04
Evaluation factor

Getting things fixed

15% weight

Test how they move engineers and product owners from a written finding to a shipped control: logging requirements, human oversight steps, model registry entries.

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

Tracks remediation to closure with owners and dates, and translates legal obligations into requirements engineers can actually implement.

Evidence-led prompts

Interview questions for a AI Legal Analyst

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

  1. 01

    Describe a project where you automated a legal process or task.

  2. 02

    Tell us about a time when your work measurably improved a legal process.

  3. 03

    Have you worked on contract analysis or clause extraction? Please explain.

  4. 04

    How do you validate the accuracy and reliability of models in legal applications?

  5. 05

    How do you approach training models with limited or unrepresentative legal data?

See the complete AI Legal Analyst 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