20 interview feedback questions for hiring teams

Last Updated October 30, 2026 | 21 min read
|

Interview feedback questions are the questions you put to candidates and interviewers once an interview ends, so you can find out how the process went and whether the panel can back its decision with something firmer than a gut feeling. Most hiring teams already collect a version of this. Yours is probably a Slack thread called “debrief: Priya, round 2” with one reply from the hiring manager and three people who read it and said nothing.

Say you’re filling a dozen roles a quarter and each one gets four interviewers. That’s close to 200 interviews. By the time the recruiter asks “why did we pass on her?” the honest answer is that nobody wrote it down, and the candidate has already told three friends what the process felt like. She didn’t need your form to do it.

The question bank comes first, in two halves: twenty for candidates and twenty for interviewers. The scoring scale that goes with them can be pasted into your own form as it stands. Worked examples follow, then the mistakes teams make with these forms. The Sogolytics build steps are last, since they only make sense once you know what you’re building.

Key takeaways

  • An interview feedback questionnaire has two audiences. The candidate tells you how the process felt. The interviewer tells you what evidence they saw. Most teams run one and assume the other.
  • If your interviewers are scoring candidates “7 out of 10” with no scale definition, those scores can’t be compared across panels, and a rejected candidate’s lawyer knows it.
  • You’ll get better candidate feedback when the request lands within 24 hours of the interview and takes under five minutes. Ask a week later and you get their feelings about the outcome, dressed up as feedback about the process.
  • Reading the feedback is where most programs stall. Somebody has to own the pattern spotting. Otherwise the forms pile up in a shared folder, and the interviewer who turns every panel into a two-hour monologue never hears about it.

What are interview feedback survey questions?

Interview feedback survey questions are a fixed set of rating and open-text items that capture what happened in an interview, from either side of the table, in a form you can compare later. Fixed is the word doing the work. Picture two interviewers writing “strong communicator” in a free-text box after the same 45 minutes. One meant she was articulate. The other meant he liked her, and a week later neither of them could tell you which. Have them both rate “Explained a technical decision to a non-technical audience” at 4 out of 5 instead and you’ve got two scores you can put side by side.

There are two kinds, and people mix them up in the same meeting all the time. A candidate experience survey goes to the person who sat in the hot seat: was the scheduling clear, would you apply here again. The interviewer evaluation goes to the panel member and asks for scores against the job description’s competencies, plus what the candidate said that earned each one. One measures your process. The other measures the hire.

Candidate feedback surveyInterviewer evaluation form
Who answersThe candidate, after each interview stage or at the end of the processEach panel member, within a day of the interview
What it measuresCommunication, scheduling, interviewer preparation, role clarity, fairnessCompetency scores, evidence for each score, hire recommendation
Best format8 to 12 items, mostly 5-point scales, one or two open comments10 to 15 items, scored rubric plus a required evidence box
What you do with itFix the process, protect the employer brand, raise offer acceptanceCompare candidates, defend the decision, coach interviewers
Who owns itRecruiting or talent acquisitionThe hiring manager, with HR reviewing for consistency

A third variant gets its own section further down: the feedback you give back to a candidate you didn’t hire. That’s a message rather than a survey, though the interviewer evaluation is where the raw material for it comes from. Picture the candidate emailing a week later to ask why. If the panel’s forms read “4 on stakeholder management, 2 on prioritization, no example of saying no to a request,” you’ve got something to tell her. If they read “not quite the right fit,” you’ll open a reply, write three drafts, and send none of them.

Why interview assessment feedback matters in the hiring process?

A bad hire costs you months. The decision that produced it usually came out of a debrief where the loudest interviewer won, and the two people who had doubts kept them to themselves. The costs of poor hiring decisions go well past the salary; there’s the ramp time, and there’s the rest of the team covering while the role is open again six months later. Scored interview feedback won’t stop every bad hire. It does make it much harder for one confident voice to carry a panel that was quietly split 2 to 2.

