The hiring manager interview: how to prepare
A hiring manager interview is a conversation with the person who would lead your team. Most of it is a deep dive into one or two projects you worked on, followed by questions about what you want from the role, how you work with others and how you take feedback, and it ends with your questions. Prepare one project you can explain at every level of detail, and questions that show you have thought about the job.
Key points
- Choose one project you know end to end, including the parts that went wrong.
- Prepare to go five levels deep: problem, approach, your part, alternatives, numbers.
- Answer role-fit questions with specifics: what you want to learn and what helps you do your best work.
- Give real examples for collaboration and feedback questions; generic answers get a follow-up.
- Bring three or four questions about the team’s work, not about perks.
The shape of the conversation
| Part | What the manager wants to learn |
|---|---|
| Project deep dive (usually the longest part) | What you personally built or decided, how well you understand it, and whether your numbers hold up |
| Role fit | Whether what you want matches what the team can offer |
| Working with others | How you handle disagreement, help teammates and share credit |
| Feedback and ambiguity | Whether you can take hard feedback and act without full information |
| Your questions | What you care about, and how much you have thought about the role |
A worked deep dive
Imagine your project was a search feature for a university course catalogue, built by a team of three students. A manager might take it five levels deep. Prepare a one- or two-sentence answer for each level before the interview; the example answers below are fictional.
- Problem: “Students searched by course code but thought in topics, so a search for ‘machine learning’ missed half the relevant courses.”
- Approach: “We indexed course descriptions as well as titles and added synonyms from a small list the department gave us.”
- Your part: “I built the indexing job and the ranking. Two teammates built the interface and the synonym editor.”
- Alternatives: “I considered a hosted search service, but the department wanted no external dependencies, so I used the full-text search already in our database.”
- Numbers and outcome: “In a test with 40 students, the share of searches that ended with a click went from 52% to 71%. Ranking was still weak for very short queries, and I would fix that first.”
How it sounds out loud
“The team built the feature; my part was the indexing job and the ranking, and I can go into either.”
“I remember the click rate going from about 50 to about 70 percent in our test; I don’t have the exact figures to hand, but the test had 40 students.”
“What I’d change: we never tested with students outside computer science, and their queries were the ones that failed.”
Role fit and working with others
Role-fit questions (“why this role?”, “what do you want to learn here?”, “what kind of manager helps you most?”) have no single right answer, but vague ones read as low interest. Tie your answer to something concrete in the role and to a real moment when you did your best work.
Collaboration and feedback questions are behavioral questions in a lighter frame. Use a real example in the STAR shape, shorter than in a behavioral round, and expect one follow-up.
Questions to ask the hiring manager
Good questions are about the work. Lists of “reverse interview” questions are a useful place to start; write your own versions in your words, and pick the ones whose answers would change your decision.
- What would a good first three months look like for this person?
- What is the hardest technical problem the team is working on right now?
- How does the team decide what to build next, and who is in that conversation?
- How do people on the team get feedback, and how often?
- What did the last person to grow quickly on this team do differently?
A one-evening preparation plan
- Pick the project and write its five-level ladder: problem, approach, your part, alternatives, numbers.
- Check every number against something you can point to: a dashboard, a report, a commit. Drop the ones you cannot.
- Write one sentence on what went wrong and one on what you would change.
- Prepare a real example each for disagreement, helping a teammate and hard feedback.
- Read the job description and write two sentences on why this role, tied to something specific in it.
- Say all of it out loud once, timed. The deep dive should take three to four minutes before the first question.
Common mistakes
- Picking the most impressive project instead of the one you understand best.
- “We” throughout the deep dive, until the manager asks three times what your part was.
- Numbers you cannot explain or back up.
- Speaking badly of a former team or manager.
- Generic role-fit answers that would fit any company.
- No questions at the end, or only questions about perks.
Questions
How is a hiring manager interview different from a behavioral round?
It goes deeper on fewer topics. A behavioral round asks for several short stories; a hiring manager often spends half the time on one project and checks how well you know it.
Will they ask technical questions?
Usually through the project: why that design, what broke, how you measured it. Expect to explain technical choices to someone who knows the field.
How many questions should I ask at the end?
Prepare four or five and ask two or three, chosen by what the conversation has already covered.
Practise this out loud with Vera
In Mockich the hiring manager conversation is part of the full loop for a role: 25 to 30 min, deep dives into one or two projects from your resume, then role fit, working with others, feedback and ambiguity, and your own questions, which Vera answers in character with how teams like this typically work. To practise the story-telling it relies on in one round, use the behavioral round, which runs 30 to 35 min: four story questions about conflict, ownership, failure and impact, built from your resume and the job when you add them. Vera lets you tell the story, then probes one thing at a time (your part, the result, the hardest moment, what you would change) and does not coach during the round. The report scores specificity and ownership, structure, impact and results, self-awareness and learning, collaboration and communication (plus leadership and influence, judgment under ambiguity at lead), quotes your words, and in voice rounds shows your pace, pauses and filler words.
Related guides
Sources
We read these sources on 2026-11-03 for how the conversation is usually structured; source 4 was read for the idea of asking about the work, and the questions listed here are written in our own words, as are the course-search project and its numbers.
- [1] Ashby, Engineer Past Projects Deep Dive
- [2] PracHub, Software engineer hiring manager interview: questions, signals and seniority
- [3] Tech Interview Handbook, Behavioral interviews (MIT)
- [4] viraptor on GitHub, Reverse interview: questions to ask the company (CC BY-SA 4.0 (ideas only, no text used))