Tell me about a time you worked with someone whose communication style was very different from yours.

This question tests adaptability and respect for difference. The trap is to make the answer about how you put up with someone difficult.

STAR walkthrough — sample answer:

Situation: I worked closely with a backend engineer on a previous team who communicated very differently from me. I tend toward verbal, conversational problem-solving — quick chats, thinking out loud. They preferred deep-focus work in long stretches, communicated almost exclusively in writing, and found conversational interruptions disruptive.

Task: We needed to collaborate on a complex API change that affected several test suites I owned. The work would naturally involve a lot of back-and-forth.

Action: Early on, I noticed they'd respond to my Slack DMs hours later in long, considered messages — and that drop-by chat questions were getting curt one-line answers if any. Rather than pushing my style on them, I shifted:

1. Batched my questions. Instead of asking five questions across the day, I'd write one structured message at start of day with everything I needed, ranked by urgency. They could respond when they had context, and the answers were thoughtful.

2. Used the doc-comments-and-PR pattern. For design questions, I'd write a one-page doc with my open questions in headed sections. They'd come back with marked-up answers in their own time. We had three rounds of doc revision over a week and never needed a meeting.

3. Named the difference openly when useful. I told them once: "I tend to think out loud — when I message you with a half-formed thought, no need to act on it; I'll usually clarify in a follow-up. If anything I send is actually urgent I'll mark it." They appreciated knowing what was a work-thinking message vs an actual ask.

4. Met in their style for hard topics. When I needed to disagree with a design decision, I wrote it up as a doc with reasoning, not a quick chat. That respected their deep-focus mode and gave them time to consider rather than react.

Result: The API change shipped clean and on time. We worked together on three further projects that quarter — still very different styles, but with mutual fluency in each other's mode. They later cited our collaboration in a peer review as one of their best of the year.

What I learned: communication-style differences usually aren't a personality clash — they're a working-mode mismatch. Adapting your style is cheaper and faster than trying to change theirs, and people remember the respect.

Why this works: shows adaptability, names the difference without blame, uses concrete tactics (batching, docs, marking urgency), and ends with mutual fluency rather than tolerance.