The candidate side is where your employer brand gets made, and it gets made whether you’re watching or not. Picture a regional hospital group filling 60 nursing roles over a summer. One candidate waits 45 minutes in the lobby. Another gets a rejection email addressed to “Dear Michael” when her name is Dana. Both of them tell someone, and in a city with four hospital systems that someone is probably interviewing with you next month. Candidate experience metrics like offer acceptance rate tend to slide a quarter or two after stories like that start circulating. The post-interview survey is where you’d have seen it coming.

The feedback has to go somewhere once it’s in, too. Only 10% of employees say their feedback always leads to change, according to The Sogolytics Experience Index: Employee Edition (EX) 2026, and that number is for people already on the payroll. That habit starts before day one. The candidate who filled in your survey on the train home and never heard another word has already learned how this company treats input. The form is a promise, whether you meant it as one or not.

Consistency is the quieter reason, and the one your legal team will care about most. When every candidate for a role is scored on the same five competencies by interviewers who had to write down the evidence, you’ve got a record that explains the decision. When the only record is “the team liked him,” you’ve got a liability.

See how Sogolytics tracks the candidate journey
Chart every touchpoint from application to offer and see where candidates drop off, stage by stage.

20 interview feedback questions for candidates after an interview

These are the interview feedback questions for candidates that hold up across industries, grouped so you can trim to the stage you’re measuring. Scheduling gets the first five. Nobody remembers a great interview that opened with a broken calendar link, and that’s where most complaints start. Items 6 through 13 are about the interview itself. Items 14 through 17 ask what the candidate learned about the role. The last three are the ones that end up in the quarterly deck.

Items 1 through 17 use a 5-point agreement scale (strongly disagree to strongly agree) unless noted. Leave the open-text questions optional. Picture a candidate finishing a four-hour loop at 5:30 and opening your survey on her phone on the way to the parking garage. She’ll tap seventeen circles. She won’t write an essay, and if you make her, you lose the seventeen circles too.

  • The job description matched what was discussed in the interview.
  • Scheduling the interview was easy and the options offered worked for me.
  • I received clear instructions on where to go, who I’d meet, and what to prepare.
  • The interview started on time.
  • I knew how many stages the process had and roughly how long each would take.
  • The interviewer had read my application before we spoke.
  • The questions asked were relevant to the role.
  • I had enough time to answer each question fully.
  • The interviewer explained why they were asking certain questions, where that was helpful.
  • I was treated with respect throughout the interview.
  • I was given the chance to ask my own questions.
  • The interviewer answered my questions openly.
  • The length of the interview felt right for the role.
  • I now have a clear picture of what the day-to-day work involves.
  • I understand how success in this role would be measured.
  • I learned enough about the team and the manager I’d report to.
  • I understand what happens next and when I’ll hear back.
  • How likely are you to recommend our interview process to a friend who’s job hunting? (0 to 10)
  • What one thing would have made this interview better for you? (open text)
  • Is there anything you wanted to say in the interview and didn’t get the chance to? (open text)

Question 20 earns its place. The quiet, well-qualified candidate who got talked over in the room will answer it, and it’s often the only place she gets to make her case. Question 18 is your candidate NPS. Trend it by recruiter and by hiring manager for two quarters and one panel will sit 20 points below the rest. That’s the conversation to have.

20 interview feedback questions for interviewers

The interviewer form has one job: get the evidence out of the panel member’s head within a day, while they still remember the example the candidate gave about the vendor dispute. Items 1 through 12 are competency scores. Items 13 through 17 make the scores defensible, and the final three are about the interviewer’s own confidence, which turns out to be a useful signal in its own right.

