Interview Questions to Ask the Hiring Manager in a Tech Interview
The hiring manager round is the most underestimated conversation in an engineering loop. Candidates spend weeks grinding LeetCode and whiteboarding distributed caches, then treat the hiring manager round like a formality. It is not. This is the conversation where leveling, scope, team placement, and often the final yes or no signal get decided.
The hiring manager is also the person whose answers have the highest signal-to-noise ratio about your future daily life. Recruiters give you polished talking points. Engineers give you the view from the trenches. The hiring manager sits between those worlds and has an incentive to answer honestly because they have to live with the consequences of hiring the wrong person.
This article gives you a working set of questions organized by theme, with commentary on why each one matters, what a healthy answer looks like, and what a red flag sounds like.
Table of Contents
- Why the Hiring Manager Round Matters More Than You Think
- Questions About Team Health
- Questions About Tech Debt and Engineering Culture
- Questions About Failure Tolerance
- Questions About Cross-Team Dynamics
- Questions About the 90-Day Success View
- Questions About the Manager Themselves
- Questions About Career Growth
- Questions You Should Never Ask
- How to Read the Answers
- FAQ
- Conclusion
Why the Hiring Manager Round Matters More Than You Think
Most candidates think the hiring manager round is a soft round. It is not. It is the round where the decision maker evaluates whether you will make their life easier or harder over the next two years. Technical rounds filter for capability. Hiring manager rounds filter for fit, judgment, and whether you will still be here in eighteen months.
The questions you ask do three things at once. They give you information you cannot get anywhere else. They signal your seniority because junior engineers ask about perks while senior engineers ask about ownership and scope. And they frame the manager's impression of you during the part of the conversation they remember most vividly, which is the end.
Ask the wrong questions and you sound like someone who is shopping for a job. Ask the right questions and you sound like someone who is shopping for the right job, which is a very different thing.
Questions About Team Health
Team health is the single biggest predictor of whether you will enjoy the role. A strong team with a weak mandate is usually recoverable. A weak team with a strong mandate rarely is.
What is the current size of the team and how has it changed over the last twelve months?
Why ask this. Growth and shrinkage both tell stories. A team that doubled in a year has absorbed a lot of new people and is probably still finding its rhythm. A team that shrank is either in decline or was over-hired and is now correcting.
What it reveals. Stability, momentum, and whether the team is in build mode or maintenance mode.
Red flag. Several recent departures that the manager struggles to explain or frames defensively.
What is the tenure distribution on the team?
Why ask this. A team where everyone has been there less than a year has no institutional memory. A team where everyone has been there more than five years has no fresh perspective. You want a mix.
What it reveals. Retention health and knowledge depth.
Green flag. A spread of tenures with the most senior people still engaged rather than coasting.
How often does someone leave the team, and why do they typically leave?
Why ask this. Attrition is the clearest measurable signal about team health. The reasons matter more than the rate.
What it reveals. Whether people leave for promotions or whether they leave to escape.
Red flag. The manager cannot remember the last time someone left, which usually means they have not talked to a former report in a long time.
How does the team handle on-call and after-hours incidents?
Why ask this. The on-call model is the clearest reflection of engineering discipline. Teams with mature on-call practices invest in observability, runbooks, and blast radius reduction.
What it reveals. Operational maturity and respect for work-life boundaries.
Green flag. A rotation that is rarely triggered because the systems are stable, with clear compensation or time-off policies when it is.
What does a typical sprint or week look like for this team?
Why ask this. Ceremonies eat hours. If the team runs five meetings a day you will not have time to build.
What it reveals. Process overhead and focus time.
How much of the team's time is spent on planned work versus reactive work?
Why ask this. Reactive-heavy teams are usually either in a crisis or stuck in a cycle of accumulated debt. Either way, you will inherit the problem.
What it reveals. Whether the team controls its roadmap or its roadmap controls the team.
Questions About Tech Debt and Engineering Culture
Every team has tech debt. The question is whether they acknowledge it, budget for it, and pay it down.
How does the team decide when to take on technical debt versus pay it down?
Why ask this. This is a values question disguised as a process question. Mature teams have an explicit framework. Immature teams wing it and always defer payment.
What it reveals. Engineering rigor and the manager's leverage with product.
Green flag. A named percentage of sprint capacity dedicated to paydown, or a regular cleanup cadence.
Can you walk me through the most painful piece of tech debt on the team right now?
Why ask this. The specificity of the answer tells you whether the manager understands the codebase or relies on their engineers to tell them.
What it reveals. Technical literacy of the manager and honesty about the state of the system.
Red flag. Vague answers like we have some legacy stuff or a claim that the codebase is in great shape.
How are architecture decisions made on the team?
Why ask this. You want to know whether senior engineers have real authority or whether architecture is dictated top-down.
What it reveals. Whether you will have influence or just execution duties.
Green flag. A documented process, design reviews, or ADRs that anyone can propose.
What does code review look like here?
Why ask this. Code review culture is a proxy for engineering quality. Rubber-stamp review cultures produce brittle code.
What it reveals. Collaboration norms and quality bar.
How does the team approach testing?
Why ask this. Testing practices are hard to change once set. You want to know what you are inheriting.
What it reveals. Risk tolerance, deployment confidence, and whether shipping is scary or routine.
Red flag. No real test strategy or reliance on manual QA as the last line of defense.
What is the deployment cadence and how do deploys typically go?
Why ask this. Deploy frequency and deploy safety are the two best proxies for engineering effectiveness.
What it reveals. Iteration speed and operational discipline.
Questions About Failure Tolerance
How a team handles failure tells you more about its culture than how it handles success.
Can you tell me about a recent project that did not go well, and what the team learned from it?
Why ask this. Every team has misses. Whether the manager can talk about them openly is the signal.
What it reveals. Psychological safety, post-mortem culture, and the manager's own self-awareness.
Red flag. A long pause followed by a sanitized story with no actual learning in it.
How does the team handle production incidents?
Why ask this. Blameless post-mortems are table stakes in mature organizations. Ask specifically whether the write-ups are shared and acted on.
What it reveals. Whether mistakes become systemic improvements or personal liabilities.
What happens when someone on the team disagrees with a technical decision?
Why ask this. Healthy dissent is a feature, not a bug. You want to know the escalation path.
What it reveals. Conflict norms and hierarchy rigidity.
Green flag. Specific examples of someone pushing back successfully.
What is your personal tolerance for calculated risks that do not pan out?
Why ask this. This puts the manager on the spot in a useful way. Their answer sets expectations for how you will be judged.
What it reveals. Whether you will be punished for swinging or punished for not swinging.
How often does the team ship something that gets reverted or rolled back?
Why ask this. Zero is a red flag because it means the team is too conservative. Too many is a red flag because it means they are reckless. The shape of the answer is the signal.
What it reveals. Deployment philosophy and recovery capability.
Questions About Cross-Team Dynamics
No team is an island. Your daily experience depends on the teams you depend on.
Which other teams do you interact with most frequently, and how are those relationships?
Why ask this. Political friction is a tax on your productivity. You want to know where the tax is highest.
What it reveals. Organizational health and the manager's diplomatic capital.
How are priorities negotiated between this team and product or design?
Why ask this. Some engineering teams are order-takers. Others are co-authors of the roadmap. You need to know which you are joining.
What it reveals. Engineering's seat at the table.
Green flag. Evidence that engineers shape the roadmap, not just execute it.
Who are the stakeholders outside of engineering that this team supports?
Why ask this. Internal platform teams have very different dynamics than external-product teams. The stakeholder map sets the vibe of your week.
What it reveals. The center of gravity for your work and who defines success.
How does this team interact with the security, infrastructure, or platform teams?
Why ask this. Friction with platform teams is one of the top causes of engineer frustration. You want to know whether paved roads exist and whether they are pleasant to drive on.
What it reveals. Platform maturity and political overhead.
What happens when your team needs something from another team that is not on their roadmap?
Why ask this. Every org has a resolution mechanism for this. Some are executive escalation, some are peer negotiation, some are just suffering in silence.
What it reveals. Operating cadence of the broader organization.
Questions About the 90-Day Success View
This is where you find out whether expectations are realistic and whether the role is set up to succeed.
What does success look like for the person in this role after ninety days?
Why ask this. A specific answer means the manager has thought about onboarding. A vague answer means you will be onboarding yourself.
What it reveals. Planning rigor and whether the role is actually scoped.
Green flag. Concrete deliverables like shipping a specific feature, owning a service, or leading a small project.
Red flag. Vague phrases like ramp up and contribute or learn the codebase.
What does success look like after twelve months?
Why ask this. The twelve-month answer is a sanity check on the ninety-day answer. They should stack.
What it reveals. Career trajectory clarity for this role.
What are the biggest mistakes new hires make in their first few months here?
Why ask this. This inverts the question and pulls out the unwritten rules.
What it reveals. Cultural landmines that nobody writes in the onboarding doc.
What does your best performer on the team do differently from an average one?
Why ask this. This tells you the real performance bar, not the stated one.
What it reveals. The invisible standards the manager uses to evaluate people.
Who would I work most closely with, and what is that person like to work with?
Why ask this. Your daily peers shape your day more than your manager does. Get a read on them now.
What it reveals. Team chemistry and whether the manager can speak with specificity about their reports.
Questions About the Manager Themselves
You are not just joining a team. You are joining a manager. Evaluate them directly.
How long have you been managing, and how long have you been at this company?
Why ask this. A first-time manager at a company for six months has a different failure mode than a tenured director.
What it reveals. Baseline experience.
What is your management philosophy?
Why ask this. The answer is almost always polished, but the specifics reveal depth.
What it reveals. Whether they have reflected on management as a craft.
How often do you do one-on-ones, and what do those look like?
Why ask this. The one-on-one is your primary interface with your manager. You should know what it will feel like.
What it reveals. Investment in people management.
How do you handle it when someone on your team is underperforming?
Why ask this. This is the stress test. How they describe handling underperformance is how they will handle it with you.
What it reveals. Directness, empathy, and process.
Who has been promoted on your team in the last two years, and what did they do to get there?
Why ask this. Promotion stories are the clearest data on growth.
What it reveals. Whether this team is a launchpad or a holding pattern.
Red flag. The manager cannot name specific recent promotions.
Questions About Career Growth
The job you accept is not the job you will have in two years. Ask about the trajectory.
What is the career ladder for this role?
Why ask this. Even if you do not care about titles, you want to know the framework.
What it reveals. Leveling structure and visibility of expectations.
What skills would I need to develop to reach the next level from this role?
Why ask this. The specificity of the answer tells you how much thought the manager puts into growth.
What it reveals. Whether growth is a real conversation or a checkbox.
Are there opportunities to work across teams or take on projects outside my immediate scope?
Why ask this. Stretch opportunities are where promotions get earned.
What it reveals. Team flexibility and the manager's willingness to share.
How is performance evaluated, and how often?
Why ask this. Surprise reviews are a sign of poor management. You want a clear cadence.
What it reveals. Feedback culture and process maturity.
Questions You Should Never Ask
A short list of things that will cost you more than they gain.
- Anything whose answer is one search away from the company website. You look unprepared.
- How much vacation do I get. Save this for the offer conversation with the recruiter.
- Why did you leave your last company. This is inappropriate and awkward.
- Tell me about the company. This is lazy and signals you did no homework.
- Anything that implies you already have the offer before it is actually extended.
How to Read the Answers
The content of an answer is only half the signal. The other half is the shape of the delivery.
- Specificity is trust. A manager who names a project, a person, and a timeline is telling you the truth. A manager who speaks in generalities is either uninformed or hiding something.
- Pauses are data. A hiring manager who has to think before answering a question about team health is more trustworthy than one who has a polished answer ready.
- Consistency across rounds matters. If the hiring manager's story about the team does not match what the engineers told you, ask the hiring manager directly in a follow-up.
- Watch for defensiveness. Good managers welcome hard questions. Managers who bristle at them are telling you exactly how they handle criticism on the job.
- Track the questions they ask you. The questions a hiring manager asks reveal what they care about. If they spend all their time on culture and none on technical depth, they are hiring for a seat filler, not a leader.
FAQ
How many questions should I actually ask? Prepare twelve to fifteen so you can adapt in the moment. Plan to ask three to five.
What if the hiring manager runs over and there is no time for my questions? Say explicitly that you have a few important questions and ask for five minutes. A manager who will not give you five minutes at the hiring stage will not give them later either.
Should I ask about salary in this round? No. Save compensation for the recruiter. The hiring manager round is for scope, culture, and fit.
What if the hiring manager seems bored or distracted? That is a signal about the role's priority in their mind. Weigh it accordingly.
How do I handle a hiring manager who dodges a question? Follow up once with a gentler version of the same question. If they dodge again, move on. The dodge is the answer.
Should I take notes during the conversation? Yes, with permission. It signals seriousness and lets you compare across companies later.
What if I do not have time to ask everything? Pick the questions that matter most for your decision. The 90-day success view and the tech debt question are the two highest-leverage ones.
Conclusion
The hiring manager round is an interview in both directions. You are being evaluated for scope and fit, and you are evaluating whether this manager will be a multiplier or a drag on your career. Good questions surface the truth that job descriptions hide.
Walk in with a prepared set of questions organized by theme. Lead with team health, move to tech and culture, probe failure tolerance and cross-team dynamics, and close with the 90-day success view. Leave time for the questions that matter most for your specific decision.
The candidates who consistently land offers at companies they actually want to work for are the candidates who treat the hiring manager round like a strategic conversation, not a formality. The questions you ask will not just give you better information. They will change how the hiring manager sees you. Ask like a peer and they will evaluate you like one.