Feedback report

Not “good job.” The exact line to change.

QWalk me through this project and what you personally owned.

72/ 100
Getting there

You proved ownership of the build and named the stack, but the impact stayed general -- the answer never showed what changed for the team.

Delivery

Words / min120
Filler words45/min
Long pauses21.9s max
Eye contact74%
  • Pace was steady at ~120 wpm and easy to follow.
  • Clear under interview pressure; tighten the impact sentence.
  • Good eye contact (74%); you looked away a few times when recalling details.
  • One 1.9s pause before describing impact

CV proof coverage

Did your answer back up the bullet?
Proved
  • React + Supabase stack
  • Personal ownership of auth
Partial
  • Analytics dashboard -- mentioned but not explained
Missing
  • A measurable outcome or who used it
The one fix that moves your score most

End with the concrete result: who used the tracker and what it replaced.

Answer transformation

Your answer

I built a job application tracker with React and Supabase. I owned the auth and the analytics dashboard, and the team used it to keep applications in one place.

Stronger

I built a job tracker in React and Supabase. I owned the auth flow and the analytics dashboard, which replaced a shared spreadsheet, so the team could see every application's status in one place.

What worked

Grounded the answer in a real project Owned specific parts instead of saying 'we'