Ten letters that say something. None are templates of air.

Dear [Hiring manager], I'm a senior backend engineer at [current company], where I own the billing service. The reason this role interests me: you're rebuilding payments, which is the exact problem I've spent the last four years on. My team cut failed charges 40 percent by moving the billing pipeline onto event-driven services, and shipped it without downtime. Two things I'd bring on day one: the same claw-your-way-through-p97 discipline, and the habit of writing design docs other people actually read. I've attached my resume; the scanner score on it is 100, but the parts matter more - my systems have carried 2M requests a day since 2023. I'm quietly looking, so no reference calls to my current employer please. Happy to talk any morning. Sincerely, [Name]

Dear [Hiring manager], Before software I spent five years as a systems administrator at [company], keeping a manufacturing floor's line-authentication running. The move to development wasn't a whim; it was the part of the job I kept doing after hours. I've since shipped two production pieces of tooling - a queue-depth dashboard in Python that paid for itself in the first sprint, and a fault-injection harness the QA team now runs nightly. The junior label is fair. What I know that other juniors don't: how production breaks at 3 a.m., and how to write the incident report so nobody repeats it. I'd rather earn seniority on your team than claim it somewhere else. Sincerely, [Name]

Dear [Hiring manager], [Referrer name], who leads design research on your team, suggested I write to you directly - so I have, and I've kept this short. I design interfaces that survive real users: my last three studies at [company] changed onboarding copy, doubled task completion, and killed two features the team loved but nobody used. Your open Product Designer role asks for "strong research instincts and pragmatic detail work" - both lines belong in the same sentence, and that's what I'd bring. My portfolio is attached. The [named case study] is the one I'd start with - it shows the fewest assumptions for a redesign that had to ship. Sincerely, [Name]

Dear [Hiring manager], I graduate from [university] this May with a statistics degree, and the honest headline on my transcript: I've run every analysis twice - once for the grade, once because I wanted the answer. Evidence beats adjectives, so here is mine. For my thesis I built a dataset of [number] municipal water readings and found that three of [city]'s key assumptions didn't hold for weekend sampling. The utilities department now collects weekend samples differently. That project taught me more about data cleaning and stakeholder communication than any course. I know the grad label means I'll need mentoring on your stack, and I'm fine saying that plainly. What I offer in return: fast SQL, careful notebooks, and the discipline to say "I don't know yet." Sincerely, [Name]

Dear [Hiring manager], I ran logistics for a [size]-person distributor for six years before taking two years off for family care. The gap is addressed in one line here and one line on my resume - and then I'd rather talk about the job. The job is a fit for a plain reason: the last thing I did before the gap, and the first thing after, was the same thing your posting asks for. I rebuilt a returns process that cut a 5-day cycle to 2 days, trained a team on it, paired it to a dashboard, and documented it so well the next manager inherited it without a single question. I return to work with sharper documentation habits and a real sense of what a whole day costs. Sincerely, [Name]

Dear [Hiring manager], Thank you for the decision note. You chose the candidate with deeper paid-social experience, and I'd have made the same call. Two things. First, the door: if the scope shifts in six months or the role reopens, I'd like to be first in line - my growth work at [company] is a fit for the whole funnel, not just the top. Second, the ask: allow me to stay subscribed to your team's job feed, and if you'd share the one skill that tipped the scale, you'll help me close a real gap. Either way, your product is the one I recommend when friends ask. Keep shipping. Sincerely, [Name]

Dear [Hiring manager], You're hiring remotely, so here's the evidence instead of the promise: three years of fully remote work at [company], with a written handover habit that let me take three weeks of leave last December without a single escalation thread. The overlap hours matter - I hold 9-5 your time zone and publish a Friday recap that my old manager used verbatim in her skip-level updates. My playbook at [company]: every account gets a health score, every risk gets an owner, and every renewal conversation gets written up the same day. Your posting's renewal-rate target is the metric I've carried for the last two years - currently [percent] at [company]. I'd be glad to do a working session on a sample account instead of another interview round about hypotheticals. Sincerely, [Name]

Dear [Hiring manager], Two questions in the interview process will be about why a [years]-year engineer is coming to a [size]-person team. Here's the answer before the questions. I want scope, not staff. At [big company] I ran the [system] for [number] engineers, and the two years I found myself proudest were the two where I also wrote the code. Your job description says the person owns the whole pipeline - ingestion to billing - and writes the incident reviews themselves. That's a better use of the next five years than more meetings about the pipeline. The way I work: I pair early, write things down, and leave systems a successor can read. Those habits transfer; the rest I'll happily learn. Sincerely, [Name]

Dear [Hiring manager], Your mission statement is the reason I applied, so I'll be straight about the rest: I've spent four years running programs, not advocating from the sidelines. At [organization] I coordinated [program], which served [number] families; the part I'm proudest of is the volunteer retention rate going from 40 to 70 percent after I rebuilt the scheduling. Two relevant facts you'd want to know. I treat budgets like promises - the last three years, the program landed within 2 percent of plan. And I write honestly, including to funders when numbers miss. Missions attract people who talk. I've spent my career being one of the people who fills the form in on time. Sincerely, [Name]

Dear [Name], You don't have a posted opening for what I do - I checked carefully, and that's the point of this note. I sell to manufacturing plants, which is whom you sell software to. At [company], cold outbound to [region] plants landed [number] demos in two quarters. I'm writing to you because your last three product posts name the exact objection I've built scripts around: plants don't buy new software until the foreman likes it. If a role opens, I'd like the email to be a callback, not a cold start. If it doesn't, you'll at least have one less cold email to ignore someday - this one has a resume attached and a specific reason to reply. Sincerely, [Name]