Every job-search email, drafted from your details

18 situations. Four tones. No [placeholders].

A job hunt is maybe two cover letters and twenty short emails. The short ones decide more than people expect, and they are where candidates lose ground quietly — not by writing badly, but by not knowing what the email is supposed to contain, or by not sending it at all.

The thank-you after an interview is the clearest example. Most candidates skip it, and most who send one write a courtesy note that adds nothing. Its real job is a second attempt at the one answer you fumbled: you have had an hour to think since, and this is the only sanctioned way to use that. Reference something specific from the conversation so it cannot read as a template, add the point you under-sold, keep it to five lines, send it within a day.

Chasing a decision is the one people agonise over most and get wrong in a predictable way. The instinct is to apologise for following up, which frames the question as an imposition. Reference the timeline they gave you instead — "you mentioned decisions by the 14th" — which makes it a reasonable question about a commitment they made, and gives them something concrete to answer. Short, dated, unbothered.

Negotiation email has one structural rule that matters more than any phrasing: open by making clear you want the job. Without that, a number reads as a threat to walk. With it, it reads as someone solving the last problem between them and a yes. Then give one number with a reason attached, not a range — ranges get you the bottom of the range — and say what happens when it is met: you sign, and you give notice.

The two most under-used are the reference request and the thank-you-after-advice. People decline references mainly because they cannot recall enough detail to be specific and do not want to sound lukewarm; remind them of the exact work you shared and you remove that. And almost nobody closes the loop with someone who gave them advice, which is exactly why doing it turns a one-off favour into a person invested in how you get on.

Every template here fills from details you enter, and any field you leave blank drops its sentence rather than leaving a bracketed placeholder in the draft — an email with [Company] in it is worse than one sentence shorter, because it looks like a mail-merge failure the moment it lands. Nothing is uploaded; the drafting runs in your browser.

• ✓18 situations: applying, interviewing, offers, at work, networking
• ✓Four tones — professional, warm, brief, formal
• ✓Blank fields are dropped, never left as [placeholders]
• ✓A "why this works" note and a worked example for each
• ✓Free, no signup, runs in your browser

What each email actually does, beyond being polite

A job-search email is not about manners; it is about information transfer and timing. A thank-you email after an interview looks polite on its surface, but its real job is to correct or emphasise something from the conversation. Most thank-yous skip this and just say "thanks for your time," which is why most thank-yous do not matter. A good thank-you references one specific thing from the interview—a question you fumbled and now have a better answer for, or a project they described that you recognised from industry writing and you have a relevant comment. It says "I have been thinking since we spoke, and here is more value." That thank-you gets read and remembered. The polite one gets filed.

A follow-up email when you have not heard back is about removing ambiguity. The instinct is to apologise for the follow-up, which frames the question as an imposition: "I hope I am not bothering you." Wrong framing. They gave you a timeline—"decisions by Friday"—and you are asking whether that timeline held. Reference that commitment. "You mentioned you would be making decisions by Friday; I wanted to check where things stand." That is a reasonable question about a commitment they made, not an imposition. Short, dated, unbothered.

A request for a reference is about specificity. Most people decline references because they cannot recall the work clearly enough to give a real reference, and they do not want to sound lukewarm. You fix that by reminding them of the exact work you shared. Not "we worked on a project together" but "you were the lead on the e-commerce rebuild where I rewrote the checkout page and we got mobile conversion up 18 percent." That detail means they do not have to scramble for memories and they can now give a specific reference. A referral request works the same way: tell them exactly who you are applying to and why, so they can make the introduction confidently or explain why they cannot.

Declining an offer without burning bridges for future opportunities

Turning down a job offer is simple in structure but feels emotionally complex because someone chose you and you are saying no thank you. The email should be short, say no clearly, and leave the door open for future conversations. Long explanations are usually rationalising the decision to yourself rather than helping them. They asked if you want the job; the answer is no. "Thank you for the offer. After careful consideration, I have decided to pursue another opportunity. I appreciated learning about the role and the team, and I hope we might stay in touch." That is it. Full stop.

The only time you need to explain is if they explicitly ask for feedback on why you declined. Even then, keep it to one sentence: you accepted another role, you decided the timing was not right, you realised the role did not align with your career direction. Do not critique the company, the salary, the team or the culture. Do not say "I got a better offer" unless they specifically ask. Decline with grace and you might get another opportunity at the company later. Vent and you have burned it.

There is a practical reason to leave the door open: companies remember good candidates and sometimes come back to them. An engineer who turned down one role but stayed professional might get called for a different, better role six months later. An engineer who turned them down sourly gets a pass. The second reason is references. If you work with someone from that company in the future and they check on you, the reference-checker will ask your previous contacts about you. Declining with grace is protecting your reputation with a wider network than you think you have.

The thank-you-for-advice email most people never send

Someone takes an hour to give you career advice, feedback on your resume, or an introduction to someone useful. Most people thank them in a message and then disappear. That favour fades. If you circle back in a month and say "I took your advice on X, I was rejected for it, but I learnt Y," or better yet, "I took your advice on X and I got an interview at Z," you have turned a one-off favour into invested interest. The person now cares about how your search goes. They will notice your LinkedIn message when you update it. They will think of you for future opportunities. They will refer you. One follow-up email after the outcome transforms the nature of the relationship.

The email should land within a month of the advice and again be specific. "You suggested I focus on startup product roles rather than agency roles. I took that to heart and applied to three companies. I got through the first round at Acme but was cut after the second. I learned that I need to read more deeply on metric-driven product priorities." That is real information. They now know their advice had an impact. They know what you are working on. They know where the gap is. The next advice they give you, if you ask, will be more targeted because they know how you work.

This is also why you do not ghost people who helped you. Someone gave you a referral and you never told them whether it worked out. Someone gave you feedback and you never mentioned that you used it. That is not their job to follow up on; it is yours. A thirty-second email saying "thanks for the feedback, I made X change and got to the interview stage" costs you nothing and banks relationship capital. People want to help people who keep them informed. They do not want to help people who vanish and then show up asking for another favour.

Frequently asked questions

Part of JobStraight — the honest AI job-search platform. Runs in your browser; your data stays on your device.