Delivering Under Pressure and Making Trade-offs

Calm prioritisation, early communication

Questions about tight deadlines, competing priorities or 'more work than time' test prioritisation and communication. Strong answers show you understood what truly mattered to users or the business, made explicit trade-offs (scope cut, phased release, temporary manual step, accepted technical debt with a plan to repay it), told stakeholders early what would or would not be ready, and protected quality where it mattered (security, data integrity). Avoid presenting heroics such as weeks of all-nighters as the main lesson; sustainable delivery and good judgement are stronger signals.

A trade-off table you can describe aloud

A fictional launch with a fixed date.

Item                       Must for launch?  Decision
-------------------------  ----------------  ----------------------------
Checkout with saved cards  yes               build fully
Gift card support          no                phase 2 (2 weeks later)
Admin reporting screen     no                CSV export as stop-gap
Load test at 2x traffic    yes               keep; non-negotiable
UI polish on settings      no                ticketed as follow-up

Communicated to product + support on day 3, not day 13.

Say what you would protect

Interviewers often ask 'What did you not compromise on?'. Have an answer, such as correctness of payments or data privacy.

Quick check: Which behaviour best shows good delivery under pressure?

• Making explicit scope trade-offs and telling stakeholders early
• Working all night and telling nobody about the risk
• Skipping security review to save time
• Promising everything and hoping it fits