Skipping the Line
In most professional contexts, expertise is assumed, not demonstrated. You can claim on a resume that you're a distributed systems expert, but the claim is indistinguishable from anyone else making the same claim. Public speaking changes this dynamic entirely. The moment you stand at a podium — even at a 20-person local meetup — the audience's brain applies a cognitive shortcut: this person was selected to speak, therefore they know something I don't. This is the "expert halo," and it is disproportionately powerful relative to the effort required to earn it.
The mistake most engineers make is waiting until they feel like an expert before proposing a talk. This is backwards. You become perceived as an expert by speaking, not the other way around. The bar for a local meetup lightning talk is "did you learn something interesting this month?" — not "have you published peer-reviewed research?"
How to Start — The Lightning Talk:
A lightning talk is a 5-minute presentation. It is the lowest-stakes, highest-ROI entry point into public speaking.
- Find a local meetup. Search Meetup.com for your city + your technology (e.g., "London Kubernetes Meetup"). Most meetups are actively looking for speakers.
- Propose a 5-minute lightning talk. Email the organizer: "I recently solved [specific problem] using [technology]. I'd like to share what I learned in 5 minutes. Would that fit your next event?"
- Pick a topic with a clear narrative arc. "One thing I learned debugging X" is a complete story: problem → investigation → solution → lesson.
The Career ROI:
Public speaking compounds in ways that passive job applications do not:
- Inbound networking: After a talk, people approach you. You don't hand out resumes — you exchange cards with people who already believe you're competent.
- Interview preparation: Explaining a technical concept to a non-specialist audience forces you to understand it at a deeper level. This is the Feynman Technique in practice — if you can't explain it simply, you don't understand it well enough. This skill transfers directly to system design interviews.
- Conference progression: A lightning talk at a meetup becomes a session proposal at a regional conference. A regional conference talk becomes a CFP (Call for Proposals) submission to a major conference. Each step builds a public record of expertise.
The Slide Rule:
For a 5-minute talk, use 5 slides maximum. One slide per minute. Each slide should have one idea, one diagram, or one code snippet — not a wall of bullet points. The audience is there to hear you think, not to read your slides.
Interviewers at senior and staff levels often ask: "How do you share knowledge within your team or the broader engineering community?" A strong answer references a specific talk you gave, a blog post you wrote, or an internal tech talk you organized — with concrete details about the topic and the audience's reaction. "I gave a 10-minute talk at our local Go meetup about how we used sync.Pool to reduce GC pressure" is infinitely more credible than "I like to share knowledge."
Key Point: The compounding effect of public speaking is social, not just reputational. Every talk you give puts you in a room with other speakers — who are often senior engineers, engineering managers, and CTOs. The hallway conversations after a meetup are where referrals happen. A single well-delivered 5-minute talk can generate more career-relevant connections than six months of cold LinkedIn outreach.