A brilliant engineer is quietly blocking a needed migration because it makes their pet system obsolete. Their objections sound technical but are really territorial. How do you handle it?
- A. Defer to their technical objections since they know the system best
- B. Separate the technical merits from the personal stake, decide on merit, and address the underlying concern directly ✓
- C. Override them unilaterally and reassign the migration to someone else
- D. Drop the migration to avoid a costly conflict with a key person
Correct answer: B. You must disentangle genuine technical concerns from self-interest, decide on the merits, and address the person's real fear, rather than being captured, steamrolling, or capitulating.
You must lay off one person from a strong team of six. How do you approach the decision and aftermath?
- A. Choose the newest hire since 'last in, first out' is simplest
- B. Decide against clear, fair criteria tied to future needs, then communicate honestly and support both leaver and stayers ✓
- C. Ask the team to vote on who should go to share the responsibility
- D. Delay the decision as long as possible hoping the mandate reverses
Correct answer: B. A defensible layoff uses fair, future-oriented criteria with honest, humane communication and attention to survivors, unlike arbitrary tenure rules, offloading, or paralysis.
Your director pushes a strategy you believe will harm the team and product. You've raised concerns and been overruled. Now what?
- A. Publicly distance yourself from the strategy so the team knows your stance
- B. Disagree and commit: represent the decision honestly to the team while continuing to surface data as reality unfolds ✓
- C. Quietly undermine the rollout so the strategy fails and proves your point
- D. Comply fully and stop raising any concerns to avoid friction
Correct answer: B. 'Disagree and commit' lets you honor the decision while staying honest and evidence-driven, whereas public distancing, sabotage, and silent compliance all fail the team or the org.
How do you best demonstrate your impact as an EM to leadership when you don't personally ship code?
- A. Report the raw volume of tickets and story points your team closed
- B. Connect the team's delivery to business outcomes, plus growth, retention, and capability you've built ✓
- C. Highlight how many hours you and the team put in
- D. Emphasize how many incidents were avoided under your watch
Correct answer: B. Real EM impact is shown by tying team output to outcomes and demonstrating durable people and capability gains, not activity volume, hours, or unfalsifiable counterfactuals alone.
A critical project is slipping. Digging in, you find the root cause is your own unclear prioritization earlier. What do you do?
- A. Reframe the narrative around external dependencies to protect credibility
- B. Own the miss to your team and stakeholders, correct the priorities, and adjust the plan transparently ✓
- C. Quietly fix the priorities without acknowledging the earlier mistake
- D. Push the team harder to make up the time the confusion cost
Correct answer: B. Owning your own contribution to the slip and transparently correcting course builds trust and models accountability, unlike deflecting, hiding it, or making the team absorb your error.
You need another team to prioritize work for you, but you have no authority over them and their manager is protective. How do you get it done?
- A. Escalate immediately to both managers' shared boss to force the priority
- B. Build the relationship, frame the ask around their goals and shared impact, and make it easy to say yes ✓
- C. Publicly point out that their team is the bottleneck to create pressure
- D. Route around them by having your team do the work unofficially
Correct answer: B. Influence without authority comes from relationships and aligning the ask to the other team's interests, not immediate escalation, public pressure, or unsanctioned workarounds.
A top performer is clearly interviewing elsewhere. You can't match likely outside offers. What's the wisest approach?
- A. Ignore it and prepare a backfill so you're not caught off guard
- B. Have an honest conversation about what they want, address what you genuinely can, and plan realistically either way ✓
- C. Make a desperate counter-offer beyond what's sustainable to keep them
- D. Freeze them out of key work now since they're probably leaving
Correct answer: B. An honest conversation about their motivations may retain them for the right reasons and, if not, enables a graceful transition, unlike denial, unsustainable counters, or punitive freeze-outs.
Your most senior engineer's technical judgment has become a bottleneck: nothing ships without their sign-off and they resist sharing authority. How do you address it?
- A. Keep the sign-off requirement since their quality bar is valuable
- B. Work with them to codify their standards and distribute review authority, framing it as scaling their impact ✓
- C. Remove their review authority abruptly to break the bottleneck
- D. Route urgent work around them quietly to keep delivery moving
Correct answer: B. Scaling a gatekeeper's impact by codifying standards and distributing authority removes the bottleneck while honoring their expertise, unlike preserving it, blunt removal, or covert routing.
Two of your engineers had a heated conflict; each privately gives you an incompatible account and both are credible. How do you proceed?
- A. Believe the more senior or more tenured engineer's version
- B. Avoid taking sides on facts, focus on behavior going forward and shared expectations, and mediate directly ✓
- C. Poll the rest of the team to determine what really happened
- D. Discipline both equally so neither feels singled out
Correct answer: B. With irreconcilable accounts, focusing on future behavior and mediated expectations is more productive than adjudicating unknowable facts, favoring seniority, crowd-sourcing, or blanket punishment.
Leadership wants a fixed feature set on a fixed date with a fixed team. As EM you know all three can't hold. How do you handle it?
- A. Commit and privately plan to negotiate scope down later once it slips
- B. Make the iron triangle explicit with data, and force an early, honest choice about which constraint gives ✓
- C. Add contractors late to try to hold all three constraints
- D. Accept it and protect the team by hiding the risk from leadership
Correct answer: B. Surfacing the scope-time-resources trade-off early and demanding an honest choice is the mature move, unlike a plan-to-renege, late staffing (Brooks's Law), or concealing risk.
You suspect a well-liked, long-tenured engineer is coasting and their impact no longer justifies their senior level. How do you handle it fairly?
- A. Leave it since they're liked and have paid their dues over the years
- B. Gather specific evidence, have a candid conversation about the level's expectations, and set a clear path or decision ✓
- C. Quietly downgrade their scope and hope they take the hint
- D. Wait for the next reorg to move them out without a direct conversation
Correct answer: B. Fairness requires specific evidence and a candid, direct conversation about level expectations with a clear path, not avoidance, passive signaling, or an ambush via reorg.
A high-visibility incident was partly caused by an engineer's mistake and partly by a systemic gap. Leadership wants a name. How do you respond?
- A. Name the engineer since accountability requires identifying who erred
- B. Present the systemic root causes and fixes, protecting the individual while owning the outcome as the leader ✓
- C. Say it was a collective team failure with no specifics
- D. Point to the process gap alone and deny any human error occurred
Correct answer: B. A leader absorbs accountability and steers toward systemic fixes rather than sacrificing an individual, offering a vague non-answer, or dishonestly denying the human factor.
You're building a team and can hire either a brilliant but abrasive senior engineer or a strong, collaborative one who's slightly less technically deep. What usually serves the team best?
- A. The brilliant abrasive one, since raw technical horsepower is rarest
- B. The collaborative strong one, because sustained team output depends on how people work together ✓
- C. Whichever one accepts the lower salary to protect the budget
- D. Hire both and let their dynamic sort itself out naturally
Correct answer: B. On a team, a strong collaborator typically raises everyone's output more than a brilliant but corrosive individual, and budget or hoping a bad dynamic self-resolves are poor bases for the call.
Your team wants to rewrite a fragile legacy system; the business sees no visible benefit and won't fund a pure rewrite. How do you reconcile this?
- A. Push hard for the full rewrite since the team knows the pain best
- B. Find an incremental approach that ties technical improvement to business-visible value delivered along the way ✓
- C. Tell the team the business said no and drop the topic entirely
- D. Do the rewrite quietly under the cover of feature work
Correct answer: B. Tying incremental modernization to business value bridges both concerns, unlike demanding a risky big-bang rewrite, dismissing the team, or hiding major work from stakeholders.
You're promoted to manage managers. One of your new EMs runs their team very differently from how you would. Their results are fine. What do you do?
- A. Have them adopt your management approach for consistency
- B. Focus on their outcomes and team health, coaching on principles while allowing their own style ✓
- C. Take over their most important decisions to ensure quality
- D. Compare their team's metrics publicly against the others to drive change
Correct answer: B. Managing managers means holding them to outcomes and principles while permitting different styles, not imposing your methods, seizing their decisions, or motivating through public comparison.
A key project depends on a vendor that's slipping, and your team is blocked and idle. Leadership blames your team's velocity. How do you respond?
- A. Push the team to look busy on other work so metrics stay up
- B. Make the real dependency and its impact visible with data, and drive the vendor issue while redeploying the team usefully ✓
- C. Accept the blame to stay politically safe with leadership
- D. Tell the team leadership is being unfair and to ignore the pressure
Correct answer: B. Surfacing the true root cause with data, managing the dependency, and usefully redeploying the team addresses reality, unlike busywork theater, absorbing false blame, or venting to the team.
You want to raise the team's engineering standards, but heavy-handed process could kill the autonomy and morale you've built. What's the best approach?
- A. Mandate a comprehensive set of new standards and enforce them strictly
- B. Co-create a lightweight set of shared standards with the team and iterate based on what actually helps ✓
- C. Lead entirely by personal example and add no explicit standards
- D. Tie compliance with new standards directly to performance ratings
Correct answer: B. Co-creating lightweight, evolving standards raises the bar while preserving ownership, whereas heavy mandates, pure implicit example, or rating-based enforcement each undercut autonomy or clarity.
An engineer challenges a strategic technical direction you set, in front of the whole team, with a partly valid argument. How do you respond in the moment?
- A. Shut it down to maintain authority and revisit it privately later
- B. Engage the valid points openly, acknowledge what's right, and either adjust or explain your reasoning transparently ✓
- C. Defer the whole thing to a vote by the team right then
- D. Thank them vaguely and move on without engaging the substance
Correct answer: B. Engaging a valid challenge openly models intellectual honesty and strengthens the decision, unlike defending authority, abdicating to a vote, or dodging the substance.
You have budget to either hire one more engineer or invest in tooling that would make your existing team meaningfully more productive. How do you decide?
- A. Always hire, since more people means more capacity
- B. Assess where the real constraint is: if the team is blocked by toil, tooling may yield more than an added head ✓
- C. Always invest in tooling, since it scales without management overhead
- D. Ask the team to vote and go with the majority preference
Correct answer: B. The right call depends on where the actual bottleneck lies, so diagnose the constraint rather than defaulting to headcount, tooling, or a popularity vote.
Your organization is pressuring all teams to ship faster, but your team is already showing early signs of burnout. How do you navigate this?
- A. Absorb the pressure and push the team to sprint harder for now
- B. Push back upward with data on sustainable pace and its long-term cost, while protecting the team's health ✓
- C. Hide the burnout signs and quietly let a few people slip on delivery
- D. Tell the team to slow down and let delivery numbers fall without explanation
Correct answer: B. Protecting sustainable pace while making the long-term cost visible upward serves both delivery and people, unlike burning the team out, concealing the problem, or unilaterally missing commitments without communication.