You lead 4 teams with 46 engineers at a $60M ARR SaaS company that must add $12M ARR next year while keeping gross margin above 78%. How do you set the engineering portfolio?

I would fund the revenue target first, but reserve explicit capacity for margin and reliability so growth does not consume the platform. - I would model the $12M gap by initiative, assign 24 engineers to the two bets with at least $4M expected ARR each, and stop either bet if qualified pipeline stays below $1M after one quarter. - I would put 10 engineers on infrastructure work with a CFO-reviewed target to cut annual cloud spend by $1.2M and preserve the 78% margin floor. - The remaining 12 engineers would cover retention and SLO work; each EM would own a quarterly scorecard, and I would rebalance when any committed outcome misses its leading indicator by 20%.

A B2B product with $35M ARR loses 9% of enterprise renewals because exports take 18 hours, and your 38 engineers have two quarters to reduce that to 2 hours. What do you prioritize?

I would make export latency the top retention program for two quarters and defer lower-value feature work. - I would quantify revenue at risk with Sales and Finance, then allocate 12 engineers if the 7-point renewal improvement protects at least $2.5M ARR. - The data EM would own a six-week design and delivery plan with p95 export time milestones of 8 hours, 4 hours, and 2 hours recorded in the portfolio brief. - I would release capacity only after p95 stays below 2 hours for 30 days and enterprise renewal intent improves by at least 5 percentage points in the next cohort.

Your company expects a European launch to produce $6M ARR in 18 months, but data residency requires work from 3 of your 5 teams and an estimated 28 engineer-months. How do you decide whether it enters the roadmap?

I would approve the launch only after the commercial case clears the full engineering and operating cost with explicit demand evidence. - I would compare the $6M forecast with 28 engineer-months at $22,000 each plus $600,000 annual regional infrastructure cost, and require at least a 3 times three-year return. - A single program brief would map residency, support, security, and product dependencies; three EMs would own milestones, while the regional GM would own signed design partners. - I would fund discovery for six weeks and commit the build only with 10 customers representing at least $2M qualified ARR and no unresolved launch-critical compliance gap.

Four teams totaling 44 engineers currently spend 82% on features, while change failure rate is 19% and the annual target requires 25% faster delivery. How do you change capacity allocation for the next two quarters?

I would move the portfolio to 65% product, 20% reliability, and 15% developer productivity for two quarters. - The allocation equals about 29, 9, and 6 engineers; I would publish it in quarterly planning so product leaders can see the exact feature capacity being traded. - The reliability EM would target change failure rate below 10%, while the platform EM would target median lead time down 25% through the three highest-delay CI and environment fixes. - I would restore feature capacity only when both thresholds hold for six consecutive weeks, otherwise the next quarter keeps the same protected investment.

You have 40 engineers and $3M of discretionary budget for three product bets forecast at $8M, $5M, and $3M ARR, but you can staff only two for the next 9 months. How do you choose?

I would rank the bets by risk-adjusted return per engineer and fund the top two in stages rather than accept all three forecasts at face value. - The portfolio model would multiply ARR by validated probability and divide by engineer-months; Finance and Product must sign the assumptions and sensitivity range. - I would give each selected bet an eight-week tranche of 5 engineers with a written artifact covering adoption, technical feasibility, and unit-economics milestones. - A bet loses its next tranche if it misses two of three milestones by more than 20%, and that capacity moves to the reserve or the third-ranked option.

A checkout domain generating $20M annually needs 14 engineer-months of debt work to keep feature lead time from rising 30% next year. Your 42-engineer group has one quarter to make the case. What do you do?

I would fund the debt work if a short measurement phase confirms that its avoided delivery cost exceeds the 14 engineer-month investment. - The owning EM would baseline queue time, defect rework, and deployment effort for four weeks, then convert the projected 30% slowdown into delayed revenue and labor cost with Finance. - The decision memo would compare roughly $308,000 of engineering cost at $22,000 per engineer-month with the value of recovered roadmap weeks and reduced checkout defects. - I would approve staged work with exits of 20% lower lead time and 30% less rework after eight weeks; failure to reach both stops the remaining scope.

A $4M ARR launch depends on identity, billing, and analytics teams, but their plans expose a 7-week critical-path gap inside a 6-month window. How do you govern the program across 36 engineers?

I would create one dependency-led program plan and remove the 7-week gap before authorizing the external date. - The three EMs would map deliverables, interfaces, and latest-start dates in one critical-path artifact, with one senior EM accountable for the $4M outcome. - I would move 4 engineers from noncritical analytics work to identity for 10 weeks if that reduces the modeled gap to under 2 weeks without breaking an existing SLO commitment. - The launch date becomes firm only after all critical interfaces pass contract tests and schedule confidence reaches 80% at the 90-day checkpoint.

A legacy product earns $1.8M ARR but consumes 9 of 48 engineers and $700,000 in annual infrastructure, while customers can migrate within 12 months. What portfolio decision do you make?

I would propose a funded 12-month sunset because the product consumes more capacity than its contribution justifies. - Finance and I would compare $1.8M ARR with about $2.7M annual engineering cost plus $700,000 infrastructure, then document the margin and opportunity-cost case. - I would assign 4 engineers to migration tooling and 2 to maintenance, with the product GM owning a customer-by-customer plan and monthly migrated ARR target. - The remaining 3 engineers move only after 80% of ARR is migrated; shutdown occurs when 95% is moved, contractual obligations are closed, and residual run cost is below $100,000.

Product wants 18 of your 50 engineers on an AI assistant expected to lift conversion by 4% within 6 months, but the estimate has no production accuracy or inference-cost data. How do you structure the bet?

