behavioral Medium GeneralSoftware EngineerProduct ManagerData / AnalyticsMarketing

Tell me about a time you made a difficult decision at work.

A full STAR example answer for this behavioral question, plus the common mistakes that weaken most answers and the follow-ups interviewers use to probe deeper.

A strong STAR example answer

The feature never shipped, and killing it was the best call I made that year. My team had spent months building a reporting module for enterprise clients, and I was the product owner who had to decide its fate.

Two weeks before launch, the beta data came back brutal: of the pilot accounts, only a handful touched it weekly, and support tickets said the rest found it confusing. Every option hurt. Shipping meant maintaining something users did not want. Killing it meant facing my team, and my manager, who had championed the project to leadership.

Before deciding, I ran another round of user interviews to make sure the beta was not a fluke. It was not. Then I asked the team what could be salvaged, and that was the good news: the underlying data pipeline could power a simpler export feature users had actually been requesting.

I took that plan to my manager first, then to the team, with the beta numbers on the table so the decision read as evidence, not whim.

We shipped the export feature a few weeks later, and it became one of our most-used enterprise tools. The cost was morale — a couple of engineers were frustrated for weeks, and honestly, so was I. Sunk cost is loud. Usage data is louder.

How to structure your own answer

  • Situation: Set up the stakes and why every option had a real cost.
  • Task: Clarify that the decision was yours to make.
  • Action: Show the criteria and input you used, not just gut feel.
  • Result: Own the outcome, including the trade-off you accepted.

Common mistakes to avoid

  • Don't pick a decision where the right answer was obvious — that is not a difficult decision.
  • Candidates often hide the emotional or political cost, which makes the story unconvincing.
  • The story collapses if the decision was really your manager's and not yours.
  • What were the criteria? Skip them, and the decision sounds like a coin flip.

Follow-up questions to prepare for

A strong answer invites follow-ups — interviewers probe to check the reasoning holds up. Prepare for questions like:

  • How did the team react, and what did you do about it?
  • What would you do differently in hindsight?
  • How do you decide when to keep gathering data versus decide?

Related practice questions

Keep drilling with these, or browse the complete question bank.

Next up

Practice this question on the clock

Reading an answer and delivering one are different skills. Run a timed round and rate yourself.

Start a practice round

Next up

Interview coming up?

Have your post-interview follow-up email ready before you need it.

Follow-up email generator