Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Communication Skills

Technical skills get you in the door. Communication skills determine how far you go. This section covers the communication skills that matter most in tech careers — from explaining complex technical concepts to writing clear documentation.

Why Communication Matters

  • Interviews: You can solve a problem perfectly but fail if you can’t explain your approach
  • On the job: Engineers spend 30-50% of their time communicating — code reviews, design docs, meetings
  • Career growth: Senior+ engineers are distinguished as much by communication as by technical skill
  • Team effectiveness: Clear communication prevents misunderstandings, reduces bugs, speeds up delivery

What’s In This Section

GuideWhat It Covers
Technical CommunicationExplaining code, architecture, whiteboard communication
Interview CommunicationHow to communicate during interviews, asking questions
Written CommunicationDocumentation, emails, technical writing, design docs

The Communication Spectrum

Technical communication exists on a spectrum:

← More Technical                                    More Accessible →
Code Comments → API Docs → Design Docs → Tech Talks → Blog Posts → User Docs

Great engineers can operate across this spectrum, adjusting their communication to their audience.

Core Principles

1. Know Your Audience

  • For other engineers: Use technical terms, focus on implementation details
  • For product managers: Focus on user impact, timelines, tradeoffs
  • For executives: Focus on business impact, high-level architecture, risks
  • For non-technical stakeholders: Use analogies, avoid jargon, focus on outcomes

2. Structure Your Communication

Every piece of communication should have:

  • A clear purpose — What do you want the audience to know/do?
  • Context — Why does this matter?
  • The core message — The key point, stated clearly
  • Supporting details — Evidence, examples, data
  • A conclusion/action — What happens next?

3. Be Concise

  • Respect people’s time
  • Lead with the most important information
  • Cut unnecessary words and tangents
  • Use bullet points for scannability

4. Be Precise

  • Use specific numbers, not “a lot” or “many”
  • Name specific technologies, not “some tools”
  • Give concrete examples, not abstract concepts
  • Avoid ambiguity — say what you mean

5. Practice Active Listening

Communication is bidirectional:

  • Listen fully before responding
  • Ask clarifying questions
  • Paraphrase to confirm understanding
  • Acknowledge others’ points before presenting yours

Quick Wins

In Interviews

  • Think out loud — show your reasoning process
  • Ask clarifying questions before diving in
  • Admit what you don’t know — honesty > bluffing
  • Summarize before moving to the next topic

In Writing

  • Use the inverted pyramid — most important info first
  • Write in active voice
  • Keep paragraphs short (3-5 sentences)
  • Use headers and bullet points for scannability

In Conversations

  • Adjust technical depth to your audience
  • Use analogies to explain complex concepts
  • Check for understanding regularly
  • Be comfortable with silence — don’t rush to fill it

Growth Path

LevelCommunication Expectations
JuniorClear code comments, good questions, status updates
MidDesign docs, code review feedback, technical discussions
SeniorArchitecture proposals, cross-team alignment, mentoring
Staff+Technical vision, org-wide communication, external thought leadership

Start building these skills now — they compound over your career.