Question 1
How would you coach someone on this team who is shipping but not growing?
Approach. Describe the feedback in one line, the change you asked for, and how you knew it landed.
Engineering manager interview questions from a job description
Get the coaching, hiring, delivery, and technical questions an engineering manager job description usually leads to.
Matched in your browser from the requirements in the posting and Luna’s interview-question hub. These are practice prompts, not a claim that this wording will be asked.
Requirements in the posting
Engineering Manager
Lead a team of software engineers shipping a customer product.
You will:
- Coach direct reports in 1:1s and performance reviews, including people who ship but are not growing
- Hire with a bar you can explain, including candidates you do not hire
- Own delivery when a stakeholder wants a date the team cannot hit
- Stay close enough to the system design to ask a useful question, without taking the design away
- Collaborate across teams and drive the outcomes you tell the organization you own
We will ask what you put on the table when the date and the quality bar disagree.
Lead a team of software engineers shipping a customer product.
You will:
- Coach direct reports in 1:1s and performance reviews, including people who ship but are not growing
- Hire with a bar you can explain, including candidates you do not hire
- Own delivery when a stakeholder wants a date the team cannot hit
- Stay close enough to the system design to ask a useful question, without taking the design away
- Collaborate across teams and drive the outcomes you tell the organization you own
We will ask what you put on the table when the date and the quality bar disagree.
Likely questions
Behavioral
People management
Engineering Manager
Question 2
Tell me about a hiring decision you would make again, including someone you did not hire.
Approach. Say the bar, the evidence, and what you refused to talk yourself into.
Question 3
A director wants a date this team cannot hit. What do you do?
Approach. Name the tradeoff you would put on the table and how you would tell the team.
System design
System design
Stay close enough to the system design to ask a useful question, without taking the design away
Question 4
Design the system behind the main workflow in this posting. What has to be fast, and what can wait?
Approach. Users and API first. Name one bottleneck and the piece you will not build in the interview.
Question 5
How would you estimate capacity before picking a database?
Approach. Use rough numbers, label every assumption, and say which number would change the design.
Question 6
What do you shed first when traffic spikes, and which user promise do you keep?
Approach. Name the load you drop and the promise tied to the product in the posting.
Behavioral
Collaboration
Collaborate across teams and drive the outcomes you tell the organization you own
Question 7
Tell me about a disagreement with someone who did not report to you. What did you do with their objection?
Approach. Name the objection, what you changed, and what you did not. Do not flatten it into “we aligned.”
Question 8
How do you bring a partner along when this posting’s work depends on their team?
Approach. Say the ask, the artifact you left them, and what you refused to take over.
Behavioral
Ownership
Collaborate across teams and drive the outcomes you tell the organization you own
Question 9
Tell me about something you owned after it shipped, when the interesting part was over.
Approach. Spend the time on the follow-through: the metric, the bug, or the user you went back to.
Question 10
What would you do in the first month if you owned the area this posting describes?
Approach. Name what you would learn, what you would not pretend to know, and the first small outcome.
What to prepare
- Prepare one coaching story and one hiring story, each with a result.
- Narrate one design in sixty seconds before you draw any boxes.
- Have one story where someone disagreed and you kept the working relationship.
- Pick one project you owned after the launch, not only until the launch.
- Mark the three requirements you cannot yet support with a story.
- Say each answer out loud once, in under two minutes.
Engineering manager postings are a people loop with a technical witness. Direct reports, coaching, and hiring are the core. Delivery dates and stakeholder lines are the “a director wants a date you cannot hit” question. System or architecture lines are there to check that you can still talk about the work without pretending to write every line.
Do not answer people questions with process names. A 1:1 is not a story. The feedback, the change in the work, and how you knew it landed are the story.
Prepare one coaching story, one hiring no, and one delivery tradeoff. The sample is a line manager for a product team.
Sample job description
The posting below is already in the tool. The questions are the ones its requirements point to. Replace it with a posting you are actually interviewing for.
Related: Amazon behavioral questions · What a hiring manager wants · Google behavioral questions