‹ Field Notes
Long-term judgment

Crusoe sold its unfinished Wyoming campus to the customer it couldn't land. The question that asks what you're willing to give up.

On November 7, 2026, TechCrunch reported that Crusoe, an eight-year-old, Denver-based data center developer "recently valued at $30.9 billion", had confirmed Friday that it sold an unfinished data center project in southeastern Wyoming to Google. The buyer was not new to the site. According to TechCrunch, Google was the customer Crusoe "had tried and failed to land" for the project, and it is taking over the development "after reportedly raising concerns about its cost and construction timeline". Crusoe had announced the project last year with Blackstone-backed Tallgrass, planning to eventually scale it to 10 gigawatts of power capacity. Google did not disclose how much it paid, TechCrunch noted, but it announced plans to invest $17 billion to develop the campus. Bloomberg had first reported the deal in June.

The article does not say what Crusoe was thinking, and it would be a mistake to supply a motive it never reports. What it does describe is the shape of the outcome. TechCrunch wrote that the sale "highlights how difficult it can be for independent data center developers to deliver massive projects on time and within budget", and then recorded two further facts: Crusoe "is developing another data center for Google near Amarillo, Texas", and the Wyoming setback did not stop it from raising a $3.9 billion round in September. Put those together and a familiar pattern appears. A company announced a flagship at a scale measured in gigawatts, then handed that flagship to the customer it had failed to sign, and remains that customer's builder elsewhere. A visible loss on one front sits next to a relationship that continues and a fundraising that went ahead anyway. That trade, accepting a concrete near-term cost in exchange for something slower and larger, is a behaviour rather than a headline. It is also what an interviewer is looking for when they ask the following.

The interview question
“Tell me about a time when you made short-term sacrifices for long-term gains.”

Why they ask it

The question is not a test of appetite for pain. Anyone can describe a hard quarter. The interviewer is testing judgment across time: whether the candidate can see that a present cost is real, that a future value is larger, and that the two are paid in different currencies on different dates. At senior levels there are two further probes hidden inside it. The first is whether the candidate can tell a sacrifice from a sunk cost, because the people who keep funding a failing project also describe themselves as patient. The second is who carried the short-term cost. A manager's sacrifice is rarely personal; it lands on a team, a partner function, or a customer, and the question quietly asks whether those people were told, consulted, or simply handed the bill.

The trap

Three failure modes account for most weak answers. The first is the sacrifice that is really just effort: the candidate worked late, skipped a holiday, carried a pager for a month. That is endurance, and it does not demonstrate a decision. The second is the gain that is asserted rather than measured. "It set the team up for success" and "it paid off in the long run" are the sound of a story that was never checked against a number. The third, and the most common among otherwise strong operators, is hindsight smoothing. The candidate tells the story as if the right call was obvious, which deletes the one thing the interviewer wanted to see: the moment of uncertainty, and how it was managed. A strong answer names what was given up in units, names what was expected in return and by when, and admits that at the time the second number was a forecast.

Applying STAR-T

Situation. An engineering manager inherits a payments service whose release process takes two weeks of manual regression testing. Sales has already committed three customer-facing features for the quarter, and the team is at capacity delivering them.

Task. Decide whether to pull two engineers off the committed features for six weeks to build an automated deployment pipeline, knowing that at least one feature will slip past the date sales promised.

Action. The manager priced both sides before choosing. The cost was concrete: one feature slips a full quarter, and a named account had been waiting on it. The gain was stated as a forecast with a date: release cadence from fortnightly to daily by the end of the following quarter, which the manager translated into roughly three additional feature releases per quarter at the current team size. They took that trade to the sales lead rather than announcing it, agreed which feature would slip, and set a checkpoint: if the pipeline was not shipping to production by week six, the engineers would return to features and the slip would be absorbed. They reported progress against that checkpoint weekly.

Result. The pipeline shipped in week five. Over the next two quarters the team released more than it had in the previous four, and the slipped feature landed one quarter late to an account that had been told the new date in advance.

Trade-off. The slipped feature cost some trust with that account, and the manager owns that. The account renewed at a smaller tier. A strong answer says so plainly, because an interviewer who hears a sacrifice with no casualty assumes one is being hidden.

The follow-up that breaks weak answers

The follow-up that separates a real decision from a retold success is some version of: how did you know the long-term gain would arrive, and what would you have done if it had not? Weak answers collapse here because the gain was never specified, so there was nothing to check it against. Strong answers already contain the checkpoint and the reversal plan, which is why the Action step above sets them out loud. A second follow-up targets the people who paid: who absorbed the short-term cost, and did they agree before or after? A candidate who cannot name them has described a decision made for others, which is a different competency than the one being tested.

Score your answer against the director’s bar

Q: Tell me about a time when you made short-term sacrifices for long-term gains.

Ready when you are

Bank this story with the number given up and the number being bought, then rehearse the follow-up until the checkpoint comes out unprompted. Try it free →

Rehearse this in L8 Loop →