Engineering Manager Interview Questions

1.1EM vs tech lead - the distinct responsibilities and why the confusion between them causes problems

1.2The manager as a multiplier - how great EMs make every engineer on the team more effective

1.3Transition from individual contributor to manager - what to let go of and what to double down on

1.4The first 90 days - how to establish trust, learn the team, and start making an impact

2.11-on-1s - how to run them, what to cover, and making them genuinely useful for the engineer

2.2Career development - understanding individual goals and creating paths to get there

2.3Managing performance - setting clear expectations, giving direct feedback, and handling underperformance

2.4Recognising and retaining strong engineers - what makes great engineers stay and what makes them leave

3.1Staying technical enough as a manager - how to maintain credibility without micromanaging

3.2Architectural oversight - how EMs provide technical direction without getting in the way of senior engineers

3.3Technical hiring - designing the process, calibrating standards, and building a high-quality bar

3.4Managing technical debt - getting engineers time to improve the codebase while still hitting product goals

4.1Sprint planning and execution - how EMs ensure the team delivers predictably and sustainably

4.2Estimation and scope management - why estimates are always wrong and how to manage expectations

4.3Managing dependencies - coordinating across teams, clearing blockers, and keeping work flowing

4.4Shipping culture - building a team that takes pride in delivering quality software on time

5.1Psychological safety - building an environment where engineers can take risks and admit mistakes

5.2Diversity and inclusion in engineering - how to hire, develop, and retain a diverse team

5.3Preventing burnout - recognising the signs, managing workload, and building sustainable pace

5.4Engineering culture - values, norms, and how the EM shapes the environment the team works in

6.1Managing up - communicating progress, risks, and needs to engineering leadership and product

6.2Working with product managers - balancing technical quality with product delivery timelines

6.3Cross-team collaboration - coordinating dependencies and building relationships with peer managers

6.4Communicating technical trade-offs to non-technical stakeholders without losing nuance

7.1Workforce planning - knowing when to hire, what skills to prioritise, and how to build team capacity

7.2Hiring process design - building a process that is rigorous, fast, and inclusive

7.3Making hiring decisions - how to synthesise interview feedback and choose the right candidate

7.4Onboarding new engineers - setting them up for success in the first 30, 60, and 90 days

8.1On-call culture - building a sustainable rota, incident response standards, and blameless post-mortems

8.2Production incidents - the EM role during an outage and how to support the team under pressure

8.3Reliability and quality - setting standards for production readiness and maintaining them over time

8.4Learning from failure - building an organisation that improves after every incident

9.1Engineering roadmap - how to build a credible technical plan aligned to the product and business strategy

9.2OKRs and goal setting - translating company goals into meaningful engineering team objectives

9.3Managing capacity - balancing feature work, tech debt, and unplanned work across the quarter

9.4Long-term thinking - how EMs balance short-term delivery pressure with building for the future

10.1Leadership and management questions - how you develop engineers, handle underperformance, and build culture

10.2Delivery questions - managing complexity, stakeholder expectations, and shipping under pressure

10.3Technical questions - demonstrating enough depth to be credible without pretending to be an IC

10.4Compensation negotiation for EM roles, key questions to ask about the team and organisation, and evaluating the role