The backstory
Earlier this year, I was job searching. I'd been applying through company websites and job boards for three weeks. I'd submitted over 40 applications. I got exactly two automated rejections and zero interviews.
So I tried something different. I stopped applying online entirely and switched to cold emailing hiring managers directly. Over the next two weeks, I emailed 22 people at 12 companies. Five of them turned into interviews. Two turned into offers.
Here's the exact template I used, a line-by-line breakdown of why it works, and the variations I tested.
The template
This is the email, word for word. I'll break down every section after.
Subject line:
Quick question about the [Team Name] team
Hi [First Name],
I saw [Company] just [specific recent event — funding round, product launch, acquisition, blog post]. [One sentence about why that caught your attention, connecting it to your experience or interests.]
I'm a [your title] with [X years] of experience in [core skill]. Most recently at [Current/Last Company], I [one specific accomplishment with a measurable result].
I'd love to learn more about what you're building on the [Team Name] team. Would you be open to a quick 15-minute chat this week or next?
Either way, thanks for your time — I know your inbox is busy.
Best,
[Your Name]
That's it. Five short paragraphs. Under 120 words. Takes about 30 seconds to read.
Why every line matters
Let me walk through each part and explain why it's there — and why changing any of it tends to hurt your response rate.
The subject line
"Quick question about the [Team Name] team"
This works for three reasons. First, it's short — most email clients cut off subject lines after 40-50 characters, especially on mobile. Second, "quick question" is curiosity-inducing without being clickbait. Third, mentioning the specific team name signals that this isn't a mass email.
I tested other subject lines. "Interested in [Company]" performed about the same. "Senior [Role] — interested in joining [Company]" performed slightly worse — it's longer and it front-loads your ask, which makes it easy to dismiss without opening.
The opening line
"I saw [Company] just [specific recent event]..."
This is the single most important line in the email. It proves you didn't send this to 50 people. You're referencing something specific that happened recently — a funding round, a product launch, a blog post, a conference talk.
Where to find this: the company's blog, their Twitter/X account, TechCrunch or industry press, or the hiring manager's own LinkedIn posts. It takes 3-5 minutes of research but it's what separates a response from the trash folder.
The second sentence connects that event to something you care about or have experience with. This creates a bridge between their world and yours. For example:
- "I saw Acme just launched their new API platform. I spent the last two years building developer tools at [Company], so the problems you're solving are really close to what I've been working on."
- "I read your post about migrating to Kubernetes — we did something similar at [Company] last year and I found the tradeoffs fascinating."
The credential
"I'm a [title] with [X years] in [skill]. At [Company], I [accomplishment]."
Two sentences, max. You need to establish credibility, but you're not writing a cover letter. The accomplishment should be specific and, if possible, include a number. Numbers are credibility shortcuts:
- "Led a team of 6 engineers shipping a real-time analytics pipeline"
- "Reduced page load time by 40% across the product"
- "Grew the design system from 12 to 80+ components"
Avoid vague claims like "passionate about building great products" or "strong communicator." Everyone says that. One concrete result is worth ten adjectives.
The ask
"Would you be open to a quick 15-minute chat this week or next?"
This is carefully calibrated. You're not asking for a job. You're not asking for a referral. You're asking for 15 minutes — a commitment so small it's hard to refuse.
"This week or next" creates gentle urgency without being pushy. It signals that you're available and flexible, not desperate.
I tested asking for a "coffee chat" instead. Results were similar, but "15-minute chat" performed slightly better — probably because it's more specific about the time commitment.
The sign-off
"Either way, thanks for your time — I know your inbox is busy."
This line does two things. "Either way" gives them an easy out, which paradoxically makes them more likely to respond. Nobody likes feeling trapped. And acknowledging that their inbox is busy shows empathy — you're a real person who respects their time, not a bot blasting templates.
A real example
Here's one of the actual emails I sent (names changed). This one resulted in a 45-minute call and eventually an offer:
Subject line:
Quick question about the Platform team
Hi Marcus,
I saw Northwind just open-sourced their query engine last month — the approach to incremental materialization is really clever. I built something similar (much smaller scale) at my current company and ran into a lot of the same cache invalidation challenges your team wrote about.
I'm a senior backend engineer with 5 years of experience in distributed systems. At Contoso, I designed the event processing pipeline that handles ~2M events/day with sub-second latency.
I'd love to learn more about what you're building on the Platform team. Would you be open to a quick 15-minute chat this week or next?
Either way, thanks for your time — I know your inbox is busy.
Best,
Alex
Total word count: 127. Reading time: about 25 seconds. The response came 4 hours later: "Hey Alex, that's cool you've been working on similar stuff. Let's chat — how's Thursday at 2pm?"
The follow-up template
About half my interviews came after a follow-up email, not the initial send. If you don't hear back within 3-5 business days, send this:
Hi [First Name],
Just bumping this in case it got buried — I know things get hectic. Still would love to chat about the [Team Name] team if you have 15 minutes. No pressure either way.
Best,
[Your Name]
That's it. Three sentences. Don't re-explain who you are or repeat your pitch — the original email is right below in the thread. Don't apologize for following up. Don't send more than one follow-up unless you have something genuinely new to add.
What I'd change looking back
After 22 emails and a lot of reflection, here's what I'd do differently:
- Research more, email fewer. My best responses came from emails where I spent 10+ minutes researching the person and company. My worst came from emails I rushed through. Five deeply personalized emails beat ten surface-level ones every time.
- Target 2-3 people per company. I made the mistake of only emailing one person at some companies. If that person is busy or not hiring, you're done. Emailing the hiring manager plus a team lead or senior IC gives you multiple shots.
- Always follow up. I skipped follow-ups on a few early emails because I felt awkward about it. At least two of my interviews came from the follow-up, not the original email. People are genuinely busy — a follow-up isn't annoying, it's expected.
The time problem
I'll be honest about the math. Each email took me about 20-30 minutes of research and writing. For 22 emails, that's roughly 8-10 hours over two weeks. That's a significant time investment, even though the ROI was dramatically better than online applications.
The research is the bottleneck — finding the right person, tracking down their email, reading their recent posts, finding something specific to reference. The actual writing takes 5 minutes once you have all that context.
This is exactly the problem dm-the-boss solves. You enter a company and role. It researches the company, finds the right contacts based on company size, figures out their email addresses, and writes personalized emails using the same principles in this template — specific hooks, concise credentials, low-friction asks. You review and edit each email in the app, then send directly from your Gmail. Nothing goes out without you clicking Send.
The 20-30 minutes of research per email becomes about 60 seconds. You still control the final message. You just skip the grunt work.
Go send some emails
You now have the exact template, the reasoning behind every line, and a real example that led to an offer. You have the follow-up template. You know the mistakes to avoid.
The only thing left is to do it. Pick a company you'd genuinely want to work at. Find the right person to email. Spend 10 minutes researching them. Fill in the template. Hit send.
The template works. The hard part is pressing send.