This is easier than you think. Most meetup organisers struggle to fill their speaking slots month after month, and providing a platform for new speakers is certainly a goal for most of them - or at least it should be!
So, show up at some meetups in areas that interest you. It won't be long before you hear the organiser asking if anyone from the audience wants to speak. If it takes more than a couple of months, collar the organiser directly during the break.
Next, write some slides and present them. The writing will take a surprisingly long time and the presenting will take a surprisingly short time. Don't pick a vast topic, pick something interesting and talk about it for a while. Also remember that "why" is often more interesting than "how".
Having done that, you now have some "material", or at least you will have after you go back and fix all the things that didn't really work during the first outing.
Now you're all set; many conferences have some kind of public call for speakers, to which you can submit your new "material". You will get loads of rejections, but that's OK. Keep plugging away at the meetups, and eventually someone who is on the program committee at a conference will remember that great talk you did about endofunctors in Angular 4.
Good luck!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How do you start speaking at conferences and meetups? I've been coding on and off for years but have never even considered it.
This is easier than you think. Most meetup organisers struggle to fill their speaking slots month after month, and providing a platform for new speakers is certainly a goal for most of them - or at least it should be!
So, show up at some meetups in areas that interest you. It won't be long before you hear the organiser asking if anyone from the audience wants to speak. If it takes more than a couple of months, collar the organiser directly during the break.
Next, write some slides and present them. The writing will take a surprisingly long time and the presenting will take a surprisingly short time. Don't pick a vast topic, pick something interesting and talk about it for a while. Also remember that "why" is often more interesting than "how".
Having done that, you now have some "material", or at least you will have after you go back and fix all the things that didn't really work during the first outing.
Now you're all set; many conferences have some kind of public call for speakers, to which you can submit your new "material". You will get loads of rejections, but that's OK. Keep plugging away at the meetups, and eventually someone who is on the program committee at a conference will remember that great talk you did about endofunctors in Angular 4.
Good luck!