The short answer
A useful mock interview report gives a mark for each skill the round tests, with a reason for every mark tied to something you actually said or wrote. It names the two or three gaps that cost you most, gives specific practice for each, and ends with a verdict at the level you are interviewing for, such as hire or lean no hire. If a report cannot tell you what to do differently in your next round, it is a summary, not feedback.
Why most interview feedback is not useful
Real interviews rarely give feedback at all. Companies worry about legal risk and time, so most candidates hear only yes or no. Mock interviews exist partly to fill that gap, but many of them fall into the same trap in a softer form: a friendly chat at the end, a few general remarks, and nothing written down.
Spoken feedback straight after a round is valuable because it is fresh. It is also easy to forget, hard to compare across rounds, and often softened to be kind. A written report, completed against a fixed rubric, forces the interviewer to be specific and gives you something to come back to before your next attempt.
The five things a good report contains
- A mark for each skill, not one overall score. A single number hides where you are strong and where you are weak. A coding round should be marked separately on problem solving, code quality, testing, complexity and communication; a system design round on requirements, design, data, scale and communication.
- A reason behind every mark. A 3 out of 5 on testing means nothing alone. "You did not check the empty input until prompted, and missed the duplicate case" tells you exactly what to change.
- What you said and wrote. Good reports refer to moments in the round: the approach you first suggested, the line of code with the bug, the trade-off you named. It shows the interviewer was paying attention and makes the note easy to recognise.
- The two or three gaps that cost you most, with practice for each. Not a list of everything imperfect. The few changes that would move your verdict, each paired with a concrete exercise.
- A verdict at your level. How the round would likely land in a real interview for the role and level you chose, on a scale such as strong hire, hire, lean hire, lean no hire or no hire.
Feedback examples: vague and useful
These are made-up examples to show the difference, not quotes from real reports.
| Skill | Vague | Useful |
|---|---|---|
| Communication | Work on your communication. | You went quiet for about eight minutes while writing the merge step. Say one sentence per block of code so the interviewer can follow and help. |
| Testing and edge cases | Think about edge cases more. | You tested only the example input. Before saying you are done, walk through an empty list, a single element and all-equal values. |
| Scale and trade-offs | Your design would not scale. | Every redirect writes a counter to the same row, so a popular link becomes a hot key. Move counting to a queue and say this before the interviewer asks. |
| Ownership (behavioural) | Be more confident. | Your story described what the team did. Say what you decided, what you did yourself and what changed because of it. |
| Complexity | Know your complexities. | You said the solution was linear, but sorting first makes it n log n. State the cost of each step, then the total. |
Red flags in a mock interview report
- Only an overall score or a pass/fail, with no breakdown by skill.
- Praise and criticism with no reference to anything you actually said or wrote.
- Personality comments, such as "be more confident" or "seems nervous", without the behaviour behind them.
- A long list of small issues with no sense of which ones matter most.
- No verdict, or a verdict that ignores the level you said you were interviewing for.
- Nothing written down at all, only a conversation at the end of the call.
How to act on a report
Read the report once straight through, then again with a notebook. For each gap, write down one exercise and when you will do it. Keep the plan small: two or three gaps over a week is realistic; ten is not.
Practise the gap on its own before mixing it back in. If testing was the weak line, spend a few sessions doing nothing but writing test cases for problems you have already solved. If communication was weak, record yourself solving one problem out loud and listen back.
Then take another round and compare the marks line by line. The overall verdict may not move straight away, but the lines you worked on should. If the same gap appears twice, change the exercise rather than repeating it.
What the Revvox report looks like
Every Revvox mock interview ends with a written report within 24 hours. The interviewer marks the five skills of your round 1 to 5, each with notes on what you said and wrote, lists what went well, names the gaps that cost you most with practice for each, and gives a verdict at your level from strong hire to no hire. You can see a full example, with sample data, on our sample report page at /mock-interviews/sample-report before you book.
In multi-round packages, each round gets its own report, so you can see whether the lines you practised actually moved.