Swap the competencies in items 3 through 12 for the ones on your job description. Ten is a ceiling. Ask a panel to score 18 competencies in 20 minutes and you’ll get 18 copies of the same number, usually a 3.

  • Which role and interview stage are you scoring? (dropdown)
  • How long was the interview, in minutes?
  • Role-specific technical skill (1 to 5)
  • Problem solving: worked through an unfamiliar problem out loud (1 to 5)
  • Communication: explained a complex idea so a non-specialist could follow it (1 to 5)
  • Collaboration: described a specific time they changed course because of a colleague’s input (1 to 5)
  • Ownership: gave an example of a mistake and what they did about it (1 to 5)
  • Prioritization: described saying no to a request, and how (1 to 5)
  • Stakeholder management: handled a disagreement with someone senior (1 to 5)
  • Learning: described something they taught themselves in the last year (1 to 5)
  • Motivation for this role specifically, as opposed to any role (1 to 5)
  • Fit with the team’s working style, as described on the job description (1 to 5)
  • For your lowest score above, what did the candidate say or do that led to it? (required, open text)
  • For your highest score above, what did the candidate say or do that led to it? (required, open text)
  • What would you want the next interviewer to probe further? (open text)
  • Did anything the candidate said raise a concern you couldn’t resolve in the interview? (yes or no, with comment)
  • Overall recommendation: strong hire, hire, no hire, strong no hire
  • How confident are you in that recommendation? (1 to 5)
  • Did you follow the interview guide for this stage? (yes, mostly, no)
  • Was there anything about the interview setup (room, tools, timing) that affected your ability to assess the candidate? (open text)

Items 13 and 14 are required. Interviewers grumble about that for about a month and then stop. A score with no evidence behind it is a vibe with a number attached. Item 18 is the one hiring managers ask about most. Say two panel members both marked “hire,” one at confidence 2 and one at confidence 5. Averaging those hides the interesting part, and the spread tells you who to call before the debrief.

Write the scale down once and put it on every form after that. The one below works for most competency items.

ScoreLabelWhat the interviewer saw
1Well below the barNo relevant example offered, or the example contradicted the competency
2Below the barA vague or partial example; the interviewer had to lead the candidate to it
3Meets the barOne clear, specific example with a result the candidate could describe
4Above the barMultiple specific examples, including one where the candidate adjusted their approach
5Well above the barExamples at a level of scope or difficulty beyond what the role needs
Burnout to breakthrough: AI in HR
An ebook on where AI is taking work off HR’s plate, from survey design to the analysis you’d otherwise do by hand.

Interview feedback examples that actually work

In the score column, good interview feedback and bad interview feedback look the same. Open the evidence box and they come apart. Take two interviewers who both gave the same project manager candidate a 4 on stakeholder management. The first wrote: “Good energy, seems organized, would probably fit in.” The second wrote: “Asked how she’d handle a sponsor who kept adding scope. She described a real case, named the two trade-offs she put in front of the sponsor, and said which one got picked and why. Scored 4 on stakeholder management.” In the debrief, somebody pushes back on the 4. Only one of those interviewers has an answer.

Weak feedback has a tell: it’s about the interviewer. “I liked him.” “Something felt off.” Picture the interviewer who wrote that second line being asked, six months on, what felt off. He won’t remember, and what he can’t remember tends to be something the job description never mentioned, like the candidate going to a different kind of school than he did. Strong feedback stays on the candidate. The question, what came back, the gap. It reads flat, and flat is what survives a hiring dispute.

The candidate side works in reverse: you’re reading the comments for the one line that explains the ratings. Suppose someone answers question 19 with “the second interviewer asked me the same three questions the first one did.” That’s a loose interview guide, found in one sentence, and you’d have stared at the rating items for a month without seeing it. A different candidate writes that she “wasn’t told the panel would include a live coding exercise.” Question 3 just failed, and the fix is a prep email somebody can rewrite before lunch.

The feedback you send to the candidate you turned down is where a good interviewer form pays for itself. Compare two rejection lines. “We went with a candidate whose experience was a closer match” tells her nothing and sounds like you’re hiding something, mostly because you are. “The panel wanted a more detailed example of managing a project through a budget cut, since the role involves several a year” is specific, tied to the job, and something she can prepare for next time. The second line didn’t take any extra effort. It came straight out of item 13.

