How To Become a Speaker at Conferences

·49 min·4 clips

Victor reveals how his first conference talk was a horrible experience and warns listeners not to do it.

Imposter fear is the starting point. The cold open treats that first conference slot as properly scary, not as some breezy inspirational milestone. Then Darren and Victor get into the work: what helps a submission survive review. The title gets most of the heat. One speaker says review can happen in phases, and a proposal may not make it past the title. Harsh, yes, but useful. Their advice is not to cram the whole talk into a giant headline that tries to prove too much. That kind of effort shows. The better move is a title that says what the session is about without turning into seven paragraphs in miniature. NixOS is the example. If the topic is clear, interesting, and sounds like the speaker knows the material, the reviewer has a reason to keep going. The first few sentences still have to land, but the episode keeps coming back to those first seconds of attention. Reviewers are moving fast. The gut check is simple: read the title before submitting and ask whether you would choose that session yourself. If not, slow down. A proposal should sound like a real talk, not a clever submission object. The conversation stays loose, sponsor bits and all, but the advice is clean: clarity beats strain.

As heard by us

A practical conversation about making a conference session clear enough to earn attention.

Becoming a conference speaker starts here as a fear problem, then settles into a more useful craft problem: getting a session submission noticed. The conversation is strongest when it shifts from stage anxiety to the small but decisive work of the title.

Read the full review in PlayNext →

Why you'd press play

You want a conference slot, but your session title is already trying to give the whole talk away.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from DevOps Paradox