I would not commit 18 engineers until a six-week validation proves task quality, privacy and safety, economics, and causal conversion lift. - Product and Engineering would define a task-specific offline evaluation against the current workflow, using representative labeled cases, per-task measures such as grounded completion and refusal correctness, confidence intervals, and zero critical safety failures. - Privacy and Security would gate any user test on data minimization, retention, access, prompt-injection, and leakage tests with zero unresolved critical findings; Finance would model inference cost and require 12-month gross-profit payback. - Analytics would preregister an online A/B test with a primary conversion metric, guardrails, minimum detectable lift, power, and stopping rule; I release more capacity only after statistically reliable lift and the cost and safety gates pass.

Halfway through the year, a 45-engineer portfolio is 15% below its $10M expansion target, while a platform program is on track to save $900,000 annually in 5 months. How do you rebalance the next two quarters?

I would protect the platform program if its payback remains credible and redirect lower-return feature capacity toward the expansion gap. - I would update the portfolio model with actual funnel data, preserving the platform team where $900,000 savings exceed its remaining cost by at least 2 times over two years. - Product and the relevant EMs would stop or shrink initiatives below 50% of planned pipeline, freeing a target of 8 engineers for the two strongest expansion levers. - The revised plan would carry monthly ARR and savings checkpoints; another reallocation triggers if either outcome is more than 10% behind for two consecutive months.

You inherit 48 engineers in 4 component teams, and 70% of roadmap items require handoffs across at least 3 teams. How would you redesign ownership over 6 months?

I would move from component teams to three durable product-domain teams plus one platform team, with migration staged over six months. - I would map the last 50 roadmap items to customer domains and target ownership that lets at least 70% ship within one team instead of the current 30%. - Four EMs would produce charters listing APIs, data, SLOs, and decision rights; unresolved boundaries go to a weekly design forum for the first 12 weeks. - The topology is accepted when cross-team handoffs fall below 35%, no team exceeds 12 engineers, and domain SLO ownership is complete for 100% of services.

Five product teams with 52 engineers spend 28% of capacity rebuilding CI, authentication, and observability capabilities. You can form one 8-person platform team. What belongs in its charter?

I would charter the platform team around the three repeated capabilities with measured internal-customer outcomes, not as an unlimited ticket queue. - A six-week demand audit would confirm at least 10 engineer-equivalents of duplication; the platform EM would publish supported products, interfaces, and excluded responsibilities. - The first-year roadmap would target self-service CI under 15 minutes, standard authentication for 90% of services, and observability onboarding under one day. - The team keeps a capability only when at least 4 product teams adopt it and aggregate duplicated effort falls from 28% to below 12% within two quarters.

You directly manage 4 EMs covering 56 engineers; one EM has 19 reports and another has 7, while the company will add 8 engineers this year. How do you reset spans?

I would create three additional EM roles and rebalance the future 64 engineers into seven teams before all 8 hires land. - Seven EMs can each support 8 to 10 engineers, so I would split the 19-person group first and sequence two more qualified internal moves or external hires against headcount arrival. - The seven EMs would submit team charters and reporting maps within 30 days, including tech lead responsibilities so management and technical ownership do not overlap ambiguously. - I would consider the change complete after 90 days when every engineer has a stable manager, no EM exceeds 10 reports, and monthly 1:1 completion stays above 90%.

Your 42 engineers sit in California, London, and Warsaw with only 2 shared working hours, and roadmap decisions currently take a median of 9 days. How do you structure the organization?

I would make each product domain executable within one regional cluster and use asynchronous decision records for cross-region interfaces. - I would map dependencies and relocate ownership so at least 80% of daily delivery decisions need no meeting outside a region's 6-hour collaboration window. - Each EM would maintain a domain log with a 48-hour review deadline; one rotating regional representative attends the 2-hour overlap for genuinely shared decisions. - The structure succeeds when median decision time falls from 9 days to under 3 for eight weeks and cross-time-zone meetings drop below 2 per engineer per week.

A 24-hour B2B service has 45 engineers across UTC-8, UTC+0, and UTC+8, but every change still requires approval from the UTC-8 team. How do you change ownership without lowering the 99.95% SLO?

I would delegate bounded production authority to each region and make approval risk-based rather than location-based. - The service EMs would define change classes, with low-risk changes locally approved and only schema or security changes requiring two-region review within 24 hours. - Each region must have 2 trained release approvers and pass 10 supervised changes; the ownership matrix and audit trail become the control artifact. - UTC-8 stops routine approval when all regions sustain under 10% change failure rate and the 99.95% SLO for 60 days.

Three teams totaling 34 engineers all modify a shared order service, and 40% of pull requests wait more than 3 days for an owner review. How do you draw the boundary?

I would give one team end-to-end ownership of the order core and expose versioned contracts for the other two teams. - I would analyze 90 days of changes and incidents to separate core order invariants from pricing and fulfillment extensions, then record the boundary in a service charter. - The owning EM gets 8 engineers and a 2-business-day review SLO; consumer teams receive delegated ownership only for isolated modules with contract tests. - The model exits transition when 90% of reviews finish within 2 days, unauthorized cross-boundary changes are zero for 8 weeks, and consumer lead time does not rise over 10%.

Four product teams share 6 security engineers, and embedded assignments leave 35% of security work duplicated over a 12-month roadmap. What topology do you choose?

I would use a central security enablement team with named product liaisons rather than permanently embedding all 6 specialists. - The security manager would reserve 4 engineers for common controls and 2 for rotating 8-week product engagements, based on a backlog showing at least 2 teams need each shared control. - Each product EM owns remediation in their domain, while the security team owns standards, threat models, and reusable tooling with published response times. - I would keep the model if duplicated effort falls from 35% to below 15% and 90% of high-risk reviews complete within 5 business days for two quarters.

A group will grow from 36 to 50 engineers and from 3 to 5 teams in 9 months, but only 2 current leads are management-ready. How do you sequence the topology change?

