Job Application Email Templates: What to Write When You Apply (With Examples)

Most job search advice is about the resume and the interview. The part in between — the actual email you send — gets treated as an afterthought, something you dash off in ninety seconds so you can get back to refreshing job boards. That's a mistake, because for a real chunk of your applications, the email is the entire first impression. If you're applying through a big company's ATS portal, the system handles delivery and you never write more than a cover letter field. But the moment you're emailing a hiring manager directly, reaching out to a company that hasn't posted anything, following up on silence, or writing back after an interview, the words are entirely yours.

This is where otherwise strong candidates lose ground they didn't need to lose. Some send something so generic it could have gone to fifty different companies with a find-and-replace on the job title. Others don't send anything at all, assuming that once a resume is submitted the process just runs on its own. Neither approach helps you. A well-timed, specific email signals that you read the posting, that you understand what the role actually involves, and that you're not blasting your resume into a hundred inboxes hoping something sticks. A generic one, or a missing one, signals the opposite — even if that's not what you meant.

This guide walks through the four emails you'll actually need during a job search: the initial email when you're sending your resume directly rather than through a portal, the cold outreach email when there's no posting to respond to, the follow-up when you've applied and heard nothing back, and the thank-you note after an interview. Each section has a real template with a subject line and body text you can adapt, along with notes on what makes it work and where people typically get it wrong.

The initial application email: when you're sending your resume directly

This situation comes up more than people expect. Smaller companies often list an email address on their careers page instead of running a full ATS. A former colleague forwards you a hiring manager's contact and says "just email them, they know you're coming." A recruiter you spoke with on the phone asks you to send materials directly rather than through the portal. In all of these cases, there's no system standing between your resume and the person reading it — which means your email is doing work that a well-designed portal usually does for you: establishing who you are, why you're writing, and what you want them to do next.

The subject line

A subject line for a direct application email needs to answer one question in about six words: what is this, and who's it from. Skip anything cute or vague. The hiring manager is scanning an inbox, not browsing a newsletter.

• Application for Senior Backend Engineer — Maria Chen
• Backend Engineer Application (Referred by David Osei)
• Resume for Marketing Coordinator Role — Req #4521

If you were referred by someone the hiring manager knows, put that name in the subject line, not buried in paragraph two. It's the single fastest way to get an email opened instead of skimmed.

Template: emailing your resume for an open role

Subject: Backend Engineer Application — Maria Chen (Referred by David Osei)

Hi Priya, I'm applying for the Backend Engineer role posted on Lattice's careers page. David Osei, who works on your platform team, suggested I reach out directly — he thought my background in distributed systems would be a good match for what your team is building.

For the past three years I've built and maintained payment-processing services at Fenwick Labs, including a migration from a monolithic checkout system to event-driven microservices that noticeably cut latency during peak traffic. I've attached my resume, and I'd welcome the chance to talk through how that experience maps to your roadmap.

Thanks for considering my application. I'm glad to send anything else that would help, and I'm available whenever works for a call.

Best, Maria Chen · (555) 019-2231 · linkedin.com/in/mariachen

Why this works

Look at what the email is actually doing in five sentences. It names the specific role and where it was posted, so there's no ambiguity about what's being applied for. It leads with the referral, which is the single strongest piece of context a hiring manager can receive — it tells them someone they trust has already vetted this person informally. It gives one concrete, specific accomplishment instead of a list of adjectives, and it closes with an easy next step rather than a vague "looking forward to hearing from you." None of this requires more than four short paragraphs. If you're not sure whether your resume itself is doing the same kind of specific, concrete work, it's worth a look at how to write an ATS-friendly resume — many of the same principles about being specific rather than generic apply to both documents.

Notice also what's missing: no life story, no restating of the entire resume, no line about being a "hard worker" or a "team player." The email's only job is to get the resume opened and read with the right context in mind. Everything else belongs in the resume and, if the role calls for one, the cover letter — which is a different document than a motivation letter, worth understanding the distinction between if you're attaching one alongside the resume.

The cold outreach email: what to send when there's no job posting

This is a different animal from the application email above, because there's nothing to apply to. You've identified a company you want to work for, but their careers page is empty, or the only listing is for a completely unrelated role. This is sometimes called a job inquiry email — you're not responding to an opening, you're creating an opportunity where one might not visibly exist yet.

The instinct most people have here is to ask directly: "Do you have any openings?" That's a weak opener, because it puts the entire burden of the conversation on the recipient — they either have to say no and end it, or go find out on your behalf, which is a bigger ask than it sounds like. A university career center's guidance on inquiry letters is useful here: rather than opening with a request, UMBC's Career Center recommends leading with your interest in the organization and a clear picture of your qualifications, then proposing a specific, low-friction next step — a short call or meeting, rather than a job outright.

