Subject lines for an email to a hiring manager
Name the role. That is the entire job of this subject line — the manager may have three requisitions open and will not guess which one you mean. “Application for Senior Backend Engineer — Maria Kovacs” beats anything clever, every time.
Twenty worked lines
Each one is a real shape. Swap in your role, your name, your date — and keep the role inside the first 35 characters, because that is roughly where a phone cuts it off.
| Subject line | Verdict | Use it when |
|---|---|---|
Application for Senior Backend Engineer - Maria Kovacs | The default. Role plus name, nothing else. | You applied and want to be findable in their inbox and their ATS. |
Backend Engineer application - applied Tuesday | Adds a date the manager can search on. | The company runs a big requisition and timing helps them place you. |
Senior PM role (req 4471) - Daniel Osei | Strongest at large employers. The req number removes all ambiguity. | The posting carries a visible requisition number. |
Data Analyst role - one question before I apply | Honest about why you are writing, and the question earns the open. | Something in the posting is ambiguous and the answer changes your application. |
Referred by Katrin Weiss - Solutions Engineer role | The best subject line available to you. Use it whenever it is true. | Someone inside the company told you to write. |
Re: Application for Senior Backend Engineer - Maria Kovacs | Only as a reply on your own thread. Never fake the Re:. | You are sending the single follow-up five to seven days later. |
Is the Content Lead role still live? | A real question with a one-word answer. Gets replies from busy people. | The posting has been up for months or was reposted. |
Platform Engineer - we spoke in March | Reactivates a real memory in six words. | They interviewed you before and a better-fitting role has opened. |
Marketing role - applied Friday, one thing to add | Promises new information rather than repetition. | You have something genuinely new since your application. |
Junior UX Designer application - Ben Aliyev | Junior candidates gain nothing from cleverness. Be findable. | Entry level, career change, internship. |
Analytics Engineer role on your team - internal | The word internal changes who opens it and how fast. | You already work at the company. |
Summer product internship - applied Monday | Plain and dated. Internship inboxes are high-volume. | Internships and placements, where the manager is a team lead. |
Your first marketing hire - applied Friday | Names the job as the founder thinks of it, not as HR wrote it. | Companies under about fifty people, writing to the founder. |
Finance Manager application - Ines Almeida | Boring on purpose. Boring is the correct register here. | Regulated industries, formal cultures, senior finance and legal roles. |
Checkout latency - Senior Backend Engineer application | Leads with their problem instead of your paperwork. Higher ceiling, higher risk. | The posting names one specific technical problem and you have solved it. |
Question about the Staff Engineer scope | Works when the question is real. Reads as a trick when it is not. | You genuinely need an answer before applying. |
Applied for Product Designer - portfolio attached below | Sets the expectation that there is something to look at. | Portfolio roles, where the work is the argument. |
Nurse Practitioner role - available from March | Availability in the subject saves a round trip in shift-based hiring. | Healthcare, hospitality, logistics — anywhere start date drives the decision. |
Backend Engineer - relocating to Berlin in May | Answers the objection before it is raised. | You are out of area and the role is on-site. |
Following up on the Data Analyst role - Priya Raman | Fine as a follow-up. Weak as a first contact, because it repeats nothing. | Second and final message on a thread that already exists. |
Five that get deleted unopened
| Subject line | Why it fails | Use it when |
|---|---|---|
Quick question | Reads as sales. Gets archived without opening. | Never, on a first contact. |
Following up | No role, no name, nothing to place you against. | Never on its own — pair it with the role. |
Excited about this opportunity! | Says what everyone says, plus an exclamation mark that reads as junior. | Never. |
Job application | A manager with three open requisitions cannot act on this. | Never. |
Are you still hiring?? Please read | Double punctuation and a plea. Both push the message toward spam scoring. | Never. |
Where the line gets cut
Gmail on an iPhone shows roughly the first 35 characters of a subject. Gmail on desktop shows about 70 when the reading pane is closed and fewer when it is open. Outlook lands around 60. Nothing you write past character 50 can be relied on to be seen before the message is opened.
Which settles the ordering argument. Role first, name second, everything else after that. Maria Kovacs - application for Senior Backend Engineer truncates to a stranger's name on a phone; Application for Senior Backend Engineer - Maria Kovacs truncates to something the manager can act on.
What pushes it toward spam
- All caps on any word, including URGENT and the role name.
- Stacked punctuation — two question marks, an exclamation mark after a question.
- Money and urgency words in a hiring context: free, guaranteed, act now, limited.
- Emoji. They survive the filter and fail the reader, which is worse.
- A faked Re: or Fwd: on a thread that does not exist.
The bigger deliverability factor is not the subject at all — it is the attachment. A resume attached to a first message from an unknown sender raises the spam score more than any wording choice. Offer it in the body and let them ask.
Writing yours
Write the body first. Find the one thing it is actually about. Then name that in under 50 characters, put your name at the end, and stop. Subject lines written before the body describe the act of emailing — following up, quick question, touching base — rather than the content, which is exactly why those three fail.
The rest of the email: how to write it line by line and twelve finished examples.
Two facts every strong line needs
Look back at the twenty that work and they all depend on the same two things: the exact role title as the employer writes it, and the manager's name. Neither is optional. A subject line built on “the marketing position” when the requisition says “Growth Marketing Manager, DACH” fails the search the manager runs a week later, and a line addressed to nobody in particular gets sorted with everything else addressed to nobody in particular.
Take the role title verbatim from the posting rather than from the job board listing, which often rewrites it. Where to get the name: how to find out who the hiring manager is.
Questions
What should the subject line of an email to a hiring manager say?
The role. A manager may have three requisitions open and will not guess which one you mean. Role plus your name — “Application for Senior Backend Engineer — Maria Kovacs” — is the reliable default and beats anything clever.
How long should the subject line be?
Aim for 35 to 50 characters. Gmail on a phone shows roughly 35 before cutting, and Outlook desktop shows around 60. Put the role in the first 35 characters and let anything else fall off the end.
Should the subject line include my name?
Yes, at the end. It makes the message findable later, when the manager is looking for you rather than reading their inbox. Put it after the role, never before it.
Do question marks in subject lines hurt?
A genuine question performs well — “Is the Content Lead role still live?” gets answered. Manufactured curiosity does not, and stacked punctuation raises spam scores.
Can I use “Re:” if there is no previous thread?
No. Faking a reply is the single fastest way to lose a manager's goodwill, and modern clients make it obvious. Use Re: only on your own real follow-up.
Should I write the subject line first or last?
Last. Write the body, find the one thing it is actually about, then name it. Subject lines written first tend to describe the act of emailing rather than the content.