Email subject lines for a hiring manager

A good subject line names the role and you: "Data analyst application — Sam Rivera." Add the job or requisition ID if the ad lists one, and a referrer's name when you have one. Put the role first, because that is what the reader looks for.

What goes in the line

Four pieces of information do most of the work. Use the ones that apply, and leave the rest out rather than padding the line.

• The role title, written the way the ad writes it. If the posting says "Senior Product Designer", use that, not "designer". A hiring manager may be running several searches at once, and the title tells them which one you mean. If the title is generic — "Analyst", "Engineer" — add the team, the location or the company name.
• Your name. It tells the reader this is a person rather than a newsletter, and it makes the thread easy to find later when they search for you.
• The job or requisition ID, when the ad gives one. Larger employers often list a reference such as "Req 24-1180". Including it saves the reader a lookup and shows you read the posting. In replies to Applier's own introductions, one recruiter's whole answer was a request for the reference number.
• A referrer's name, when you have one. "Referred by Priya Raman" belongs in the subject if a current employee pointed you to the role and agreed to be named. Don't name someone who hasn't agreed to it.

Two things to leave out: your availability and your ask. "Free for a call any weekday" and "would love 15 minutes" belong in the body, where they have room to be polite. The subject line only has to get the message opened.

One thing to make obvious, in the subject or the first sentence: that you've already applied. In Applier's own records from October 2026, the most common reply to an introduction, 16 of 40, was a request to apply through the job ad, even though every application was already in. A subject that starts with "Application:" and a first line that says you've applied make it plain. Here's what 981 introductions got back.

Keep it short, and front-load the role

You'll find advice that a subject line must sit under some exact number of characters. The published research doesn't support a specific figure. A 2022 study in Review of Managerial Science looked at 5,765 promotional emails sent to 455 million users in 73 countries between 2013 and 2018 and found no direct relationship between subject-line length and open rates. The authors also say they didn't control for the device people read on, and note that with so many emails opened on phones, a reader may judge a message on only its first few characters.

That is the practical case for front-loading, and it isn't about a character count: the end of the line may never be seen. Role first, name second, everything optional after that. If the line still runs long, cut adjectives — "Application: Data Analyst — Sam Rivera" rather than "Application for the exciting Senior Data Analyst opportunity — Sam Rivera" — instead of dropping the role or the reference number.

Example subject lines by situation

These assume a fictional candidate, Sam Rivera, applying for a data analyst role. Swap in your own details and keep the shape.

Follow-ups: reply, don't restart

When you follow up, reply to your own sent message rather than starting a new one. The subject stays the same, the earlier note sits underneath, and the reader can see what you already said without hunting for it. A new thread with a new line makes them do that work, and it can read as a separate cold email rather than a nudge.

Replying also keeps the "Re:" honest. Google's guidelines for email senders tell senders to keep headers and content accurate and not to start a subject line with "Re:" or "Fwd:" unless the message really is a reply or a forward. In a reply, both the prefix and the thread are true.

The one good reason to start fresh is a genuinely different subject — a different role at the same company, say — and then the new role title should carry the new line. Otherwise stay in the thread. A common schedule, and the one Applier uses, is a first follow-up 3 business days after your introduction and a second 7 business days after it. Our guide to following up after a job application covers what to say in each note.

What to avoid

• A fake "Re:" or "Fwd:". It implies a conversation that never happened, and the reader will open it to an empty thread. Google's sender guidelines say not to use either prefix unless the message is an actual reply or forward. US law takes the same view of commercial email: under 15 U.S.C. § 7704(a)(2), it is unlawful to send a commercial email whose subject heading is likely to mislead a reasonable recipient about a material fact about the message. A note to one company about one job usually isn't commercial email, so the statute likely doesn't reach it. The question it asks — is this line true? — is still the right one.
• All caps and exclamation marks. "URGENT: DATA ANALYST!!!" reads like bulk mail and spends the visible words on volume instead of the role. Sentence case is enough for a professional email.
• Emojis. Google's guidelines tell senders not to use emojis or other non-standard characters to imitate graphic elements with the intent to deceive or influence recipients. Even setting that aside, a symbol takes the space where the job title would sit, and a hiring manager has no reason to decode it.
• Vague openers. "Quick question", "Following up" and "Hello" tell the reader nothing about the role or about you. The same study treats the sender name and subject line as the only information a person has before opening, which is exactly why an empty subject wastes the one chance you get.
• Invented urgency or deadlines. "Final notice" on a first email isn't true, and "time-sensitive" claims a deadline the posting doesn't have. If a real deadline exists — an application window closing — say so plainly in the body.
• A wall of brackets. "RE: [URGENT] Application for [Role] at [Company] – [Your Name] – [Phone]" looks like a template that was never filled in. One or two brackets at most.

