In this post12 sections
- What the interviewer is testing when the news is bad
- The structure: news, cost, confidence, ownership, cause, options, ask
- The spoken answer, word for word
- The follow-up email
- Phrases that make it worse, and what to say instead
- When the account executive promised the date
- The behavioral version: a commitment you missed
- Before the call: a checklist
- Practice it out loud
- Questions people ask
- Keep reading
- More from the blog
The interviewer says, “The integration is three weeks behind. I’m the customer’s CTO. Tell me.” Then they stop talking and wait. It’s the client round of the interview (the FDE interview guide maps every round), and the easiest way to fail it is to be too nice.
Here is the short answer. Say the news and the new date in your first two sentences, then what it costs her, how sure you are, that it’s on you, the cause in one line, your options, and the decision you need. Apologize once, and send a short email the same day that repeats it in writing. The rest of this post gives you the exact words for the call and the email, the phrases that make it worse, and the two follow-ups that come next.
What the interviewer is testing when the news is bad
The prompt looks like a communication exercise. It is really a test of whether you act like the person responsible for the outcome, the part of the job that stays fixed across very different FDE teams. Natalie Meurer, Sierra’s head of engineering, said in her AI Engineer World’s Fair 2026 talk that the one constant across the versions of the role is that every forward-deployed engineer is accountable to the customer. Source 1The Dirty Secret of Forward Deployed Engineering (Natalie Meurer, Head of Agent Engineering, Sierra; AI Engineer World's Fair 2026)PublisherAI EngineerSource typerecorded talk or interview A late project is where that accountability either shows or doesn’t.
Even a technical CTO will forward what you say to people who aren’t engineers. Sarah Khalid, an FDE director at Salesforce, said on Salesforce’s blog that customer-facing skills matter because FDEs deal with business and executive stakeholders who “definitely don’t understand technical jargon.” Source 2Today's Hottest Role: Forward Deployed EngineerPublisherSalesforce 360 BlogSource typecompany blog So the interviewer is listening for three things:
- Do you lead with the news? Or do they sit through context while they wait for it?
- Do you own it? Or does the cause arrive first, sounding like an excuse?
- Do you leave them with a decision? Or with an apology and nothing to do?
The weak answer to watch for is not rude or evasive. It is an apology that runs for a minute, followed by a technical story, followed by the date. The CTO spent that minute wondering how bad it is.
The structure: news, cost, confidence, ownership, cause, options, ask
This is our method for bad news; the lesson Delivering slips and bad news takes it further. It works whether you are shipping an AI agent for a lab’s customer or a data pipeline for an enterprise platform.
- The news and the new date. A specific date, in your first two sentences. “The go-live moves from the first to the twenty-second.”
- What it costs her. In her units, not yours: which team waits, which process stays manual, what she can no longer promise her own boss. Say it before she has to work it out.
- How sure you are, as a condition. Not a feeling: “This date holds if we get the labeled sample by Thursday.” A condition tells her what to watch. “I’m pretty confident” tells her nothing.
- Own it, including when you knew. One sentence that says it is on your side, and the day you found out. That is the first thing a real CTO asks.
- The cause in one line. Plain language, then stop. If she wants the detail, she will ask, and now it is an answer rather than an excuse.
- Options and your recommendation. At least two, with what each costs her. The strongest option, when one exists, is a smaller release on the original date.
- The ask. A named thing, from a named person, by a date. A decision counts.
Apologize once, inside the ownership move, in a single sentence. Then spend your words on the cost, the condition, the options and the ask, because those are the parts she can use.
Tell your own side first
Before the customer hears it, tell your manager and the account executive. Agree on the new date and on who says it. A CTO who hears one date from you and another from sales stops believing both.
The spoken answer, word for word
Here is a fictional scenario at speaking speed. You are building an AI assistant for a regional insurer. It reads incoming claim documents and fills in the claims system. Go-live was promised for the first of the month. It will be three weeks late, because the forms from the insurer’s two oldest branches are handwritten, and extraction on them misses the accuracy bar you agreed with Priya, the insurer’s CTO, and her team.
Say this:
“Priya, I’ll start with the news. The claims assistant will go live three weeks late, on Monday the twenty-second instead of the first. For your claims team, that’s every claim keyed by hand until the twenty-second, and I know that’s the relief you planned around.
“The twenty-second holds on one condition. The remaining work is a review step that sends the fields the assistant is unsure of to a person. We tune where that line sits on fifty of your handwritten forms, labeled by one of your claims supervisors by Thursday. The date holds if we get them by then. If that slips, I’ll tell you the same day what it does to the date.
“That’s on us: we committed to the first before we had tested on your handwritten forms, and I’m sorry. We found this on Tuesday, when we first ran your handwritten forms through it, and I’m telling you now because I have a plan to bring with it.
“The cause in one line: the assistant reads typed forms well, but it misreads too many handwritten ones to run without a person checking them.
“You have two options. First, we go live on the first with typed forms only. Your team keeps handling handwritten claims by hand until the twenty-second, and the rest come off their desks on schedule. Second, we wait and launch everything together on the twenty-second, which is one cutover instead of two. I recommend the first, because it gets most of the relief to your team on the date you planned for.
“I need two things from you: which option you want, by Wednesday, and the name of a supervisor for the labeling.”
Count what happened. The new date arrived in the second sentence. The cost to her came next, in her team’s hours, not in model accuracy. The apology took two words. The cause took one sentence. Most of the words went to the cost, the condition, the options and the ask, which are the parts she can act on.
The cause here is an AI system misreading forms; explaining AI mistakes to executives covers how to say that without losing the project.
If you want to rehearse this out loud, the practice question tell the CTO you will be three weeks late is free, with a model answer and the follow-ups an interviewer asks next.
The follow-up email
End the call with “I’ll send you this in writing within the hour,” then send it. The email is what she forwards to her boss, so write it for someone who was not on the call.
Subject: Claims assistant go-live moves to Monday the twenty-second: one decision needed by Wednesday
Priya,
As we discussed, go-live moves from the first to Monday the twenty-second. We committed to the first before testing on handwritten forms, and that was our mistake.
Why: the assistant misreads too many handwritten forms to run without a person checking them. We are adding a review step for those forms.
How sure we are: the twenty-second holds if we receive fifty labeled handwritten forms by Thursday. I will confirm on Thursday either way.
Your options:
- Go live on the first with typed forms only; handwritten claims stay manual until the twenty-second, and there are two cutovers. (Our recommendation.)
- Launch everything together on the twenty-second: one cutover, but every claim stays manual until then.
What we need: your choice by Wednesday, and a claims supervisor for about two hours of labeling this week.
Next update: Thursday, after the labeling.
Five rules the email follows:
- The subject line carries the news and the ask. She should know both without opening it.
- The first line is the date, not “Thanks for your time today.”
- Bold labels, short lines. It reads on a phone in a hallway.
- One recommendation, marked. Options with no recommendation hand the thinking back to her.
- A date for the next update. Silence after bad news reads as more bad news.
The lesson on the follow-up email and executive summaries goes further into structure and length.
Phrases that make it worse, and what to say instead
These three phrases sound reasonable, and each one costs you trust.
“We’re doing everything we can.” She cannot plan around effort. Say instead: “The date holds if we get the labeled sample by Thursday. I’ll confirm that day.”
“Unfortunately, due to some unforeseen complexity...” Passive, vague, and it puts the cause before the ownership, so it lands as an excuse. And “unforeseen” invites the obvious question: why didn’t you foresee it? Say instead: “That’s on us. We committed before we had tested on your handwritten forms.”
“I’m so sorry, I feel terrible about this, I know how much this matters...” A long apology makes her manage your feelings while she waits for the date. Say instead: “I’m sorry.” Then give the date.
A fourth one is worth avoiding in any version: “To be fair, your team was late with the forms.” Even when it is true, it tells her no one on your side is in charge. If her team’s delay is part of the cause, fold it into the ask (“the date depends on the sample by Thursday”) rather than the blame. And if the real cause was a request that kept growing, the scope creep interview answer covers how to say no to the extra work before it costs you a date.
When the account executive promised the date
This is the follow-up that makes the prompt hard. The CTO says, “Your salesperson promised me this date.”
Do not distance yourself from sales; “that was sales, not engineering” tells her your company does not speak with one voice. Own it as the company, and move to the date you now stand behind:
“He did, and he spoke for all of us, so the miss is ours, not his. Before this call he and I agreed on the twenty-second, so you’ll get one date from us. The difference this time is that it’s based on your handwritten forms, not on a sample.”
It works because you agreed on the date with the account executive before the call, and because the new date rests on real testing, which the old one lacked.
The interviewer may push further: “So why should I believe you this time?” Answer with the condition and the next check-in, not with more reassurance. “Because the twenty-second rests on one thing, the labeled sample by Thursday, and you’ll hear from me on Thursday either way.”
Or: “When did you know?” Answer with the day, and own any delay between knowing and telling.
The behavioral version: a commitment you missed
The same skill comes back in the behavioral round as a question about your past. Palantir’s careers page, which covers all its hiring rather than the FDE loop alone, says its onsite interviewers ask how you have executed and made judgments, and where you have failed in the past. Source 3Getting Hired - Palantir CareersPublisherPalantir TechnologiesSource typecompany hiring page “Tell me about a commitment you missed” is one form of that question, and the same moves map straight onto it.
Answer it in this order:
- The commitment and the miss, in one sentence. Who you promised, what, and by when.
- When you knew and when you told them. This is the part a good follow-up question digs into. If you waited a week, say so, and say what you would do differently.
- What you offered. The options, the new date and how it held.
- The ask and the outcome. What you needed from them, and what happened.
- What you changed afterward. A habit, not a feeling: “Now I test on the customer’s real data before I give a date.”
A fictional example, to show the shape: “I promised a hospital’s operations team a staffing forecast by the end of the quarter, and I missed it by two weeks. I knew ten days before the deadline, when the historical data turned out to cover only one of their three sites. I told their director that afternoon, offered a forecast for the one site on the original date and the rest two weeks later, and she took it. Now I check data coverage in the first week of any project before I commit to a date.”
The story spends its time on when you told them and what you offered, not on how bad it felt. Rehearse this exact prompt with Tell me about a commitment you missed, which comes with a framework and the follow-ups interviewers ask. Delivering bad news to an executive is its twin. Both are in Pro.
Before the call: a checklist
Before you tell the customer
- Your manager and the account executive know, and agree on the new date
- You can say the new date and the one condition it rests on
- You can say the cause in one sentence with no jargon
- You have at least two options, with what each costs, and a recommendation
- You know exactly what you need from the customer, and by when
- The follow-up email is drafted, so you can send it within the hour
Practice it out loud
Reading the structure is easy. Saying the date in your second sentence while someone stares at you is not, so rehearse it until the order is automatic. If the interviewer plays the CTO and pushes back, the customer role-play interview covers staying in the role.
The lesson Delivering slips and bad news is included in Pro. It walks through impact before cause, asking for what you need and the same-day follow-up in writing. Pro comes with a 7-day free trial. See what it includes.
The free case gives you the other half of this skill. It puts you in front of a deputy mayor whose boss has already promised an AI review tool, stakeholders who disagree, and facts they share only when you ask the right question. It runs on a ten-minute clock and ends with a score that quotes your own words back to you. Sign in free and run the free case.
Questions people ask
How do you tell a customer a project is delayed?
Say the news and the new date in your first two sentences. Then say what the slip costs the customer, the one condition the new date rests on, that it is on you and when you knew, the cause in a single sentence, your options with a recommendation, and the decision you need.
Should you apologize when a project is late?
Once, briefly, and then move to the plan. A long apology delays what the customer needs to hear, which is the new date, what caused it and what they can decide now.
What should the follow-up email after a delay say?
Restate the new date and your confidence in it, the cause, the options you discussed, the decision the customer made or still has to make, and when you will update them next. Keep it short enough to forward to their manager.
Keep reading
Lessons
More from the blog
Interview rounds
Scope creep in the client round: how to say no without losing the customer
How to handle scope creep in an FDE client round: trade, defer or phase, with scripts, a change-request note and what hiring leaders say.
Interview rounds
A customer says requests are failing: how to run the first hour in an FDE interview
A customer says requests are failing. Your first hour in the FDE interview: scope, timeline, recent changes, error classes, rollback and the update.
Interview rounds
Discovery call questions for engineers: what to ask a customer in the first meeting
What to ask a customer in the first meeting, by outcome, users, data, systems and constraints, with follow-ups that turn vague answers into requirements.