How do you balance speed and quality under a deadline?

Question

Accepted Answer

Interviewers want a **deliberate, context-aware tradeoff** — not a dogmatic "always ship fast" or "never compromise." The key is making the tradeoff *consciously and visibly*.

## How to approach it

```text
1. Identify what quality is non-negotiable (correctness, security, data safety)
2. Find what can be deferred (polish, edge cases, refactors)
3. Cut scope, not core quality — ship less, not worse
4. Name any debt out loud and schedule paying it down
```

## Worked example

```text
S: We had three days to launch an MVP for a client pilot.
T: Full feature set wasn't possible without risking stability.
A: I shipped the core happy path solidly, deferred two edge cases behind a flag,
   and wrote a ticket for the debt with a date. I told the client which parts
   were preview-only.
R: The pilot launched on time and stable. We closed the deferred tickets the
   following sprint.
```

## Good vs weak

```text
✓ Conscious tradeoff, debt tracked, scope cut
✗ Shipping broken code silently to hit a date
✗ Refusing to ever bend, missing the deadline
```

## Why it matters

Speed and quality are usually a scope problem in disguise — cutting scope protects both.

Naming debt out loud keeps shortcuts honest, so they get paid back instead of forgotten.

Knowing *which* quality is non-negotiable is judgment that comes with experience — it's what interviewers are probing.