Before You Take the Stage

Every first-time speaker carries the same fear into the first CFP: that they are not ready, not experienced enough, not the right person to be up there. That fear is normal, and it is almost never a reliable signal about whether you should submit.

The people who decide who speaks at most conferences are not who you imagine. They are not a panel of credentialed experts with a long checklist. They are practitioners and researchers, volunteering their time because they want to see the community grow. They are hoping the next proposal that lands in their inbox is something worth putting on stage. That proposal can be yours.

The Point of It All
Conferences exist to share knowledge and surface diversity in thought across the field. That is only possible if more people contribute to the conversation. That includes you.

A few things are worth knowing before you write a word of the proposal:

Nervous is not the same as unready. Almost every experienced speaker still feels some version of stage nerves before walking up. What separates them from a first-timer is not the absence of nerves, it is a body of evidence that the nerves do not predict the outcome. You are building that evidence starting with this talk, not waiting for it to arrive before you start.

The room wants you to succeed. An audience that shows up to a talk has already decided the topic is worth 30 minutes of their time. Nobody in that room is hoping you fail. Program committees who accepted your proposal have already vouched for it once. You are not walking into a hostile room, you are walking into a room full of people rooting for the talk to be good.

Practice out loud, not just in your head. A talk that sounds finished in your head almost never sounds finished the first time you say it out loud. Rehearse standing up, at speaking pace, in front of at least one real person if you can manage it. The gap between "I know this material" and "I can deliver this material in 30 minutes" only closes by actually doing the delivery, repeatedly, before the day it counts.

You do not have to be the expert in the room. What a reviewer, and later an audience, is looking for is a story: a real problem, a real approach, a real outcome. The researcher who has studied a topic for fifteen years may have more depth than you. But the practitioner who ran into the hard version of that problem last quarter has something else entirely: proximity, specificity, and the memory of what it felt like to not understand it yet. That is often more useful to a room full of working practitioners than an authoritative survey.

The Anatomy of a CFP

Most conferences collect speaking proposals through what is called a CFP, a Call for Papers. This is your starting point as a presenter. When a reviewer reads your CFP, they are looking for one thing: can they feel the structure? A CFP that follows the story arc (problem, why it matters, solution, action) tells them you have a real talk, not just a topic. Make it read like a miniature version of the story you are promising to tell.

You do not need a finished talk to submit a CFP. You need a clear idea and the honest confidence that you can deliver it. The proposal is a commitment to a direction, not a contract to submit your slide deck unchanged. Most speakers refine, restructure, and deepen the talk significantly between acceptance and the conference date. Submit with the idea. Build the talk after.
01
The Title
Its job is to earn the click, from the reviewer reading submissions to the attendee choosing between sessions.
Be concrete and benefit-driven. "How We Stopped 80% of Phishing Attempts by Changing One Onboarding Email" beats "A Novel Approach to User Security Awareness." The audience should be able to guess what they will walk away with from the title alone.
Avoid: clever titles with no content signal. They look like the speaker is hiding behind wit instead of substance.
02
The Abstract
Its job is to show the reviewer that you have a clear story, a real audience, and a specific outcome.
Structure it in three beats: the problem the talk addresses, your specific approach or experience with it, and what attendees will be able to do after seeing it. Reviewers are reading fast. Front-load the value.
Avoid: vague statements about "exploring" or "examining" a topic. Those signal that the talk doesn't have a point yet. Reviewers can tell.
03
The Audience & Level
Its job is to help the organizers schedule the talk in the right track and help attendees self-select into the right sessions.
Be honest. If the talk is aimed at practitioners two to four years in, say so. If it requires familiarity with Kubernetes, say so. A well-targeted talk beats a vaguely universal one every time. "This talk is for everyone" is almost never true and often sounds naive.
Avoid: overstating the audience breadth to seem more competitive. You'll fill a smaller room with the right people, which is better than a larger room with the wrong ones.
04
The Bio
Its job is to establish why you are the right person to give this specific talk, not to list your credentials in full.
Connect your experience directly to the talk topic. "I have spent three years managing incident response for a healthcare organization and this talk comes from 40+ real incidents" is more compelling than a resume paragraph that ends with your LinkedIn URL.
Avoid: starting with your job title. Start with what you have done that qualifies you to tell this story.

Reviewers are reading for confidence and clarity, not perfection. A CFP that knows what it is and says so plainly beats a polished proposal that hedges on everything.

Read the Guidelines Before You Write a Word

