Every speaker on every programme was a first-time speaker once, and the regional circuit exists partly to make that first time survivable. Small events are where it happens: the rooms are smaller, the stakes are lower, the committees are actively looking for new names, and several of them hold slots back for exactly this purpose. The path from sitting in the audience to standing at the front is shorter than it looks from the audience.
Why regional events want new speakers
A conference that programmes only established speakers runs out of them. The circuit depends on a continuous supply of people giving a first talk, and organisers are aware of this in a way that is not always visible from outside: several reserve a slot or two, several weight a close decision towards the unknown name deliberately, and almost all of them would rather hear about a first talk than discover it afterwards.
The practical consequence: being a first-time speaker is worth saying in the notes field. A committee cannot apply a policy it does not know applies, and the field is private, so saying so costs nothing and occasionally decides the slot.
Where the first talk usually happens
Not at a conference. The usual first outing is a local user group, in front of twenty people, for five minutes, on something the speaker did last month. There is no call for speakers to get through, the organiser is generally delighted to be asked, and the failure mode is a slightly awkward evening rather than anything memorable.
That first five minutes does two things that no amount of preparation does. It establishes that standing up and talking is survivable, which is the part everybody underestimates. And it produces the sentence for a future speaker bio saying the talk has been given before, which is the single most useful thing an unknown speaker can put in front of a committee.
A room of twenty is not a smaller version of the real thing. It is the real thing.
Choosing a first subject
The reliable first subject is something the speaker did recently and had to work out, described concretely. Not a survey of a field, not a tutorial on a technology in general, and not an opinion about how software should be written. Something that was broken, what was tried, and what happened.
Why that shape works: the speaker is the world expert on their own experience, which removes the fear of being caught out by a question, and the specificity is exactly what a committee is short of in the pile. A talk about one build that was too slow beats a talk about build performance, and it is easier to give.
The subject does not have to be novel. Almost everything a first-time speaker knows is new to somebody in the room, and a room at a regional event contains people at every level. The instinct that says the subject is too basic is nearly always wrong.
Submitting the first proposal
Three things make a first submission stronger, and none of them is about writing.
Submit a lightning talk as well. It gives the committee a cheap way to say yes. A five-minute slot costs an event almost nothing, so a proposal that is interesting but risky is much easier to accept in that format.
Submit to a small event first. The ratio is better, the committee is closer to the audience, and a regional single-track day is a far kinder first room than a track at a large conference.
Say it is a first talk in the notes. Private field, no downside, and it is what lets a reserved slot find its way to the right person.
What does not help is apologising in the abstract. A proposal that says the speaker is new to this and hopes it might be of interest is asking the committee to take a risk on somebody who has announced they think it is one. The bio is the place for that fact, stated plainly.
The day itself
Practical things, in the order they matter. Time the talk out loud at least once, because everything runs longer spoken than read and a talk that overruns gets cut off rather than extended. Ask the organiser what the room looks like, since a projector, a clicker and a stage are three separate uncertainties that can all be removed by email. Expect to be more nervous beforehand and less nervous during than anticipated, which is the near-universal experience.
Questions afterwards are the part first-time speakers fear most and the part that most often goes well. The honest answer to a question with no answer is that there isn’t one, and a room takes that far better than an improvised guess. The corridor conversation that follows is, for most speakers, the reason to do it again.
The mechanics of getting there are on the call for speakers page, with the individual fields on the title, the abstract and the speaker bio. Lightning talks covers the format most first talks use, and if the first submission is declined, rejection and resubmission explains why that is usually about the day rather than the proposal. For the other half of a first conference, the attending half, the newcomer track starts there.
Questions
Do first-time speakers realistically get accepted?
At regional events, yes, and often deliberately. Several reserve slots for people who have not spoken before, and committees choosing between two similar proposals frequently take the new name, because the circuit depends on a supply of new speakers.
Should a proposal mention that it is a first talk?
In the notes field, yes. It is private, it costs nothing, and it is the only way a reserved slot can find the right person. In the public abstract, no: an apology there asks the committee to take a risk the proposal has just announced.
What is a good subject for a first talk?
Something done recently and worked out the hard way, described concretely. One broken thing, what was tried, what happened. The speaker is the only expert on their own experience, which removes most of the fear of questions.
Is a subject ever too basic for a conference?
Far less often than it feels. A regional room holds people at every level, and almost everything a first-time speaker knows is new to somebody in it. The instinct that a subject is too obvious is one of the commonest reasons good talks never get proposed.
Where should somebody speak before a conference?
A local user group, for five minutes. There is no call for speakers to pass, organisers are generally glad to be asked, and it produces the one line a committee most wants from an unknown speaker: that the talk has been given before.