The Competing Roadmaps

“Two product teams both want 6 weeks of your Android platform team's time. You have 6 weeks. Both PMs have escalated to their VPs.”

The Situation

You're the Staff Android engineer leading a small platform team (2 engineers + you). Two product teams each need 6 weeks of platform work this quarter: Team A needs a new deep-link routing framework; Team B needs a redesigned notification permission flow. Both are on their Q3 OKRs. Both PMs have gone to their respective VPs to advocate for priority. Your manager has asked you to resolve this without escalating further.

Context

Team A's deep-link framework is technically a prerequisite for three other teams' Q4 work
Team B's notification flow affects a legal compliance requirement with a Q3 soft deadline
You could deliver Team B's notification flow in 3 weeks instead of 6 by descoping the analytics instrumentation
One of your two engineers is significantly more senior and could lead one project independently
Both PMs believe their project is the higher business priority

The Question

“Tell me about a time you had to make a resource allocation decision that you couldn't satisfy in full for all stakeholders. How did you navigate the competing interests?”

Response Options

One of these is the strongest response. The others reflect common approaches with real trade-offs.

I asked my manager to make the priority call since both VPs had already been brought in and it was above my pay grade.

I convened a single joint meeting with both PMs, presented the full constraint picture including the legal soft deadline and Team A's Q4 dependency chain, proposed delivering Team B's core notification flow in 3 weeks (descoped) and starting Team A immediately, and asked the PMs to align on this plan together rather than in separate conversations.

I allocated 3 weeks to each project and told both teams to scope their work accordingly.

I prioritized Team A's deep-link framework because it unblocks Q4 for three teams and has broader organizational impact, and told Team B to shift their notification work to Q4.

The Debrief

Why the Best Response Works

Answer B works because it changes the negotiation structure. When Team A and Team B's PMs are negotiating separately, each optimizes for their own OKR. When they're in the same room with the full constraint picture — including the legal deadline and the Q4 dependency chain — the business logic often aligns them naturally. The descope option for Team B is the unlock: it delivers the legally-required core without consuming the full 6 weeks, freeing capacity for Team A.

What to Avoid

The equal-split feels like the conflict-avoidant but 'fair' answer. But equal-split ignores that the two projects have very different organizational impact — a legal compliance requirement and a Q4 enablement dependency are not equivalent. Fairness in resource allocation is impact-optimized, not time-equal.

What the Interviewer Is Probing

The interviewer is evaluating whether you can create alignment conditions rather than just making decisions. Staff engineers at large companies spend significant time in the 'convene, inform, propose, align' loop — not just the 'decide and execute' loop. The joint meeting with shared information is the instrument of that.

SOAR Structure

**Situation:** Two teams need 6 weeks of platform capacity; only 6 weeks available; both VPs involved; manager asked me to resolve without escalating. **Obstacle:** Both PMs had incomplete picture of each other's constraints; legal deadline and Q4 dependency chain not surfaced. **Action:** Convened joint meeting; presented full constraint map; proposed descoped 3-week delivery for Team B plus immediate start of Team A; both PMs aligned in the meeting. **Result:** Both projects delivered this quarter; legal requirement met; Team A framework unblocked Q4 roadmap.

The Learning Arc

"This taught me that most resource conflicts are information conflicts. Each PM was optimizing for what they knew — their own OKR. Once I put them in the same room with the same data, they optimized for the business together. I now share the full platform constraint picture proactively at the start of every quarter rather than reactively when conflicts surface."

IC Level Calibration

senior

Gather the constraints from both teams, make a recommendation with a rationale document, and present it to your manager for final approval.

staff · Primary Target

Convene the joint stakeholder meeting, surface the full constraint picture, propose a specific plan that optimizes for organizational impact (legal deadline + Q4 dependency), and reach alignment without escalation.

principal

Same as staff, plus: identify why the two teams were negotiating separately (lack of cross-team visibility into platform capacity) and propose a platform capacity planning process for future quarters — a quarterly roadmap sync with consumer teams before OKR finalization.

Company Calibration

Google

Googleyness: collaborative decision-making over unilateral authority