Engineering Management interview prep.

Behavioural questions to expect

1. Walk me through your CV.
2. Tell me about your most impactful management decision or call.
3. Tell me about a weakness, a failure, or feedback you've received and worked on.
4. Why engineering management - and why at a devtools / infra firm specifically?
5. Which team or org would you want to run, and why?
6. Why the firm?
7. How would you describe the firm's engineering organisation + infrastructure in your own words?
8. What does a great EM at the firm actually do day-to-day - and what does great look like vs average?

Technical concepts to master

• Performance management + the underperformer playbook (infra layer)

  1:1 cadence + structure · The underperformer playbook (with customer-impact lens) · Calibration + leveling (infra ladder) · Career ladder + growth conversations (IC / OSS / EM tracks)

• Hiring + interviewing at the infra bar

  Loop design + rubric · Bar-raiser + debrief discipline · OSS / community signal (where relevant) · Onboarding + the 30 / 60 / 90 (infra layer)

• Technical strategy + API + platform roadmap

  Multi-quarter strategy (devtools / infra flavor) · Roadmap + allocation · API + backward-compat budget · RFC + design-review discipline

• Cross-functional + OSS community + customer dynamics

  PM + DX / Docs / DevRel partnership · Customer success + TAM coordination (especially for major customers) · OSS community + maintainer relationships (where relevant) · Stakeholder + exec + customer communication

Practical drills

• An engineer on your team has missed deliverables, owned a P0 that escalated to a major customer, and the team is starting to route around them. Walk me through what you'd do over the next 90 days.
• You're the Senior EM for 2 teams (8 + 7 engineers) at the firm: one product team owning a customer-facing API surface, one platform team owning shared infra + the SDK. The org OKR is 'lift NRR by 5pts'. The API has 30% of customers on a behavior we'd like to deprecate. Walk me through your 12-month strategy + roadmap.
• Your team is about to ship a paid-product feature - workspace-level governance + RBAC - that the OSS community has been requesting in the open-source project. Several prominent maintainers are arguing it 'belongs' in OSS. Walk me through how you'd navigate this over the next 4 weeks.

Smart-question anchors

• Team + scope - the team's surface area, current challenges, what the EM would own in 6-12 months
• API + platform discipline - backward-compat policy, deprecation cadence, RFC + API-review culture
• OSS posture - OSS-led vs open-core vs proprietary; project-vs-product line; maintainer + governance model
• Customer-SLO + on-call - SLO tiering, error budgets, customer-published postmortems, recent incidents
• Performance + calibration + leveling - cadence, ladder, IC / OSS / EM tracks, bar-raiser in hiring + promo

Sourced from

IGotAnOffer - Engineering Manager Interview Prep · Interview Kickstart + Engineering Manager Tools - Senior EM question banks · interviewing.io + Hello Interview - Senior Engineer + EM System Design at infra scale · Google SRE Book + canonical SRE reference - SLOs + customer-published postmortems + cell-based architecture · GitHub + open-source maintainer community - governance + community dynamics · Postman + Devinterview - API Design at scale