To get tech speaking gigs, you need to do three things well: pitch a specific, defensible idea (not a topic area), show evidence that you've done the thing you want to talk about, and make it easy for the organiser to say yes without having to dig. Most pitches fail on the first point before organisers even reach the other two. This guide covers what conference programmers are genuinely evaluating, how to frame your pitch, and the common mistakes that quietly kill otherwise good applications.
Why most speaker pitches get rejected
Conference programmers, especially at well-run UK tech events, are reading dozens to hundreds of pitches for a handful of slots. The overwhelming majority are rejected not because the person is unqualified, but because the pitch is vague. Submissions that say 'I'd love to talk about AI in product development' tell the organiser almost nothing. What angle? What outcome for the audience? What have you personally shipped, fixed, or broken to earn that conversation?
The other quiet killer is pitching your CV rather than a talk. A long list of credentials without a clear talk thesis is just noise. Organisers are building a programme, not a roster. They need to know exactly what your session delivers to the person sitting in the audience at 2pm on a Thursday.
What conference programmers are actually evaluating
Having sat on both sides of this, here's what a programmer is working through when they read your submission:
- Specificity of the idea. Is there a real, arguable claim at the centre of this talk? 'Here's what we learned building X' is a talk. 'The role of AI in modern engineering' is a chapter heading.
- Credibility of the speaker. Have you actually done the thing? Practitioners who've shipped real products, made real mistakes, and can name specific decisions carry more weight than people who've studied a topic.
- Fit for the audience. Does this serve the people likely to be in the room? A UK fintech conference needs different specificity than a generalist developer meetup in Manchester.
- Evidence of delivery. Can you actually stand up and talk? A short video of a previous talk, even from a small meetup, removes enormous uncertainty for programmers.
- Ease of working with you. Did you follow the submission format? Did you answer the brief? Small signals about professionalism matter more than most speakers realise.
How to write a pitch that gets read properly
- Start with the talk title, not your bio. The title is your hook. It should make the organiser want to read the next line. 'Why we rebuilt our entire data pipeline in six weeks (and what we'd never do again)' is more compelling than 'Lessons from scaling a startup'.
- Write a one-paragraph abstract that answers three questions: What is the specific claim or insight? Why does it matter to this audience? What will someone be able to do or think differently after hearing it? Keep this under 150 words.
- Describe your evidence for the talk. Not your job title, your evidence. Name the product, the problem, the decision you made and why. This is where practitioners beat generalists every time.
- Keep your bio short and relevant. Two or three sentences that connect your background directly to this talk topic. Nothing else. The organiser doesn't need your full career history.
- Include a talk link or short video if you have one. Even a five-minute lightning talk recording from a local meetup signals that you can actually deliver. If you don't have one yet, start there.
- Research the event before you pitch. Read last year's programme. Look at who spoke and what they covered. Pitch something that fits the programme's direction without duplicating what's already been done.
- Tailor the pitch to the specific event. A single generic pitch sent to fifteen conferences gets worse results than five targeted pitches. Programmers can tell when a submission has been mass-applied.
Building credibility before you pitch the big stages
If you're newer to speaking, the path into larger conferences runs through smaller venues first. UK tech meetups, local developer groups, product community events, and internal company conferences are all places where you can develop material, get comfortable on stage, and, crucially, get a recording. Groups like those that run under the Tech Nation network, local Python, JavaScript, and product meetups in cities like Leeds, Manchester, Birmingham, and Newcastle, are consistently looking for speakers and far more accessible than headline conferences.
Pitch a lightning talk (5-10 minutes) before you pitch a full session. It's lower risk for the organiser, lowers the barrier to a yes, and gives you a format where tight material shines.
Writing publicly about the same topics you want to speak on also builds the trail that programmers look for. A well-reasoned post on your own site or on a platform like Substack that gets shared in relevant communities is quiet social proof. It shows you can organise your thinking, that other practitioners find it valuable, and it gives organisers a direct sense of your voice before they invite you into a room.
The format question: keynote vs. breakout vs. panel
Most first-time conference speakers get their break in a breakout or workshop slot, not a keynote. That's not a consolation prize; breakouts often have higher engagement because the audience has actively chosen to be there. Panels are worth doing once or twice to get comfortable on stage with others, but they're a poor place to make your mark because the format dilutes individual voice. Keynotes come from a track record, not a pitch.
When you're pitching, match your format suggestion to your experience level and the talk's natural shape. A hands-on technical walk-through fits a workshop. A clear argument about a direction in the industry fits a 30-minute talk. Don't pitch a keynote slot for your first conference submission. Do pitch the format that serves the material.
What makes a talk genuinely memorable
The talks that get referenced in hallway conversations and shared on social media share one feature: they have a real point of view. Not 'here are five things to consider' but 'here is what I actually think, here is why, and here is the specific experience that changed my mind.' Audiences at tech conferences are, on the whole, smart and allergic to watered-down takes. They've read the blog posts. They want to know what someone who's actually shipped something believes.
Conference programmers remember speakers who made the audience think differently about something they thought they understood. That's the bar worth aiming for.
Specificity is what creates that effect. Naming the exact problem, the exact decision, the exact failure creates a texture that generic advice never can. You don't need a famous company name on your CV. You need a real story told with enough specificity that the audience can picture themselves in it.
A note on speaking fees and UK conference norms
The majority of UK tech conferences, particularly community-organised events, do not pay speakers beyond covering travel and accommodation. Paid keynote slots exist at larger commercial events, but they are the minority of the market. If you're starting out, the return on speaking is in credibility, visibility, and the conversations that follow, not in the fee. As your track record builds, fee negotiations become more straightforward. Going in with clear expectations about this saves a lot of unnecessary friction with organisers.
How do I find tech conferences in the UK that are open to new speakers?
Start with community-run events rather than large commercial conferences. Lanyrd no longer operates, but tech event listings on Meetup, Eventbrite, and community Slack groups (particularly those for JavaScript, Python, product management, and AI) are active sources. Many conferences publish open calls for proposals (CFPs) on their own sites and announce them on social media. Following conference organisers directly on LinkedIn or X is one of the most reliable ways to catch CFP windows early.
What should I include in a speaker bio for a conference pitch?
Keep it to two or three sentences. State what you build or have built, name a specific product or outcome if you can, and connect your background directly to the talk topic. Avoid job-title-led bios that read like a LinkedIn summary. Organisers want to know why you are the right person for this specific talk, not a general overview of your career.
Do I need previous speaking experience to pitch a UK tech conference?
Not always, but you do need to reduce the organiser's uncertainty. If you have no speaking history at all, a short recording from a meetup, an internal talk, or even a well-produced video essay can substitute. The bar at community meetups and local events is much lower, and they're the right place to build that evidence before approaching larger conferences.
How long should a conference talk pitch abstract be?
Most CFP forms will specify a word or character limit, and you should hit it precisely, not go over. If no limit is given, aim for 100 to 150 words for the abstract. That's enough to state the idea, the argument, and the audience benefit without padding. A shorter, tighter abstract signals that you can organise your thinking, which is itself a signal about your ability to deliver a tight talk.
What's the fastest way to get a first tech speaking gig?
Pitch a local tech meetup or community group with a lightning talk on something specific you've built or solved. The bar is lower, the feedback loop is faster, and you come away with a recording. From there, pitch a regional conference with a developed version of the same material. This path is slower than mass-applying to big conferences, but it produces real results because each step builds the credibility the next step requires.