In this article
- What the hiring-manager round is for
- How the round is scored
- What the questions cover
- Start here: the learning path
- Technical questions inside the round
- Role fit: lead developer or manager
- Motivation: what excites you at work
- Scope: what were your exact contributions
- Follow-ups and the question after the question
- Staff-level questions: scope and trade-offs
- Questions interviewers ask on the hiring-manager round
- All 4 guides in Hiring-manager round
- Follow-up questions
- Sources
- Hiring manager
- A hiring manager is the person who owns an open role, would manage whoever fills it and often has the deciding say in the hire, so their interview is the one with your future boss.
- Hiring-manager round
- A hiring-manager round is an interview with that person, in which they test how your experience matches the team's work, how you think about technical and people problems, and whether you would be good to work with.
- Individual contributor
- An individual contributor (IC) is an employee who does the work themselves and does not manage other people, such as a software engineer; senior ICs hold bigger problems but still have no direct reports.
- Staff level
- Staff level is a seniority step above senior on many engineering ladders (often followed by principal), where the job is to set technical direction and carry decisions across several teams; the exact titles differ by employer.
What the hiring-manager round is for
A hiring manager decides on fit, scope and judgement. Fit asks whether your experience matches the team's actual problems, scope asks how much you really owned, and judgement asks how you decide when the answer is not obvious. Recruiters screen for basic match and technical interviewers score skills, so the manager round is where those threads meet. Where the round sits in a loop varies by employer, so ask your recruiter, and read how interview loops fit together for the usual shapes.
How the round is scored
Some employers score the manager round with a fixed structure, and some run it as a conversation. Google's re:Work guide (updated March 2026) describes the structured version: every candidate for a job gets the same questions, and answers are graded against a rubric with levels such as poor, borderline, solid and outstanding. The U.S. Office of Personnel Management (OPM) (read 2026-10-24) describes the same idea: all candidates are asked the same predetermined questions in the same order, and all responses are evaluated on the same rating scale.
Structure carries weight. In a 2022 re-analysis of selection research, structured interviews had the highest mean operational validity of the procedures reviewed, r = .42, though with a relatively high spread around that mean. Here r is the correlation between interview scores and job-performance ratings, where 0 means no link and 1 means a perfect one; "operational" means corrected for measurement limits such as unreliable ratings; and "spread" means the estimates from individual studies varied a lot around .42, so the figure is an average, not a promise.
This comes from the HumRRO summary of the paper by Sackett and colleagues (September 2022). Wikipedia's article on job interviews (read 2026-10-24) adds that unstructured interviews are less reliable. So a manager who improvises is not scoring on a scale, but still forming a judgement; prepare for both. For the broader theory of scored behavioural answers, read the behavioral interviews hub.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →What the questions cover
This guide groups preparation for the hiring-manager round into six areas. The grouping is our own, built from the question bank and the sources above, not an employer's list.
Text description of the diagram
- The guide groups preparation for the hiring-manager round into six areas.
- The hiring manager decides on fit, scope and judgement.
| Area | A question in our words | What it tests |
|---|---|---|
| Technical probes | How would you design this, or explain that concept? | Depth, use-case judgement |
| Role fit | Do you see yourself as a hands-on lead or as a manager? | Self-awareness, match to the role |
| Motivation | What kind of work excites you, and why this team? | Drive, research |
| Scope | Walk me through your background, then: what exactly did you do on that project, and what did others do? | Relevance, ownership, honesty |
| Follow-ups | Tell me about a conflict and how it ended; what would you do differently? | People skills, learning |
| Staff-level | How do you decide what not to build, and what did that cost? | Trade-offs, direction across teams |
The three things the manager decides (fit, scope and judgement) cut across all six rows; they are the outcome, not a seventh area.
Our question bank holds 10,471 reported interview questions across its four unit files, and tags 110 of them to the hiring-manager round (computed 2026-10-24).1 Of the 110, 29, or 26%, sit in the unit that our bank files as technical probes, so prepare for some technical questions rather than a purely behavioural round. By the bank's own level tags, 32 are from senior individual-contributor candidates, 26 from engineering managers or senior managers, 25 from staff or principal individual contributors and 27 are unlabelled. These are candidate reports, not any employer's policy, and the mix varies by company and level.
Start here: the learning path
Prepare in this order, because every later step reuses the same project stories. Start with the shape of the round, which is on this page. Then prepare the technical questions that sit inside the round, then the role-fit and motivation prompts, then the scope and follow-up questions that test what you say, and last the Staff-level questions. A story you built for tell me about yourself can open the round, and the situation, task, action, result (STAR) structure on the STAR method page fits the stories.
Questions that candidates have reported from this round include, in our own wording: do you see yourself as a lead developer or a manager, what excites you at work, what were your exact contributions to the projects mentioned, what have you learnt lately about AI, how would you design a multi-task system that handles varying domains, and how would you help build a platform for data science and research teams. Each was reported once in our bank, so treat them as examples, not a ranking. The sections below cover the common shapes of these prompts. For the AI-learning prompt, name one specific thing you learned recently, where you tried it, and how it applies to this team's work.
- Do you see yourself as a lead developer or a manager?
- What excites you at work?
- What were your exact contributions to the projects mentioned?
- How do you use AI in your daily work? How to answer it
- How would you design a multi-task system that handles varying domains?
- Hiring as an EM: how to run a hiring process and decide
Technical questions inside the round
A hiring manager may ask technical questions even when a separate technical round exists, to judge depth and use-case judgement. They run from fundamentals such as what is random about a random variable, to explaining a model architecture, to designing a system in a short slot. The manager listens for whether you pick an approach for the problem in front of you, not for the tool you know best.
Start with the user's problem, state two or three constraints, name the main trade-off and offer to go deeper. If you are asked a fundamental cold and blank, say what you do know, reason aloud and flag what you would check. For the design side, the machine learning system design hub and the AI engineer question list give worked material.
Role fit: lead developer or manager
The role-fit question asks whether you want to build or to lead, and the manager is checking it matches the job. Answer with the work you have done, not a slogan. If the role is a management role, name what you have managed, how many people or how large a surface, and one decision about a person or a team. If it is a lead role, name what you decided technically, who you influenced without authority and how you kept others productive. Admit the pull of the other side honestly if it exists. The engineering management hub covers the management track, and the leadership interviews hub covers the wider leadership questions.
Motivation: what excites you at work
Motivation questions test whether your reasons fit the team's real work. A weak answer is general ("I love solving problems"). A strong one names a type of problem you have seen up close, a moment you enjoyed it and something specific about this team that connects to it. Do your reading before the round: the posting, the team's public work and the product. Avoid praising the company's size or brand, because it says nothing about the job. Keep the answer under a minute and end on the role, so the manager can pick the next thread. The answer is also a chance to ask a question back, which the questions to ask the interviewer page covers.
Scope: what were your exact contributions
Scope questions test what you personally did on work a team shared. The manager asks "what was your role" and "what did others do" to separate your contribution from the team's and to see whether you overclaim. Prepare each project with three lines: the problem and why it mattered, what you decided or built yourself, and the result with the number you can defend. Use "I" for your actions and "we" for the team's, and name the others. If a figure is a team figure, say so. A project deep dive often follows with "what would you change", so write that line too. The behavioral interviews hub shows how to structure each story.
Follow-ups and the question after the question
The follow-up is where a prepared answer meets a real conversation. Common ones are "what would you do differently", "how did you measure that" and "what did the other person say". A rehearsed first answer without depth fails the second question. For each project, write the three follow-ups you expect and a one-sentence answer to each, and plan the metric and its limits.
If a follow-up reaches past what you know, say what you did know then and what you learned later. For example: asked "how did you measure that?", give the metric and its limit; asked "what would you change?", name one decision and what you would test first; asked "what did the other person say?", quote their objection and how it changed the plan. The aim is to stay specific for four or five exchanges, not only for the opening.
Staff-level questions: scope and trade-offs
At Staff level (defined above) the manager tests judgement over breadth. Expect questions on how you set direction without becoming a bottleneck, how you decide what not to build and how you weigh quality, speed and risk. The answers are decisions with a reason and a cost, not a list of techniques. Choose stories where you changed an outcome for a group beyond your team, and say what you gave up.
When the manager pushes back, treat it as information and respond to the reason. Staff candidates are also expected to be exact about scope: never imply ownership of work others did. At employers that hold a debrief or hiring committee, calibration is the step in which interviewers compare a candidate's evidence with the expectations for the level and with peers already at it, so a Staff answer is judged against Staff-sized scope, not against how well it was told.
Questions interviewers ask on the hiring-manager round
The ten prompts below are common shapes of the round, in our own words, with what each tests; we make no claim about how often each is asked.
| Prompt (our wording) | What it tests |
|---|---|
| Walk me through your recent experience. | Relevance |
| What did you personally own on that project? | Scope |
| Describe a conflict and how you handled it. | People skills |
| What was your biggest project and what went wrong? | Learning |
| Do you want to lead people or build? | Self-awareness |
| What are you learning right now? | Curiosity |
| How would you design this system in a short time? | Technical judgement |
| Explain a concept from your field to a newcomer. | Depth, clarity |
| Why this team and why now? | Motivation |
| What would you do differently next time? | Reflection |
Follow-up questions
Do you see yourself as a lead developer or a manager?
Answer with work you have done: name what you decided technically or what you managed, and say honestly which side pulls you. See the engineering management hub and the leadership interviews hub.
Can you walk me through your engineering manager experience?
Give size, then a decision: how many people or how large a surface you managed, one hard call about a person or a team, and the outcome. Prepare it with the engineering management hub.
What is your biggest project?
Pick the project where you can state the problem, your own action and a result you can defend, then expect the follow-ups. The STAR method page shows the shape.
Should I ask about the team's problems in the hiring manager round?
Yes, in the form of a real question about the work, such as what the team's hardest current problem is and how success is measured in the first months. The questions to ask the interviewer page has ready-to-adapt wording.
How do I answer when asked what I would have done differently?
Name one specific change, say what you knew then versus now, and show what you did with the lesson, without blaming others. The behavioral interviews hub covers structure.
- The hiring manager decides on fit, scope and judgement, so prepare stories that show all three.
- Some managers score with a rubric and some improvise; prepare for both.
- Write three lines per project: the problem, what you personally did, a result you can defend.
- Technical questions can appear inside the round; reason aloud and state trade-offs.
- Expect follow-ups, and write the answer to each before the round.
Sources
- A guide to structured interviewing for better hiring practices — Google re:Work (updated March 2026), 1 Mar 2026
- Structured Interviews — U.S. Office of Personnel Management (date = read date), 24 Oct 2026
- Is cognitive ability the best predictor of job performance? New research says it's time to think again — HumRRO (summary of Sackett, Zhang, Berry and Lievens, Journal of Applied Psychology, 2022), 27 Sep 2022
- Job interview — Wikipedia (date = read date), 24 Oct 2026
