Most candidates do the same thing after a rejection: read the template email again, guess what went wrong, and carry that guess into the next interview.
This article covers how to ask for feedback in a way people can actually answer, and how to debrief an interview while you still remember what happened. It also covers turning whatever you learn into one change you can practice. Ask once, write your notes the same day, and plan to rely on them, because most companies will tell you very little.
The advice comes from Phyl Terry, whose book Never Search Alone has put thousands of candidates through job search councils; Lauren Ipsen, who recruits senior executives at Daversa Partners; and Matt Abrahams, who lectures on strategic communication at Stanford Graduate School of Business.
Ask for a signal before the interview ends
The best time to find out about a concern is while you can still do something about it. Near the end of the conversation, ask one question that invites the interviewer to bring up any concern they still have.
Pick one closing question
- "Is there any part of my background you'd like me to clarify before we finish?"
- "Based on our conversation, is there a capability you'd want more evidence of?"
- "What would you need to learn in the next round to feel confident about this hire?"
If they name a gap and there's time, give one concise example that speaks to it. If the gap is real, say so and explain how you'd close it. Either way, listen without arguing. You're there to gather information about the decision, and pushing back turns a useful answer into a debate.
After a rejection, make the request easy to answer
Reply within one business day, while the interviews are still fresh for everyone. Keep the note to four parts: thanks, something you genuinely liked about the process, one narrow question, and explicit permission to decline. "Can you give me any feedback?" asks a busy recruiter to write a performance review. A recruiter can answer a narrow question in one sentence from their phone.
- "Was there one experience the selected candidate demonstrated more clearly?"
- "Was my main gap role fit, interview communication, or depth in a particular area?"
- "Which answer would you recommend I strengthen for future interviews?"
Ask once. Many companies bar interviewers from giving detailed feedback, and many recruiters skip it because they're busy or worried about legal exposure. If the answer is no, thank them and let it go. Pressing again costs you the relationship and almost never gets you the feedback.
Debrief the interview the same day
Phyl Terry, who has coached thousands of job seekers through the job search councils in Never Search Alone, tells candidates to debrief with someone else right after the interview, because your first emotional read of an interview is often wrong. One director of product texted him after an interview convinced she'd blown it. The company was already moving her to the next round. He told her the story she was telling herself came from her inner critic, and that the inner critic was lying to her.
Talk it through with someone else. The player below is queued to 1:07:08, the exact moment Phyl Terry says it. Watch on YouTube.
"You've got to go do a debrief right afterwards, Lenny, because we all have these cockamamy ideas about what happened. We think we did terribly when we did well... and we need to talk it through with someone else who can help us, like, parse exactly what happened and really where we're at."
Before you compare notes with anyone, write your own account. Capture every question you remember, the example you used for each, the follow-up questions, the moments the interviewer leaned in, and the moments you lost them. Do it within an hour if you can. The details fade fast, and by the next day you'll mostly remember how you felt.
Separate observations from conclusions
Observation: The interviewer asked twice how I measured adoption.
Conclusion: They thought my result was weak.
Next test: Prepare an example with a baseline, a measurement window, and a business result.
Get the feedback the company won't send
Work Coach runs the same interview again and scores the answer you actually gave, including how long you took to reach the point. You get the specifics no recruiter will put in writing.
Start Free Trial2-week trial, no credit card needed. Your data is never shared with your employer.
Look for patterns across interviews
One interviewer's reaction is just a data point, but a signal that repeats across interviews is worth acting on. Keep a simple log for every interview: the role, the stage you reached, the questions, your answers, any outside feedback, the outcome, and the one change you'll make next time.
Lauren Ipsen recruits senior executives at Daversa Partners, and she's watched candidates spend most of a search learning to tell their own story.
The tenth-interview problem. The player below is queued to 54:16, the exact moment Lauren Ipsen says it. Watch on YouTube.
"Being able to tell your story, like practice telling your story. So often people don't do that, especially when they're not looking for jobs. And then it's not until their tenth interview that they know how to tell their story and what they did and what they impacted and why they were someone to be missed when they moved on."
Review the log after every third interview. If different interviewers keep probing the same result, transition, or skill, strengthen that part of your story first. The behavioral interview questions guide covers what hiring leaders listen for in those answers. And if your processes keep ending at the same stage, prepare for the decision that stage exists to make, whether that's the recruiter checking fit and clarity or a final round testing judgment.
Turn feedback into one visible change
Feedback like "be more concise" is too vague to practice. Convert it into behavior you can observe: answer the question in your first sentence, use one example instead of three, and say why it matters for this role.
Matt Abrahams teaches strategic communication at Stanford Graduate School of Business, and he has a structure for exactly this. He calls it ADD: answer, detailed example, describe the relevance. It gives an on-the-spot answer a clear start, one piece of proof, and a clean ending.
The ADD structure. The player below is queued to 1:04:16, the exact moment Matt Abrahams explains it. Watch on YouTube.
"It's called ADD, for adding value. You answer the question cleanly and concisely, you then give an example to reinforce the answer, and then you explain the relevance or significance of the answer."
Practice the changed answer out loud three times, then stop. You want to remember the structure and the evidence while the wording stays flexible. If your answers tend to bury the point, the stop rambling guide shows you how to shorten the opening, pick one example, and finish cleanly.
Feedback email scripts for common situations
Adjust the details and keep the shape: thanks, one narrow question, permission to decline.
After a rejection from the recruiter
"Thanks for letting me know, Maya. I enjoyed meeting the team and I'm still impressed by the work. If you can share one skill or example I could demonstrate more clearly in future interviews, I'd be grateful. I understand if you're not able to give individual feedback."
After an internal interview
"Thank you for the conversation today. I want to keep growing toward roles like this one. Could we spend 15 minutes next week on one strength I should keep using and one gap I should close? Specific examples would help me build a practical plan."
When the process ends after a final round
"I appreciate the time everyone put into the process. Since I reached the final stage, one observation about what separated the selected candidate would be especially useful. Even a high-level answer would help me focus my development."
When the feedback is vague
"Thank you. When you say the team needed more strategic depth, could you share one example of where my answer stayed too tactical? No problem if you can't share more detail."
If nobody replies, don't send a second request. Keep the relationship intact and work from your own notes instead.
Frequently asked questions
Is it okay to ask for feedback after an interview?
Yes. A short request that shows you want to improve is professional. Make it easy to decline, because some companies restrict what interviewers can share.
Should I ask why I didn't get the job?
Ask for one forward-looking observation instead of an explanation of the decision. "What could I demonstrate more clearly next time?" is easier to answer than "why didn't I get it?", and the answer is more useful to you.
What if I disagree with the feedback?
Thank the person and write it down anyway. You don't have to accept every interpretation. Look for the same signal in other interviews before you change anything major.
Can I ask for feedback after every round?
During the process, ask what the next round needs to establish. Save the direct feedback request for a rejection or a scheduled debrief, unless the recruiter invites ongoing questions.
The post-interview learning loop on one page
In the interview
- Ask one closing question about anything you can still clarify.
Same day
- Within an hour, write down the questions, your answers, the follow-ups, and the reactions you observed.
- Debrief with one trusted person the same day.
After a rejection
- Reply within one business day with one narrow, forward-looking question and permission to decline.
- Ask once, then stop.
Across interviews
- Log every interview and review the log after every third one.
- Act on repeated questions, repeated gaps, and the stage where processes keep ending.
Before the next interview
- Change one answer or behavior and practice it out loud three times.
Sources
- Lenny's Podcast: Land your dream job in today's market, with Phyl Terry (Sep 2024)
- Lenny's Podcast: Lessons from one of the world's top executive recruiters, with Lauren Ipsen (Nov 2022)
- Lenny's Podcast: How to speak more confidently and persuasively, with Matt Abrahams (Mar 2024)