Situation: I worked closely with a senior backend engineer who had an extremely blunt, terse communication style in pull requests and design reviews, which initially created tension and defensive reactions across the squad.
Task: I needed to establish an effective, respectful working relationship with him so we could collaborate productively on our shared API migration project.
Action: Rather than reacting defensively or venting to peers, I scheduled an informal coffee chat with him. I learned that English was his second language and that his brevity was an effort to be efficient rather than dismissive. I also realized he held immense domain expertise and valued direct, data-backed technical arguments above all else. I adapted my approach: I engaged him with concise bullet points, framed my architectural suggestions around concrete performance metrics, and sought his early input before publishing RFCs. I also encouraged him to share the rationale behind his PR comments.
Result: Our mutual understanding grew into one of the most productive partnerships on the team. We co-authored our company's core API conventions, and our collaborative dynamic set a strong model for professional empathy across the engineering organization.