Speaking at your first technology conference: a six-step path from proposal to stage

Giving a talk at a technology conference starts with submitting a proposal – but the process feels opaque if you've never done it before. Most speakers worry about whether they're experienced enough, how to write a strong pitch, or what happens if they're rejected. This guide walks you through the proposal submission process, from finding a call for proposals to delivering your talk, so you can get your first conference presentation done.

Understanding what conferences are looking for

Conference organisers are not hunting for the most famous person in the room. They want talks that solve a problem, teach something useful, or show a perspective their audience hasn't heard yet. A talk from someone with honest hands-on experience often lands better than one from someone with a bigger name but less practical knowledge.

Most conferences make their criteria clear in their call for proposals – you'll see what length they want (usually 30 to 45 minutes), what kind of topics fit the conference, and what the selection committee values. Read this carefully before you start writing. The angle of your proposal should match the conference's focus, not the other way around.

Finding a call for proposals that suits you

A call for proposals – often abbreviated to CFP – is an open invitation from a conference asking speakers to submit ideas. Once you know you want to speak, finding the right conference to approach comes first.

Start with events you've attended or would like to attend. Organisers of those conferences often publish their CFP in email newsletters sent to past attendees, on their website's speakers page, or in social media. If you follow conference accounts on social platforms, you'll see calls appear in your feed. Specialist sites and newsletters that focus on technology events list open calls by topic and deadline, which saves time if you're hunting across several conferences at once.

Set a reminder for deadlines. Conference submissions close on a fixed date, and no late proposals are read. A call that closes in three weeks gives you enough time to draft, revise and polish; anything shorter feels rushed unless you already have your talk mostly planned.

Writing a proposal that gets accepted

Your proposal needs a compelling title, a clear summary, and a description that shows you know what you're going to say. The proposal is not your full talk – it's a pitch. Its job is to convince the selection committee that your talk deserves a slot.

A strong title is specific, not vague. "Lessons from Building a Real-Time Data Pipeline" works better than "Working with Data" because it tells organisers exactly what you'll cover. Your summary – usually one or two sentences – should answer why someone attending the conference would want to sit in your session. Avoid generic phrases. Instead of "Learn best practices for cloud infrastructure", try something like "How we cut deployment time by switching to a different approach – and what we'd do differently now".

In the full description, lay out the journey your talk will take. Explain the problem you'll address, any background the audience needs, the main ideas or techniques you'll show, and what listeners will be able to do differently afterwards. Write as if you're explaining the talk to a friend – conversational but clear. If your talk has a personal story or a particular failure you learned from, mention it. Selection committees value talks grounded in real experience.

Be honest about your experience level if the form asks. Conferences welcome first-time speakers and often have dedicated slots for new voices. Claiming five years of experience in something you learned last month is a fast way to get rejected or, worse, to commit yourself to a talk you can't deliver well.

Choosing the right conference format

Most technology conferences offer different session lengths and formats. Understanding what fits your material matters.

A standard talk slot runs 30 to 45 minutes – that's your main option for a first speaking experience. Shorter lightning talks (5 to 10 minutes) suit a single idea or a quick case study; they're lower pressure but leave less room for depth. Workshops and panel discussions need a different kind of preparation. If you're unsure which format suits your topic, look at the conference schedule from a previous year and see what works.

The format you choose shapes how you'll prepare. A 30-minute talk needs tighter slides and faster pacing than a 45-minute one. A workshop needs hands-on material and time for questions. If you're new to speaking, stick with a standard talk slot the first time – it's the most forgiving format.

Preparing your talk once you're accepted

Once the conference accepts your proposal, the real work begins. You now have a contract – spoken or written – to deliver a talk that matches what you described.

Start early. A good conference talk needs time to draft, revise, test and refine. Expect to spend 10 to 20 hours preparing from acceptance to the day you speak – more if you're adding code examples or demonstrations. Begin with an outline. Write down the main point of each section, roughly how long you'll spend on it, and what you want the audience to take away. This outline is your map; it keeps you from going off track.

Build your slides around your spoken words, not the other way around. Slides should support what you say, not replace it. Too many slides packed with text bore your audience and force them to choose between reading and listening. Aim for slides that show visuals – charts, code, diagrams – with minimal text, and let your voice carry the explanation.

If your talk includes live code or a demonstration, practise it many times. Demos fail in front of an audience more often than you'd think. Have a backup – a screen recording or screenshots – so you're not stranded if your demo breaks.

Managing nerves and performing well

First-time speakers almost always feel nervous before they go on stage. That's normal and doesn't mean you're not ready. The nerves usually fade once you start talking.

A few weeks before the conference, practise your talk out loud – not in your head, actually speaking it. Do this in front of a mirror or, better, in front of someone else who can give feedback. Time yourself. Adjust sections that ran long or felt rushed. Practice until the flow feels natural, not memorised.

Arrive early on the day you speak. Introduce yourself to the person running the session, test your slides and your laptop connection, and get familiar with the room. Knowing the space takes away one source of anxiety. Breathe before you start. Take a moment backstage or at the side of the room – in for four, hold for four, out for four.

When you're on stage, make eye contact with different parts of the audience rather than staring at your slides or your notes. Speak clearly and at a pace that lets your words land – rushing makes you sound less confident, not more. If you lose your place, pause, look at your notes, and carry on. Your audience won't know you stumbled unless you act as if it's a disaster.

What happens after your talk

Many conferences record talks and publish them online, sometimes weeks or months later. Before the conference, ask whether your talk will be recorded and whether you'll get a copy. This is useful both for your own learning – watching yourself is awkward but teaches you a lot – and for your portfolio.

Collect feedback if the conference gathers it. Not all feedback is useful, but patterns matter. If three people mention that you rushed through a section, that's worth knowing for next time. One person saying they didn't like your accent is something to disregard.

After the conference, write down what went well and what you'd change. Did you cover everything you meant to? Did the audience ask questions you hadn't anticipated? Was your timing off? This reflection is gold for your next talk. You're building experience faster when you write it down than when you just move on to the next thing.

Starting with one talk

Your first conference talk doesn't have to be perfect. It has to be honest, prepared, and delivered with care. Most speakers give awkward first talks – that's universal. The difference between someone who speaks once and someone who speaks regularly is that the regular speaker gave a second talk, then a third.

Pick a conference whose call for proposals is open now, or set a reminder for a conference you know well. Draft a proposal this week. The worst outcome is that it gets rejected; the best outcome is that you're booked for a stage and three months later you're sharing something you know with people who want to learn it.

#Speaker submission #First-time attendee #Professional development

Download PDF: Your Speaking Preparation Checklist PDF, 29 KB