Template: cold outreach to a hiring manager

Subject: Question about the design team at Northline

Hi Tomas, I've been following Northline's work on the embedded lending product you launched earlier this year — it's the kind of problem I'd like to be working on. I'm a product designer with five years in fintech, most recently leading the redesign of the onboarding flow at Circa, which cut time-to-first-transaction significantly.

I don't see an open design role on your careers page right now, but I wanted to introduce myself in case that changes, or in case you'd be open to a fifteen-minute call so I can learn more about how the team is structured. I've attached my portfolio and resume.

Either way, thanks for reading this. I know unsolicited emails aren't always welcome, and I appreciate you taking a look.

Best, Jordan Reyes · jordanreyes.design · linkedin.com/in/jordanreyes

Why a small ask beats a big one

This email does two things well. First, it's specific about the company — naming an actual product launch, not a generic "I admire your mission" line that could apply to any company in the industry. Second, the ask at the end is small: a fifteen-minute call, not a job. That's easier for a busy hiring manager to say yes to, and it opens a conversation rather than forcing a binary answer. Indeed's guide to cold emailing for a job makes a similar point — framing the email around what you can offer, rather than what you're asking for, tends to land better than a direct request for employment.

Finding the right person to send this to matters as much as the writing. Don't send it to a general info@ inbox — look for the actual hiring manager or team lead on LinkedIn or the company's team page. If your own LinkedIn profile is thin, this is also the moment it matters most, since the person you're emailing will almost certainly click through to it before responding; optimizing your LinkedIn profile for recruiters is worth doing before you start sending cold emails, not after.

The follow-up email after applying with no response

Silence after applying is normal, not a signal that you did something wrong. Most companies are slower at reviewing applications than job seekers expect, and a follow-up email is a legitimate, low-risk way to nudge things along — as long as you get the timing and tone right.

Template: application follow-up

Subject: Following up — Marketing Coordinator Application (Maria Chen)

Hi Anna, I applied for the Marketing Coordinator role on July 14th and wanted to check in, since I haven't heard back yet. I'm still very interested — particularly in the campaign work your team has been doing around the fall product launch.

In my current role I manage a content calendar across four channels and grew organic email signups by a meaningful margin over the last two quarters, which feels directly relevant to what this role is asking for. If there's an update on timeline, or anything else useful for me to send, I'm glad to follow up.

Thanks for your time. Best, Maria Chen

How long to wait, and how many times

Indeed's guidance on following up on a job application recommends waiting seven to fourteen days after applying, or one to two days after a posted deadline passes, before sending anything. Send it earlier than that and you risk looking impatient before the hiring team has had a reasonable chance to review applications; wait much longer and the role may already be filled or the recruiter's attention has moved elsewhere. The same guidance is direct about one thing: if a posting explicitly says "no phone calls" or "no contact," respect it and skip the follow-up entirely — sending one anyway won't help your case.

One follow-up is usually the right amount. If you still hear nothing after that, a second note two or three weeks later is defensible, but a third starts to read as pressure rather than interest. And send it to the actual hiring manager or recruiter if you can find them, rather than a general HR inbox — a message addressed to a specific person is far more likely to get a reply than one sent into a shared inbox that ten other applications are also sitting in. If you're applying to enough roles that keeping track of who you followed up with (and when) is getting hard to manage on its own, it's worth reading how many jobs you should actually apply to per week — follow-up discipline gets harder, not easier, as volume goes up.

The thank-you email after an interview

This is the email people skip most often, usually because they assume the interview itself was the last real chance to make an impression. It isn't. A short, specific thank-you note is one of the cheapest, most effective things you can do in a job search, and it's frequently the only follow-up communication a hiring team receives from a candidate at all.

Timing matters more here than in any of the other email types. SHRM's guidance on post-interview thank-you notes recommends sending it within 24 hours of the interview, ideally the same day — sending it while you're still fresh in the interviewer's mind matters more than getting the wording perfect. If your interview runs late in the day, sending it first thing the next morning is fine; waiting two or three days is not.

Template: post-interview thank-you

Subject: Thank you — Backend Engineer interview

Hi Priya, thank you for taking the time to talk with me today about the Backend Engineer role. I enjoyed hearing about how the platform team is rethinking the event pipeline — it's exactly the kind of problem I'd want to be working on, and our conversation about the tradeoffs between throughput and consistency confirmed I'd genuinely like to be part of that work.

