THE PEOPLE ROUND
Practise the manager interview
before the panel asks about your team.
Forty-five minutes with an AI director: four real people situations, one scenario, and the management mistake you keep making. For engineering managers and team leads in any field. Then a report per management area with the panel's notes.
Your audio is handled according to our Privacy Policy. One interview credit.
MANAGER INTERVIEW
Listening
45 minutes · four people stories, one scenario, one hard question about yourself
THE ROUND, MINUTE BY MINUTE
What happens in the 45 minutes
- 0 to 3 min
Hello and the plan
How are you, the role, and what the round covers: four situations, one scenario, one question about you, then yours.
- 3 to 10 min
Your first people story
Often someone who was not meeting the bar. What was really going on, the plan you made with them, and what happened.
- 10 to 17 min
Your second story
Another area: a conflict, a partner team, a strong performer you grew.
- 17 to 23 min
Your third story
A project that slipped, told with your part in the miss first.
- 23 to 29 min
Your fourth story
A hire that did not work out, or a team you scaled.
- 29 to 34 min
One scenario
A top performer who is a difficult teammate. Name the options, pick one and defend it.
- 34 to 38 min
The hard question
The management mistake you keep making, and what you do about it now.
- 38 to 45 min
Your questions
Four minutes for yours, then the next step. The director never gives the result in the round.
WHAT YOU WILL BE ASKED
The questions you will hear
These come up in most people-management rounds. Your director picks four areas from your focus and the role, then follows up on what was really going on.
- Tell me about someone on your team who was not meeting the bar. What did you do?
- Tell me about a time you managed someone out.
- Tell me about a project that slipped. What was your part in it?
- Tell me about a hire that did not work out.
- A top performer is also a difficult teammate. What do you do?
- Two people on your team are in conflict. How do you handle it?
- Tell me about a difficult relationship with a product manager.
- Tell me about a time you killed a project.
- How did you scale your team, and what broke on the way?
- How do you structure your one-to-ones?
- Your best performer tells you they are looking to leave. What do you do?
- How do you decide between tech debt and new features?
- Tell me about a time you got it wrong with another team.
- What management mistake do you keep making?
AFTER THE ROUND
What your report covers
Coaching and development
Whether you mentored, coached or sponsored, and how the person grew.
Performance and feedback
Raised early, written down, told with dignity, and an outcome either way.
Hiring and team building
A hire that failed, the signal you missed, and what your process changed.
Delivery and owning the miss
Your part in the slip first, then how you re-scoped with the people involved.
Conflict and hard conversations
The hard conversation told with what was said, not "it resolved itself".
Working across teams
Agreement built on the other team's goals, not on an escalation.
Priorities and trade-offs
One option picked and defended, with what it gives up and how you would measure it.
Self-awareness
A mistake you repeat, when it last happened, and the habit that now catches it.
Technical judgment, for engineering roles
How the technical trade-offs show up in your stories. Added only when the role is an engineering one.
AN EXAMPLE
What the panel would write down about you as a manager · an example
Performance: raised it in week two, wrote it down, agreed a plan with him. 'I asked what was going on at home before I asked about the tickets.'
Delivery: owned the slip first. 'I said yes to the date before I asked the team.' Re-scoped with product the same week.
Working across teams: got the payments team to agree by tying the change to their own fraud goal, not by escalating.
Self-awareness: says she takes work back when a report struggles, and now asks "what would you try?" first.
Scope: manages six, two levels, one partner team. Has hired three, managed one person out.
Consistency: team size and dates match across all four stories.
Readiness for the manager loop: Ready, because every story had a diagnosis, a plan made with the person and a clear outcome.
Questions before you start
What if the whole round is on one project?
A whole round on one project is the project deep dive. Practise the project deep dive
Is this for engineering managers?
Yes, and for every other people manager: team leads, store and district managers, operations and sales managers. The people questions are the same. When your role is an engineering one, the director adds technical judgment, read from how technical trade-offs show up in your stories.
What does a strong management answer look like?
Five parts, in order: what was really going on, the plan you made with the person, what you did, what happened, and what changed in you. Panels trust the messy version, where the first conversation did not land, over a clean story that worked first time. Read how to answer the people questions.
Will it ask about system design?
No. This round is about people. System design is its own interview: practise it on a whiteboard. See the system design interview.
How is this different from the behavioral interview?
The behavioral interview asks for STAR stories on any competency. The manager round asks only about people: performance, coaching, hiring, conflict, delivery and other teams. It is judged on your diagnosis and the plan you made with the person, not only on what you did.
Can I practise the situation I dread most?
Yes. Tell us the people situation you least want to be asked about, and the director makes it one of the four stories.
Does it tell me if I passed?
No, just like a real round. Your report has the notes a panel would write down, a read of your scope, and how ready you are for the manager loop.
Checking your plan…
BETTER TOGETHER
Prepare for what comes next.
Use the same company context and experience across your application and interview preparation.
TAKE YOUR NEXT STEP
Tell your people stories before the panel asks for them.
Say the messy version out loud once: what was going on, the plan, what happened and what you changed. Then read what a panel would write down.