A free, copy-paste podcast guest email template for booking developers and engineers. Subject lines, full email body, follow-up script, FAQ. Written for hosts who actually book guests.
Senior software engineers, staff engineers, and engineering managers. If you're booking developers and engineers as podcast guests — for an interview show, narrative show, or panel format — this template is built for the cold first touch when you don't have a warm intro.
Every winning podcast guest email to a developer cites something concrete the guest made in the last 60 days. The template below structures that reference around a 30-minute recording ask in under 160 words.
Developers ignore "tell us your story" pitches. These angles consistently get replies because they ask for operator detail, not narrative:
They distrust marketing language and have a strong allergy to fluff. The fix is a concrete reference to recent work. Acceptable proof points include a recent open-source contribution; a technical blog post; a conference talk in the last 6 months. If you can't find one of those within the last 60 days, this is the wrong week to pitch this guest — wait until they ship something new.
Three subject lines built for under 55 characters, lowercase, no clickbait: "{{specific_project}} — quick question", "{{first_name}}, podcast invite re: {{topic}}", and "30 min on the {{technology}} migration?". Each is short enough to render fully on mobile and specific enough to clear pattern-matching delete.
Hey {{first_name}}, I run {{podcast_name}} — {{audience_short}} listen on commutes. Your write-up on {{specific_thing}} answered a question I've been chewing on for months, especially the part about {{specific_paraphrase}}. Want to do a 30-min conversation on the architecture: what you'd undo, the alternatives you considered, the operational gotchas. Plain conversation, no slides, we record over whatever you're already comfortable with. Audience ~{{listener_number}} per episode, mostly senior engineers and EMs. Past guests: {{name_1}}, {{name_2}}. Open in the next 2–3 weeks? {{your_name}}
Reply to your own thread, no new subject. Cap at one follow-up — anything more trades reply rate for trust. Suggested body: Hey {{first_name}}, quick nudge. If the {{specific_thing}} angle isn't interesting, happy to point at {{alternate_topic}} instead — whatever you want to talk about. {{your_name}}
Short, specific, and human. "{{specific_project}} — quick question" works because it references something they actually shipped. Generic "love your work" subject lines from a stranger get archived on sight.
Under 160 words. developers and engineers scan in under 8 seconds — anything longer is a delete. The template above is intentionally tight: hook, ask, format, close.
One follow-up about 5–7 days after the original is the practical maximum. After that, you're trading reply rate for trust. Add the prospect to a 6-month re-pitch list instead of sending a third email.
Check their personal site (/about, /contact, footer), LinkedIn contact info, and recent newsletter reply-to address. If nothing surfaces, an email finder like Hunter or Apollo plus a verifier like NeverBounce is the standard playbook.