Four rules
- Be specific. Name the role, the technology or the project. "Internship" alone could be about anything.
- Keep it short. Phones show about 40 to 60 characters. Put the important words first.
- Sound like a person. Sentence case, no tricks, no brackets or emoji.
- Promise only what the email delivers. A subject that implies a connection or an application you don't have gets the email deleted.
Patterns that work
Subject line patterns
| Pattern | Example | Use it when |
|---|---|---|
| Role and proof | Backend intern, built a rate limiter in Go | You are writing about a specific role |
| A direct question | Question about the backend intern role | A posting exists and you want to confirm it |
| Project first | Student who built a webhook retry service | You're writing to an engineer |
| Shared context | VIT student, question about the payments team | You share a school or a community |
| Reply thread | Re: Backend intern, built a rate limiter in Go | Following up |
25 examples
Use these as shapes, not as text to copy. Replace the details with your own, and don't claim anything that isn't true.
Role and proof
- Backend intern, built a rate limiter in Go
- Frontend intern with a shipped React app
- Data engineering intern, built a Spark pipeline
- ML intern, wrote a retrieval evaluation set
- SDE intern from June, open-source contributor
A direct question
- Question about the backend intern role
- Is the data intern role still open?
- Do you take interns for platform work?
- Who should I write to about internships?
- Quick question about intern timing
Project first
- Student who built a webhook retry service
- A job queue in Go, and a question
- What I learned building a Raft key-value store
- I fixed a bug in your open-source library
- Small tool built on your API, feedback welcome
Shared context
- VIT student, question about the payments team
- IIT alum, question about your team
- We met at the Bangalore Go meetup
- Following your talk on connection pooling
- From the Hacktoberfest thread, a question
Follow-ups
- Re: Backend intern, built a rate limiter in Go
- Re: Question about the backend intern role
- Re: A job queue in Go, and a question
- One more note, then I'll stop
- Re: Student who built a webhook retry service
What to avoid
Subject lines to avoid
| Avoid | Why |
|---|---|
| URGENT: Internship opportunity!!! | Reads as spam. Spam filters also look for urgency words and punctuation. |
| Application for software intern | Too generic and too formal. It could come from anyone. |
| Hello | Tells them nothing, so there's no reason to open it. |
| Re: our conversation | Implies a conversation that never happened. It gets you marked as spam. |
| Looking for opportunities | It's about what you want, not what you offer. |
A quick test
Read the subject as if you knew nothing about the sender. Would you open it? Does it match what the email says? Is anything in it a claim you can't back up? If you can't answer yes, no and no, rewrite it.
Frequently asked questions
- How long should a cold email subject line be?
- Under about 50 characters. Phones cut subjects off at roughly 40 to 60, so put the important words first.
- Should I put my name in the subject?
- Not usually. Their inbox already shows your name next to the subject. Spend the characters on the role or the project.
- Should I use "Re:" to get them to open it?
- No. Only use it in a real reply thread. Faking a conversation gets you flagged and loses trust.
- Are emoji or brackets okay?
- Leave them out. They look like marketing, and some filters treat them as spam signals.