Most bad cold-email subject lines aren't obviously bad — they look professional. They feel safe. They're what most candidates default to. And they're the reason most cold emails go unread.
For the patterns that actually work, see cold email subject lines for jobs. This post is the inverse: twelve common patterns that look fine, fail consistently, and what to send instead.
The twelve worst patterns
1. The job-application title
What gets archived
“Application for Senior Software Engineer — Sarah Chen”
It looks professional, but it reads as automated. The whole point of cold emailing is to skip the application. Don't make the email look like the application you're trying to bypass.
What to send instead
“Quick question about the Platform team”
2. The single-word greeting
What gets archived
“Hello”
Spam filters love it, hiring managers don't. Single-word greeting subjects are the most common spam pattern there is. Even if it lands in the inbox, no one opens it.
What to send instead
“Re: your post on the new pricing experiment”
3. The resume attachment subject
What gets archived
“Sarah Chen — Resume”
They didn't ask for a resume. The subject implies you're sending unsolicited attachments, which most security filters flag. Even when it lands, the recipient hasn't agreed to invest the attention an attachment requires.
What to send instead
“Backend engineer who shipped your same architecture”
4. The reverse-pitch question
What gets archived
“Opportunity at Stripe?”
It frames the recipient as gatekeeper of an opportunity you're asking for. The whole subject is about your need. Reverse the framing: lead with what you bring.
What to send instead
“Built a similar billing system at my last role”
5. The all-caps shouter
What gets archived
“URGENT: SENIOR ENGINEER LOOKING FOR ROLE”
Caps trigger spam classifiers. They also signal sales-y energy that hiring managers archive on sight. Even one all-caps word in the subject hurts.
What to send instead
“Senior engineer with experience on the new platform team”
6. The exclamation-mark-stack
What gets archived
“Excited to apply!!!”
Multiple exclamation marks read as junior or as marketer-energy. One exclamation mark is debatable. Two or more is decided.
What to send instead
“Quick question about the engineering team”
7. The emoji bomb
What gets archived
“🚀 Excited to join your team! 🚀”
Works in B2C marketing. Fails in cold outreach to senior people. The emoji signals you treat this like a marketing send, not a 1:1 message. Skip them entirely.
What to send instead
“Re: the engineering blog post on cell-based”
8. The "quick favor"
What gets archived
“Quick favor — got a minute?”
It frames the recipient as doing you a favor before you've told them anything. Reverse the polarity: lead with what's in it for them, or with a specific question they'd enjoy answering.
What to send instead
“Quick question about your migration to Rust”
9. The buzzword stack
What gets archived
“AI-powered, blockchain-savvy senior engineer”
Trying too hard to land on every keyword. Reads as someone optimizing for ATS, not someone reaching out to a human. Pick one specific signal.
What to send instead
“ML engineer who built a similar inference platform”
10. The vague enthusiasm line
What gets archived
“Excited about the great culture at Stripe”
Says nothing specific about you, the company, or the role. "Great culture" is the lowest-information phrase in cold email. Replace with one concrete observation.
What to send instead
“Re: the public engineering principles document”
11. The follow-up counter
What gets archived
“Follow-up #2”
Numbering follow-ups makes recipients feel watched and tracked. The honest way to follow up is to bump the original thread, or to write a clean new subject without a counter.
What to send instead
“Re: Quick question about the Platform team”
12. The full-pitch subject
What gets archived
“Senior backend engineer with 8 years in distributed systems applying to your platform team”
The subject does the body's job. It's also too long — most clients truncate after 50 characters and the recipient sees a fragment. The subject should earn the open; the body should earn the reply.
What to send instead
“Quick question about the Platform team”
The pattern behind the patterns
Every bad subject line above shares one of two underlying problems: it's either generic (could be sent to anyone) or it front-loads the ask (signals need before signaling value). The good versions invert one or both of those — they're specific to the recipient or the company, and they signal something about the sender that the recipient might find interesting.
One more anti-pattern: stuffing personalization tokens
If you're using a sequencing tool, double-check that your mail merge variables actually filled in. Subject lines like "Quick question about [team_name]" with the placeholder still visible are the fastest way to get filed under "mass send." This happens more often than people admit.
Where to go next
- The pillar: cold email subject lines for jobs — the four patterns that actually work.
- The cold email template that got me 5 interviews
- What hiring managers actually think when they get a cold email