I would create the two teams only as leadership and hiring capacity become ready, not split all domains on day one. - The workforce plan would open one external EM role now, develop one internal lead over 90 days, and cap interim teams at 10 engineers. - I would split the highest-handoff domain first after its charter, tech lead, and 6-person core are in place; the second split waits at least 8 weeks for evidence. - Expansion completes when 5 EM or acting-manager seats are filled, every team has a documented boundary, and no new hire lacks an assigned manager for more than 5 days.

Your 5 engineering teams and 47 engineers share only 3 product managers for the next 2 quarters. How do you pair leadership and preserve decision speed?

I would group the five teams into three product domains and give each PM one domain outcome rather than spread every PM across every team. - Two related team pairs would share a PM and a quarterly outcome, while the fifth team owns a platform charter with its EM as internal product lead. - Each domain writes decision rights for PM, EM, and tech lead, including a 48-hour escalation path and one prioritized backlog artifact. - I would revisit the model if decision lead time exceeds 4 days, unplanned work rises above 20%, or either paired domain misses two monthly outcome checkpoints.

Across 5 teams and 60 services, 18 services have two claimed owners and 11 have none; the next planning cycle starts in 6 weeks. What do you do?

I would complete a service ownership reset before planning and refuse roadmap commitments for ownerless critical services. - The 4 EMs would classify all 60 services by business criticality, SLO, primary owner, consumer, and lifecycle status in one catalog within 3 weeks. - Duplicate claims are resolved by write authority and operational accountability; ownerless tier-1 services receive capacity before new work, with me accountable for final boundaries. - Planning opens when 100% of tier-1 and 95% of all services have one owner, an escalation route, and a reviewed SLO, with zero duplicate primary owners.

Engineering Manager interview questions

100 real questions with model answers and explanations for Director of Engineering candidates.

See a Engineering Manager resume example →

Practice with flashcards

Spaced repetition · Hunter Pass

Questions

portfolioportfolio-managementcss

I would fund the revenue target first, but reserve explicit capacity for margin and reliability so growth does not consume the platform.

I would model the $12M gap by initiative, assign 24 engineers to the two bets with at least $4M expected ARR each, and stop either bet if qualified pipeline stays below $1M after one quarter.
I would put 10 engineers on infrastructure work with a CFO-reviewed target to cut annual cloud spend by $1.2M and preserve the 78% margin floor.
The remaining 12 engineers would cover retention and SLO work; each EM would own a quarterly scorecard, and I would rebalance when any committed outcome misses its leading indicator by 20%.

Why interviewers ask this: The interviewer is testing whether the candidate converts a business target into a constrained, measurable portfolio rather than listing strategic themes.

prioritization

I would make export latency the top retention program for two quarters and defer lower-value feature work.

I would quantify revenue at risk with Sales and Finance, then allocate 12 engineers if the 7-point renewal improvement protects at least $2.5M ARR.
The data EM would own a six-week design and delivery plan with p95 export time milestones of 8 hours, 4 hours, and 2 hours recorded in the portfolio brief.
I would release capacity only after p95 stays below 2 hours for 30 days and enterprise renewal intent improves by at least 5 percentage points in the next cohort.

Why interviewers ask this: A strong answer links an engineering bottleneck to retained revenue, staged delivery, a named owner, and a measurable exit.

roadmapestimationroadmapping

I would approve the launch only after the commercial case clears the full engineering and operating cost with explicit demand evidence.

I would compare the $6M forecast with 28 engineer-months at $22,000 each plus $600,000 annual regional infrastructure cost, and require at least a 3 times three-year return.
A single program brief would map residency, support, security, and product dependencies; three EMs would own milestones, while the regional GM would own signed design partners.
I would fund discovery for six weeks and commit the build only with 10 customers representing at least $2M qualified ARR and no unresolved launch-critical compliance gap.

Why interviewers ask this: The question checks whether the candidate combines portfolio economics, cross-team dependencies, and commercial validation before committing scarce capacity.

capacity-planningcapacity

I would move the portfolio to 65% product, 20% reliability, and 15% developer productivity for two quarters.

The allocation equals about 29, 9, and 6 engineers; I would publish it in quarterly planning so product leaders can see the exact feature capacity being traded.
The reliability EM would target change failure rate below 10%, while the platform EM would target median lead time down 25% through the three highest-delay CI and environment fixes.
I would restore feature capacity only when both thresholds hold for six consecutive weeks, otherwise the next quarter keeps the same protected investment.

Why interviewers ask this: The interviewer wants a numerical capacity decision tied to portfolio-level delivery and quality exits, not a generic call to balance debt and features.

I would rank the bets by risk-adjusted return per engineer and fund the top two in stages rather than accept all three forecasts at face value.

The portfolio model would multiply ARR by validated probability and divide by engineer-months; Finance and Product must sign the assumptions and sensitivity range.
I would give each selected bet an eight-week tranche of 5 engineers with a written artifact covering adoption, technical feasibility, and unit-economics milestones.
A bet loses its next tranche if it misses two of three milestones by more than 20%, and that capacity moves to the reserve or the third-ranked option.

Why interviewers ask this: This evaluates disciplined portfolio allocation under scarcity, including comparable economics and a mechanism to stop weak bets.

I would fund the debt work if a short measurement phase confirms that its avoided delivery cost exceeds the 14 engineer-month investment.

The owning EM would baseline queue time, defect rework, and deployment effort for four weeks, then convert the projected 30% slowdown into delayed revenue and labor cost with Finance.
The decision memo would compare roughly $308,000 of engineering cost at $22,000 per engineer-month with the value of recovered roadmap weeks and reduced checkout defects.
I would approve staged work with exits of 20% lower lead time and 30% less rework after eight weeks; failure to reach both stops the remaining scope.

Why interviewers ask this: The interviewer is looking for a business-grounded technical debt decision with measured causality rather than fear-based modernization.

