“Tell Me About a Time You Had a Conflict”
“I don't really have conflicts” sounds like a pushover, and a story where the other person is the villain makes you look hard to work with. Get a specific, believable answer that picks a real, professional disagreement, shows the steps you took to resolve it, ends on a relationship that survived, and turns your career change into proof of your people skills.
Generated for: Project manager interviewing for a senior PM role
I try to get the disagreement onto the table as a question about the work rather than a question about who's right, and I do it early, before it turns into two people defending positions in public.
Last quarter our lead engineer and our designer were stuck on a checkout redesign — he said the animation spec would tank performance on low-end Android, she said the flow was unusable without it. I stopped the thread and asked for the actual number: what's the budget, what does the spec cost. It turned out to be 140ms against a 200ms budget, which nobody had measured. The argument evaporated in a twenty-minute call because it had been a values fight standing in for a measurement nobody had taken.
That's not always how it goes — sometimes it really is a priority conflict and someone has to decide. In those cases I'd rather name it as a decision and take it to whoever owns it than let it grind for another sprint.
Why this one works
- Describes a repeatable approach and then proves it with one specific conflict.
- The resolution turns on evidence, which shows judgment rather than diplomacy alone.
- Acknowledging the cases that don't resolve cleanly keeps it from sounding scripted.
Yours is written from your own background and the role you're actually interviewing for — not this one. One credit per generation, $9.99 for a single credit or $49.99 for ten. Fill in the form below to generate it.