Best practices for using an interview feedback questionnaire

Most of what goes wrong with an interview feedback questionnaire goes wrong in the setup, long before anyone reads a response. The list below is what teams running these at scale tend to settle on after a year or two.

  • The interviewer form goes out the moment the interview ends and is due before the debrief. The candidate survey goes out within 24 hours, with one reminder two days later. Beyond a week, memory has blurred into the outcome.
  • Under five minutes for candidates, under ten for interviewers. Time it on three colleagues before launch. If the slowest one takes twelve minutes, cut.
  • Scale definitions on the form. Paste the rubric table right next to the scoring items, every single time. Interviewers won’t go looking for it in a wiki, and without it a 3 in March drifts into a 4 by January.
  • Evidence before scores, where the tool allows it. Picture an interviewer who has already clicked 4. Whatever she types next is a defense of that 4, and she’ll find one. Put the evidence box first and the number has to fit what she already wrote.
  • Interviewers submit before they see anyone else’s form. A panel that compares notes in the hallway produces four copies of the first opinion.
  • Anonymity for candidates, by default. A candidate still in the running isn’t going to criticize the person who might sign her offer. Say so in the first line. An anonymous survey with a response threshold before results display is the setup that gets you the honest version, and candidates can tell the difference.
  • Neutral wording. “Was the interviewer well prepared?” leads the witness. “The interviewer had read my application before we spoke” doesn’t. How to avoid bias in surveys covers the mechanics, and the stakes here are plain: a leading item inflates the score, and next quarter you’ll be trusting that score.
  • An owner for the patterns. One person, named, reads the results every month and walks into the talent meeting with two findings. Picture her slide: recruiter scores on the left, hiring manager scores on the right, one bar visibly shorter. No owner, and the forms become an archive nobody opens.

The one that gets skipped is closing the loop with the candidates who scored you low. Picture a recruiter writing back three weeks later: “you mentioned the panel ran 40 minutes over, and we’ve since capped stage two at an hour.” That candidate applies again, and tells people why. Tying survey responses to your job application form data is worth doing too, because sometimes every low score traces back to one job board, and that’s the whole story.

How Archbright cut client report time from 13 hours to 1
An HR services provider automated employee surveys across email, SMS, and kiosk, and gave clients live report links.

How to create an interview feedback survey questions with Sogolytics?

Start with a sentence in Create with AI
A sentence is enough to start with. Say it’s 4:50 on a Friday and the recruiter types “post-interview feedback survey for candidates, 10 questions, 5-point scale, one open comment” into Create with AI. A complete draft is on her screen in seconds. Two of the generated questions are fine, one gets reworded, three get replaced from the bank above. She’s out the door at five.

Build the interviewer form separately
The interviewer form is a separate project, and this is the step worth arguing over. Items 3 through 12 get swapped for whatever the job description calls its competencies, and the rubric table goes into the instructions where interviewers will see it. Items 13 and 14 get the required flag. The panel will push back on that. Hold the line.

Turn anonymity on for candidates only
Anonymity goes on for the candidate version, and only that one. Sogolytics collects responses without names and tells candidates so before they answer. Results stay hidden until a minimum response count is reached. A hiring manager with two candidates in the pipeline can’t work out which one said the lobby wait was 45 minutes, which is the point. The interviewer form stays attributed, because there you need to know whose score is whose.

Distribute where the candidate is
Distribution goes wherever the candidate already is. Email covers most people. The walk-in candidate for a forklift role hasn’t opened a laptop in a year. He gets an SMS, or a QR code on the card the receptionist hands him on the way out, and he answers it in the parking lot. Reminders run on a schedule you set once.