The migration project I mentioned, moving our checkout system off a monolith, ran into a lot of the same tradeoffs your team is navigating now, so I'd be glad to dig into that further whenever it's useful. Please let me know if there's anything else I can send in the meantime.

Looking forward to hearing about next steps. Best, Maria

Multiple interviewers? Send separate notes

If you spoke with more than one person, SHRM's guidance is to send each of them a brief, individual note rather than one message CC'ing the group. That means referencing something specific from each conversation — the same paragraph copy-pasted to three people is easy to spot and undoes most of the goodwill the gesture was meant to create. Keep each one short: acknowledge their time, reference one real detail from what you discussed, and restate interest without repeating your entire interview answer. If you're still refining how you talk about your own background in interviews generally, a strong answer to "tell me about yourself" tends to produce the same kind of specific, memorable details that make a good thank-you note easy to write afterward. And if the interview was remote, the small talk and context you'd normally pick up walking through an office is missing, so pay closer attention during the call itself — remote interview etiquette covers a few things worth doing differently on video.

What makes any of these emails actually work

The four templates above share a handful of underlying habits. If you understand why they work, you can write a good version of any of these emails without a template in front of you.

Specificity beats enthusiasm

"I'm very excited about this opportunity" tells the reader nothing, because every applicant writes some version of that sentence. "I've been following your work on embedded lending" tells them you did something before writing the email. Specificity is the cheapest, most reliable way to sound different from the other forty people who applied — it doesn't require better writing, just one extra sentence of actual research about the company, the product, or the person you're emailing.

Brevity is a signal, not just politeness

A long email doesn't read as more thorough. It reads as unedited. Every template above fits comfortably in four short paragraphs or fewer, because the goal isn't to restate your entire resume in prose — it's to give the reader enough context to open the attachment, remember who you are, or take the next step you're asking for. If you find yourself writing a sixth paragraph, cut it and see if the email still makes sense. It usually does.

End with one clear ask

Every email above ends with something concrete: a call, an update on timeline, a reply about next steps. Compare that to ending with "looking forward to hearing from you," which asks for nothing in particular and gives the reader no reason to act today rather than next week. A clear, small ask is easier to say yes to than a vague one, and it gives the recipient a specific reason to reply rather than just noting the email and moving on.

Professional without sounding like a form letter

There's a version of "professional" that reads as stiff — "I am writing to express my sincere interest in the aforementioned position" — and it does you no favors. Write the way you'd talk to a colleague you respect but don't know well yet: complete sentences, no slang, but also no throat-clearing phrases that exist only to sound formal. Contractions are fine. A sentence that starts with "I" is fine. The goal is to sound like a competent person wrote this in five minutes, not like it was generated from a mail-merge field.

Common mistakes that quietly kill your email

None of these are dramatic errors. They're small habits that make an email easy to skim past, and most job seekers do at least one of them without realizing it.

• Generic mass-email tone — "To Whom It May Concern" or "Dear Hiring Manager" when the recipient's name is findable on LinkedIn or the company site. It's a small detail, but it's the first thing that signals a template rather than a person.
• No subject line, or one so vague it gets lost — "Application," "Resume," or worse, a blank subject line that shows up as a re-send in the recipient's inbox.
• Attaching enormous files. A resume PDF should be well under a megabyte; if you're attaching a portfolio, embed a link instead of a 40MB file. Gmail's own limit for outgoing attachments is 25 MB per Google's support documentation, and anything approaching that gets auto-converted to a Drive link, which not every recipient will bother clicking.
• Following up too soon — sending a check-in two days after applying reads as impatient rather than eager, before a hiring team has had any realistic chance to review applications.
• Following up too aggressively — a third or fourth message after two unanswered follow-ups stops looking like interest and starts looking like pressure, which rarely helps a candidacy.
• Restating the whole resume in the email body. If the reader wanted a wall of text, the resume already provides one — the email's job is to add context, not duplicate content.
• Sloppy file names, like "resume_final_v3_USE THIS ONE.pdf." Name it FirstName_LastName_Resume.pdf. It looks like a small thing until you imagine a recruiter's downloads folder with forty resumes named "Untitled.pdf."
• No clear next step at the end of the email, leaving the reader unsure whether you're expecting a reply, a call, or nothing at all.
• Typos in the company name or the hiring manager's name — an easy, avoidable error that undercuts an otherwise strong message instantly.

Several of these overlap with mistakes people make in cover letters for the same reason: generic phrasing that could apply to any company, no specific detail that proves you actually read the posting. If any of the mistakes above sound familiar, it's worth a look at common cover letter mistakes that get candidates rejected — the underlying problem, writing something that could go to anyone, shows up in both documents.

