In 2023, I would have told you cover letters in tech are theater. Write something inoffensive, hit submit, move on. The resume does the work.
I think that’s still roughly true for obvious strong candidates. Where cover letters actually matter is in the 40% of applications that are on the fence, which is, depending on the role, a lot of people.
The thing is, most tech cover letters aren’t read. They’re scanned for about 8 seconds, according to eye-tracking research on recruiter behavior that’s been replicated several times over the past decade. In those 8 seconds, the recruiter is looking for two things: a reason to keep reading, and a reason to stop. Most cover letters give them the second thing immediately.
The first sentence is doing almost all the work
Not the first paragraph. The first sentence.
The most common opening I see from engineers: “I am writing to express my interest in the Senior Software Engineer position at [Company].” That sentence contains no information the recruiter doesn’t already have. They know you’re interested. You applied. They know what role it is. They posted it.
A better opening is a specific claim about a relevant thing you did. “The checkout flow I redesigned at Acme reduced abandonment by 23% and brought in two other payment methods the team had been trying to ship for a year.” That’s a sentence with content. It tells the recruiter something they didn’t know. It also tells them you can quantify work and care about outcomes, not just activity.
If you don’t have a number, you can use specificity instead. “The team I joined was shipping once a month. We got to daily deploys in about eight months, mostly by killing a release process that had seventeen manual approval steps.” Still concrete. Still shows reasoning.
The four-paragraph template is fine as scaffolding, not as a script
Hook, match, proof, close. You’ll see this structure in basically every cover letter guide. It works as a starting point because it forces you to answer the recruiter’s actual questions: what did you do, why do you fit, can you prove it, what do you want next.
Where people go wrong is treating it as a fill-in-the-blank. They write:
“I am excited about [Company]’s mission to [restate the mission statement]. With my experience in [list of skills from job posting], I believe I would be a strong fit for this role.”
That’s not a cover letter. That’s a mirror held up to the job description. It signals nothing except that you can read and restate.
What the template should produce is something that answers: what specific thing about this role or company made you apply to this one instead of the 12 others like it? That question has a real answer or it doesn’t. If it doesn’t, the letter will feel hollow no matter how well-structured it is.
What actually gets through to engineers vs non-engineers in the screening process
A lot of job applications at tech companies get screened first by a recruiter, not an engineer. This matters because the recruiter isn’t reading for technical depth, they’re reading for signals that you understand what the role requires and that you can communicate clearly.
The cover letter that’s heavy on acronyms and architecture diagrams described in text is not helping you here. The recruiter doesn’t know what gRPC is. They do know that “I reduced API latency by 40% by switching from a synchronous request pattern to an event-driven one” sounds like something with a measurable outcome. That’s what gets forwarded.
For purely technical roles at companies with a technical recruiter, this is less of an issue. But at most mid-sized companies, the first human to see your application is not the hiring manager. Write the cover letter for that person first.
Senior roles need a different letter entirely
At L5 and above, the cover letter (when read) is being evaluated for something different. The recruiter and hiring manager want to know whether you can lead, influence without authority, and make decisions about trade-offs rather than just executing someone else’s decisions.
This changes what you should write about. “Led a team of seven engineers” is table stakes for a staff role. “Convinced a reluctant VP to kill a three-year-old product that was consuming 30% of the team’s maintenance burden” is the kind of decision-making that gets attention at senior levels.
The LinkedIn Economic Graph research on hiring has consistently shown that communication and stakeholder management are among the fastest-growing requirements in senior technical roles. A cover letter for a staff or principal position should reflect that, not just list technical outputs.
The research problem nobody solves well
Cover letter guides always say “do your research on the company.” Almost nobody does meaningful research. They read the about page and the blog post from six months ago and mention “I was impressed by your recent post on reliability engineering.”
Meaningful research means knowing something specific that the company has been working on that isn’t on the homepage. Their engineering blog, recent conference talks by their engineers, GitHub repos if they have public ones, job postings from the past three months (which tell you where they’re investing). If you know the company just acquired a new team and the role you’re applying to is probably adjacent to that acquisition, you can say something real about why you’re interested.
That level of specificity is what separates the cover letters that get read from the ones that get scanned for 8 seconds and closed.
A few things that consistently hurt tech cover letters
Longer isn’t better. One page, three to four tight paragraphs. Anything longer signals you don’t edit.
Restating your resume in prose is not a cover letter. The recruiter has your resume open in a different tab. The cover letter should say things the resume can’t: context, motivation, reasoning.
Avoid phrases like “I am passionate about” unless you follow them immediately with evidence. The BLS Occupational Outlook Handbook projects 17% growth in software developer roles through 2033, which means recruiters at desirable companies are reading a lot of these. “Passionate about” reads as filler by the third application of the day.
Proofread. Seriously. An engineer applying for a job that requires precision and attention to detail who submits a cover letter with typos is making a statement about their work quality, whether they intend to or not.
The cover letter doesn’t get you the job. It gets you the first conversation. That’s it. Keep that scope in mind and the whole thing gets simpler.