This is a sample report.
Run a real interview to get one scored on your own answers.
Here's the honest read.
new grad swe @ google · scored on substance and delivery
Larpy: “You said 'we' so many times I thought I was interviewing the whole team.”
delivery 7.4
Substance
Tell me about a time you led a project.
partialYou set up the problem clearly and showed initiative taking it on.
You never said what YOU personally decided or built, and gave no metric.
A top answer: Name the call you owned and the measurable result it drove.
Walk me through a hard technical tradeoff.
answeredStrong reasoning on latency vs cost, anchored to a real number (300ms).
Slightly rushed the conclusion, so the decision got buried.
A top answer: End on the decision and why it held up in hindsight.
Why this role, why this team?
dodgedSome genuine enthusiasm came through.
No specific tie to the team or product. It read generic.
A top answer: Reference one specific thing about the team and connect it to your goals.
Delivery
Pace ran hot at 184 wpm and you hedged twice ("kind of", "I think"). Slowing down and cutting the hedges will read as noticeably more senior.
“When the caller stops, endpointing fires around 300 milliseconds, then the first token...”
Specific, quantified, and showed real systems depth. This is your level when you commit.
“it was, um, pretty successful i think”
Vague and hedged. No metric, no ownership. This is the line that capped your score.
Your top 3 fixes
Replace "we" with "I" and name your decision.
Drill · Re-answer Q1 in 60s using "I decided X, which led to Y."
Cut the hedges ("kind of", "I think").
Drill · Record a 30s answer, replay it, and count hedges. Target zero.
Quantify every outcome.
Drill · For each resume project, write the one number that proves impact.
Own your impact: every story ends with a number and a decision you personally made.
Run your own interview