Free template · Word and PDF

Software Developer reference check template

A reference check form for software developers and engineers. It adds eight questions on code quality, delivery, debugging, code review and whether they work at the level they claim.

Download Word (.docx)Download PDF
  • Free, no sign-up
  • Editable Word file
  • 8 software developer questions

What to focus on in a software developer reference check

The key question for developers is seniority: did they work independently at the level of the role? Ask the engineering manager or tech lead about specific systems and incidents.

8 reference check questions to ask about a software developer

Ask these after the standard verification and performance questions. They are already in the Word and PDF template.

  1. 1.Which systems and languages did the candidate work on, and what did they own?
  2. 2.How would you describe the quality of their code and pull requests?
  3. 3.How reliably did they estimate and deliver work?
  4. 4.Tell me about a hard bug or production incident they handled.
  5. 5.How did they give and take code review feedback?
  6. 6.How much direction did they need compared with others at their level?
  7. 7.How did they work with product, design and non-technical colleagues?
  8. 8.Would you hire them onto your team again, and at what level?

What a strong reference sounds like

  • Owns features end to end
  • Clear, reviewed, tested code
  • Calm and methodical in incidents
  • Referee would rehire at the same or higher level

Red flags to follow up

  • Needed more direction than their level
  • Defensive in code review
  • Missed estimates without warning
  • Referee suggests a lower level

Download the software developer reference check template

Free, no sign-up. The Word version is editable; the PDF is ready to print.

Download Word (.docx)Download PDF

Want more questions? See 35 reference check questions to ask references. Prefer referees to answer online? HiveRef sends the form, chases replies and builds the report. Start with 4 free checks.

Software Developer Reference Check Template

For phone or written reference checks. Use the same questions for every referee so answers are comparable.

1. Candidate and referee details

  • Candidate name
  • Role applied for
  • Referee name
  • Referee job title and organisation
  • Referee email and phone
  • Relationship to the candidate (for example, direct manager)
  • Date of reference check
  • Checked by

2. Consent

Confirm the candidate agreed to you contacting this referee. Tell the referee their answers are used only for this hiring decision.

  • Candidate consent confirmed (yes / no)
  • Date consent was given

3. Verification questions

  1. 1.How do you know the candidate, and what was your working relationship?
  2. 2.What were the candidate's start and end dates, as far as you remember them?
  3. 3.What was their job title, and did it change while you worked together?
  4. 4.Did the candidate report to you directly? If not, how often did you see their work?
  5. 5.What were the main reasons the candidate left, as far as you know?

4. Performance questions

  1. 6.Which parts of the role did the candidate own day to day?
  2. 7.Tell me about a deadline the candidate missed or nearly missed. What happened next?
  3. 8.Give an example of the candidate producing good work with incomplete information.
  4. 9.What result improved while they were in the role, and what was their contribution?
  5. 10.When results were below expectations, how did they respond to feedback?
  6. 11.What skill did the candidate develop most while you worked together?

5. Software Developer questions

  1. 12.Which systems and languages did the candidate work on, and what did they own?
  2. 13.How would you describe the quality of their code and pull requests?
  3. 14.How reliably did they estimate and deliver work?
  4. 15.Tell me about a hard bug or production incident they handled.
  5. 16.How did they give and take code review feedback?
  6. 17.How much direction did they need compared with others at their level?
  7. 18.How did they work with product, design and non-technical colleagues?
  8. 19.Would you hire them onto your team again, and at what level?

6. Working style and integrity

  1. 20.Describe a disagreement the candidate had with a colleague. How did they move the work forward?
  2. 21.How did the candidate ask for help when they needed it?
  3. 22.When the candidate made a mistake that affected others, what did they do?
  4. 23.What would you tell a new manager about working with this person?

7. Closing questions

  1. 24.Is there anything we have not asked that you think we should know?
  2. 25.What kind of manager or team would get the best out of this person?
  3. 26.Would you hire or work with this person again? Why or why not?

8. Recommendation

  • Overall: recommend / recommend with reservations / do not recommend
  • Strengths confirmed
  • Concerns or follow-ups
  • Signed and dated

Do not ask about health, family, age, religion or other protected personal information, and check the law where you hire.

Frequently asked questions

What is the most revealing developer reference question?

Ask whether the referee would rehire them, and at what level. It tells you whether the seniority on the CV is real.

Who should be a developer's referees?

An engineering manager or tech lead, plus a peer who reviewed their code.

Can the referee answer without technical detail?

Yes. The form asks for examples and comparisons, which non-specialist managers can also answer.

Send these software developer questions online instead.

HiveRef emails the referees, chases them for you and puts every answer into one report. First 4 checks free, no card needed.

Start freeSee a sample report