Hiring manager mock interview: “Was that part actually you?”
The first interview with the hiring manager is the most common round, and usually the one that matters most. The person asking is your future boss, and they care about one thing: can you start doing the work.
So they don't keep it general. They pick the project on your resume that's most relevant to the role and keep asking until they reach details and numbers. Say “my team” and they'll bring the question straight back to you.
Start a hiring manager mock interviewLanguage note: the practice room's on-screen controls are currently in Chinese. Under 高级设置 (Advanced settings), set the interview language to English — the interviewer then asks, follows up and writes your report in English.
What this round decides
Whether you can hit the ground running. The manager needs three things confirmed: the results on your resume are real and yours, you have enough depth and care about metrics, and you can work with product, design and other roles. Pass this, and the later rounds are about level and fit.
The four things this interviewer checks
Depth of expertise
What was hard, how you solved it, and what you would change if you did it again. Describing features without any trade-offs costs you.
Resume authenticity
Which part of the project was yours, how big the team was and how the work was split. Results have to land on you.
Speed to impact
How quickly you'd produce something in an area you don't know yet, and how.
Communication
How you handle disagreement with other roles, and whether you lead with the answer before the story.
How the session runs
- 1
Opening
A self-introduction focused on this role.
- 2
Resume drill
The most relevant project, questioned in depth, to confirm the results are real and yours.
- 3
Competency
Depth of expertise, awareness of metrics, and how you work across roles.
- 4
Pressure
Pushing to isolate the part of the result that was really yours, and watching whether you change your story when challenged.
- 5
Candidate questions
The floor is yours. Asking about the team and what this role must deliver in its first three months lands better than asking about perks.
How it follows up
- Digs into details, asks for numbers, and keeps asking “why this way and not that way?”
- When you talk only about the team, pulls the question straight back to your own contribution.
How it asks (examples, not a question bank)
Which part of this project were you personally responsible for? How many people were on the team, and how was the work divided?
You said you led this, but it sounds like the decisions weren't yours. Is that right?
The three most common ways to lose this round
- Talking only about the team, never about yourself.
- Not being able to give measurable results.
- Coming apart after two follow-up questions.
Have these ready
- One or two projects most relevant to the job description, each with: context, what you personally did, the result in numbers, and how that number was measured.
- For every “I owned” or “I led”, one concrete decision: what the alternatives were and why you chose yours.
- Something that went wrong, or that you'd do differently now.
- The job description of the role you're targeting.
What you get afterwards
- A three-tier hiring verdict — Hire / Borderline / No-hire risk — instead of an inflated score.
- Ratings on six dimensions: content credibility, structure, role fit, handling follow-ups, delivery and pacing, and the quality of your own questions.
- Three to six pieces of evidence, each of which must be a verbatim fragment of what you said — if a quote doesn't match the transcript, the whole report is rejected — each with the original audio to replay.
- Question-by-question notes: what you said, what was wrong with it, and a better way to say it; plus the interviewer's overall note, up to three next actions, and the questions you skipped.
- The report flags your weakest dimensions, and you can start a practice round aimed at exactly those.
Questions
How is this different from the HR screen?
The HR screen checks your resume and fit, not your skills. The hiring manager tests whether you can do the job: they pick a project, go down to details and numbers, and keep separating what the team did from what you did.
My project was a team effort. How do I talk about it without falling apart under follow-ups?
Replace “we” with “I”, mark exactly which part you delivered yourself, and say openly which parts colleagues did. Clear boundaries are more believable. After a session, the report quotes the exact sentence where you overclaimed.
Will this round get technical?
It covers the hard parts, trade-offs and metrics of your own projects, but doesn't go down to first principles the way the technical expert round does. If you have both rounds coming up, practise both.
Hiring manager mock interview: “Was that part actually you?”
Start a hiring manager mock interview