Route alerts to a named person
Alerts go to a named person. Say a candidate for a warehouse supervisor role rates “I was treated with respect” at 1. With an alert set, that lands in the recruiting lead’s inbox the same afternoon, and she can call him back before he’s finished telling his brother-in-law about it. Without one, it turns up in a quarterly export in January. Prospera Financial runs this kind of alert across both its client and employee programs, with feedback flowing into Salesforce.

Read reports by segment
Reports get read by segment. A grand total hides everything useful. Filter candidate scores by recruiter, then by stage. The outlier panel is usually visible on the first chart. The 200 open comments from question 19 get grouped into themes with sentiment attached to each, which turns them into six things to fix. AI Reports then ranks those findings by impact and attaches an action plan with an effort rating to each one.

Let the ATS do the sending
The applicant tracking system does the sending. Sogolytics integrates with applicant tracking and HR systems such as Greenhouse and Workday (availability varies by platform and edition). A candidate moves to “interviewed” in the ATS and the survey goes out. Nobody has to remember.

Scheduling the interview takes longer than building the interview feedback survey in Sogolytics does. The steps below cover the candidate version and the interviewer version. The build itself is quick. Two decisions deserve a meeting: which competencies go on the interviewer form in step 2, and whose phone buzzes when an alert fires in step 5.

Role-based access does the rest. Hiring managers see their own panels and recruiting sees everything. The three people who compare interviewers across the whole company get the one view that lets them do that.

Conclusion

Interview feedback questions pay off at two moments: when a candidate’s comment reaches somebody who can fix the process that week, and when an interviewer’s scores arrive at the debrief with the evidence still attached. Sogolytics’ employee experience platform treats hiring as one stage of the same lifecycle as onboarding and exit, with the anonymity thresholds and alerts described above built in. That’s what lets the two forms run as one program rather than two spreadsheets that nobody reconciles.

Run interview, onboarding, and exit feedback as one program
Sogolytics for HR teams connects every stage of the employee lifecycle to the same dashboards and alerts.

FAQs about interview feedback questions

How do you give constructive feedback after an interview?

Name one competency from the job description, say what was missing, and stop there; two sentences she can act on beat a paragraph she can’t. “The role involves several budget cuts a year, and the panel wanted a more detailed example of managing one” tells someone what to prepare next time. The raw material for that sentence comes from the interviewer’s required evidence box, which is why the box is required.

What is the difference between interview feedback and a performance review?

Interview feedback judges someone against a job description before you’ve seen her work; a performance review judges her against goals set after she joined. In the interview room you’ve got her account of the past and nothing else, so the form has to ask for examples. A manager filling in employee performance evaluation questions has watched a year of real work and can ask about outcomes instead.

How many questions should an interview feedback survey include?

Somewhere between 8 and 12 for candidates, 10 to 15 for interviewers; that’s roughly five minutes and ten, and it’s where most teams settle. Go longer and people start skipping, while the ones who finish give question 14 the same answer they gave 13. The 20-question banks above are for trimming, not for using whole.

How can interview feedback questions help reduce hiring bias?

They force every interviewer to score the same competencies, with written evidence, before seeing anyone else’s opinion. Picture a panel member who has to write down what the candidate said about prioritization before the 2 goes in: “something felt off” won’t fill that box, so the 2 has to be earned or dropped. Filter scores by interviewer over a few quarters and the one person who always rates a particular group lower shows up too, which is a conversation worth having early.

What should an interview feedback questionnaire include?

For candidates, it walks the process in the order she lived it, from the scheduling email through to what she learned about the role, and ends on a recommend score and one open question. For interviewers, it’s a handful of competencies on a defined scale, evidence for the highest and lowest, and a recommendation with a confidence rating beside it. Run new hire onboarding survey questions 90 days later and you’ll find out whether any of those scores predicted anything.

SHARE:

See what your feedback data is already telling you. Request a Demo

Client

Company Size

Industries

Customer Since

Read more

Typical Rave Review

Description