Skip to content
Alexander

“Tell me about a conflict” and “a mistake”: STAR answers

How to answer behavioral questions about a conflict and a failure: which story to pick, how to fit it into two minutes, and which follow-ups to expect.

“Tell me about a conflict” and “a mistake”: STAR answers

"Did you have conflicts at your last job?" and "tell me about your biggest screwup" come up in screening calls, in final rounds, and between technical questions. In the Sobes question bank, "Were there conflicts at your previous job? How did you resolve them?" was recorded after interviews at 8 companies, and the question about your biggest failure at 10. Analysts get their own version: "Were there conflicts or misunderstandings with a customer or a developer over requirements? Give a specific example".

There are two bad answers. "No conflicts, I'm not a confrontational person" is heard as "I don't remember" or "I won't tell you". The other bad answer lasts seven minutes, and by the end it is unclear what the speaker actually did. In Sobes users' interview reviews, behavioral interviews score lower on average than HR screenings: 73% against 83%. Usually the telling is the problem. People do have the stories.

What the interviewer listens for

In a conflict question:

  • How you describe the other side. "The product manager understood nothing about tech" ends the conversation.
  • What you personally did to reach agreement, and when.
  • How it ended and whether you stayed on working terms.

In a mistake question:

  • Whether you own it, without "circumstances just turned out that way".
  • What you did in the first minutes: fixed, reported, rolled back.
  • What changed afterwards: in your habits and in the team's process.

The wording from the bank, "Tell me about a serious outage or failure: how did you react and what did you conclude?", lists these points almost word for word.

STAR without the stiffness

STAR stands for situation, task, action, result. The scheme works, but recited point by point it turns into a report. It is easier to keep four questions in your head and answer them in plain words:

  1. What was going on. One or two sentences: team, product, deadline.
  2. What the problem was for you.
  3. What you did. Half of the total time. First-person verbs: "I wrote", "I called", "I proposed".
  4. How it ended and what you do differently now.

The whole story takes a minute and a half to two minutes. Leave the details for follow-up questions, there will be some.

How to pick the story

For a conflict, take a work disagreement about substance: deadlines, priorities, architecture, requirements. You acted in it, and it ended somehow. Personal dislike doesn't fit, nor does a story where you were simply right, nor one where you kept quiet and it went away on its own.

For a mistake, you need a real one with consequences that taught you something. "I once made a typo in a comment" doesn't count. A story that got you fired, or one where customers lost money and you changed nothing, doesn't work either. A good age for the story is six months to three years. Fresher looks like an open problem, older looks like a lack of experience.

Example: a conflict with a product manager

We were building a new pricing plan for the start of the quarter. Two weeks before release the product manager brought one more feature and insisted we couldn't launch without it. I estimated it at ten days, so we wouldn't make it. At first we argued in chat, and it only got worse. Then I suggested a half-hour call and brought two options: release on time without the feature and add it two weeks later, or ship a cut-down version of it in three days. We chose the cut-down one, launched on time, and finished the full version in the next sprint. Since then, if a chat argument goes past three messages, I suggest a call right away and come with options instead of a "no".

It works because the product manager is not the villain, the speaker's actions are specific, and it ends with a habit that can be tested with a question.

For a conflict with a team lead or a customer the frame is the same: the subject of the dispute, your step toward the other side, the decision. If the decision went against you, that is still a good story. Say that you kept your opinion, did it the way it was decided, and how it turned out.

Example: I took down production

I rolled out a migration that added an index to a large table and didn't check that it takes a lock. At two in the afternoon checkout was down for seven minutes. I saw the alerts, wrote in the incident channel right away that it was my release, and stopped the migration. Then I wrote a postmortem: what happened, how many orders we lost, what we're changing. We added a pipeline check for blocking operations in migrations and a rule that migrations on large tables only run at night. I now run every migration on a copy of the production database myself.

There are numbers here (seven minutes, two in the afternoon), there is "it was my release" in the first minute, and there are changes on two levels: a personal habit and the team's process.

Follow-up questions

A story is almost always followed by one or two questions. Prepare the answers in advance:

  • "What would you do differently now?"
  • "How did your manager react?"
  • "How are things with that person now?"
  • "What would the other side say if they were telling it?"
  • "What did it cost the company?"
  • "Why didn't a check catch it earlier?"

The question about the other side is the most useful one for rehearsal. If their version is very different from yours, rewrite the story.

What to avoid

  • "We decided", "we fixed it" all the way through. The interviewer won't know what you did.
  • Blame, even deserved. How to name disagreements neutrally is covered in a section of Why are you leaving your job?
  • Mistakes that are really virtues: "I took on too much". That is the same "perfectionist" in different wrapping. More on it in the article on weaknesses.
  • Other people's secrets. If the story is under NDA, anonymize it. How to do that is covered in How to talk about an NDA project in an interview.

Write two stories and time them

Write one story for each question, five or six sentences each. Tell it out loud with a timer: if it runs over two minutes, cut the first part, not the third. Then answer the six follow-up questions from the list above out loud.

You can test the stories on a live counterpart in a mock interview in HR screening or final-round mode: the interviewer asks follow-ups based on your answer, and you see right away where the story sags. If you also need a story about a hard technical task, it is built differently and has its own article: “Tell me about a challenging task”: how to answer.