Reference Check Questions for Engineers: A 20-Question Bank

A reference check is a structured source of past-work evidence. It is not a personality referendum and it is not the same as employment verification. Select roughly 8-12 questions from this bank based on the role and gaps in your interviews. Ask the same core questions of comparable candidates, get permission, and record direct observations separately from hearsay.

TL;DR

• Reference Check Questions is a small-team hiring and candidate experience guide: use it to make one decision, not to collect generic advice.
• Start with the smallest useful version: a clear role, a fair process, and a decision that can be explained; add complexity only when the evidence requires it.
• Treat every claim as either an observation, an estimate, or a hypothesis; do not present a signal as proof.
• Before you publish or act, check the role's evidence, the candidate's consent, and the actual working terms.
• The practical outcome is a dated next step, a clear owner, and a reason to stop or revisit the decision.

Before the call

Tell the candidate who you will contact, what you will ask, and that you will not contact a current employer without explicit permission. Prefer a former manager plus a peer or cross-functional partner. Verify the relationship, dates, role, and what work the referee actually observed. Use a consistent scorecard tied to the job description.

The 20 questions

Context and ownership

1. In what capacity did you work together, and for how long?
2. What were the team, product, and technical context?
3. What did the candidate own directly versus contribute to?
4. What was the hardest problem they owned end to end?
5. What was the outcome, and how did you know?

Technical judgment and reliability

1. Tell me about a decision they made with incomplete information.
2. How did they approach a system or bug they had not seen before?
3. What did their code reviews usually improve?
4. How did they behave during an incident or customer-impacting bug?
5. What did they build that remained useful after they moved on?
6. What technical area did they improve while you worked together?

Collaboration and communication

1. How clear were their written updates, design notes, or RFCs?
2. Tell me about a disagreement with a teammate or manager.
3. How did they respond to critical feedback?
4. Did they make other engineers more effective? What happened?
5. Tell me about a project that failed, changed direction, or was cancelled.
6. What management or working conditions brought out their best?

Calibration and close

1. What should their next manager know to set them up for the first 90 days?
2. Would you hire or work with them again, and for what role?
3. What did I not ask that would help us evaluate this role fairly?

Ask for a story after vague praise: “Could you give me a specific example?” Avoid “rate them 1-10”; behavior and outcomes are more useful than an unsupported score.

Evidence examples

Do not treat a dates-only response from a large employer as negative. Employment verification often confirms employer, dates, title, and sometimes status; it does not establish performance or why someone left. A criminal or credit check is a different process with different consent and legal requirements.

Consent, fairness, and documentation

Use candidate-nominated references unless the candidate gives permission for another contact. Never contact a current employer by surprise. Ask job-related questions, avoid protected personal information, and document the source and date of each statement. If references conflict, give the candidate a fair opportunity to respond and compare the claim with work samples and interview evidence. Do not use a reference call as an excuse to search for disqualifying personal information.

Reference request email

Subject: reference for [Candidate] at [Company]

Hi [Name] — [Candidate] shared your name as someone who worked with them on
[context]. Could we speak for 15 minutes on [two options]? I will ask about
their ownership, technical judgment, and collaboration. We will not contact a
current employer without written permission. Thanks, [Name and contact].

Decision record

candidate:
role_scorecard:
referee_and_relationship:
permission_date:
questions_used:
direct_evidence:
open_questions:
employment_verification:      # scope, provider, consent, result
candidate_response:
decision: green | yellow | red
decision_owner_and_date:

Green means evidence confirms the role requirements. Yellow means a specific gap needs clarification or a different support plan. Red means a consistent, job-related concern or refusal to rehire that remains unresolved. Do not reduce a person to a color; keep the underlying evidence.

Match the referee to the evidence gap

One referee rarely observed every part of an engineer’s work. A former manager may know ownership, delivery, and feedback; a peer may know design discussion and code review; a product or operations partner may know communication and customer impact. Ask the candidate which person can speak to each area and record the relationship before treating an answer as evidence.

Do not treat a famous referee, senior title, or enthusiastic tone as a substitute for first-hand examples. A short dates-only verification may be the only response a former employer permits. That is a limitation of the source, not proof of poor performance.

A structured call flow

1. Confirm the referee’s relationship, dates, team, and scope of observation.
2. Explain that you will ask job-related questions tied to the role.
3. Start with the candidate’s direct ownership and a specific outcome.
4. Ask for one story about judgment, reliability, and collaboration.
5. Probe vague praise with “What did they personally do?”
6. Ask what support or conditions helped them succeed.
7. Ask whether the referee would hire or work with them again and for what role.
8. Summarize what you heard and invite correction.
9. Record direct evidence, interpretation, and unanswered questions separately.

If a referee raises a concern, do not cross-examine them for private or protected information. Ask for the job-related context and compare it with the candidate’s work sample and interview evidence. Give the candidate a fair opportunity to respond before making a decision.

Illustrative evidence reading

Illustrative scenario, not a benchmark: A referee says, “They were excellent and everyone liked them.” That is positive but vague. The interviewer asks for a project the candidate owned and what changed because of their work. The referee describes a migration, a rollback plan, and an incident review the candidate led. The interviewer records those observations and asks what the candidate did personally. In another call, a referee says, “I would hire them again, but not for an ownership role.” That is not an automatic rejection; it is a role-specific question about autonomy, scope, and support.

