Speaking at developer conferences: What programme committees expect from tech talks

Programme committees at developer conferences expect a tech talk that solves a real technical problem from production, has a clear audience level and contains no sales pitch. Almost all of these conferences fill their programme through an open call for papers, and practitioners from the community decide on the proposals. At large conferences there are more than ten proposals for every speaking slot, which is why a proposal has to answer every question the committee might ask in advance. This article explains the selection process and the route onto these stages.

How do developer conferences allocate their speaking slots?

Developer conferences fill most of their speaking slots through a call for papers, the public invitation a conference issues to collect talk proposals. If you want to speak, you submit an abstract, the short description of your planned talk that later appears in the programme, and often an outline as well. A programme committee decides on the proposals: the group of experts who review every submission and assemble the programme from them.

At developer conferences this committee almost always consists of practitioners who build software themselves and review on a voluntary basis. The Cloud Native Computing Foundation describes the process for KubeCon + CloudNativeCon in three stages. First, at least five volunteer reviewers per track score and comment on every proposal, then the track chairs recommend the top 30 per cent. The two programme co-chairs make the final selection from that list and look for a mix of companies and for a fixed share of people speaking at the conference for the first time.

Some conferences review the first round anonymously. Reviewers then see only the proposal itself, and your name or employer plays no part in the first assessment. For experts without stage experience this is an advantage, because their proposal competes on content alone. How a call for papers runs from discovery to acceptance is explained in the call for papers guide.

The Cloud Native Computing Foundation published the first figure for its European conference. More than eleven proposals competed for each slot, 58 per cent of submissions came from vendors, and among the accepted talks the share from end-user companies was higher than among submissions, at 45 per cent. The second figure comes from DOAG, which runs JavaLand as a community conference for the Java ecosystem. The third comes from our analysis of 2,415 conferences that publicly advertise speaking slots for 2026, where a further 99 fall under software architecture and backend.

What do programme committees expect from a tech talk?

Programme committees expect a tech talk to address a clearly defined technical problem and a solution proven in production, with an honest picture of the effort and the mistakes along the way. Proposals that introduce a tool or explain a technique in general terms fail, because the audience already knows these basics from documentation and videos. Proposals get accepted when they report something that can only come from your own work, such as the migration of a legacy system with measured response times before and after, or an outage with its root cause and the changes that followed.

The second criterion is level. Almost every form asks whether a talk is aimed at beginners or at advanced practitioners, and the committee checks whether the proposal matches that claim. A talk submitted as advanced that spends twenty minutes on basics disappoints the room and hurts the conference's ratings. Reviewers therefore read the outline closely, because it shows how much time goes into each part and whether the talk fits the planned slot.

The third criterion is what the audience takes away. People at a developer conference want knowledge they can apply in their own project, such as a pattern for error handling or a decision rule for choosing a database. An abstract that names these takeaways explicitly makes the committee's job easy. Many committees value live demos and code on slides, yet they also weigh the risk, because a demo that fails in front of the audience costs the session its strongest part. What committees look for across all types of conference is covered in what a programme committee looks for in an abstract.

What formats exist at developer conferences?

Developer conferences have four basic formats: the lightning talk of five to ten minutes, the regular talk of 30 to 50 minutes, the workshop lasting half a day or a full day, and the keynote. Lightning talks present a single idea, and many conferences allocate them at short notice or through a separate call. The regular talk is the format through which most experts get on stage, and it makes up the bulk of every programme. Workshops require their own submission, with learning objectives and the technical setup participants need to bring.

Programme co-chairs usually fill keynotes by invitation, and at large conferences sponsored keynotes are part of the top sponsorship packages. JavaLand runs a separate newcomer call for people speaking for the first time, and many conferences offer new speakers mentoring by experienced colleagues. Meetups and user groups, the regular local gatherings of a tech community, offer small stages with short lead times, and a talk there gives you the recording that many forms for large conferences ask for.

Why do product pitches fail at developer conferences?

Product pitches fail at developer conferences because committees protect their programme from advertising and the audience spots sales intent immediately. In its submission guidelines, the Cloud Native Computing Foundation states explicitly that sales or marketing pitches are almost always rejected because they undermine the integrity of the event. Similar rules appear in the calls of most community conferences, often combined with a code of conduct for all speakers.

Software vendors still have good chances on these stages. At large conferences they submit the majority of proposals and give a large share of accepted talks, but they speak about a problem the audience has even without their product. A talk on debugging distributed systems that features your own tool as one of several examples gets accepted, while a talk with the product name in the title fails. Where audiences draw the line is described in expert talk or sales pitch.

Alongside the open call, large conferences sell sponsorship packages, some of which include a speaking slot. This model is called pay to speak, and such a slot easily costs 10,000 euros or more for a single speaking slot. Sponsored sessions are often not labelled as such in the programme, yet a technical audience frequently reads them as advertising. A slot from the call for papers costs you only preparation and travel, and the committee's selection confirms the technical quality of your talk in front of the room.

How do you get onto developer conference stages as an expert?

As an expert, you get onto developer conference stages with a series of submissions, each tailored to the track and level of the conference in question. There are many calls, deadlines sit close together, and every form asks for outline and experience differently. In our analysis, the median time between the close of a call for papers and the start of the conference is 50 days, and if you miss a deadline you usually wait a year for the next edition. International conferences require abstract and talk in English, which the article on international conferences covers in more detail.

Stage Starter takes this work off your hands: we find the right calls, write the submission and submit it. That includes tailoring your talk to developer and community conferences, versions in German and English, and following up until acceptance. You provide your expertise from projects and approve the talk and abstracts once before we start. Working with Stage Starter starts from €990 net per month, and if you want a written roadmap first, you begin with the Speaker Audit from €2,000 net.

With our submissions for clients we reach up to 19 per cent acceptances per conference, while 5 per cent at most is usual in the market for this volume of submissions. Across ten conferences, the chance of at least one acceptance is around 88 per cent at 19 per cent per conference and around 40 per cent at 5 per cent per conference. This is based on 2,189 submitted abstracts and around 22,700 conferences in our database, with around 1,500 open calls for papers on the reference date. No agency can guarantee an acceptance, because each programme committee decides for itself. How an agency works for IT and software companies is described in the article on the speaker agency for IT and software.