Delivering a Project Without Enough People, Budget or Time

The interviewer asks for a real example from your work: a project that was missing something it needed, such as engineering capacity, budget, time or tooling, and how you got it delivered anyway. Walk through the constraint, the choices you made and the outcome. ```hint Show the decision The strongest stories make the constraint concrete and center on a choice: what you cut, sequenced, reused or negotiated for. Pick a story where you can name that choice and what it cost. ``` ### Clarifying Questions - Which kinds of resource count here: engineering headcount, budget, time, data or tooling? - Does "delivered" have to mean the original scope shipped, or does a smaller scope that met the core goal count? - Can the example be an internal tool or side initiative that had no formal funding, rather than a planned roadmap project? ### What a Strong Answer Covers - A precise statement of the gap: what was needed, what was available, and why the project was still worth doing. - The prioritization behind the plan: what was cut, deferred, simplified or reused, and how the minimum valuable scope was chosen. - How extra capacity or support was won without formal authority, for example by aligning the work with another team's goals. - How expectations were reset with stakeholders and risks raised early. - A measurable result, an honest account of what was given up, and a lesson applied since. ### Follow-up Questions - What did you decide not to build, and who disagreed with that call? - If people from other teams helped you, how did you make sure it did not hurt their own commitments? - Looking back, should the project have been paused instead? What signal would have told you?