Candidate Feedback Forms People Actually Answer

The cheapest research your hiring process will ever get

Every interview hands you a person who just spent an hour — or five — inside your process and formed a precise opinion of it, before they even know whether they got the job. That opinion is free. The only question is whether your collection method ruins it before it reaches you.

Usually, it does. Long static forms get skimmed, abandoned, or answered politely, and the feedback that does arrive comes disproportionately from the extremes. This page covers the questions worth asking, a structure that respects the candidate’s time, and how to build the whole thing in Formware — with templates at the bottom if you’d rather start from something proven (the full recruiting and talent collection is there too).

Questions that earn honest answers

Ask less than you want to know. These are the questions that survive contact with real candidates, grouped by the moment you send them.

Same-day, after an interview

• Overall, how would you rate today’s interview? — a 1–5 rating question gives you the number you can trend across roles and quarters.
• Did the interview match what the job posting described? — Yes/No. A “no” here is a posting problem, not an interviewer problem.
• How clearly did {{interviewer}} explain the next steps? — pass the interviewer’s name in through a hidden field and recall it in the question text. A form that knows who interviewed you reads as written, not generated.
• What’s one thing we could have done better? — long text, optional.

After the full process

• How likely are you to recommend applying to {{company}}? — an NPS question, trended by role.
• Rate the communication you received. — an opinion scale, one row per aspect: how interviews were scheduled, what happens next, how long decisions take.
• If you could change one thing about the process, what would it be? — long text. This single question outperforms most of the others combined.

If you’d rather start from the full-journey versions, the candidate experience survey and recruitment satisfaction template cover this ground pre-built.

After a rejection — the most valuable, most neglected group

Rejected candidates have the least reason to be polite and the clearest view of how your process treats people who don’t get offers. The ask has to be small and safe:

• Did you feel the process treated you with respect? (Yes/No)
• Did you hear back within the timeframe you were given? (Yes/No)
• Is there anything you’d want us to change? (Long text, optional)

Don’t require a name. The anonymous feedback template simply never asks for one — what the form doesn’t ask, it can’t store.

Candidate feedback is the outside-in view. For the inside-out pair — the interviewer’s structured evaluation of each candidate, and the hiring team’s own read on how the process ran — start from the interview evaluation template and the recruitment evaluation survey.

On mixing question types: scales and NPS give you numbers you can compare; long text gives you the reasons the numbers moved. A form that is all one or all the other disappoints in a predictable way. The full set is in the question types reference.

A structure that works: the 90-second form

Eight questions, roughly a minute and a half, arranged so each answer earns the next:

1. Name — optional. Optional fields are a signal in themselves.
2. Which stage is this about? — multiple choice: phone screen, first interview, final round, the whole process.
3. Overall rating — 1–5.
4. Communication clarity — opinion scale.
5. What went wrong? — long text, only shown when the rating in question 3 is 2 or lower. Conditional logic handles this, and every logic feature is available on the free plan — it’s not a paid gate in Formware.
6. What did we do well? — long text, optional.
7. Would you apply again? — Yes/No. The most honest single number in the set.
8. Anything else? — long text, optional.

Two details that cost nothing and change how the form feels: a progress bar, so people can see the scale of the ask before committing, and a thank-you page that closes the loop — “every response is read by the hiring team” is only worth writing if it’s true.

This structure is pre-built in the candidate feedback survey template.

Getting responses, not just sending forms

• Send it the same day. Candidate memory has a half-life measured in days. The feedback link belongs in the same-day follow-up email, not a quarterly campaign.
• Keep the ask under two minutes — and say so. “About 90 seconds, 8 questions” belongs in the invitation itself. Share the direct link: one click, no account needed on the respondent’s side.
• Tag the source. A hidden field for role, stage, or source — or the UTM builder for campaign-style attribution — tells you which candidates report the best experience. Referral candidates and job-board candidates will not describe you the same way, and you want to know it.
• Expect abandonment, keep the data. On Pro, partial submissions save what a respondent entered before leaving — sometimes the five answers someone completed before quitting say more than a finished form would have.

What to do with the answers

• Read all of them, trend the numbers. Responses land in one dashboard; if you’re using NPS, the NPS calculator turns the score into something you can report upward.
• Pipe them where the team works. A webhook can push each response into your ATS — if it accepts webhooks — a spreadsheet, or an automation platform. Included on free.
• Close the loop internally. Harsh feedback about a specific interviewer is a pattern to document across candidates, never a conclusion from one response. That’s exactly why consistent, trendable questions matter more than an elaborate one-off survey.
• Involve the panel. Formware’s free plan is single-user. If hiring managers should review feedback together, Pro adds shared workspaces with roles and permissions.

The form is part of the question you’re asking

There’s an irony built into this use case: you’re asking “did you feel respected and well-communicated with?” — through the medium of a form. A 27-question grid of collapsed dropdowns makes the answer for you before the candidate types a word.

One question at a time is not a styling preference here. It’s the difference between a form that contradicts its own message and one that demonstrates it. If you’re weighing options, the Formware vs. Google Forms comparison covers the free-and-familiar route, and the Typeform comparison covers the other conversational builder.

When these forms run at volume — embedded on your careers page, sent to every applicant — the branding around them becomes employer-brand material. Pro removes the Formware badge and adds your own logo and domain, so candidates meet one brand instead of two. The free plan keeps Formware branding and is otherwise fully usable for everything above.

And when the candidate says yes: the next survey in their journey is employee onboarding.

Frequently Asked Questions