Practice

A key feature is late and the launch date is fixed. What do you do?

Read first: a sample answer

Fictional sample answer written by JoRoute to show the shape of a strong answer. Do not copy it: replace every detail with what is true for you.

First I would find out why the feature is late, because the fix depends on the cause. Then I would lay out options: cut a secondary part of the feature, release it in two phases, or move people from lower-priority work. For example, I would ship the core flow on the fixed date and the reporting part two weeks later. I would agree the trade-off with the decision owner the same day and tell sales and support early, so problem solving happens before the launch date, not on it. In my last role in Seattle I phased a release like this to keep a fixed trade-show date in 2023, and the second phase shipped 12 days later.

Use only details that are true for you. The benchmark below is fictional.

What you type here is sent to JoRoute's server to produce this result, then discarded. It is not stored or logged, and no account is needed.

Next in your job search