Skip to content
article

What I actually write in the interview feedback form (and what gets people rejected)

A hiring manager in Chennai opens the form. Real examples, anonymised.

Divya Ramanathan@divya_ramanathan

August 7, 2026 · 2 min read

Candidates almost never see what happens after the interview. I've been a hiring manager for six years and have filled in some hundreds of these forms, so here is what is actually on it and what I write.

The form

Ours has five fields, and most companies I know use something similar:

  • Problem solving
  • Coding
  • Communication
  • Ownership and attitude (with a specific example required)
  • Overall: Strong No / No / Yes / Strong Yes, plus free text

Two real examples (details changed)

"Jumped into code without asking about input size or edge cases. Solution was correct for the main case but candidate could not explain why it worked when asked. Did not test. Lean No."
"Got stuck at the halfway point, explained what was blocking them, took the hint well and finished with some help. Asked good questions about our on-call setup at the end. Yes."

Notice that the second candidate did not finish alone. They still got a yes.

What gets people rejected

  • Not knowing your own resume. "I used Kafka." "Why Kafka and not a simple queue?" Silence. This ends more interviews than any DSA question.
  • Blaming the previous team for everything that went wrong in a project.
  • Inflated titles. If you were "Tech Lead" for a team of two for three months, say so honestly. We will find out.
  • Arguing with hints. A hint is help, not a test of your ego.

What I love to see

  • "I don't know, but here's how I'd find out."
  • Clear trade-offs: "This is simpler but slower. If the data grows, I'd switch to..."
  • Questions at the end about the team, how decisions get made, what on-call looks like. Not "what is the work-life balance" as the only question (though it is a fair question).

There is an Avvaiyar line my grandmother used to say: கற்றது கைம்மண் அளவு, கல்லாதது உலகளவு. What you have learned is a handful of sand, what you have not learned is the size of the world. The candidates I remember best were comfortable with the second half of that sentence.

Hiring managers: what do you write that candidates would be surprised by?

Written by

Divya Ramanathan

Engineering manager at a SaaS company in Chennai. 11 years, 3 teams, 1 kid. I write about 1:1s, hiring and not burning out. Filter coffee mandatory.

Get the best of #interview_horror weekly

One email each Monday with the most useful posts. No spam; unsubscribe in one click.

Comments

7

Sign in to join the conversation.

Sign in to comment
Kunal Bhatia@kunal_dsa#2 in Interview Horror Stories
"Why Kafka?" followed by silence. I have seen this kill more interviews than any DSA question. Know why you used every tool on your resume.
3 net votes
Rohit Verma@rohit_codes6 rep in Interview Horror Stories
ye post har us bande ko padhna chahiye jo resume pe 15 technologies likhta hai 😂 "I don't know, but here's how I'd find out" is golden
1 net votes
Karthikeyan S@karthik_embedded3 rep in Interview Horror Stories
Love the Avvaiyar line. Hiring in embedded, I ask the same "why" questions about their final year project and it reveals everything in 5 minutes.
3 net votes
Ankit Khurana@faang_or_bust#9 in Interview Horror Stories
"ownership/attitude" is where managers hide bias tbh
2 net votes
Divya Ramanathan@divya_ramanathan#7 in Interview Horror Stories
That's a fair concern, and it's exactly why our form requires a specific example under that field. "Bad attitude" with no example gets sent back to the interviewer. Vague feedback is how bias hides, so we don't accept it.
2 net votes
Ankit Khurana@faang_or_bust#9 in Interview Horror Stories
ok thats actually reasonable
2 net votes
Omkar Joshi@omkar_java4 rep in Interview Horror Stories
Service company interviews too, "why this tool" is the killer. Most people's honest answer is "the client chose it", and that's fine, say it! Then explain what you learned from using it.
2 net votes