This is the deep dive on software-engineering subject lines. For the cross-role overview and the four universal patterns, start with cold email subject lines for jobs and come back here for the SWE-specific moves.
Why software engineers need a different playbook
Engineers spot marketing copy faster than any other audience. A subject line that reads as "produced by a recruiter" gets archived without a click. A subject line that sounds like another engineer wrote it — referencing a stack, a problem, a repo, a specific architectural choice — gets opened almost reflexively.
The hierarchy of credibility for engineering audiences is roughly: shipped code > conference talks > engineering blog posts > specific tech stack mentions > vague claims. Lean on the top of that hierarchy in your subject line and the open rate problem mostly solves itself.
Five rules specific to engineering subject lines
- Name the tech, not the role. "Backend engineer" is forgettable. "Built a similar Postgres sharding setup" isn't.
- Reference shipped work, not interest. "Interested in distributed systems" is empty. "Shipped a Raft implementation last year" is not.
- Show you read their engineering content. Engineering blogs, talks, OSS repos. Mentioning one of these outperforms almost everything else.
- Skip the corporate phrasing. Words like "synergy," "passionate," "dynamic" signal that this didn't come from engineering.
- Don't fake fluency. If you write "Re: your Kubernetes operator" and don't actually know what an operator is, the body of the email collapses on contact.
Subject lines by sub-discipline
A backend engineer reading their inbox cares about different signals than an iOS engineer or an SRE. Tune the subject to the sub-discipline.
Backend / distributed systems
- “Quick question about the Platform team”
- “Built a similar event pipeline at scale”
- “Re: your post on incremental materialization”
- “Backend engineer who shipped the same problem”
- “Saw the new query engine — would love to chat”
- “Re: hiring on the data infra team”
Frontend / mobile
- “Re: the new design system rebuild”
- “Frontend engineer who's shipped your stack”
- “Saw the React 19 migration post”
- “Quick question about the iOS team”
- “Re: the rewrite to SwiftUI”
- “Loved the new editor performance work”
Infrastructure / DevOps / SRE
- “Re: your Kubernetes migration post”
- “SRE who's run a similar incident program”
- “Quick question about the platform reliability team”
- “Saw the move from EKS to bare metal”
- “Built a similar CI pipeline last year”
- “Re: your incident retrospective post”
ML / AI engineering
- “Re: the new foundation model launch”
- “Quick question about the ML platform team”
- “Built similar inference infra at my last role”
- “Saw the post on RAG evaluation”
- “ML engineer with experience in your stack”
- “Re: the move to vLLM in production”
Subject lines by experience level
Senior, staff, principal
At this level, the subject line should signal that you've shipped real things and that you can engage on architecture, not just implementation. Keep it confident and specific.
- “Staff engineer who built your same architecture”
- “Senior backend, 8 years on distributed systems”
- “Principal eng with experience in your stack”
- “Re: the platform rebuild post — built a similar one”
- “Tech lead who shipped a similar migration”
Mid-level (3-7 years)
Mid-level is where most cold emails get sent. The subject line has to be specific and curious without overclaiming credibility you don't have.
- “Quick question about the Platform team”
- “Backend engineer who shipped a similar pipeline”
- “Re: the new pricing infra”
- “Saw your post on cache invalidation”
- “Engineer with two years on your stack”
Early career and new grads
Don't lead with what you don't have. Lead with something you actually built, even if small. A side project mentioned specifically beats a degree mentioned generically.
- “Built a tool inspired by your CLI”
- “CS senior who's used your API for two years”
- “New grad who shipped a similar thing in a hackathon”
- “Quick question about your new-grad pipeline”
- “Built something with your open-source tracer”
Subject lines that reference engineering content
These are the highest-converting subject lines in the entire playbook for engineering roles. If the company has any public engineering content — a blog, a talk, a repo, a tweet thread — find it and reference it. Specifically.
Referencing a tech stack choice
- “Re: your migration from Python to Rust”
- “Saw the move to TypeScript across the stack”
- “Re: your case for choosing Postgres over Mongo”
- “Followed your move from Kafka to Redpanda”
Referencing an open-source project or repo
- “Re: the open-sourced query engine”
- “Used your Rust HTTP client in a side project”
- “Contributed to your tracer last month”
- “Re: the issue I opened on your repo last week”
Referencing a conference talk or engineering blog post
- “Your KubeCon talk on tracing — quick question”
- “Re: your post on async cancellation in Rust”
- “Saw your QCon talk on cell-based architecture”
- “Re: the engineering blog post on rate limiting”
Startup vs big tech: what actually changes
At a small startup (under ~30 people), you're probably emailing a founder or one of the first engineers directly. The subject line can be looser and more direct. Founders read their own inboxes and appreciate brevity.
- “Founding engineer interested after the seed”
- “Want to help with the next launch”
- “Saw the announcement — quick question”
At a mid-stage startup (~30-300 people), you're likely emailing an engineering manager or tech lead. The patterns from the pillar work cleanly here — specific reference plus quick question.
At big tech (Google, Meta, Stripe at this size), the recipient is usually a recruiter or a senior IC, and their inbox is overflowing. The subject line has to be even more specific and even shorter. Skip cleverness — go straight to a single sharp signal.
- “Re: the engineering blog post on cell-based”
- “Senior eng with experience in the new infra team”
- “Backend engineer who shipped a similar migration”
What engineers see through immediately
These all look reasonable to non-engineers but get archived instantly by engineering audiences:
- "Passionate about [your tech]" with no proof. Passion without shipped artifacts means nothing.
- "Excited about your culture" — non-information, sounds like every other application.
- Listing skills without context. "Python, SQL, AWS, React" in a subject line says nothing about what you actually shipped.
- Buzzword bingo. If your subject line includes "blockchain," "AI-powered," or "disruptive" without specific technical context, it dies on impact.
- Pretending fluency. Mentioning a tech you don't actually understand. The follow-up call exposes it within 30 seconds.
- "Looking for an engineering opportunity"— generic and reads like a recruiter wrote it. You're an engineer, sound like one.
The research bottleneck
Every great SWE subject line above relies on one thing: real research about the company. Their engineering blog, their public repos, their talks, their tech stack. You can't fake this. You also can't scale it manually past 5-10 emails before it consumes your week.
dm-the-boss compresses that research. You enter a company and role, it pulls the company intel, finds engineers and managers worth contacting, and writes a subject line and email body using the patterns in this post and the pillar. You review every email in the app and send straight from your Gmail. Nothing leaves without your edit and your click.
Where to go next
- The pillar: cold email subject lines for jobs — the four cross-role patterns this post builds on.
- The exact cold email template that got me 5 interviews — what to put in the body once your subject earns the open.
- How to find anyone's work email — the unglamorous prerequisite.
Pick a company whose engineering blog you've actually read. Find the right engineer or manager. Use one of the patterns above. Send it.