You have the address. The compose window is open. This page is about the hundred-odd words that go in it — which line does what, what to put in each one, and what to delete.
Read this if: you know who you are writing to and need the wording.
Read instead: whether to send it at all and when, how to find the address, 12 finished examples, and every situation in one table.
The five lines and what each one does
Every email to a hiring manager that gets answered does the same five jobs. Anything beyond them is padding.
- Subject. Tells them which of their open roles this is about, before they open it.
- Context line. States that you applied, and when.
- Evidence line. One result they could check, tied to something the posting actually asks for.
- Relevance line. Why this team and not a hundred others.
- Ask. One question small enough to answer with a yes.
Five lines, roughly 75 to 125 words. A hiring manager reading on a phone between meetings sees about the first 40 before deciding whether to keep going.
The subject line
Name the role. That is the whole job of a subject line here. The manager may have three requisitions open and will not guess which one you mean.
Application for Senior Backend Engineer - Maria Kovacs
Backend Engineer application - quick question
Senior PM role (req 4471) - applied TuesdayNo question marks, no capitals for emphasis, no curiosity gap. "Quick question" on its own reads as sales. "Following up" without a role name reads as a mass send. Both get archived unopened.
The context line
One sentence. You applied, for this role, on this day. It answers the first thing the manager wonders, which is whether you are already in the pile or trying to skip it.
I applied for the Senior Backend Engineer role on Tuesday through your careers page.
Say the date. It signals you are following a process rather than firing off cold notes, and it gives the manager something to search their ATS for.
The evidence line
This is the line the whole email exists for. One result, specific enough that someone could go and verify it, connected to a problem named in the posting.
Weak:
I have extensive experience scaling backend systems in high-growth environments.
Checkable:
At Zalando I cut p99 latency on the checkout service from 1.4s to 310ms over two quarters — your posting mentions checkout reliability as the first priority.
The second version is not longer by much. It is specific, and specificity is the only thing separating your email from the other four the manager got that week. If you cannot name a number, name a thing you built and who used it.
The relevance line
One sentence on why this company. It has to be something you could not copy-paste into an email to their competitor. A product decision they made, a change in the market they are responding to, something in the posting that reads like it was written by a person with a problem.
If nothing comes to mind after five minutes on their site, cut the line. An empty compliment does more damage than a missing sentence. "I have long admired your commitment to innovation" tells the manager you know nothing about them.
The ask
Ask for the smallest thing that moves you forward. A yes to a small question is easy. A yes to twenty minutes on their calendar is a decision, and decisions get postponed.
- Works: "Would it help if I sent the two most relevant projects?"
- Works: "Is this still open, or has it moved to final rounds?"
- Works: "Happy to answer anything about my background — just reply here."
- Too heavy: "Do you have 30 minutes this week for a call?"
- Too heavy: "Could you forward my resume to the right person?"
Word budget
Between 75 and 125 words in the body — emails of 50–125 words see roughly 50% higher reply rates than longer ones, per the Instantly 2026 benchmark. Below 60 you have not given the manager anything to act on. Above 150 you are asking for a reading commitment from someone who has 200 unread messages.
Write the draft, then delete every sentence that would still be true if you were applying somewhere else. What survives is usually the right length already.
Three rewrites
Rewrite 1: the cover letter in an inbox
Before, 210 words:
Dear Hiring Manager,
I hope this email finds you well. I am writing to express my strong
interest in the Marketing Manager position at your esteemed company,
which I discovered on LinkedIn. With over 7 years of progressive
experience in digital marketing, I believe I would be an excellent
fit for this role and your organization.
Throughout my career I have developed a comprehensive skill set
spanning SEO, paid acquisition, content strategy and marketing
automation. I am passionate about data-driven marketing and have a
proven track record of delivering results...After, 84 words:
Hi Anna,
I applied for the Marketing Manager role on Monday.
Last year I took Payhawk's paid acquisition from EUR 140 to EUR 61
blended CAC while tripling spend. Your posting says the first job is
getting CAC down before the Series C — that is the exact problem I
spent eighteen months on.
I know the German market side of it less well than the UK. Happy to
talk about that too.
Worth a look at my last two campaigns?
MartaWhat changed: the greeting uses her name, the claim carries two numbers, the weakness is stated rather than hidden, and the ask is answerable in one word. The admission about Germany is the part that gets replies — it reads like a person, not a candidate.
Rewrite 2: the note with nothing in it
Before:
Hi,
Just applied for the data analyst role and wanted to flag my
application. Really excited about the opportunity, would love to
chat!
Thanks!After:
Hi Tom,
I applied for the Data Analyst role yesterday.
The posting mentions you are moving reporting off spreadsheets. I did
that at Hellofresh - rebuilt 40-odd operational reports into dbt
models, and the ops team stopped asking me for numbers because they
could get them.
Anything specific you want to see from my side?
PriyaThe first version contains no information. It costs the manager time and returns nothing, which is why it gets no reply rather than a rejection.
Rewrite 3: the career changer
Before:
Dear Hiring Team,
Although my background is in teaching, I am eager to transition into
UX design and am confident that my transferable skills in
communication, empathy and problem-solving make me a strong
candidate...After:
Hi Sofia,
I applied for the Junior UX Designer role on Thursday.
I taught secondary maths for six years, then spent last year
redesigning the parent portal our school used - 900 families,
support tickets about it dropped by roughly two thirds after we
shipped. That is the project in my portfolio, and it is why I
changed direction.
I am junior at this. Happy to do a task if that is easier than
reading a portfolio.
Ben"Transferable skills" is a phrase that appears in career-change emails and nowhere else in the language. Replacing it with one thing he actually shipped does the same work and sounds like a human.
Phrases to cut
- "I hope this email finds you well." Eleven wasted words in the position where you have the most attention.
- "I am writing to express my interest in..." They can see that you are writing.
- "I am passionate about..." Unverifiable. Show the thing you did because you were interested.
- "Proven track record." If it were proven you would be citing it.
- "I would love the opportunity to..." Ask directly.
- "Please find my resume attached." Attachments on a first cold message trip spam filters. Offer to send it.
- Anything in brackets. One unreplaced
[Company Name]ends the conversation.
When you have no impressive number
Most people writing this email are not sitting on a metric. That is fine — the evidence line does not have to be a number. It has to be checkable.
- A thing that exists. A repo, a shipped feature, a report someone still uses.
- A scale. How many users, tickets, accounts, students, or square metres you handled.
- A decision you made. What you chose, what it cost, what happened after.
- A named tool at a named place. "Ran the Salesforce migration at a 60-person insurer" beats any adjective.
Say the thing plainly and stop. Volunteering a limitation — you are junior, you have not worked in this sector, you are relocating — reads as confidence rather than weakness, and managers reply to it far more often than they reply to polish.
Where a generated draft helps, and where it does not
A draft written from the job posting and your own profile solves the blank-page problem and gets the five lines in the right order. It cannot know that the manager gave a talk about the exact migration you ran, and it will reach for a confident register when the honest register works better.
Treat the generated version as the skeleton. Then do three things by hand: replace the evidence line with your most checkable result, add the one detail that proves you looked at this company, and cut whatever sentence you would not say out loud.
DearHiringManager writes that first draft from the job posting and your LinkedIn profile, alongside the manager's name and verified address, so the version you edit already names the right role and the right person.
Works with LinkedIn, Indeed, Greenhouse, Lever, and company career pages.
More on the trade-off: can a hiring manager tell your email was written by AI.
Send it, then stop
One email. If nothing comes back, one follow-up five to seven days later, and then you let it go — a second follow-up moves nothing and costs you the next role at that company. The no-response playbook covers the timing.
FAQ
How long should an email to a hiring manager be?
Between 75 and 125 words in the body, which is four to six sentences. That fits on a phone screen without scrolling, which is where most of these are read.
What do I say if I have not applied yet?
Say that. "I am about to apply for the Backend Engineer role and wanted to ask one thing first" is a legitimate opening, and the answer often tells you whether applying is worth it. Everything else in the structure stays the same.
Should I attach my resume?
Not on the first message. Attachments from unknown senders raise spam scores and a manager who wants the resume can pull it from the ATS. Offer to send it and let them ask.
How do I open the email if I do not know their name?
Spend ten more minutes looking — the name is usually findable and it changes the response rate. If it genuinely is not, see the verdict on every common greeting; the short version is that no salutation at all beats an invented one.
Do I write differently to a recruiter?
The structure holds, but the evidence line changes. A recruiter is screening against a requirements list, so lead with the requirement you clearly meet. A hiring manager is thinking about a problem, so lead with the problem you have solved before. The difference between the two decides which one you get.
Is one email enough?
One email plus one follow-up. Reply rates for a short, specific note to the right person land in the 10–20% range against 2–5% for a portal application on its own (see job search statistics), so most of your emails will go unanswered and that is the normal outcome rather than a signal about you.
