Preparing for Interviews After a Startup Failure
A polished press-release account of a failure is the common instinct, and the source advises against it.
Why the Polished Version Feels Safe
Suppose a startup you worked on or founded has failed. Your first instinct, when you think about it later, is probably to tell its story in the most favorable light. You smooth over the bad decisions, shorten the painful parts, and finish with a tidy sentence about what you learned. This feels safe because it seems to protect your reputation.
The trouble appears when you need to talk about that failure in a job interview. The polished version is the one most people reach for first, and it is usually the wrong one. The source for this article is direct about it: the common instinct is a polished press-release account of the failure, and the advice is to resist it.
Two Versions of the Same Startup
The two versions of a failure story differ mainly in what they are trying to do. The press-release version is shaped to protect the speaker. The honest version is shaped to show the listener how the speaker thinks. Both can describe the same startup, but they select, omit, and emphasize different things.
The diagram below sets the two versions side by side. Read it column by column. The honest column is the one the source recommends, and the reason is that only it gives an interviewer something concrete to assess.
Notice what the rewrite does not require. It does not require making the failure sound worse than it was. It requires making the account specific. Specificity is what separates a credible story from a generic one.
What a Real Failure Story Contains
An honest failure story is the real version of what happened, told in your own words, with the lessons named explicitly. It has two parts that must both be present: the events, and the lessons drawn from those events.
The events are the sequence of things that actually happened, including the decisions that went badly. The lessons are the conclusions you drew, stated explicitly rather than implied. A story with events but no named lessons leaves the interviewer to guess what you took from it. A story with lessons but no real events sounds like a press release.
The source also makes a point about why this matters in an interview. The story itself serves as your credential, and its honesty is what sets it apart from other candidates' accounts of failure.
The timeline above is an illustrative shape, not a record of any particular startup. Its purpose is to show the structure: events come in order, and each lesson is attached to the stage it was drawn from. Your own story will have its own events, and you should fill in the stages with what actually happened to you.
Tracing a Story Stage by Stage
The best way to see the difference is to take one polished sentence and trace how it becomes an honest one. The worked example below uses an invented situation purely to show the method. It is not drawn from the source.
Rewriting a polished sentence into a specific one
The polished version reads: We learned a lot and moved on with a clearer sense of our market. Rewrite it as an honest account that an interviewer could assess.
- 1Identify what the sentence hides
The phrase learned a lot names no event and no lesson. It conceals what the founders actually did and what they concluded from it.
- 2Recover the events in your own words
Write down what happened in order. For example: we built the product before confirming that customers would pay for it, and we kept building for several months after the signs appeared.
- 3Name each lesson explicitly
Attach a stated conclusion to the events. For example: I now check for paying customers before committing months of engineering time.
- 4Check for specificity, not severity
The rewrite should be specific. It should not be made to sound worse than it was. Keep only what you can stand behind.
The honest version names the decision, the signs that were missed or ignored, and the specific lesson drawn. An interviewer can now ask follow-up questions about each part, which is exactly what the polished version prevented.
Mistakes That Turn a Story Back Into a Press Release
Common mistake Not writing a press-release version
Why it failsThe source names the polished press-release version as a mistake, but the mistake is the instinct to write one for the interview. A polished story replaces the real account with a managed one.
Do this insteadStart from the real events, then decide what to say in your own words.
Common mistake Listing events without naming lessons
Why it failsAn interviewer is left to guess what you took from the failure, and the story loses its value as a demonstration of how you think.
Do this insteadAfter each important event, state the lesson you drew from it explicitly.
Common mistake Ending on a tidy sentence
What it looks likeWe learned a lot and moved on with a clearer sense of our market.
Why it failsThe sentence names no specific lesson, so it sounds managed rather than honest.
Do this insteadReplace the closing sentence with the specific lessons, each tied to the event that produced it.
Common mistake Making the failure sound worse than it was
Why it failsThe source's point is about specificity, not severity. Exaggerating the failure is also a distortion of the real account.
Do this insteadAim for an accurate account that you can defend when asked follow-up questions.
Drafting Your Own Short Version
Write a short failure story, in your own words, about a startup you worked on or founded. Keep it short enough to say aloud in a few minutes. Include the events in order and name at least two lessons explicitly, each tied to the event it came from. Do not write a closing sentence that avoids naming a lesson.
Hints
- Start by listing the events in the order they happened, before you write any sentences.
- For each lesson, ask which event produced it, and place the lesson directly after that event.
- Read your draft and mark every vague phrase such as learned a lot. Replace each one with a specific event or a specific lesson.
- Check that the story is specific rather than dramatic. You should be able to answer a follow-up question about any sentence in it.
Key Takeaways
- A polished, press-release account of a failure is the common instinct, but the source advises against using it in an interview.
- The polished version protects the speaker, while the honest version shows the listener how the speaker thinks.
- A real failure story contains the events in your own words and the lessons named explicitly, with each lesson tied to its event.
- The story is your credential in an interview, and its specificity rather than its severity is what makes it credible.