program-managementlaunches

I would create one dependency-led program plan and remove the 7-week gap before authorizing the external date.

The three EMs would map deliverables, interfaces, and latest-start dates in one critical-path artifact, with one senior EM accountable for the $4M outcome.
I would move 4 engineers from noncritical analytics work to identity for 10 weeks if that reduces the modeled gap to under 2 weeks without breaking an existing SLO commitment.
The launch date becomes firm only after all critical interfaces pass contract tests and schedule confidence reaches 80% at the 90-day checkpoint.

Why interviewers ask this: A strong candidate manages the cross-team critical path through ownership, capacity movement, and evidence-based date confidence.

portfolioportfolio-management

I would propose a funded 12-month sunset because the product consumes more capacity than its contribution justifies.

Finance and I would compare $1.8M ARR with about $2.7M annual engineering cost plus $700,000 infrastructure, then document the margin and opportunity-cost case.
I would assign 4 engineers to migration tooling and 2 to maintenance, with the product GM owning a customer-by-customer plan and monthly migrated ARR target.
The remaining 3 engineers move only after 80% of ARR is migrated; shutdown occurs when 95% is moved, contractual obligations are closed, and residual run cost is below $100,000.

Why interviewers ask this: The interviewer is evaluating whether the candidate can make a bounded product sunset decision using full cost and customer migration gates.

estimation

I would not commit 18 engineers until a six-week validation proves task quality, privacy and safety, economics, and causal conversion lift.

Product and Engineering would define a task-specific offline evaluation against the current workflow, using representative labeled cases, per-task measures such as grounded completion and refusal correctness, confidence intervals, and zero critical safety failures.
Privacy and Security would gate any user test on data minimization, retention, access, prompt-injection, and leakage tests with zero unresolved critical findings; Finance would model inference cost and require 12-month gross-profit payback.
Analytics would preregister an online A/B test with a primary conversion metric, guardrails, minimum detectable lift, power, and stopping rule; I release more capacity only after statistically reliable lift and the cost and safety gates pass.

Why interviewers ask this: This checks whether the manager turns a fashionable technology request into a staged investment with product, technical, and economic evidence.

portfolioportfolio-managementprogram-management

I would protect the platform program if its payback remains credible and redirect lower-return feature capacity toward the expansion gap.

I would update the portfolio model with actual funnel data, preserving the platform team where $900,000 savings exceed its remaining cost by at least 2 times over two years.
Product and the relevant EMs would stop or shrink initiatives below 50% of planned pipeline, freeing a target of 8 engineers for the two strongest expansion levers.
The revised plan would carry monthly ARR and savings checkpoints; another reallocation triggers if either outcome is more than 10% behind for two consecutive months.

Why interviewers ask this: The interviewer wants evidence that strategy is a revisable allocation system and that cost programs are not sacrificed reflexively for a missed revenue target.

roadmapownershipcomponents

I would move from component teams to three durable product-domain teams plus one platform team, with migration staged over six months.

I would map the last 50 roadmap items to customer domains and target ownership that lets at least 70% ship within one team instead of the current 30%.
Four EMs would produce charters listing APIs, data, SLOs, and decision rights; unresolved boundaries go to a weekly design forum for the first 12 weeks.
The topology is accepted when cross-team handoffs fall below 35%, no team exceeds 12 engineers, and domain SLO ownership is complete for 100% of services.

Why interviewers ask this: The question tests whether org design follows value flow and produces explicit, measurable ownership rather than merely renaming teams.

capacity-planningauthobservability

I would charter the platform team around the three repeated capabilities with measured internal-customer outcomes, not as an unlimited ticket queue.

A six-week demand audit would confirm at least 10 engineer-equivalents of duplication; the platform EM would publish supported products, interfaces, and excluded responsibilities.
The first-year roadmap would target self-service CI under 15 minutes, standard authentication for 90% of services, and observability onboarding under one day.
The team keeps a capability only when at least 4 product teams adopt it and aggregate duplicated effort falls from 28% to below 12% within two quarters.

Why interviewers ask this: A strong answer defines a platform as a product with validated demand, boundaries, adoption targets, and a test for whether centralization pays off.

I would create three additional EM roles and rebalance the future 64 engineers into seven teams before all 8 hires land.

Seven EMs can each support 8 to 10 engineers, so I would split the 19-person group first and sequence two more qualified internal moves or external hires against headcount arrival.
The seven EMs would submit team charters and reporting maps within 30 days, including tech lead responsibilities so management and technical ownership do not overlap ambiguously.
I would consider the change complete after 90 days when every engineer has a stable manager, no EM exceeds 10 reports, and monthly 1:1 completion stays above 90%.

Why interviewers ask this: The interviewer is checking whether the manager uses spans, growth, and role clarity to design a workable reporting structure.

roadmaproadmapping

I would make each product domain executable within one regional cluster and use asynchronous decision records for cross-region interfaces.

I would map dependencies and relocate ownership so at least 80% of daily delivery decisions need no meeting outside a region's 6-hour collaboration window.
Each EM would maintain a domain log with a 48-hour review deadline; one rotating regional representative attends the 2-hour overlap for genuinely shared decisions.
The structure succeeds when median decision time falls from 9 days to under 3 for eight weeks and cross-time-zone meetings drop below 2 per engineer per week.

Why interviewers ask this: This tests practical geographic design that reduces synchronous dependency while preserving a measurable cross-region decision mechanism.

sloownership

I would delegate bounded production authority to each region and make approval risk-based rather than location-based.

The service EMs would define change classes, with low-risk changes locally approved and only schema or security changes requiring two-region review within 24 hours.
Each region must have 2 trained release approvers and pass 10 supervised changes; the ownership matrix and audit trail become the control artifact.
UTC-8 stops routine approval when all regions sustain under 10% change failure rate and the 99.95% SLO for 60 days.

