Free lesson · The Job Search System

Cover Letters: When They Matter and When They Don't

Easy11 min readjob-searchcareerresume

Cover Letters: When They Matter and When They Don't

Student: Swati, I've heard conflicting advice about cover letters. Some people say they're dead - nobody reads them. Others say they're essential. What's the truth?

Swati: The truth is that both sides are right, and both are wrong - because they're answering different questions. The real question isn't "are cover letters important?" It's "are cover letters important for this specific application?" And the answer depends on the company, the role, the stage of your career, and whether you have a non-obvious story to tell.

Let me give you the honest breakdown.

The 80/20 Reality

For roughly 80% of standard tech job applications - applying to a mid-to-large tech company for a software engineering role through their careers page - nobody reads your cover letter. The recruiter is screening your resume. The ATS is parsing your resume. The hiring manager is evaluating your resume. The cover letter, if you uploaded one, sits in a field that most people skip.

I know this because I've been on the hiring side at Google for years. When I'm reviewing a stack of candidates, I read resumes. I almost never click through to cover letters for standard engineering applications. The resume tells me everything I need to know about technical qualifications, and the interview tells me about communication and fit.

Student: So why do companies even ask for them?

Swati: Two reasons. First, some application systems include a cover letter field by default - it's a legacy feature from when cover letters were universally expected. Second, for some roles and some companies, cover letters genuinely do matter. The 20% where they matter is where the value is, and knowing which situations fall into that 20% saves you from wasting time on the 80% while missing opportunities in the 20%.

When Cover Letters Matter

Here are the specific situations where a cover letter can change the outcome of your application:

1. Startup Applications

At a startup with fewer than 200 employees, the hiring process is more personal. The founder or engineering leader might be the one reviewing applications. They're not just looking for technical qualifications - they're looking for someone who understands what they're building and why it matters. A cover letter that demonstrates you understand their product, their market, and their technical challenges signals genuine interest in a way a resume cannot.

Student: Why is that different from a large company?

Swati: Volume. Google receives hundreds of thousands of applications per year. No one at Google is reading cover letters for standard SWE roles - there isn't time. A 30-person startup receives maybe 100 applications for an engineering role. The hiring manager might read every one. In that context, a well-written cover letter that says "I used your product, I noticed you're using React with a Go backend, and I have experience with exactly that stack" creates a genuine advantage.

2. Career Switcher Applications

If your resume tells a non-obvious story - financial analyst turned software engineer, teacher turned data scientist, military veteran turned DevOps engineer - a cover letter explains the narrative. Without it, the recruiter sees a resume that doesn't fit the pattern they're used to and moves on. With it, the recruiter understands the deliberate career transition and evaluates you accordingly.

Olena's cover letter to Zalando is the best example I know. She'll tell you about it in the next topic. But the short version: her resume said "financial analyst at PwC." Without a cover letter, she's a confusing applicant. With a cover letter explaining her transition and connecting her analytical background to engineering, she's an intriguing one.

3. Internal Transfers and Referrals

When you're applying internally at your current company or being referred by someone, a brief cover letter or message that accompanies your resume provides context. "I'm on the Search Infrastructure team and I'm looking to move into the ML team because I've been working on ranking models in my 20% time" is context that helps the receiving manager understand why you're a fit.

4. Non-Standard Roles

Product engineering, developer experience, developer relations, technical program management, and roles that blend engineering with communication - these roles value written communication as a core skill. A well-written cover letter is a demonstration of that skill.

5. Companies That Explicitly Request One

If the job posting says "please include a cover letter explaining why you're interested in this role," write one. Not writing one when explicitly asked signals that you didn't read the posting carefully - which is worse than writing a mediocre one.

