BEHAVIORAL · RESILIENCE AND COURAGE
Describe a setback that almost made you give up. What kept you going?: sample answer
Whether you keep going after something goes wrong, without denial or blame, and whether you have the courage to make or support a hard call. They want to see how you kept yourself and others steady and what changed because you persisted.
Also asked as
- Tell me about a time your judgment turned out to be right when others disagreed.
- Describe a setback that almost made you give up. What kept you going?
- Tell me about an unpopular decision you made or supported.
The short version: Show you kept going through a setback or made an unpopular call that was right.
Sample STAR answer
An invented example from typical software engineering work, about 280 words, around two minutes spoken. Use the structure, not the story: yours should be real.
Situation My team rebuilt the checkout page of our shopping app to make it faster. We launched it twice, and both times we rolled it back within a day: first for a payment bug on one browser, then for a drop in completed orders we could not explain. Leadership was close to cancelling the project.
Task I was the lead engineer. Morale on the team was low, and I had to decide whether to argue for a third attempt and, if so, make sure it would not fail the same way.
Action I took a day to understand both failures. The browser bug was simple; the order drop was the real issue. From session recordings, I found that the new page hid the delivery-date selector behind a tap, and people abandoned when they could not see the date. Neither failure meant the rebuild was wrong; both meant our launch process was. I wrote a short plan for a third attempt with three changes: an automated test across our top five browsers, a gradual rollout starting at five percent with a comparison of completed orders against the old page, and an automatic switch back if orders dropped more than one percent. I presented it to leadership and said plainly that if this attempt failed, I would recommend stopping. I also talked to the team openly about the two rollbacks so nobody carried the blame alone.
Result The third launch went to a hundred percent over two weeks with no rollback. Page load time fell by 40 percent and completed orders rose by about two percent. The gradual rollout with an automatic switch back became the standard for every customer-facing launch on our team.
Weak answer vs strong answer
Weak
"I never give up. When our project had problems, I kept working hard and stayed positive, and eventually it worked out."
Why it scores low: It is a slogan, not a story. There is no setback described, no hard choice, no analysis of what went wrong and no change that made the next attempt succeed.
Strong
A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Show you kept going through a setback or made an unpopular call that was right.
How the story changes with level
At SDE 1, a setback on your own work, like a feature that kept failing review or a hard bug, is enough. Show how you stayed calm, asked for help and kept going.
At senior or staff level, show that you made a hard call others doubted, protected the team through it, and turned the setback into a lasting change in how the group works.
Follow-up questions interviewers ask
- Why did you think a third attempt was worth it?Separate "the idea was wrong" from "the launch process was wrong", with evidence.
- What would you have done if leadership had cancelled it?Say you would accept it and keep the lessons, such as the safer rollout.
- How did you keep the team motivated?Talk openly about failures and share the plan, not pep talks.
- Tell me about a time you decided to stop something.Knowing when to quit is also resilience; have a short example.
Companies that test this
Prepare your own
Write your story in the story bank and tag it "Resilience and courage"; it will show up against every company value that tests this theme.
Related: Ambiguity and judgment · Disagreement and candor