Tone at a startup versus a large company

The information in the line stays the same. What changes is how much context the reader already has, and how the company writes about itself.

• Small company or startup. A founder or a department head often owns the role and reads their own inbox, so a bare "Data Analyst — Sam Rivera" is enough. There is usually no requisition number to add, and no coordinator filtering first. A short, plain line matches how the team writes to candidates.
• Large employer. A recruiter or coordinator may read your email before the hiring manager does, and one title can be open on several teams. Include the reference number and the team or location: "Data Analyst, Payments (Req 24-1180) — Sam Rivera". Being specific is not coldness; it is what makes the email routable.
• Either way. Mirror the company's own wording. If the ad says "Data Analyst II", don't flatten it to "analyst". Skip "Dear Sir/Madam" and skip first-name familiarity you haven't earned — use the person's name if you know it, and see our guide to finding the hiring manager if you don't.

Check the line before you send

1. Does it name the role the way the ad does?
2. Is your name in it?
3. Is the reference number there, if the ad has one?
4. Is a referrer named, and did they agree to be?
5. Does it still work if the reader sees only the first few words?
6. Would you open it if it landed in your own inbox?

If you'd rather not write from scratch, the free hiring manager email templates include a subject line and body for the introduction and for two follow-ups, with the role and your name already in place. For whether to send the email at all, and who should get it, see emailing the hiring manager after applying.

One line decides whether the rest gets read. Get the role and your name into the first few words, and the body of the email can do the rest of the work.

How Applier handles this

After Applier submits an application on the employer's own site, it writes a short introduction, subject line included, to people on the hiring team and sends it from your own Gmail: 1 contact per application on Starter and during the free trial, 2 on Pro and 3 on Max. Each introduction carries the resume tailored to that job as a PDF, and follow-ups go as replies in the same thread 3 and 7 business days later, so the subject line stays the same.

Introductions start in Review mode, so you see each subject line, body and attachment and approve or decline it before it's sent. Replies show in your dashboard as needing you. What Applier does in your Gmail · every Applier feature.

Related guides

• Should you email the hiring manager after applying?
• Should you attach your resume when emailing a hiring manager?
• When to follow up after a job application

Frequently asked questions

What should the subject line of an email to a hiring manager say?

Name the role the way the job ad writes it and add your name, for example "Data Analyst — Sam Rivera". Add the job or requisition ID if the posting lists one, and a referrer's name if a current employee pointed you to the role and agreed to be named.

How long should the subject line be?

Short enough that the role and your name survive on a phone screen. A 2022 study of promotional email found no direct link between subject-line length and open rates, so there is no magic character count; the reason to keep it short is that the end of the line may be cut off, so put the role first.

Should a follow-up use the same subject line?

Yes. Reply to your own sent message so the thread and its history stay together, and don't put a "Re:" on a new email: Google's sender guidelines say the prefix belongs only on real replies or forwards. Start a new subject only when the topic really changes, such as a different role at the same company.

Sources

1. May I have your attention, please? An investigation on opening effectiveness in e-mail marketing, Review of Managerial Science (Springer), 2022
2. Email sender guidelines, Gmail Help (Google), 2026
3. 15 U.S. Code § 7704 - Other protections for users of commercial electronic mail (CAN-SPAM), Legal Information Institute, Cornell Law School, 2003