17 · BUDGET PRESSURE
The best design you can afford — not the best design you can imagine.
Fixed budget, sprint timeline, or headcount limit. Design explicitly within them, justify every trade-off, compare your allocation to the benchmark.
Approaching limit — 8 pts remaining
Trade-off justification required for each cut →
Three real-world constraint types.
Story points
Engineering Budget
Each component costs story points. Stay under the limit.
Trade-off forced
Speed vs. completeness — which features survive the cut?
Working days
Sprint Timeline
Each decision costs implementation days. Ship by the deadline.
Trade-off forced
Quality vs. velocity — where do you take shortcuts?
Available engineers
Headcount Limit
Some components need multiple engineers to build safely in parallel.
Trade-off forced
Parallelization vs. sequencing — what can you build alone?
You can't cut without explaining why.
Every removed component triggers a justification prompt. The reasoning is the work.
Rating system can be shipped in Sprint 2 once core trip flow is stable. Risk: drivers may game the system in the first sprint without any accountability mechanism in place. Acceptable short-term given that the core user journey is unblocked…
This reasoning is what senior interviewers are evaluating.
See where the benchmark invested differently.
Side-by-side allocation reveals what experienced engineers prioritise versus what candidates consistently miss.
Your allocation
32 ptsBenchmark allocation
40 ptsThe pattern: experienced engineers protect resilience and observability first. Candidates optimise for feature completeness.
What Budget Pressure includes.
Real constraint types
Story points, sprint days, or headcount — each forcing a distinct class of engineering trade-off.
Explicit trade-off tracking
Every component is costed. Every cut is recorded. The budget bar depletes in real time as you design.
Justification prompts
Cutting a component triggers a structured prompt. You explain what you're sacrificing and why it's acceptable.
No gold-plating
The constraint is enforced — you cannot submit a design that exceeds budget. The skill is choosing well, not just designing well.
Allocation comparison
After submission, see how the benchmark allocated the same budget — and where your priorities diverged.
Senior interview format
Problems are calibrated to the constraint reasoning expected at senior, staff, and principal engineering levels.
Who Budget Pressure is for.
Preparing for roles where the interview explicitly evaluates trade-off reasoning and constraint-aware design — not just structural correctness.
Building the skill to think beyond "what's the ideal design" toward "what's the right design given these real constraints."
Practitioners who already navigate sprint planning and resource allocation — and want to practice articulating those decisions in an interview setting.
Engineers who regularly make build-vs-cut decisions in practice but want to sharpen the precision and clarity with which they communicate the reasoning.
FAQ
Questions people ask
→ Explore more