graph TD
    A["Should I Write<br/>a Cover Letter?"] --> B{"Is it explicitly<br/>requested?"}
    B -->|Yes| C["✅ Write one<br/>It was asked for"]
    B -->|No| D{"Is it a startup<br/>under 200 people?"}
    D -->|Yes| E["✅ Write one<br/>It'll likely be read"]
    D -->|No| F{"Are you a career<br/>switcher or non-traditional?"}
    F -->|Yes| G["✅ Write one<br/>Explain your story"]
    F -->|No| H{"Is it an internal<br/>transfer or referral?"}
    H -->|Yes| I["✅ Brief note<br/>explaining context"]
    H -->|No| J{"Standard SWE role<br/>at a large company?"}
    J -->|Yes| K["⏭️ Skip it<br/>Focus on your resume"]

    style C fill:#51cf66,color:#fff
    style E fill:#51cf66,color:#fff
    style G fill:#51cf66,color:#fff
    style I fill:#339af0,color:#fff
    style K fill:#868e96,color:#fff

This decision tree helps determine whether to write a cover letter. If it's explicitly requested, write one. If it's a startup under 200 people, write one because it'll likely be read. If you're a career switcher or have a non-traditional background, write one to explain your story. If it's an internal transfer or referral, write a brief note explaining context. If it's a standard software engineering role at a large company and none of the above apply, skip it and focus on your resume.

When Cover Letters Hurt

Student: Can a cover letter actually hurt me?

Swati: Yes. A bad cover letter is worse than no cover letter. Here's when it hurts:

Generic templates. "I am writing to express my interest in the Software Engineer position at your esteemed company. With my strong background in computer science, I believe I would be a valuable addition to your team." If this is your cover letter, it communicates that you used a template, you didn't research the company, and you have nothing specific to say. That's a negative signal. No cover letter is better.

Repeating your resume. If your cover letter just restates what your resume says - "In my current role, I build microservices using Java and Spring Boot" - it adds zero information. The hiring manager already has your resume. If the cover letter doesn't add something new - context, motivation, narrative - it's wasted words.

Excessive length. A cover letter that runs beyond one page signals poor editing judgment. If you can't make your case in 250 to 400 words, you're including unnecessary content. Engineers are expected to communicate concisely. A rambling cover letter undermines that expectation.

Desperation or excessive flattery. "I have always dreamed of working at Google since I was 12 years old. It would be the greatest honor of my career to join your team." This doesn't convey passion - it conveys dependence. The hiring manager wants to hire someone who would make the team better, not someone who thinks the team would make them better.

Warning: The generic cover letter is worse than no cover letter. If you can't spend 20 minutes writing a cover letter that mentions the company by name, references something specific about their product or engineering challenges, and connects your experience to their needs - don't write one at all. A generic letter signals laziness. Silence at least signals neutrality.

The ROI Calculation

Student: It sounds like writing a cover letter for every application isn't worth it. But for some applications it's very worth it. How do I decide where to invest the time?

Swati: Think of it as an investment portfolio. Your time is the capital. Each application is an investment. The question is where the marginal return is highest.

The key insight: cover letters are a targeted weapon, not a standard-issue tool. Use them selectively and invest the time you save on the 80% of applications that don't need them into resume tailoring and networking - both of which have higher baseline returns.

Tip: The 5-application rule: For every batch of applications you send, identify the top 5 that you care most about. Write cover letters for those 5. Skip cover letters for the rest. This ensures you're investing your highest-quality writing effort where it matters most, without burning time on applications where the cover letter won't be read.

If you're using the AlgoInsight Jobs Portal to find and apply to roles, use the portal's company-size filters to identify startups where cover letters carry the most weight.

The Cover Letter as a Signal

Student: You keep using the word "signal." What exactly is a cover letter signaling?

Swati: Three things that a resume cannot:

1. Motivation - why this company specifically. Your resume says what you can do. Your cover letter says why you want to do it here. "I've been following your work on distributed inference optimization, and the technical challenges in your recent engineering blog post about multi-model serving resonate with problems I've solved at scale." That tells the reader you've done your homework and you have a genuine reason to apply here rather than everywhere.

2. Narrative coherence - how your story connects. For career switchers, returners, and anyone with a non-linear path, the cover letter provides the thread that ties your experiences together into a coherent direction. The resume shows the dots. The cover letter connects them.

3. Communication quality - can you write? For roles where written communication is a core competency (technical writing, developer relations, product engineering), the cover letter is a writing sample. A well-structured, clearly articulated, appropriately concise cover letter demonstrates the skill directly.