Why interviewers ask this: The interviewer is evaluating whether distributed authority is introduced through explicit controls, readiness evidence, and reliability gates.

code-review

I would give one team end-to-end ownership of the order core and expose versioned contracts for the other two teams.

I would analyze 90 days of changes and incidents to separate core order invariants from pricing and fulfillment extensions, then record the boundary in a service charter.
The owning EM gets 8 engineers and a 2-business-day review SLO; consumer teams receive delegated ownership only for isolated modules with contract tests.
The model exits transition when 90% of reviews finish within 2 days, unauthorized cross-boundary changes are zero for 8 weeks, and consumer lead time does not rise over 10%.

Why interviewers ask this: A strong response resolves shared ownership with evidence, contracts, one accountable team, and safeguards against creating a new bottleneck.

roadmaproadmapping

I would use a central security enablement team with named product liaisons rather than permanently embedding all 6 specialists.

The security manager would reserve 4 engineers for common controls and 2 for rotating 8-week product engagements, based on a backlog showing at least 2 teams need each shared control.
Each product EM owns remediation in their domain, while the security team owns standards, threat models, and reusable tooling with published response times.
I would keep the model if duplicated effort falls from 35% to below 15% and 90% of high-risk reviews complete within 5 business days for two quarters.

Why interviewers ask this: The question checks whether scarce specialists are organized to create leverage without removing security accountability from product teams.

I would create the two teams only as leadership and hiring capacity become ready, not split all domains on day one.

The workforce plan would open one external EM role now, develop one internal lead over 90 days, and cap interim teams at 10 engineers.
I would split the highest-handoff domain first after its charter, tech lead, and 6-person core are in place; the second split waits at least 8 weeks for evidence.
Expansion completes when 5 EM or acting-manager seats are filled, every team has a documented boundary, and no new hire lacks an assigned manager for more than 5 days.

Why interviewers ask this: The interviewer wants a growth sequence constrained by leadership supply, team viability, and clear readiness gates.

I would group the five teams into three product domains and give each PM one domain outcome rather than spread every PM across every team.

Two related team pairs would share a PM and a quarterly outcome, while the fifth team owns a platform charter with its EM as internal product lead.
Each domain writes decision rights for PM, EM, and tech lead, including a 48-hour escalation path and one prioritized backlog artifact.
I would revisit the model if decision lead time exceeds 4 days, unplanned work rises above 20%, or either paired domain misses two monthly outcome checkpoints.

Why interviewers ask this: This tests whether the manager adapts topology and decision rights to a real product-leadership constraint instead of accepting fragmented attention.

I would complete a service ownership reset before planning and refuse roadmap commitments for ownerless critical services.

The 4 EMs would classify all 60 services by business criticality, SLO, primary owner, consumer, and lifecycle status in one catalog within 3 weeks.
Duplicate claims are resolved by write authority and operational accountability; ownerless tier-1 services receive capacity before new work, with me accountable for final boundaries.
Planning opens when 100% of tier-1 and 95% of all services have one owner, an escalation route, and a reviewed SLO, with zero duplicate primary owners.

Why interviewers ask this: The interviewer is assessing whether ownership ambiguity is closed through a time-bound artifact, decision rule, and planning gate.

Locked questions

