Interview Feedback Examples: Honest Before and After Answers
Annotated fictional interview answers showing how feedback can improve clarity without adding invented facts, plus what useful feedback looks like and when to question it.
Show contentsHide contents
Feedback on an interview answer can help when it points to a specific part, explains why and suggests a change you can make without adding anything untrue. This guide shows annotated fictional examples. In each one, the revised answer uses only the facts the speaker already had. Nothing is added to make it sound stronger.
The practice suggestions here are optional, so adapt them to the question and to any limit or instruction the interviewer gives. Truth, confidentiality and consent are not optional. All examples are invented. Do not copy them or present their details as your own. Feedback cannot guarantee any outcome.
How to read the examples
Each example has four parts: the facts the speaker has, a first answer, a note a reviewer might give and a revised answer that uses only those facts. The aim is clearer wording, not a better story. If a revision would need a fact you do not have, leave it out or say that you do not know.
Five annotated examples
1. Your part is unclear
Fictional facts: The speaker was on a small team project. Their own tasks were writing the instructions and testing them with a colleague. The project manager made the decisions. The project finished. The speaker felt it went well but has no specific evidence for that, and does not know whether the instructions are still used.
First answer: "We wrote some instructions and it went well."
Note: "It is not clear what you did, or what 'went well' means."
Revised answer: "On a small team project, my part was writing the instructions and testing them with a colleague. The project manager made the decisions. The project finished, and I don't know whether the instructions are still used."
What changed: the revision says who did what and replaces "went well" with what the speaker actually knows.
2. The result is only a feeling
Fictional facts: The speaker answered customer emails for a small shop. A customer was upset about a late order and complained. The speaker apologised, checked the order record and passed the complaint to the owner, who decided what to offer. The speaker thought it was handled fine but does not know what the customer thought afterwards.
First answer: "I handled an angry customer and it was fine."
Note: "'Fine' does not say what happened. Say what you did and what you know."
Revised answer: "A customer complained about a late order. I apologised, checked the order record and passed the complaint to the owner, who decided what to offer. I don't know what the customer thought afterwards."
What changed: the revision names the actions, says who made the decision and admits what is unknown.
3. The background is long and the action arrives late
Fictional facts: The event was a community event on a Saturday. Many people came, and several volunteers did different jobs. The speaker was on the registration table. A queue was forming. The speaker asked the volunteer coordinator for a second sign-in sheet, and the coordinator agreed.
First answer: "So the event was on a Saturday and it was a community thing and lots of people came and there were different volunteers doing different jobs and I was at the registration table and then a queue started to form and so what I did was ask the coordinator for a second sign-in sheet."
Note: "The action comes at the end. Keep only the background the listener needs."
Revised answer: "At a community event, I was on the registration table. A queue was forming, so I asked the volunteer coordinator for a second sign-in sheet. The coordinator agreed."
What changed: the revision keeps the same facts, shortens the set-up and puts the action earlier.
4. Habit hedges and honest uncertainty
Fictional facts: The speaker drafted a schedule. The speaker does not know whether it was used.
First answer: "I think I probably helped with the schedule, maybe."
Note: "You know you drafted it, so say that plainly. Keep the uncertainty for the part you really don't know, which is whether it was used."
Revised answer: "I drafted the schedule. I don't know whether it was used afterwards."
What changed: the revision removes doubt about something the speaker knows and keeps doubt about something they do not. Removing every softening word is not the aim, because it can push you to sound more certain than you are.
5. A word that claims more than the speaker did
Fictional facts: For a week, while the supervisor was away, the speaker handled rota swap requests within rules the supervisor had set. The supervisor made the other decisions.
First answer: "I led the rota."
Note: "'Led' may claim more than you did. Check what you decided and what your supervisor decided."
Revised answer: "While my supervisor was away for a week, I handled rota swap requests within the rules my supervisor had set."
What changed: the revision says what the speaker did and whose rules applied. Choose the verb that matches your role.
What useful feedback looks like
- It points to a specific part of the answer.
- It says why that part is unclear, not only that it is.
- It suggests a change you can make truthfully.
- It separates what you said from how you said it.
- It does not ask you to add a number, a title or a result you do not have.
A note such as "Be more confident" gives you nothing to change. A note such as "I couldn't tell which part was yours" does.
Feedback to question or ignore
Some feedback is not worth acting on. You can question or set aside a note that asks you to invent a figure, to claim a bigger role than you had or to sound more certain than you are. You can also set aside comments about your accent, appearance, a speech difference or a disability. Those comments are not about the content of your answer, and you decide what to act on. If a note is about whether you could be understood, you can ask what exactly was hard to follow.
Using feedback on your own answers
- Choose the notes you want to act on. You do not have to act on all of them.
- Change the answer, and check that every statement is still true.
- Answer again and compare the two versions.
Optional experiment: try the same answer shorter and longer, and notice which is clearer. This guide sets no required length, but follow any limit the interviewer sets. If you want a routine for practicing, see our guide to behavioural interview practice, and for structure see our STAR examples guide.
Giving feedback to someone else
Describe what you noticed, not the person. Point to a specific line, say why it was unclear and offer a change. Ask whether your reading is accurate, because they know what happened. Do not push them to claim more than they did. If you are asked for feedback, our guide to asking for interview feedback covers the other side of the conversation.
If you record a practice session with another person, agree with them before recording and before sharing any recording, and respect confidentiality. Use true examples, and leave out confidential information. In a real interview, do not use any tool to generate answers unless the organiser has explicitly allowed it, and do not record the conversation unless the interviewer has agreed.
This guide is published by Muqabala. You can visit our interview practice page for your next practice session. Use any method that suits you, and check how any tool handles your data first. Do not paste confidential employer, client or personal information into a practice tool.
Get one interview tip a week
Short, practical tips from 20 years on the hiring side. One email a week.