Fairness, privacy, and verification boundaries

Obtain permission before contacting the nominated referee and explain the topics. Never surprise-contact a current employer. Keep questions consistent across comparable candidates and tied to the published scorecard. Avoid questions about health, family, age, religion, disability, protected characteristics, or other personal matters unrelated to the job. Store notes securely, limit access, and follow applicable retention rules.

Employment verification is narrower than a performance reference. Confirm what the provider actually checked: employer, dates, title, responsibilities, or another field. Criminal, credit, identity, and right-to-work checks are distinct processes with separate legal and consent requirements. Do not bundle them under “reference check” as if they produced the same evidence.

Reference decision checklist

1. Map each reference to a role-related evidence gap.
2. Confirm candidate permission and the referee relationship.
3. Prepare eight to twelve questions, not an improvised interrogation.
4. Ask for examples, ownership, outcomes, and conditions.
5. Separate direct observation from hearsay and interpretation.
6. Record source, date, and what was not answered.
7. Compare concerns with interviews and work samples.
8. Give the candidate a fair response opportunity when accounts conflict.
9. Keep verification and performance decisions separate.
10. Retain only what the process and applicable rules require.

When the evidence conflicts

Conflicting references are common enough to require a process. First check whether the referees observed the same work. A manager may describe delivery while a peer describes collaboration, and both accounts can be accurate. Then compare the statements with the candidate’s own explanation, work sample, interview notes, and the requirements of the role.

Ask the candidate a narrow clarification question rather than presenting a vague accusation: “Your former manager described you as the primary owner of the migration, while the peer described shared ownership. How did responsibilities divide?” Record the response and the remaining uncertainty. A disagreement about credit is not automatically dishonesty; a repeated mismatch about a job-critical responsibility deserves closer review.

Do not let one enthusiastic or negative call decide the hire without considering source quality, recency, relationship, and direct observation. If the role requires incident ownership, a referee who never saw an incident cannot confirm or disconfirm that competency.

Reference-check decision checklist

1. Tie every question to a role requirement or interview gap.
2. Confirm the referee personally observed the relevant work.
3. Ask for one concrete example and outcome.
4. Distinguish “I saw” from “I heard.”
5. Give the candidate a fair chance to explain material conflicts.
6. Compare references with work samples and interview evidence.
7. Keep verification, performance, and legal checks separate.
8. Document the decision owner, date, and unresolved risk.

The reference check questions operating standard

This guide is written for a reader who needs to use reference check questions in a real workflow, not merely understand the definition. The dependable version starts with the decision that must be made, names the evidence available today, and keeps the next step small enough to complete. That is the editorial standard used throughout this guide and across the Parlel library: practical guidance should help a founder, operator, candidate, or freelancer act without hiding uncertainty behind confident language.

Decide what success means before you start

Write the result in one sentence: “After this exercise, I will know whether , and the next action will be .” For reference check questions, that sentence prevents the most common failure mode — doing more research after the useful question has already been answered. If the work concerns a person, company, role, client, or vendor, record the source and date as you go. If it concerns a template or message, define the recipient, context, and desired response before polishing the wording.

Use a small fixture rather than an abstract example. Pick three to five real records, situations, or drafts and run the method end to end. Keep one case that should succeed, one ambiguous case, and one case that should be rejected. That mix exposes whether the process can distinguish a useful signal from a convenient story. It also gives you material for a later review without pretending that a tiny sample is a benchmark.

Make the work explainable to another person

A high-quality result should survive a handoff. Another person should be able to see what was known at the time, which assumptions were made, what action was taken, and what would change the decision. For this topic, preserve the original input alongside the conclusion. Keep a short “why now” note, the owner, the due date, and the stop condition. This makes reference check questions useful in an agency-style operating system: the work is repeatable without becoming mechanical, and a reviewer can improve it without rewriting the whole process.

Quality-control pass before you ship

1. Intent: Does the page answer the query implied by its title in the first screen?
2. Evidence: Are current facts linked to a source, date, or clearly labeled assumption?
3. Specificity: Could a reader use the checklist, script, table, or example immediately?
4. Boundaries: Does the guide say when the method is a poor fit or should stop?
5. Next action: Is there one useful action rather than a pile of competing calls to action?

Those checks matter more than adding another paragraph of general advice. They also protect search quality: the page earns attention by resolving the reader's problem, not by repeating reference check questions unnaturally. If the evidence is thin, say so and explain how to improve it. If the answer changes by country, role, plan, or company size, make that branch visible instead of burying it in a footnote.

Run it on Parlel

Attach structured reference notes to the candidate record while the process is fresh.

REFERENCE LOG
- candidate: [profile URL]
- referee: { relationship, dates, permission }
- evidence: [{ question, direct_note, source_date }]
- verification: { employer, dates, title, scope }
- next_action: { clarify_with_candidate|offer|decline }
- guardrail: current_employer_contacted = false

Use the people directory only for public role context, not as permission to contact someone privately. Keep the hiring brief, work sample, references, and offer letter together.

Keep reading

Continue the workflow with three closely related guides: - contract to hire - job description template - offer letter template

Sources and further reading

• US OPM: reference checking
• Guardian Recruiters: reference questions
• TekRecruiter: tech references
• IRS: contractor and employee distinction