Tell me about a time you had to negotiate for resources that were not under your direct control.

Question

Anonymous · Accepted Answer

I recently led a nine-month migration from a legacy CMS to a headless CMS. While
the technical migration was important, the real success metric was ensuring that
editors who had been for nearly 15 years could continue publishing content with
minimal disruption.

Early in discovery, I realized every stakeholder wanted something different.
Marketing wanted a redesigned homepage, engineering wanted to simplify legacy
workflows, and editorial teams wanted every existing shortcut preserved.
Delivering everything would have pushed our timeline significantly.

To align everyone, I used the MoSCoW prioritization framework and defined an MVP
focused on business continuity. The Must Have scope included the core editorial
workflows, publishing capabilities, and content management functions. Should
Have items included homepage redesign, navigation improvements, SEO
enhancements, and GTM optimizations. Could Have items such as AI-powered search,
minor UX refinements, and retiring low-usage legacy pages were intentionally
deferred.

One important trade-off was around workflow automation. Many legacy business
rules weren't fully documented, so instead of rebuilding complex automation
based on assumptions, we launched with validated manual workflows first. We
planned to prioritize automation in subsequent releases based on real editor
feedback and usage data.

These compromises allowed us to protect the delivery timeline while minimizing
change for editorial users. We successfully launched the migration on schedule,
ensured business-critical publishing workflows remained intact, and created a
data-driven roadmap for future enhancements instead of investing months building
features that users might not need.

Anonymous · Answer

I owned the product strategy for our shared Enterprise AI Platform, where my
goal was to build a centralized capability-registration model allowing our
80,000-person organization to securely onboard and build autonomous AI agents
without spinning up redundant data pipelines. However, I faced a major resource
constraint: my immediate team had zero dedicated front-stack software engineers,
and to build the user-facing developer intake portal and automated registration
contracts, I needed three senior engineers from our Core Developer Experience
tools division—a completely separate engineering org with its own heavily locked
roadmap. The engineering director of that division flatly denied my initial
request due to competing priorities, so instead of making an emotional plea, I
gathered hard internal operational data to build a highly objective business
case. I audited our internal repository logs and proved to him that individual
lines of business had already wasted thousands of developer hours building 24
distinct, un-reusable custom AI integrations that were actively breaking company
standards and driving up his own infrastructure teams' support ticket workloads.
I proposed a low-risk talent exchange where his three engineers remained
embedded in his team but allocated 50% of their velocity to a single, focused
6-week sprint, while my team handled 100% of the cross-functional specifications
and user testing to shield his organization from product overhead. Seeing that a
unified portal would directly eliminate his team's long-term maintenance burden,
the director released the resources, and our joint squad delivered the intake
model precisely on time. This single negotiation permanently replaced shadow
infrastructure with a centralized platform scaling to 4 core shared
capabilities, completely eliminating redundant integration work and returning
over 1.3 million engineering hours back to the bank

Tell me about a time you had to negotiate for resources that were not under your direct control.

Practice this question with AI

Go Premium

Community Answers

Unlock Full Access

Unlock Full Access

Practice More Questions