DEV Community

Justin Jackson for Transistor.fm

Posted on

How to Start a Developer Podcast

Podcasts are where listeners go for authentic conversations on topics they care about. It's one of the last places on the web where you don't have to fight with AI content slop.

And software developers love consuming podcasts. On Transistor.fm, the podcast hosting platform I co-founded, programming podcasts are one of the most popular niches.

If you've always wanted to start a podcast, it's simpler than you think. Here's my guide.

1. Choose your topic and format

"I interview Laravel developers who work on SaaS products" is better than starting a general podcast "about tech and startups.”

Examples that work:

  • Indie Rails – interviews with indie devs and small business owners who use Rails
  • DevOps and Docker Talk – a podcast focused on Docker and container tools like Kubernetes
  • Mostly Technical – two programmers talk about starting a business, and their personal lives

Action: Write your one-sentence pitch.

“A 20-minute weekly show where I [format] about [specific topic] for [specific listener].”

2. Get your audio gear

Here's your data in markdown table format:

Item My Pick Cost
Mic Samson Q2U $56
Headphones Sony MDR7506 $99 (used $60)
Boom arm Elgato Wave LP $100
Pop filter Foam windscreen $5
Software Audacity (free) or Descript $12
Hosting Transistor.fm $19/month

Pro tip: Record in a closet. Being surrounded by clothes = free sound treatment.

3. Recording and editing

These days, I mostly record and edit my episodes in Descript.

Here are a few editing tips:

  1. If you're recording with a co-host/guest, cut the first 5-10 minutes (warm-up chatter)
  2. Listen to the episode and cut any section where it drags
  3. Add intro/outro music (5-15 seconds each)
  4. Export MP3 128 kbps, -16 LUFS for loudness.

4. Hosting & RSS: Don’t overthink it

Use Transistor (yes, I’m biased—but it’s $19/mo and handles everything).

We'll give you:

  • An easy to use CMS for creating + publishing episodes
  • An awesome developer API if you want to build a custom publishing workflow
  • Properly formatted RSS and XML for podcast apps
  • One-click distribution to: Apple, Spotify, Overcast, YouTube, etc.
  • Analytics and stats

5. Publishing routine

Choose a publishing frequency, and stick to it. For example:

Publish every Tuesday at 8am UTC.

Develop a routine/calendar for producing episodes:

  • Wednesday: Outline episode
  • Thursday: Record episode
  • Friday: Edit + schedule
  • Tuesday: Publish episode + promote

Final thoughts

Starting a podcast isn't about having perfect equipment or a huge audience on day one. It's about showing up consistently and having conversations that matter to your niche.

The developers who succeed with podcasting are the ones who:

  • Pick a topic/format you're excited about
  • Commit to a schedule (even if it's just once a month)
  • Don't wait for permission to hit publish

Your first 10 episodes will be rough. That's normal. Every successful podcast you listen to started the same way.

The best time to start was last year. The second best time is today.

Ready to launch? Sign up for Transistor.fm and publish your first episode this week. You can always upgrade your gear later—but you can't upgrade without starting.

Top comments (0)