Tell me about a situation where poor communication led to a problem.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess how you recognize, diagnose, and recover from communication breakdowns. They are usually not looking for a perfect story; they want to see whether you can honestly explain your role in the problem, understand why the communication failed, and take effective action to repair both the work and the working relationship. At higher levels, they also want to see whether you improve the surrounding system so the same failure is less likely to recur.
Key Insights
- You do not need a dramatic failure. A strong answer often comes from an ordinary but consequential misalignment where expectations, context, or ownership were unclear.
- You should name your own contribution to the communication problem, even if others were involved. Mature candidates do not frame the story as 'they misunderstood me'; they show how they investigated the gap and adjusted.
- Do not stop at the immediate fix. Strong answers explain what changed afterward in your habits, team process, or communication style so the issue became less likely to repeat.
What interviewers probe atlevel
Top Priority
For junior candidates, the key is showing that you did more than apologizeâyou actively clarified expectations and helped get the work back on track.
Good examples
đ˘I set up a quick conversation, restated my understanding in plain language, confirmed what each of us thought was happening, and updated the task so we had one shared reference.
đ˘I corrected my part of the work, walked through the mismatch with the teammate, and wrote down the agreed next steps so we did not drift again.
Bad examples
đ´Once I noticed the confusion, I sent a longer message explaining my point and assumed that would clear it up.
đ´I told my lead there had been a misunderstanding and waited for them to decide how to fix it.
Weak answers rely on passive clarification; strong answers show active repair of both understanding and execution.
Valuable
Example answers atlevel
Great answers
On a small feature project, I told a teammate that my part was 'ready,' and they started building on top of it. What I meant was that the basic path worked, but I still had one edge case and a test issue open. When their work started failing, I realized I had used a shortcut description that sounded much more complete than it really was. I reached out right away, explained exactly what was done versus still in progress, and we spent a few minutes aligning on what they could safely use. After that I updated the task with a clearer status summary and started being more explicit about what 'ready' means when I give updates. It helped us finish the feature without more confusion, and my lead later mentioned that my updates had become much easier to work from.
On a small bug-fix I picked up while working remotely, the ticket description said âmatch legacy behaviorâ but didnât say which edge case counted as legacy; I guessed and pushed a change that made a few UI texts inconsistent. QA caught it and we had to revert and rework the fix, which cost the team a day of cycles. I owned up, fixed the immediate issue, and then updated the ticket with a clear acceptance checklist and examples of expected text for each state so there was no room for guessing. I also started sending one quick clarifying question in the ticket or a Slack thread before I began coding on ambiguous tasks. That small change cut down follow-ups and made handoffs smoother, which my QA partner appreciated because it saved them time when testing.
Poor answers
I had a situation where another engineer used my work before it was finalized and it caused some extra debugging. I had already mentioned in chat that I was working on it, so I think the main issue was that they moved a little too quickly. Once we found the problem, I explained what my code was doing and they adjusted their part. After that, I just made sure to answer messages faster so things would keep moving.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Hello Interview Premium
Your account is free and you can post anonymously if you choose.