The Hiring Manager Interview: Walk Through Your Work, Answer 'How Would You', and Ask the Right Questions

The hiring manager is the most common interviewer in a second round, as The Muse notes. The round usually runs 45 to 90 minutes, sometimes with a teammate in the room. At some companies a shorter hiring manager screen of 30 to 45 minutes comes before the full loop.

The recruiter asked whether you could do a job like this. The manager asks a narrower question: can you do this job, on this team, with these problems? They have a gap to fill. Maybe a project nobody owns, a skill the team lacks, or a person who left. Every question is a way to find out whether you fill it.

That changes how to prepare. Generic answers that would work anywhere do badly here. Before the round, write down what you think the gap is. Use the job description, what the recruiter told you and anything the company has said in public. Then shape each answer toward it.

"Walk me through your resume" usually comes first. The trap is to read it aloud, job by job, from the start. The manager already has it in front of them. What they want is the thread.

Aim for about two minutes. Find the one reason or direction that links your moves, and tell the walk through it. "Each move took me closer to the billing side of the business" is a thread. A list of titles and dates is not. Put one result in the middle, a number or a change someone could see. Then end on this role: why it is the obvious next step. Then stop, and let them ask.

Time it out loud before the day. First tries almost always run long, and every extra minute comes out of the questions that matter more.

The manager will ask why you want this role. A generic answer here costs more than it did with the recruiter. An interviewing.io guide says a generic "Why Apple?" is grounds for rejection, and the same is true of most teams.

Give one concrete reason, and tie it to what this role does. Then add one detail that shows you looked: a product the team ships, a problem named in the posting, a change the company announced. "You are moving invoicing in house, and I have done that once already" is an answer. "It is a great company with great people" is not. Never criticise where you work now. It is one of the common failure modes in Meta's own preparation guide, along with a generic why.

Expect to talk about one or two pieces of past work: the one you are proudest of, and often a hard decision or a mistake. In a behavioral round, the interviewer checks you covered the situation, the task, the action and the result. A hiring manager goes further. They want the decisions.

So keep the context short and spend the time on what you chose. What did you decide, and why that? What else could you have done? What did you give up to do it your way? "I split the cutover by region, so a bad night hit one market, not all of them. It cost us two weeks" tells the manager how you think. "We migrated the system and it went well" tells them nothing.

Use "I" for your part and "we" for the team's. End with the result and how you knew. For a mistake, add what you would do differently now. A story with no decision in it sounds like something that happened to you, not something you did.

This is the part most candidates do not prepare for. The manager describes a real problem of the team and asks how you would deal with it. Microsoft's interview tips tell candidates to expect questions on how they would approach a task or scenario from the role.

There is rarely one right answer, and the manager knows it. They are listening to how you reason. Google's guide to structured interviewing suggests follow-ups on exactly that: the factors behind a decision, the pros and cons, and the effect on the rest of the organisation. Five steps cover it.

1. 1Clarify. Ask one question about the problem before you answer it.
2. 2Factors. Name the constraints, people and numbers that would shape your choice.
3. 3Options. Give at least two ways to tackle it.
4. 4A choice. Pick one, say why, and say what it costs.
5. 5A measure. Say how you would know it worked.

The most common mistake is theory: a tidy framework with no choice at the end. The second is one answer with nothing weighed against it. If you have solved something like it before, say so, and use it as your example. That is stronger than any framework.

"How would you spend your first 90 days?" is a question about priorities. You do not need a slide deck. You need an order.

Start with what you would learn first, and from whom: the people you would meet, the systems or customers you would study. Then name one early result you would aim for, small enough to be real. "Meet each engineer in the first two weeks, learn the billing flow, and ship one fix by month two" is a plan. "Hit the ground running" is not. Avoid promising to change everything before you have seen it. A manager hears that as a risk.

The manager will ask what management style works for you, and how you like to give and receive feedback. They are asking because they will be the one managing you.

"I adapt to anything" sounds safe and says nothing. Name a real preference: clear goals and room to decide how, weekly one-to-ones, feedback while the work is still in progress. Then give a time it mattered. Then name one adjustment you have made, a habit you changed or still work on. That one sentence shows more self-awareness than any list of strengths. Be honest. If your style and theirs do not fit, it is better for both of you to find out now.

"What questions do you have for me?" is part of the assessment. Indeed's guide suggests preparing at least five. A 2016 Harvard Business Review article tells interviewers to be wary of a candidate who asks no strategic questions.

Strategic here means questions about the team's goals and the role's gap. What must this team achieve this year? What would make someone great in this role after six months? Why is the role open? What is the hardest problem on your desk right now? Ask how the team works and who is on it. Then confirm the next step: when you will hear, and from whom. Save hours, perks and pay for the recruiter.

After the round, the manager writes up what they saw, and in the debrief they weigh two things above the rest: whether you fit the team, and whether you fill the role's gap. A useful way to picture their note: it covers your fit for the gap, your relevant work with a decision you made, how you would approach their problem, how you like to work, the questions you asked, and a recommendation.

That gives you a way to prepare. Write the note you want the manager to write. "Led a smaller version of our migration, split the cutover to limit risk, asked what slow meant before answering our problem, wants weekly one-to-ones, asked why the role is open." Then make sure each answer hands them one line of it. If a line is missing, find the story or the question that fills it.

Knowing the shape helps. Saying it out loud helps more. The resume walk is longer than you think, the decision inside your best story is harder to name than to remember, and the "how would you" questions are hard to practise alone.

Star Interview runs a 45-minute practice round with an AI hiring manager. It walks through your resume, asks why this team, digs into two pieces of your work, asks two "how would you" questions built from your job description, then takes your questions. Afterwards you get a report on the seven things a hiring manager checks, with the line the manager would give the panel. See what the practice round covers.