Subject lines that actually get opened

The subject line decides whether the rest of your email gets read at all, which makes it worth more attention than most people give it. A few patterns work consistently well across all four email types in this guide.

• [Job Title] Application — [Your Name]
• [Job Title] Application (Referred by [Name])
• Following Up — [Job Title] Application
• Thank You — [Job Title] Interview
• Quick Question About the [Team Name] Team at [Company]

And a few patterns to avoid, because they either get ignored or read as spam:

• Anything with no job title or company name — recruiters manage dozens of open roles and won't know which one you mean.
• Excess punctuation or all caps, like "URGENT — PLEASE READ!!!" — it reads as a mass email, not a personal one.
• Overly casual openers like "Hey there!" in a subject line for a formal application — save the casual tone, if any, for the body.
• Subject lines longer than about eight or nine words — most inboxes truncate them anyway, and the important part gets cut off.

Attachments: format, size, and naming

Send your resume as a PDF unless the posting specifically asks for a Word document — PDFs preserve formatting across devices, while a .docx can shift fonts and spacing depending on what the recipient has installed. If you're also attaching a cover letter, keep it as a separate file rather than merging it into the resume PDF; some hiring managers only want one or the other, and a combined file makes that harder to navigate.

Keep total attachment size well under the ceiling most email providers enforce. As noted above, Gmail caps outgoing messages at 25 MB including attachments, and anything close to that limit risks landing as a Drive link the recipient has to click through rather than an attachment they can open directly. A resume PDF exported normally should land somewhere around 100–300 KB; if yours is several megabytes, it likely has an oversized embedded photo or an unnecessarily high-resolution export setting worth fixing before you send it anywhere.

Name your files the way you'd want them to show up in someone else's downloads folder next to thirty other applicants' resumes:

• MariaChen_Resume.pdf, not resume_final_v2.pdf
• MariaChen_CoverLetter.pdf, kept as a separate file from the resume
• JordanReyes_Portfolio.pdf or a portfolio link, not a 40 MB unoptimized export

Frequently asked questions

What should I write in the email when I send my resume?

Keep it to three or four short paragraphs: state the role you're applying for and how you found it (or who referred you), give one or two specific, quantified pieces of experience relevant to the job, mention that your resume is attached, and close with a clear, low-effort next step like being available for a call. Avoid restating your entire resume in prose — the email's job is to give context, not duplicate the attachment.

How soon should I send a follow-up email after applying?

Wait seven to fourteen days after submitting your application, or one to two days after a posted deadline passes, per Indeed's guidance on following up on job applications. Sending it sooner risks looking impatient before the hiring team has had a realistic chance to review applications. If the posting explicitly says not to contact them, skip the follow-up entirely.

What's a good subject line for a job inquiry email when there's no posting?

Something short and specific that names the team or area you're interested in, like "Question About the Design Team at [Company]" — avoid anything that sounds like you're asking whether they have openings in the subject line itself. Save that framing, softened into a small, specific ask, for the body of the email.

How long should I wait before sending a thank-you email after an interview?

Within 24 hours, and ideally the same day. SHRM's guidance on post-interview thank-you notes notes that sending it the same day keeps you top of mind while the interviewer is still comparing candidates, and that waiting much longer risks the message arriving after the hiring team has already moved on with their decision.

Is it okay to follow up more than once if I still haven't heard back?

One follow-up after the initial waiting period is standard and reasonable. A second, spaced two to three weeks after the first, is defensible if you're still genuinely interested. Beyond that, additional messages tend to read as pressure rather than enthusiasm, and your time is usually better spent applying elsewhere.

Should I attach my resume as a PDF or a Word document?

PDF, unless the job posting specifically requests a .docx file. A PDF preserves your formatting exactly as designed regardless of what software or device the recipient opens it with, while a Word document can shift fonts, spacing, and page breaks depending on their setup.

Write it once, adapt it every time

These four templates cover the entire lifecycle of a single application: the introduction, the outreach when there's no posting to respond to, the nudge when things go quiet, and the note that closes the loop after an interview. None of them need to be reinvented from scratch each time — swap in the specific detail about the company, the role, and your own background, and the underlying structure holds up across almost any application.

The harder part, in practice, is doing this consistently across dozens of applications a week without every email starting to sound the same. If you're applying at real volume, that's specifically what zeroApply's auto-apply tool is built to handle: it writes a tailored application email for each job based on your resume and the posting, and if you connect your Gmail account, it can send it — or leave it as a draft for you to review first — straight from your own inbox. How auto-apply works walks through the full process, or you can see pricing if you're ready to put it to use.