Form questions

Job interview feedback form questions for a hiring panel

Twenty questions covers a structured panel process and ten covers a single interview. Three can never be dropped: a score for each competency in the brief, the evidence behind at least one of those scores, and a single overall recommendation. A scorecard without evidence is an opinion with a number attached to it.

An interview scorecard exists to make panellists commit to a judgement before they hear anyone else. These questions score against the job brief, ask for the evidence behind every score, and end with one recommendation rather than a discussion.

The questions

The interview

  1. Which candidate is this?Short textRequired

    A shortlist reference number rather than a name, so the record can be compared and stored without spreading the name further.

  2. Which panellist are you?DropdownRequired

    Hiring manager, second interviewer, technical assessor, people team. Needed to compare independent scores.

  3. When did the interview take place?DateRequired

  4. Which stage was this?DropdownRequired

    First interview, technical exercise, panel, final conversation.

  5. How long did it run?Single choice

    A short interview that produced a no hire is worth flagging as a process issue.

Scoring against the brief

  1. Score the first competency in the job briefRating gridRequired

    Row one of a grid whose columns are not evidenced, below the brief, meets the brief, above the brief.

  2. Score the second competency in the job briefRating gridRequired

    Row two. Use the brief wording verbatim so the score attaches to something written down.

  3. Score the third competency in the job briefRating gridRequired

    Row three.

  4. Score the fourth competency in the job briefRating gridRequired

    Row four. Four to six rows is the workable range; beyond that panellists start pattern filling.

  5. Score the fifth competency in the job briefRating gridRequired

    Row five.

  6. Score the sixth competency in the job briefRating gridRequired

    Row six.

  7. What did the candidate actually say or do behind each score?Table

    Columns for the competency, the evidence and the score. Four rows forces four specifics.

  8. Which competency did the interview fail to cover?Single choice

    Pairs with the not evidenced column and tells the next interviewer what to probe.

Your recommendation

  1. What is your recommendation?Single choiceRequired

    Strong hire, hire, not yet but would interview again for another role, no hire.

  2. How confident are you in that recommendation?Single choice

    Low confidence on a hire is a request for a second opinion, not a weakness.

  3. What is your main concern, if any?Long text

    Ask for it to be tied to a competency and to something that happened in the room.

  4. What would this person need in their first three months?Long text

    Only answered for a hire, and it is the beginning of the onboarding plan.

  5. What should the next interviewer probe?Long text

The process

  1. Did anything make it harder to assess this candidate fairly?Single choice

    An unclear brief, an exercise that did not suit the role, time running short, technology failing.

  2. Was the job brief clear enough to score against?Single choice

    A scorecard that cannot be scored is a hiring defect, and the panel is the only group that ever sees it.

Which questions to make required

Six things are required. The candidate reference, the panellist and the stage are required because a scorecard that cannot be matched to an interview is worthless in a debrief and unusable in a later dispute. Every competency row is required because a partly scored grid cannot be compared between panellists. The overall recommendation is required because the whole instrument exists to force one. The evidence table stays optional so a panellist who ran out of time still files a score rather than nothing at all.

The form built from these questions

A static copy of a form built from part of the bank, exactly as it renders.

Interview scorecard, Senior Support Analyst

Ledgerline hiring panel. Complete within two hours of the interview and before you talk to the other panellists. Ten questions, about six minutes.

The interview

Scoring against the brief

Score every competency against the job brief, not against the other candidates. Use not evidenced where the interview simply did not cover it, rather than guessing a middle score.
Not evidencedBelow the briefMeets the briefAbove the brief
Diagnosing a problem from a vague report
Written explanation to a non technical customer
Judgement about when to escalate
Working with the engineering team
Handling a customer who is already angry
Learning a product they have not seen
CompetencyWhat the candidate actually said or didScore you gave

Your recommendation

How to change this for a different hiring process

A technical exercise or work sample. Replace the competency grid with the marking rubric for the exercise, scored the same way, and add a question about how much help the candidate was given, because assessors differ enormously on that and it silently changes every score. Keep the evidence table and ask for the specific output rather than an impression. A volume or seasonal hiring round. Twenty questions per candidate does not survive forty interviews a week. Cut it to a four row grid, a recommendation and one concern, and make the reference number a dropdown of that day shortlist so it can be filled on a phone between interviews. Consistency matters more than depth when the same two people interview everyone. A final panel for a senior role. Add a question about whether the candidate would change anything about how the organisation works, add a row for judgement under uncertainty, and ask each panellist to name the single risk of hiring this person. Senior hiring fails on risks nobody said out loud, and a scorecard filled in before the debrief is the only place they reliably get written down.

Questions people ask

Why use a reference number instead of the candidate name?

Because the scorecard is compared, stored and occasionally disclosed. A reference number keeps the record useful without spreading the name into every system it passes through, and it makes the debrief marginally less prone to the halo that a familiar name carries with it.

Should panellists score before the debrief?

Always, and the form should say so on the first screen. The value of a panel is independent judgement, and it evaporates the moment the most senior person in the room speaks first. Collecting scores beforehand also gives you a spread to discuss rather than an average to rubber stamp.

What does not evidenced mean?

That the interview never covered the competency at all. It protects the average from an invented middle score and produces a precise instruction for the next stage. A candidate with three not evidenced rows has not been assessed, whatever the overall recommendation says, and that is worth knowing before an offer.

How many competencies should a scorecard have?

Four to six. Below four you are not assessing the role, and beyond six panellists start pattern filling down a column. If the brief lists ten, the brief is a wish list rather than a specification, and the first useful outcome of the scorecard is finding that out.

Should candidates see their scorecard?

Not the raw form. Write the feedback separately from the concerns section and the evidence table, because a scorecard is written for a debrief and reads harshly out of context. What a candidate deserves is two specific things that went well and one that did not, in plain language.

What if two panellists disagree sharply?

Open the debrief with the widest gap rather than the average. A two point difference on the same competency usually means the two interviewers asked different questions or heard the same answer differently, and finding out which is more valuable than settling on a number somewhere in between.

Should the form ask about culture fit?

Not in those words. Culture fit is where unexamined preference enters a scorecard, and it cannot be evidenced. Replace it with the specific behaviours the role needs, such as working with a team you disagree with, and score those against the brief like everything else.

Build this form in about a minute

The button opens the form generator with this form already described. Change the wording to match your own, generate, then edit any field.

Create a form with OneCraft

Other question banks

On writing the questions themselves, read How to write survey questions. For everything the builder can do, see the form maker. Step by step: Create a form with AI, then Control who can fill in your form.

Sources

Written and checked by the OneCraft team. Last checked .