graph LR
    subgraph "Resume Alone"
        A1["What you CAN do<br/>Skills, experience, metrics"] --> B1["Hiring manager infers<br/>motivation and fit"]
        B1 --> C1["Inference may be<br/>wrong or incomplete"]
    end

    subgraph "Resume + Cover Letter"
        A2["What you CAN do<br/>Skills, experience, metrics"] --> B2["WHY you want to<br/>do it HERE"]
        B2 --> C2["Hiring manager gets<br/>the full picture"]
    end

    style C1 fill:#ff6b6b,color:#fff
    style C2 fill:#51cf66,color:#fff

This diagram compares two scenarios side by side. With a resume alone, the hiring manager sees what you can do through skills, experience, and metrics, and then has to infer your motivation and fit - and that inference may be wrong or incomplete. With a resume plus cover letter, the hiring manager sees both what you can do and why you want to do it at their specific company, giving them the full picture. The cover letter fills the gap between capability and intent.

Student: So the cover letter fills the gap between "can you do this job" and "do you actually want this specific job."

Swati: Precisely. And for most standard engineering applications, the hiring manager doesn't need that second question answered in writing - the interview handles it. But for the five situations I listed above, answering it in writing gives you an edge before the interview even starts.

There's also a meta-signal that most candidates miss: the act of writing a targeted cover letter signals effort and selectivity. A hiring manager who sees a cover letter that clearly took 20 minutes to write - referencing their specific tech stack, their recent blog post, their product challenges - knows that you didn't spray this application to 50 companies. You chose THEM. That selectivity is flattering and creates a reciprocal attention.

This is especially powerful at startups where the hiring manager is often the founder or CTO. They've poured their life into this company. A candidate who demonstrates that they understand and care about the mission? That candidate gets a closer look every time.

Important: A cover letter is not a plea - it's a pitch. The difference matters. A plea says "please consider me, I really want this job." A pitch says "here's why I'm the right person for this specific challenge." Pleas create obligation. Pitches create interest. Every sentence in your cover letter should create interest, not obligation.

Formatting and Logistics

A few practical points:

Length: 250 to 400 words maximum. That's roughly one page with standard margins. Shorter is better than longer.

Format: If the application system has a text field, paste your cover letter as plain text (no formatting, no letterhead). If it asks for a file upload, use a clean PDF that matches your resume's visual style.

Addressing: If you know the hiring manager's name, use it: "Dear [Name]." If you don't, "Dear Hiring Team" is fine. Don't use "To Whom It May Concern" - it sounds like you're writing to a government agency in 1997.

Subject line (for email applications): "[Role Title] Application - [Your Name]". Clear, scannable, professional.

Interview: Your Cover Letter Sets Up Interview Conversations

A well-written cover letter creates conversation starters for the interview. If your cover letter mentions a specific engineering challenge at the company, the interviewer might ask about it. If it references your career transition story, the interviewer has context before you walk in.

This is a strategic advantage. Instead of answering "Why do you want to work here?" cold, you've already planted the seed with your cover letter. Your verbal answer reinforces what they've already read, creating consistency and credibility. "As I mentioned in my application, I've been following your distributed inference work, and here's how my experience at Meta maps to those challenges..."

Exercise: Starter: Look at your last 10 job applications. For how many did you write a cover letter? For how many should you have written one, based on the decision tree in this lesson? Identify the missed opportunities.

Intermediate: Pick one application where a cover letter would have made a difference - a startup, a career-switch role, or a dream company. Write a 300-word cover letter for it using the signals framework: why this company, how your story connects, and what you bring specifically. Even if you've already applied, this is practice for the next one.

Advanced: Research 3 companies you'd like to apply to. For each, find one specific thing about their engineering work that genuinely interests you - a blog post, an open-source project, a product feature, a technical challenge mentioned in the JD. Write the "why this company" paragraph for each. This paragraph is the hardest part of any cover letter, and practicing it makes the full letter dramatically easier to write.

Student: I've been writing generic cover letters for every application and getting nowhere. Now I realize I should be skipping most of them and writing really good ones for the 20% where they matter.

Swati: Exactly. And in the next topic, Olena and I are going to show you exactly how to write one that gets read. She'll share the actual cover letter strategy that got her the Zalando interview - the one that changed her career.

Let's go.

Back to The Job Search System