Example report — this is the structure you'll get

Everything below is illustrative sample data for a fictional Senior Backend Engineer interview at ExampleCo. It is not a real user's result — it shows exactly how your own feedback report will be laid out after you complete a mock interview.

Interview Report

Example
Senior Backend Engineer @ ExampleCo
Sample completed session
4.2out of 5

Overall Score

Strong

Coach's summary

“A strong, well-structured set of answers. You consistently grounded your responses in real systems and showed clear ownership. The biggest opportunity is to lead with the measurable impact earlier — the results are there, but they often arrive at the very end of the story.”

Start here: Lead with the measurable outcome earlier instead of saving it for the end.

STAR Performance Analysis

Completeness

Did you cover the full situation, what you did, and the outcome?

4.3/5
StrongAim for 4+

Why this score: Strong — clear and specific.

Specificity

Did you use real names, numbers, and examples?

4.4/5
StrongAim for 4+

Why this score: Strong — clear and specific.

Relevance

Did your answer address what was actually asked?

4.1/5
StrongAim for 4+

Why this score: Strong — clear and specific.

Impact

Did you show the result and why it mattered?

3.3/5
MixedAim for 4+

Why this score: Partly there — add detail and structure.

Conciseness

Was the answer focused, without rambling?

3.8/5
StrongAim for 4+

Why this score: Partly there — add detail and structure.

Strengths

  • Anchored every answer in a concrete system or project rather than generic claims.
  • Clearly connected past backend experience to the demands of the target role.
  • Demonstrated genuine ownership — you described decisions you drove, not just tasks you were assigned.

Areas for Improvement

  • Lead with the measurable outcome earlier instead of saving it for the end.
  • When discussing system design, make the tradeoffs explicit (throughput vs. fairness vs. failure handling).
  • Tighten longer answers so the narrative arc stays sharp from start to finish.

Missed Opportunities

You mentioned reducing incident volume but never gave the before/after numbers.
The rate-limiter answer skipped how you'd handle a downstream dependency failing under load.

Per-Answer Breakdown

Get a report like this for your own interview

This was just an example. Run a real mock interview and get personalized, answer-by-answer feedback in minutes.

Create an accountI already have an account