Every conference publishes submission guidelines, and most people skip them. This is a mistake. The guidelines tell you exactly what the committee is weighting, which tracks are oversubscribed, and the things that will get your submission disqualified. They also reveal softer signals: which audience levels they are short on, whether they prefer case studies over tutorials this year. That intelligence shapes how you frame your proposal without changing the substance of your talk. Two disqualifiers come up consistently across almost every conference that runs blind reviews.

Revealing your identity
Blind review means the program committee evaluates your proposal without knowing who you are. Any detail that identifies you (your name, your employer, your LinkedIn URL, a phrase like "in my role at Acme Corp") breaks the blind and can get your submission automatically disqualified. Write the abstract as if a stranger submitted it. Your bio goes in a separate field that reviewers see only after scoring is complete.
Write in the third person or use generic references ("at a mid-size healthcare organization") if specific context is needed. Save the personal details for the bio field.
Pitching a product
Conferences are built around thought leadership: ideas, lessons, and perspectives that advance the field. They are not a sales channel. A submission that is structured as a pitch for your company's product or service, or that heavily features a vendor's tool as the hero of the story, will be rejected by most program committees without further discussion. The expo hall exists for exactly this reason. Vendors who want to demonstrate products book a booth; speakers who want to share what they have learned submit a CFP.
The test: remove every mention of the product name. Does the talk still have a point? If yes, you have a talk. If no, you have a pitch, and it belongs in the expo hall, not on the main stage.

Rejection Is the Default, and That Is Fine

Most talks do not get accepted. At competitive conferences, acceptance rates run between 15% and 40%, meaning experienced speakers with strong proposals get turned away regularly. This is not evidence that you were not ready; the conference had limited slots, a specific program direction, or forty other submissions in your topic area. None of that is a verdict on your work.

01
Every "no" is information
If the conference offers feedback, read it carefully. If it doesn't, look at what was accepted. You will often see what the committee was weighting (format, audience level, topic area) and that tells you exactly how to sharpen the next submission.
02
You get better at submitting by submitting
The first CFP you write will not be your best. The fifth will be noticeably stronger. The people who become regular conference speakers almost universally have a drawer full of early rejections. The drawer is part of the process, not evidence of failure.
03
Not every conference is the right fit
Conferences have personalities. Some skew deeply technical. Some prioritize practitioner stories over research. Some are built for leadership, others for individual contributors. A talk that lands flat at one conference can be exactly what another community has been waiting for.

Submit the same talk to multiple conferences; there is nothing wrong with it and most speakers do. A proposal lightly adapted for each community can run at three or four events in a year. The audience at each one is different, and you will get better at the talk every time you give it.

The only way to find out which conferences fit your style and message is to submit and see. You cannot know in advance which room is the right room. The data only comes from being in the process.

Call to Action

The talk you could give today is better than the perfect talk you will be ready for someday. Do it this week. Here is how to move from intention to submission.

1
Brainstorm five topic ideas
Write down five things you know from real experience: a problem you solved, a lesson you learned the hard way, a concept you had to explain repeatedly. Do not filter. Quantity first. The best talk idea is usually not the first one you write down.
2
Draft the abstract for the topic you feel best about
Pick the idea from your list that excites you most and write the abstract. Then ask one person to read it and tell you what they think the talk is about, not whether it is good. If their summary matches yours, it is working. If it does not, you have found what to fix before the reviewer does.
3
Find one conference that is a fit
Not the biggest conference in your field, but the one where the audience matches the people you are trying to reach. Local and regional events are excellent starting points: smaller stakes, more receptive to new speakers, and often where first-timers get the warmest reception and most honest feedback.
4
Submit, even if it doesn't feel finished
A submitted CFP that gets rejected has taught you something. An unsubmitted one has not. The feedback loop only starts when you enter it.
5
Repeat: Reps Are How You Get Better
Submit the same CFP to multiple conferences, or go back to your brainstorm list and develop a second idea. Either path works. What does not work is spreading yourself across five half-formed proposals at once. One or two well-crafted submissions will outperform a handful of rushed ones every time. The goal is volume over time, not volume all at once.

The field grows when more of the people doing the actual work share what they have learned. You are one of them.

Find the deadline. Write the one sentence. Submit it.

Bridge the Gap. Empower Their Decisions.

Whether you are preparing to present at a conference or building the communication skills to lead your team, the bridge between technical depth and clear communication is the career move that compounds. Tech CoLab's games put that translation in motion across your whole organization.

Read: Be the Bridge → The Heart of a Teacher →