21
Two first-time EMs now lead 8 engineers each inside your 38-person group, and quarterly planning begins in 10 weeks. How do you develop them without taking back their decisions?
quarterly-planning
22
One of your 4 EMs will take a planned 4-month leave in 6 months, and their 12-person team owns 40% of a $5M launch. How do you prepare succession?
succession-planninglaunches
23
Four EMs rate 41 engineers, but one team gives 45% top ratings while the other three average 12%; compensation review is in 5 weeks. How do you calibrate?
compensation
24
Six of 44 engineers are proposed for senior promotion across 4 teams, but the budget supports only 3 this cycle and packets are due in 30 days. How do you make the decision?
promotion
25
Your 50-engineer organization needs 2 additional EMs within 12 months, but only 1 of 7 senior engineers has expressed management interest. How do you build the bench?
26
You approve 70% of cross-team decisions for 4 EMs and 43 engineers, causing a median 6-day wait; you need that below 2 days this quarter. What do you delegate?
cross-teamdelegation
27
Four EMs in a 46-engineer group spend 11 hours each week in overlapping status meetings, while 22% of quarterly dependencies are discovered after work starts. How do you redesign the management cadence?
dependencies
28
Two of your 3 EMs came from nontechnical roles and lead 30 engineers across a platform with a 99.95% SLO; architecture reviews start in 8 weeks. How do you build sufficient technical judgment?
slo
29
You may move to a new domain in 9 months, but none of your 4 EMs can yet run the full 52-engineer portfolio for more than 2 weeks. How do you prepare a successor?
portfolioportfolio-management
30
One of 5 teams has 7 of the group's 10 senior engineers while two teams with a $7M roadmap have only 1 each; you have 45 days before planning. How do you rebalance the leadership bench?
roadmaproadmapping
31
Your 4 teams have 40 engineers and request 16 hires next year, but Finance caps growth at 10 positions and expects $8M incremental ARR. How do you build the headcount plan?
headcount-planning
32
You must hire 12 engineers in 6 months, but the current funnel produces 1 accepted offer per 40 applicants and interviewers can conduct only 24 loops monthly. What capacity do you plan?
capacity-planningcapacityfunnel
33
A 50-engineer group has a $13M annual budget, and Finance asks for a 7% cost reduction without reducing the 4 committed product outcomes. Where do you look first?
34
A 9-month compliance program needs 6 engineers; contractors cost $210 per hour and full-time hires cost $220,000 loaded annually but take 5 months to start. What staffing mix do you choose?
program-management
35
Five teams spend an estimated 14 engineer-years building an internal developer portal; a vendor costs $900,000 annually plus $350,000 implementation over 3 years. How do you make the build-versus-buy call?
procurementestimation
36
Your observability vendor will rise from $600,000 to $1.1M annually for 55 services, while an open-source alternative needs 5 engineers for 8 months and $180,000 yearly hosting. What do you do?
procurementobservability
37
Eight engineering vendors cost $2.4M annually across 4 teams, and 3 contracts renew in 90 days without named owners or usage thresholds. How do you establish governance?
procurementgovernance
38
You can place 8 new roles in New York at $260,000 loaded each or Warsaw at $145,000, but the owning teams need 4 shared hours and current managers are all in New York. What do you recommend?
39
A proposed 10-person integration team costs $2.2M annually and is forecast to unlock $5M ARR, but only 6 customers worth $1.4M have signed letters of intent. How do you treat the P&L case?
40
Your 3-year plan grows engineering from 38 to 58 people, salaries are forecast to rise 6% annually, and Finance limits the year-three run rate to $15M. How do you test feasibility?
41
Four teams and 48 engineers produce 25 architecture proposals per quarter, but review takes a median 18 days and 30% are reopened after implementation starts. How do you redesign RFC governance?
governancearchitecturedecision-making
42
Across 5 teams and 70 repositories, only 38% meet the company's security and testing baseline, and you have 2 quarters to reach 90% without a central rewrite team. What do you do?
testing
43
Thirty-six product engineers deploy to Kubernetes, but platform review is required for every service change and adds 4 days to a 9-day lead time. How do you replace review with guardrails?
kubernetesdeploymentguardrails
44
Your 5 teams report deployment frequency from daily to monthly, but definitions differ and the CEO wants a portfolio DORA view in 60 days. What do you publish?
portfolioportfolio-managementdeployment
45
Sixty services across 4 teams have 22 different availability targets from 99% to 99.99%, and only 15 use error budgets; you need portfolio SLO governance in 2 quarters. What do you do?
portfolioportfolio-managementreliability
46
A 50-engineer organization must support 3 times transaction volume in 30 months, reduce infrastructure cost per transaction by 25%, and keep 99.95% availability. How do you build the technical roadmap?
roadmaptransactionsroadmapping
47
Two years after mandating event sourcing for all transactional services, 31 of 44 services use it, change lead time is 35% worse, and 6 of the last 9 incidents involved replay complexity. How do you withdraw the broadly adopted standard?
incidentsdecision-makingtransactions
48
Five teams maintain 17 internal API versions, costing an estimated 11 engineer-months per quarter, and you need to halve that within 12 months. What company-wide lifecycle standard do you set?
estimationapi
49
Across 4 teams, CI costs $720,000 annually, p95 build time is 42 minutes, and each team uses a different release process; Finance wants 20% savings in 9 months. What standard do you introduce?
releasesconcurrency
50
Your 4 teams own 9 databases and 3 event systems; data duplication adds $480,000 annual cost, and a new analytics product must launch in 24 months with data freshness under 5 minutes. What roadmap do you set?
roadmapsystem-designconsistency
51
Five teams with 48 engineers are 10 weeks into a 24-week billing program, only 35% of committed scope is complete versus 55% planned, and $6 million in renewals depends on launch. What do you do in the next 72 hours?
program-managementscope-managementlaunches
52
A four-team product launch is on schedule for six weeks from now, but a production pilot shows $100 monthly revenue and $140 variable cloud and support cost per customer; 3,000 contracted customers are in the rollout. What do you do?
launchesreleases
53
Your portfolio has five teams, 52 engineers, and capacity for 420 engineer-weeks next quarter, but approved initiatives require 570. One protects $8 million ARR, one saves $1.2 million annually, and three growth bets have no signed customers. How do you reprioritize?
portfolioportfolio-managementcapacity-planning
54
Three of your five teams are blocked by an identity platform owned by another director; its API is 5 weeks late, 26 engineers are losing 40% capacity, and a $4 million customer launch is 7 weeks away. What do you do this week?
launchescapacity-planningapi
55
A top-10 customer paying $2.8 million ARR escalates after four teams miss the same integration date twice; they threaten nonrenewal in 30 days and demand daily access to engineers. How do you respond?
escalation
56
A four-team compliance program with 36 engineers is 8 weeks from a legal deadline, but the audit finds only 62% of 140 controls implemented and the current plan predicts 78%. Fines can reach $5 million. What do you change now?
program-managementestimation
57
Five teams commit to a common launch in 12 weeks, but two EMs report green while dependency data shows 18 of 31 handoffs have no acceptance date and milestone reliability is 64%. What do you do before the executive review?
milestonesdependenciesplanning
58
A 44-engineer, four-team program has spent $3.2 million of a $4 million budget, is 45% complete, and has 4 months left on a 9-month plan. The sponsor asks you to keep the original scope and date. What is your recommendation?
program-managementscope-managementsponsor
59
A shared data migration across five teams is 6 weeks from launch; reconciliation errors are 3.8% against a 0.1% limit, two teams propose separate fixes, and $12 million ARR depends on accurate invoices. What do you decide?
launchesmigrationsreact
60
After 7 months, a five-team developer platform program has 22% adoption versus a 60% target, costs $450,000 per month, and would need another $2 million to finish. Product teams report no delivery improvement. Do you continue it?
program-managementdecision-making
61
One of four EMs, leading 11 of your 46 engineers, has missed 7 of 10 quarterly commitments, regrettable attrition is 27%, and two senior engineers report six months without useful feedback. What do you do?
feedbackattrition
62
Two EMs running 24 of your 50 engineers have argued for 8 weeks over ownership of a shared service; 14 incidents were bounced between teams and MTTR rose from 45 to 110 minutes. How do you resolve it?
incidentsownershipincident-management
63
Skip-level interviews across three of your five teams show 9 of 21 engineers cannot name their top priority, while all three EMs report healthy alignment and 90% confidence. How do you use the evidence?
alignment
64
Your strongest EM gives 6 weeks notice, owns two of five teams and 19 of 47 engineers, and no successor meets more than 60% of the role rubric. A critical launch is 10 weeks away. What do you do?
launchesperformance-rubric
65
An externally hired EM for one of four teams resigns after 90 days; engagement fell 14 points, three senior engineers are interviewing elsewhere, and the search cost $85,000. What do you do next?
engagementhiring
66
A principal engineer spanning four teams starts assigning work directly to 17 engineers and overturning EM priorities; architecture decisions are faster, but milestone reliability falls from 88% to 69%. How do you reset the boundary?
milestonesplanningreliability
67
An EM leading 13 of your 55 engineers marks a program green for three months, but an audit shows forecast data was manually altered and the true date is 9 weeks late. $1.5 million ARR is exposed. What do you do?
program-management
68
You inherit five EMs and 58 engineers; one EM has 41% regrettable attrition over 12 months, but their team delivered 96% of roadmap commitments and the VP calls them a top performer. How do you assess them?
roadmapownershiproadmapping
69
Two of your four EMs are covering vacant roles, each managing 20 engineers, and both report 60-hour weeks for 10 consecutive weeks. Hiring will take 4 months and one critical program is due in 9 weeks. What do you change?
program-managementhiring
70
A staff engineer and an EM dispute who should lead a 35-engineer, three-team migration; the staff engineer owns technical direction, the EM owns the date, and the conflict has delayed decisions by 3 weeks. Who leads?
conflict-managementmigrations
71
The CFO orders a 20% engineering budget reduction within 30 days across your five teams and 60 engineers; payroll is 82% of cost, contractor spend is $1.1 million, and the roadmap contains $9 million ARR commitments. What do you propose?
roadmaproadmapping
72
You must remove 9 of 45 roles across four teams by quarter end, while one team supports 70% of revenue and another has 8% product adoption. How do you allocate the reduction?
decision-making
73
Five EMs in a matrix organization have functional directors and three product GMs assigning work; 54 engineers receive conflicting priorities, 32% of work is reprioritized mid-cycle, and two launches lacked one accountable owner. How do you fix dual accountability?
launchesconflict-management
74
Three months after a reorg of four teams and 40 engineers, cross-team tickets rose 65%, p75 lead time increased from 12 to 19 days, and engagement fell 9 points. The COO wants more time. What do you do?
engagementcross-teamreorganization
75
Finance asks you to close one of two engineering sites within 6 months to save $2.4 million annually; the smaller site has 18 of 52 engineers, owns two critical services, and 7 people are flight risks. What do you recommend?
76
After a reorg announcement, 11 of 48 engineers across four teams are rated high retention risk, including all three database experts; replacing them would take 9 months and put $7 million ARR at risk. What do you do in 2 weeks?
retentiondatabaserisk-management
77
The CPO wants 35 of your 50 engineers on a feature expected to add $4 million ARR, while the CTO wants 20 on reliability after error budgets reached 180% burn for two quarters. The allocations cannot coexist. What do you recommend?
reliability
78
The board meets in 48 hours after four teams slip a platform migration by 2 quarters; $6 million of cost savings and a $10 million customer renewal depend on it, while confidence in the new date is 55%. How do you communicate the risk?
risk-managementmigrationscommunication
79
Your five teams spend $2.7 million annually on 22 contractors, and Finance requires $1.5 million savings in 60 days; 8 contractors hold production access for revenue services and 6 are on a launch due in 10 weeks. What do you cut?
launches
80
You must consolidate two sites into one and reduce headcount 15% across 56 engineers, but local consultation requires 45 days and a customer migration is due in 70 days. The CEO wants announcement and names next week. What do you do?
headcount-planningmigrations
81
A Sev-1 affects checkout, identity, and billing across four teams and 43 engineers; revenue loss is $180,000 per hour, no single team owns the failure, and 25 people are already in one call. What do you do in the first 15 minutes?
82
A cross-region outage has lasted 70 minutes, three teams are testing conflicting mitigations, customer support has 4,000 tickets, and the CEO asks to join incident command. How do you run the next hour?
risk-managementincident-managementincidents
83
A portfolio disaster-recovery exercise across four teams fails: 7 of 18 tier-1 services exceed a 4-hour recovery target, 5 cannot prove data loss under 15 minutes, and customer contracts contain different commitments. How do you establish RTO, RPO, and testing?
portfolioportfolio-managementtesting
84
Across five teams, only 3 of 11 Sev-1 postmortem actions closed last quarter, 4 incidents repeated known causes, and EMs say delivery deadlines leave no time. How do you fix the culture?
incidentsestimationincident-management
85
Security finds an actively exploited dependency in 27 services owned by five teams; 8 services process payment data, a patch exists, and disclosure is due in 72 hours. Product asks to wait for the weekend. What do you do?
dependenciesconcurrency
86
An audit 12 days before certification finds admin access without MFA in 9 of 34 systems across four teams; certification protects $14 million in contracts, and remediation may delay two launches. How do you respond?
launchessystem-design
87
A platform migration involving five teams reaches 40% traffic, then error rate rises from 0.2% to 4.7% and rollback will discard 6 hours of replicated writes unless reconciled. $300,000 daily revenue is exposed. What do you do?
migrationsreplicationrollback
88
A 3-hour Sev-1 across three teams has affected 18 enterprise customers and breached a 60-minute notification SLA; Sales wants individualized engineering calls while restoration is incomplete. How do you handle communication?
soft-skills
89
Two Sev-1 incidents start 10 minutes apart in services owned by four teams; one blocks 65% of revenue, the other affects internal payroll for 6,000 employees due in 5 hours. You have one experienced incident commander. How do you allocate leadership?
incident-managementincident-commandincidents
90
After three cross-team outages in 8 weeks, the proposed reliability work costs 14 engineer-months and delays a $2 million feature by 6 weeks; the same failure mode has already caused $900,000 loss. What do you decide?
cross-teamprioritizationreliability
91
You have 10 business days to assess a 38-engineer acquisition target; 45% of its $12 million ARR runs on an undocumented platform, security reports are 18 months old, and three key leaders have no retention terms. What do you recommend?
retention
92
Thirty days after an acquisition, you oversee five teams and 57 engineers; duplicate products cost $3 million annually, the acquired team’s attrition risk is 35%, and customers require 12 months of support. What do you do first?
attritionrisk-management
93
Four teams have spent 9 months and $2.6 million building an internal workflow engine; it is 5 months late, while a vendor now covers 85% of needs for $480,000 annually and can migrate in 4 months. Do you reverse the build decision?
procurement
94
Eighteen months after choosing a vendor over building, annual cost has risen from $700,000 to $2.1 million, p95 latency breaches the 300 ms contract by 40%, and exit migration needs 30 engineer-months across three teams. What do you do?
procurementmigrationslatency
95
Your 50 engineers work across four teams in California, Poland, and Singapore; decision lead time doubled to 6 days, 38% of one region says meetings exclude them, and defect handoffs rose 45%. How do you correct culture drift?
defectsiac
96
Across five teams, pass rates for the same senior-engineer interview range from 18% to 62%, offer acceptance is 54%, and first-year regrettable attrition reached 22%. You need 15 hires in two quarters. What do you change?
attrition
97
After bonuses were tied to deployment frequency, four teams increased deployments 80%, but change-failure rate rose from 9% to 21% and teams split commits to inflate counts. What do you do before bonus review?
deployment
98
The CRO asks you to hide a known 2% billing overcharge affecting 14,000 customers until after quarter close because correcting it now reduces recognized revenue by $1.8 million. Four teams can fix it in 10 days. What do you do?
99
A manager reports that an executive asked one of five teams to use customer location data for an unapproved sales model; 8 million records are involved, consent coverage is unknown, and a demo is in 6 days. What do you do?
coverage
100
You lead five teams and 60 engineers during a quarter-end crisis: a Sev-1 risks $500,000 per day, a security patch is due in 48 hours, the CFO demands a 15% cost cut, and the only qualified EM has disclosed a family emergency. What do you decide in the next hour?

