A few years ago, I made a goal for myself that I would start speaking at conferences. In the past I had gone to quite a few awesome conferences and I really admired the folks who could get on a stage, share a bunch of knowledge and inspire an audience to do cool stuff. While I had a bit of experience with public speaking (I spoke at some local iOS/Android meetups and moderated two panels at SXSW back in ’11 and ’13), I wanted to try for a “real” conference spot.
I think the conference that convinced me to start applying was Swift Summit, which I attended in 2015. There were a number of really inspiring talks, and the community felt really fresh and welcoming. One interesting aside: I learned after joining Lyft that no fewer than three of my current coworkers on iOS spoke at that conference (Keith, Sam and JP, though only Keith was working at Lyft at the time) and a few others attended that year. I’m not sure if that’s correlation or causation at work.
Step 1: Applying to speak
According to my Google Doc which keeps track of my CFP applications, I started applying heavily in 2016. There was a gap between when I wanted to apply and when I started to apply simply because I felt I didn’t have much to talk about. Once I had some interesting experience with iMessage and accessibility while working at Starbucks, I figured people might want to know about those things, too. In retrospect I think I probably waited too long. If you are passionate about something, don’t wait until you feel you’re an expert on the subject. That day probably (at least for me) will never come, and you can always do research about your topic once it’s been accepted!
In all of my CFPs I use a template which I learned about during my time in the Twilio Heroes program. Essentially, you need to:
- State a problem or challenge
- Give some general solutions (set up a straw man)
- Give your specific solution that is better than #2, because you are awesome.
Here’s an example of my iMessage talk, which used that template:
(1) Messaging apps are huge and getting huger. With WhatsApp, WeChat and Facebook Messenger users in the millions or billions, it’s clear that messaging is not a fad. So how can a developer take advantage of this growth? (2) Starting a new messaging app is probably out of the question. (3) Thankfully, Apple has introduced iMessage app extensions in iOS 10. Learn how to use iMessage to let your users send rich, interactive messages, and learn how to take advantage of the network effects that iMessage app extensions allow, including updates introduced in iOS 11 like Live Message Layouts and the Direct Send API.
Step 2: Getting rejected
After using this template for talks and applying to pretty much every iOS related conference in 2016, I ended up getting a ton of rejections. This is totally fine and to be expected since I think most conferences get way more talk proposals than they have spots. I also noticed that conferences tend to invite speakers who have spoken before, which is a form of risk management but also kind of unfair for people who have never spoken.
The best way to beat this sort of chicken and egg situation is probably to aim at local meetups which are always looking for people to give talks! Another benefit of this is that you get to practice your talk and refine it before taking it to a bigger stage and audience (which is exactly what I did for my accessibility talk that I gave at iOSCon in London this year). Because I had given my talk at an Xcoders meeting two weeks before the conference, I was able to time my talk, practice it in front of people, get their questions to incorporate back into the talk, and feel like I was ready once I spoke in front of a larger crowd.
Step 3: Getting accepted
The first year I really started getting serious about applying to conferences, my acceptance rate was 1 of 7¹. Success! I attended the first CodeMobile conference in Chester, UK and talked about iMessage apps. The experience of going on stage, sharing something I thought was interesting, and then getting feedback that it actually was interesting to people was great! The attendees were all amazing and I finally got to travel outside of North America for the first time in my life. I had reached my goals and become an International™ Speaker as well as generally becoming an iOS Conference Speaker all in one go.
Step 4: Preparation
The thing that most people don’t tell you, and the thing that you quickly find out when preparing a conference talk is how much work it is to prepare! As an audience member to some great talks, I always assumed that the talk took maybe a handful of hours to prepare and format.
In practice, a talk can take something like 40–50 hours for a 45 minute session. That includes coming up with the proposal, learning about the subject (often this happens after the proposal has been accepted!), coming up with a format that will educate and inspire (and hopefully entertain) your audience, and practicing the delivery of the material. You probably also want to tailor your presentation for the audience you’re speaking to; are they mostly students? What skill level would be most appropriate to present to? What kinds of jokes might work well with your audience?
A good amount of the time that I put into preparing talks is practicing. It’s really up to you how polished you want the talk to be, and how comfortable you will be presenting with the amount of practice you’ve put into it. As I mentioned before, presenting early to a smaller group can really help by creating a deadline that is sooner than the actual talk and providing a method of gathering feedback to tweak your talk to make it even better.
One thing that’s great about having a conference talk lined up is that you can do some pretty productive stuff while procrastinating. In order to avoid preparing my iOSCon talk, I applied to speak at a conference in New York called !!Con. That application ended up getting accepted, so I started down a pretty vicious cycle of speaking at more conferences!
I recently came across this Twitter thread of many speakers sharing their process and how much time they put into their talks:
Step 5: Actually presenting
Giving the actual talk is kind of a weird experience. After putting a ton of time into a talk upfront, I’ve found that the actual talk goes by faster than I think it will. Once I get up and start talking, I’m more or less on autopilot, and it’s almost like having an out of body experience. It might be because I put all of my brain power into giving the talk, but I can’t even really remember how I did once it’s done. Then at the end everyone claps and hopefully people ask insightful questions and no one asks a question that’s really just a statement that they’re trying to use to prove that they know something.
Once I’ve given the talk, I can actually enjoy the conference. I’ve been lucky that the first few conferences I’ve spoken at, I was the first speaker after the keynote speaker on the first day. Going earlier is also nice because then people have seen you talk and they’re usually more open about chatting with you in the hallway.
Presenting some more
After speaking at CodeMobile in Chester, UK, I didn’t get any talks accepted for about a year. I ended up speaking again in the UK, this time in London for iOSCon in March of 2018. Then I most recently spoke at !!Con in New York in May. I’ll be giving an updated version of my iOS accessibility talk in Boston next month for SwiftFest.
This time around my acceptance rate was 3/6, which is much better. I would mostly chalk this up to the fact that I gave a talk at CodeMobile last year. I also applied to some more diverse types of tech conferences since there were fewer iOS specific ones (I think a few that I applied to didn’t actually happen).
In the future, I hope I can speak again but with the three consecutive talks I’m doing in March/May/June this year, I’m ready for a little break before I get back on the conference speaking circuit. I’m really happy that I’ve been given the opportunity to share some of my experiences and the conferences I’ve been to have been really enjoyable so far.
You should talk, too!
When I first set my personal goal to talk at some conferences, I really wasn’t sure if I had what it would take to succeed. I don’t consider myself a great public speaker, nor would I consider myself to be an exceptional software engineer. The secret is that neither is really a requirement to share cool stuff with people. You just need to have some passion for something and effectively communicate that passion by telling your story.
If you’re looking for iOS conferences to apply to, there’s a well maintained list along with CFP deadlines here. Good luck!
Finally, if you see me at a conference, say hi! I’m always happy to chat with people, even if I look like I’m busy or focused on other stuff.
¹Actually I ended up getting another talk accepted but the conference was not interested in reimbursing me for any travel expenses so I politely declined. Given the amount of time it takes to prepare a good presentation, a conference should absolutely reimburse you for speaking.