Crusoe raised $3.9 billion to build data centers that travel by truck. The question that tests whether you can anticipate a customer.
On September 17, 2026, TechCrunch reported that data center developer Crusoe had raised $3.9 billion in a Series F round that pushes its valuation to $30.9 billion. The raise came 10 months after the company raised $1.38 billion at a $10 billion valuation. According to TechCrunch, the money will help finance existing projects, including a large site in Abilene, Texas, used by OpenAI. It will also fund smaller, modular AI factories, called Spark, that can be transported by truck and connected to large power sources almost anywhere. TechCrunch wrote that building them at its own facilities lets Crusoe deploy compute capacity quickly and without large construction workforces. It added that the smaller centers could help Crusoe sidestep, at least in part, backlash from local communities protesting massive complexes near their neighborhoods. Chief executive Chase Lochmiller said in a statement that reaching an era of abundance will mean "controlling the infrastructure from electrons to tokens".
Consider what the modular product addresses. As TechCrunch describes them, its benefits are about what stands between a customer and compute: the time a build takes, the labor it needs, and the neighbors who object to it. A customer signing a lease usually asks for capacity. The schedule slip and the zoning fight come later, and by then they are expensive. A company that builds around those obstacles before they arrive is betting that it understands its customers' coming year better than their current requests describe it. The article hedges on whether the bet pays off, and it should. The behaviour behind the bet is acting on a need before it is voiced. An interviewer is testing for the same behaviour with the question: "Tell me about a time you anticipated the needs of a customer."
Why they ask it
Most customer work is reactive. A ticket arrives, a request comes up on a call, or a renewal is at risk. Managers who only respond can be excellent at responding and still leave the customer to find every problem alone. The interviewer wants to know whether the candidate watches the customer's situation as well as the customer's inbox. They also want to know whether the candidate will spend effort on something nobody has asked for yet.
The question also tests judgment, because an anticipated need is a prediction, and predictions can be wrong. The interviewer is listening for how the candidate formed the prediction, how they checked it, and how much they committed before they knew.
The trap
The common failure is answering with responsiveness. The customer mentioned a concern, the candidate moved fast, and the customer was delighted. That is a good service story, and it answers a different question. If the customer raised the issue, nothing was anticipated.
The second failure is the intuition story. The candidate just knew, or had a feeling about the account. This may well be true, but it gives the interviewer nothing to evaluate. An anticipation that can't be traced to a signal looks like luck, and luck is no basis for a hire.
The third failure is the unilateral build. The candidate decided what the customer needed, built it, and presented it as a surprise. It can sound bold. To an experienced interviewer it sounds like someone who spends company resources on unverified guesses.
Applying STAR-T
Situation. Set up what the customer was asking for, then what they were not asking for. For example: a retail customer on a logistics platform was growing quickly. Every conversation with their team was about reporting features, and nobody on their side had mentioned the peak season ahead.
Task. State your responsibility and the gap you noticed. For example: as the account lead, the renewal was mine. The import volumes in their usage data were climbing toward a batch limit, and they would hit it during their busiest weeks. Nothing in their open requests touched it.
Action. Most answers are too thin here. A strong answer names the signal, the check, and the commitment, in that order. The signal was the usage trend compared against last year's seasonal pattern. The check was a short call with the customer's operations lead to ask about their forecast. The call confirmed the growth and showed they hadn't connected it to the limit. The commitment was a request to engineering for a staged import path, scoped small enough to ship before the peak, along with a plain note to the customer explaining what was coming and why. The check matters most. It turns a guess into a finding, and it costs almost nothing compared with building the wrong thing.
Result. Give the outcome in the customer's terms before your own. For example: the peak weeks passed without a failed import, the operations lead raised it unprompted at the renewal conversation, and the account expanded. If there is a number, give it. If there isn't, say exactly what happened and leave out the adjectives.
Trade-off. Naming a cost helps here, because anticipation always takes effort away from something that was explicitly requested. In this example, the reporting feature the customer had asked for slipped, and the candidate had to tell them so directly. Saying that aloud shows the interviewer that the prioritisation was deliberate. It also shows the candidate can keep a customer's trust while delivering something different from what was asked for.
The follow-up that breaks weak answers
A good interviewer will press on the prediction itself: How did you know, and what would you have done if you had been wrong? A weak answer repeats the intuition more firmly. A strong answer goes back to the evidence and the cheap check. It then describes the exit: what the work would have cost had the forecast not held, and at what point the candidate would have stopped.
A sharper version asks for a time the anticipation missed. Prepare that story too. A candidate who has only ever predicted correctly has either predicted very little or is not counting the misses. Describing a wrong call calmly, and what it changed about how you read accounts, often earns more credibility than the success did.
Score your answer against the director’s bar
Q: Tell me about a time you anticipated the needs of a customer.
Bank your own anticipation story with its signal, its check, and its cost, and rehearse it against the follow-up until the evidence comes out before the outcome. Try it free →