Questions

1You lead 4 teams with 46 engineers at a $60M ARR SaaS company that must add $12M ARR next year while keeping gross margin above 78%. How do you set the engineering portfolio?

2A B2B product with $35M ARR loses 9% of enterprise renewals because exports take 18 hours, and your 38 engineers have two quarters to reduce that to 2 hours. What do you prioritize?

3Your company expects a European launch to produce $6M ARR in 18 months, but data residency requires work from 3 of your 5 teams and an estimated 28 engineer-months. How do you decide whether it enters the roadmap?

4Four teams totaling 44 engineers currently spend 82% on features, while change failure rate is 19% and the annual target requires 25% faster delivery. How do you change capacity allocation for the next two quarters?

5You have 40 engineers and $3M of discretionary budget for three product bets forecast at $8M, $5M, and $3M ARR, but you can staff only two for the next 9 months. How do you choose?

6A checkout domain generating $20M annually needs 14 engineer-months of debt work to keep feature lead time from rising 30% next year. Your 42-engineer group has one quarter to make the case. What do you do?

7A $4M ARR launch depends on identity, billing, and analytics teams, but their plans expose a 7-week critical-path gap inside a 6-month window. How do you govern the program across 36 engineers?

8A legacy product earns $1.8M ARR but consumes 9 of 48 engineers and $700,000 in annual infrastructure, while customers can migrate within 12 months. What portfolio decision do you make?

