Amazon's cloud grew 39% and its free cash flow hit negative $42.4 billion. The question that tests how you decide what to cut.
On October 29, 2026, TechCrunch reported that Amazon had missed analysts' expectations for both total revenue and earnings per share in its third-quarter results. The same report carried what TechCrunch called "a big, bright spot": Amazon Web Services beat revenue expectations and "grew a whopping 39% compared to the year-ago quarter." Then came what TechCrunch called "the biggest ouch of the report." Free cash flow for the trailing 12 months fell to a negative $42.4 billion, against positive free cash flow of $14.8 billion for the trailing 12 months ended September 30, 2025. The company said the spending was driven largely by its investments in AI, and, according to TechCrunch, Amazon reiterated that it still expects to end 2026 with cash capital expenditures of about $220 billion. For scale, TechCrunch noted that Amazon forecast fourth-quarter net sales of between $240 billion and $247 billion.
Read those numbers as one decision rather than a scorecard. A company that size does not drift into negative free cash flow. It gets there by choosing, ahead of time, which line it will protect and which lines it will let the market read for itself. Amazon says the spending is largely its AI investment, and on the day it reported the miss it reiterated the capital plan rather than trimming it. That is not a scope cut in the engineering sense, but it is the same shape of decision. You cannot hold every number at once, so you decide which one the date is for, and you say out loud which ones you are letting go. Managers make the small version of this call every quarter, which is why interviewers ask about it directly.
Why they ask it
The question is usually worded almost exactly as "Describe a time you had to cut scope to hit a date, and how you decided what to cut." The second clause is the one that matters. Anyone who has shipped software has cut scope. The interviewer wants the method, because a scope cut is the moment a manager's stated priorities become visible. A roadmap can rank ten things. A cut shows which one you actually ranked first when the ranking cost something. Interviewers listen for three signals: whether you knew what the date was for, whether you had a rule rather than a mood, and whether the people affected heard about the cut from you before they discovered it on their own.
The trap
The most common weak answer is the deferral dressed as a cut. We moved the reporting export to phase two. Phase two never had a date or an owner, so nothing was decided; the work was simply hidden from the schedule. The second failure is cutting by effort. Under pressure, teams drop the hardest item, and the hardest item is often the one the date existed for, leaving a product that technically hit the day and functionally did not. The third is the silent cut, where the stakeholder learns at launch what they did not get. The fourth is the heroic non-answer: we didn't cut anything, we worked weekends. That tells the interviewer you do not know how to cut, only how to absorb. A strong answer starts from the purpose of the date, sorts every item against that purpose, and names who was told and when.
Applying STAR-T
Situation. A billing migration had a hard date because the contract with the old payments vendor ended on a fixed day. Six weeks out, the team was tracking roughly three weeks behind. The committed scope included the migration itself, a redesigned invoicing screen, and a reporting export the finance team had requested for month-end close.
Task. Hit the vendor date without any customer losing the ability to pay, decide what shipped on the day and what did not, and get the affected teams to agree to the cut before it was final rather than after.
Action. The manager wrote down, in one sentence, what the date was for: no customer could be unable to pay on day one. Every item was sorted against that sentence. The migration was required by definition. The invoicing screen was not, because the old screen still worked against the new backend. The export was needed for close, but close fell two weeks after the vendor date, so it could ship second. The manager took the proposed cut to the finance lead and the product lead with three things attached: what they would lose on the date, what they would get instead, and when. Deferred items were written down with a named owner and a date, not a phase number. The team then re-planned against only the required work and re-checked the burn weekly.
Result. The migration shipped on the vendor date with no payment failures. The export landed before close. The invoicing screen shipped three weeks after the date, which is roughly when it would have shipped anyway had the team tried to carry all three and slipped everything together.
Trade-off. The delayed invoicing screen meant sales ran demos on the old screens for most of a quarter, and one enterprise prospect asked about it. The manager named that cost to the sales lead at the time of the cut rather than letting it surface in a pipeline review. It was the right call, and it was still a cost.
The follow-up that breaks weak answers
Who pushed back on the cut, and what happened to their item? Weak answers say nobody pushed back, which means one of two things: the cut was trivial, or nobody was told. Strong answers name the person, state their argument fairly, and say what changed because of it, even if the answer is that the cut held and the owner got a date instead of a promise. A second follow-up tests the method rather than the story: if the date had moved a week closer, what would you have cut next? A candidate who sorted against a purpose can answer in a sentence. A candidate who cut by instinct has to start over.
Score your answer against the director’s bar
Q: Describe a time you had to cut scope to hit a date, and how you decided what to cut.
Bank this story with the one sentence the date was for, then rehearse the cut and its cost until the follow-up has an answer. Try it free →