Public Speaking Preparation
Prepare for technical talks, podcasts, panels, and AMAs. Covers
Public speaking is a skill, not a talent. Speakers who appear effortless on stage have rehearsed extensively; speakers who appear natural in interviews have prepared answers; speakers who run good AMAs have anticipated questions. The variance between speakers is mostly preparation, not innate ability. ## Key Points - **Week -8**: Outline the talk. Sections, time per section, key points per section. - **Week -6**: Draft the slides. Bullet points, key visuals, code samples. Don't write the script yet. - **Week -4**: Write the script. Aim for ~140 words per minute of delivery. A 25-minute talk is ~3,500 words. The script is for finding gaps; you won't deliver it verbatim. - **Week -3**: First rehearsal, alone, to time. Identify rough sections. - **Week -2**: Rehearsals 2–5. Cut. Tighten. Smooth transitions. Have someone watch one of these and give feedback. - **Week -1**: Rehearsals 6–10. The talk should be in muscle memory. Practice the demo five times if there is one. - **Day before**: One full rehearsal. Sleep early. - **Day of**: Don't rehearse. Light food. Voice warmup (humming, lip trills). Trust the practice. - **Listen to 2–3 episodes** of the podcast you're going on. Tone, format, host style. - **Note 5–8 stories** you can tell. Specific stories with characters, conflict, resolution. Stories beat abstractions on podcasts. - **Anticipate the obvious questions.** What got you into this field? What's a recent project? What do you think of [topic]? Have answers; don't memorize them, but know the shape. - **One memorable line.** Have one quotable sentence ready. Podcast listeners remember lines, not arguments.
skilldb get devrel-content-skills/Public Speaking PreparationFull skill: 142 linesPublic speaking is a skill, not a talent. Speakers who appear effortless on stage have rehearsed extensively; speakers who appear natural in interviews have prepared answers; speakers who run good AMAs have anticipated questions. The variance between speakers is mostly preparation, not innate ability.
This skill covers preparation for talks, podcasts, panels, and AMAs — the four formats most engineering speakers encounter. Each has its own rhythm; each rewards specific kinds of practice.
Talks (Pre-Written)
A pre-written talk — conference, internal company talk, recorded webinar — is the highest-stakes format. The audience is large; the recording lives forever.
Preparation timeline for a 25–45 minute talk:
- Week -8: Outline the talk. Sections, time per section, key points per section.
- Week -6: Draft the slides. Bullet points, key visuals, code samples. Don't write the script yet.
- Week -4: Write the script. Aim for ~140 words per minute of delivery. A 25-minute talk is ~3,500 words. The script is for finding gaps; you won't deliver it verbatim.
- Week -3: First rehearsal, alone, to time. Identify rough sections.
- Week -2: Rehearsals 2–5. Cut. Tighten. Smooth transitions. Have someone watch one of these and give feedback.
- Week -1: Rehearsals 6–10. The talk should be in muscle memory. Practice the demo five times if there is one.
- Day before: One full rehearsal. Sleep early.
- Day of: Don't rehearse. Light food. Voice warmup (humming, lip trills). Trust the practice.
Most speakers underprepare. Eight to twelve full rehearsals is the standard for a great talk; most speakers do two to four.
Podcasts (Conversational)
Podcasts are conversational. Less to memorize; more to think about beforehand.
Preparation:
- Listen to 2–3 episodes of the podcast you're going on. Tone, format, host style.
- Note 5–8 stories you can tell. Specific stories with characters, conflict, resolution. Stories beat abstractions on podcasts.
- Anticipate the obvious questions. What got you into this field? What's a recent project? What do you think of [topic]? Have answers; don't memorize them, but know the shape.
- One memorable line. Have one quotable sentence ready. Podcast listeners remember lines, not arguments.
- Question for the host. Hosts appreciate guests who engage with them, not just monologue.
On the day:
- Quiet room with absorption (carpet, curtains; not a hard-walled office).
- Decent microphone. USB condenser mics ($100) are fine; built-in laptop mics are not.
- Wired headphones to avoid latency.
- Water nearby; not at the keyboard.
During the recording: speak in complete sentences. Don't um-and-uh. If you stumble, pause and restart the sentence; the editor will cut. Be okay with silence — let the host process before jumping in.
Panels
Panels are unpredictable. Three to five speakers, a moderator, an audience. Less time per speaker; more risk of being upstaged or talked over.
Preparation:
- Know the other panelists. Look up their work. You'll be able to engage with their points, which makes you look engaged.
- Have 2–3 strong points ready to make at any opportunity. Adjust to the moderator's questions; come back to your points.
- One contrarian take. Panels become repetitive when everyone agrees. The contrarian view is memorable; the audience appreciates it; the moderator will follow up.
- Brevity. Panel time per speaker is short. 45 seconds per answer is plenty; 90 seconds is risky; 120 seconds is too long.
In the panel:
- Listen actively. Don't draft your next answer while another panelist talks.
- Reference what the previous speaker said when relevant. "Building on what Alice said..."
- Don't talk over. Wait for the natural pause. The moderator will route to you.
- If you don't have a strong view, say so. "I don't have a strong opinion on that — what I do think is..." Better than waffling.
AMAs and Q&A
AMAs and Q&A sessions are the wildest format. The audience asks anything; you respond live.
Preparation:
- Know your topics. AMAs are usually narrow ("AMA about X" not "AMA about everything"). Be deeply prepared on the topic.
- Anticipate hostile questions. Critics, gotchas, attempts to sandbag. Have responses ready that engage the substance without taking the bait.
- Prepare 5 stories that demonstrate your perspective. Stories answer questions vividly; abstractions don't.
During:
- Read the full question before answering. The first sentence might be context; the actual question might be in the third.
- Restate the question briefly if it's complex. Confirms you understood; gives you a beat to think.
- Be willing to say "I don't know." "I haven't worked on that recently — what I can tell you is..." Better than guessing.
- Time-box. Long answers eat the AMA. Two minutes per answer; move on.
- Don't fight the difficult question. Engage the substance. If the questioner is hostile, the audience can tell; staying composed wins the room.
Voice and Body
Across all formats, voice and body matter:
- Voice — projects from the diaphragm, not the throat. Rises and falls in pitch (monotone is hypnotic). Slows down for emphasis. Pauses for breath.
- Body (in person) — open posture; weight balanced; gestures coming from the shoulders, not the wrists. Eye contact with the audience or the camera.
- Pace — most speakers go too fast when nervous. Aim for slightly slower than feels natural. Pauses are okay; they let the audience process.
Vocal warmups before any recorded format:
- 5 minutes of humming, lip trills, tongue twisters.
- 5 minutes of speaking the first paragraph of the talk at full energy.
- Sip warm (not hot) water with lemon for the throat.
Anxiety Management
Public-speaking anxiety is normal. Even experienced speakers feel it. The goal is not to eliminate it but to channel it.
Techniques:
- Reframe the physical sensation. The hammering heart and tight breathing are not anxiety; they're energy. The same chemistry that produces stage fright produces stage presence.
- Pre-talk routine. Same routine every time. Eat the same kind of meal; do the same warmups; go to the bathroom 15 minutes before. Routine displaces anxiety.
- Box breathing. 4 seconds in, 4 seconds hold, 4 seconds out, 4 seconds hold. Slows the heart rate within 90 seconds.
- Power posing. Two minutes alone in a quiet space, arms wide, expanding posture. The research is debated, but many speakers report it helps.
- First-line anchor. Memorize the first 30 seconds verbatim. Once delivered, the rest comes more easily.
For severe anxiety, talk to a coach or a therapist. Beta blockers (prescribed by a physician) can take the edge off physical symptoms; they're a controversial topic but used by many performers.
Recording Discipline
For recorded formats (podcasts, webinars, virtual talks):
- Lighting — light from in front, not behind. Window or ring light at eye level.
- Camera — at eye level. Below or above looks unprofessional.
- Background — neutral. A real bookshelf is fine; a busy room is distracting.
- Wardrobe — solid colors. Patterns moiré on cameras.
- Test the setup — record a 1-minute test the day before. Watch it back. Adjust.
The thing that ruins recorded talks more often than content is bad audio. Invest in the microphone first.
Anti-Patterns
Underprepared. Two rehearsals for a 25-minute talk. The talk lands at 60% of its potential. Rehearse 8–12 times.
Reading from notes. The audience tunes out. The script is for finding gaps; deliver from memory and beats.
Anxiety unmanaged. Spirals into freezing or rambling. Develop a routine.
No anticipation of hostile questions. Caught flat-footed in the AMA. Prepare answers.
Hard-walled audio. Echoey podcast. Listen to your own audio first; check the room.
Long answers in panels. Eats other speakers' time. The moderator gets frustrated. Be brief.
Install this skill directly: skilldb add devrel-content-skills
Related Skills
Engineering Blog Posts
Write engineering blog posts that bring traffic, build trust, and
Developer Conference Talks
Plan, write, and deliver a 25–45 minute developer conference talk that
Open Source Community Management
Run an open-source community around a project — issue triage, PR review,
Technical Tutorial Writing
Write tutorials that get developers to working code in their first 20
Investigative Deep-Dive Journalist Archetype
Pursue stories that institutions do not want told. Multi-month or
Narrative Feature Journalist Archetype
Write long-form magazine pieces that turn reporting into story — the