9Product wants 18 of your 50 engineers on an AI assistant expected to lift conversion by 4% within 6 months, but the estimate has no production accuracy or inference-cost data. How do you structure the bet?

10Halfway through the year, a 45-engineer portfolio is 15% below its $10M expansion target, while a platform program is on track to save $900,000 annually in 5 months. How do you rebalance the next two quarters?

11You inherit 48 engineers in 4 component teams, and 70% of roadmap items require handoffs across at least 3 teams. How would you redesign ownership over 6 months?

12Five product teams with 52 engineers spend 28% of capacity rebuilding CI, authentication, and observability capabilities. You can form one 8-person platform team. What belongs in its charter?

13You directly manage 4 EMs covering 56 engineers; one EM has 19 reports and another has 7, while the company will add 8 engineers this year. How do you reset spans?

14Your 42 engineers sit in California, London, and Warsaw with only 2 shared working hours, and roadmap decisions currently take a median of 9 days. How do you structure the organization?

15A 24-hour B2B service has 45 engineers across UTC-8, UTC+0, and UTC+8, but every change still requires approval from the UTC-8 team. How do you change ownership without lowering the 99.95% SLO?

16Three teams totaling 34 engineers all modify a shared order service, and 40% of pull requests wait more than 3 days for an owner review. How do you draw the boundary?

17Four product teams share 6 security engineers, and embedded assignments leave 35% of security work duplicated over a 12-month roadmap. What topology do you choose?

18A group will grow from 36 to 50 engineers and from 3 to 5 teams in 9 months, but only 2 current leads are management-ready. How do you sequence the topology change?

19Your 5 engineering teams and 47 engineers share only 3 product managers for the next 2 quarters. How do you pair leadership and preserve decision speed?

20Across 5 teams and 60 services, 18 services have two claimed owners and 11 have none; the next planning cycle starts in 6 weeks. What do you do?

Locked questions