A practice prompt we wrote. No company or candidate report names it, so it carries no company tag.

How to answer

If your answer takes a minute to reach the bad news, you have shown how you deliver it. Start with the news in one sentence, then spend most of your time on preparation.

Pick news the executive owned: their data, their team’s process, a number already given to their board. A slip in your own schedule shows less.

  1. The news and the executive. Who they were, and what the news cost them.
  2. How you prepared.
    • Confirmed what you could that day and wrote down what was unknown and when you would know, so nothing you said would move.
    • Told your own side first, so the executive heard one story.
    • Wrote the first two sentences: the news, then what it means for them.
    • Prepared options, a recommendation and the decision you needed.
    • Wrote down the first hard question you expected, and your answer.
    • Left out the blow-by-blow timeline, who on their team caused it, and options you would not recommend.
  3. The conversation. Your opening line, quoted, then how they reacted.
  4. What they decided, and what they did next with you. Whether they took your recommendation, and something observable afterward, such as coming to you directly next time.

Keep the mechanism out of the opening. Sarah Khalid, director at Salesforce, said on Salesforce’s blog in November 2025 that customer-facing skills are very important because FDEs often engage business and executive stakeholders who do not understand technical jargon. Source 1Today's Hottest Role: Forward Deployed EngineerPublisherSalesforce 360 BlogSource typecompany blog Prepare the cause as one sentence about their business; keep the technical detail for their follow-up.

The traps: a thorough account of the cause and no decision for them to make; email because the conversation felt hard; and waiting to be certain of everything, so they heard it late. For the words themselves, practice the client question about a three-week slip.

GlossaryForward deployed engineerA software engineer who builds and ships production systems inside a customer’s problem and environment, accountable to that customer’s outcome.More on Forward deployed engineer

Follow-ups

What the interviewer may ask next, once your first answer is on the table.

  • What was the first question the executive asked, and had you prepared for it?
  • What did you leave out of the conversation, and why?
  • Who heard the news before the executive did, and why in that order?
  • What would you have done if they had asked you to keep it from their CEO until next quarter?

Where answers go wrong

  • Opens the answer, as in the meeting it describes, with a minute of background before the news itself.
  • Describes preparing an explanation of the cause but no options, no recommendation and no decision for the executive to make.

Answer this in two minutes

Write the answer you would say out loud. The clock starts with your first word.

Two minutes

Illustrative answer about a fictional project

The news was that the number our customer’s head of claims had given her board was wrong, and the error was in her own team’s data. We were deploying a triage model at a regional home insurer that routed water-damage claims to the right adjuster on the first day.