Download to read offline
Uploaded bySven Peters
How to Become a Conference Speaker
The document provides guidance on becoming a conference speaker, emphasizing the importance of crafting a compelling submission that includes a clear title, abstract, and background information. It highlights the necessity of addressing relevant topics, engaging with pain points, and presenting concrete solutions, particularly in relation to burnout culture in the tech community. The authors offer insights into the process for submission and acceptance, alongside personal experiences as developer advocates at MongoDB.
More Related Content
Similar to How to Become a Conference Speaker
![[NYC Scrum] 4 bad ideas about productivity... and what Agilists should do ins...](https://cdn.slidesharecdn.com/ss_thumbnails/nycscrum4badideasaboutproductivity-250320014757-d85c2fbe-thumbnail.jpg?width=640&height=640&fit=bounds)
How to Become a Conference Speaker
- 1. Sven Peters |Developer Advocate | MongoDB | @svenpet Lauren Hayward Schaefer | Developer Advocate | MongoDB | @Lauren_Schaefer How to Become a Conference Speaker
- 2. How did webecome conference speakers?
- 3. The Program Committee Firstyou need to convince
- 4. Invited Call forspeakers Opens for 1-2 months 3 - 5 months before the conference
- 5. Where to find conferences? Co-Workers Newsletter:SeeCFP or CFP Land Twitter Other Presenters
- 6. Schedule from last year Doesit resonate? Find a Topic AttendeesPassion
- 7.
- 8. Popular Topics Future 3 Slots 10Submissions Methodology & DevOps 5 Slots 102 Submissions
- 9. A typical submission Title Abstract Moreinfo About you
- 10. The Talk Title Catchthe attention - Make your talk stick
- 11. MongoDB Retail UseCase Need for Speed
- 12. 50 - 80chars Avoid “super clever” titles Ingredients Hungry for moreSimple & Clear
- 13. Catch the attention Makeit stick Represents your message For Reviewers
- 14. 7 Things: Howto Tune Your Database Sharding: The Data Jigsaw Puzzle
- 15.
- 16. Convince the committee(and the attendees) The Abstract
- 17.
- 18. Problem Solution Solve the problem Beconcrete Examples
- 19.
- 20. A successful applicationwill require modifications over its lifetime. The question is not if, but when. This presentation will follow the life of an application and the diverse life-altering events it will go through. Events that require changes to the schema, the resources it needs, growing into a sharded cluster and, the security requirements it must satisfy. Knowing that you can evolve your application without downtime may be for you a sufficient single reason to use MongoDB for your applications. Problem
- 21. A successful applicationwill require modifications over its lifetime. The question is not if, but when. This presentation will follow the life of an application and the diverse life-altering events it will go through. Events that require changes to the schema, the resources it needs, growing into a sharded cluster and, the security requirements it must satisfy. Knowing that you can evolve your application without downtime may be for you a sufficient single reason to use MongoDB for your applications. Solution
- 22. A successful applicationwill require modifications over its lifetime. The question is not if, but when. This presentation will follow the life of an application and the diverse life-altering events it will go through. Events that require changes to the schema, the resources it needs, growing into a sharded cluster and, the security requirements it must satisfy. Knowing that you can evolve your application without downtime may be for you a sufficient single reason to use MongoDB for your applications. Learnings
- 23.
- 24. Use a spellchecker Ask a native speaker
- 25. Decision on yoursubmission
- 26. You’ve come along way…. More Info
- 28.
- 29. Qualifications Talk Outline More examples Topicrelevance Conference acceptance
- 30. A bit aboutyou Bio
- 31. Sven Peters, developeradvocate at MongoDB, has been studying trends in software development for the last 10 years uncovering the cultural and technical attributes to help development teams work effectively and drive innovation. He has 20 years experience in writing code, leading teams, and sharing his experience with thousands of developers at uncountable conferences in 25+ countries.
- 32. Great submission …but areyou a good speaker?
- 33.
- 34. There is novideo of you presenting? Create one!
- 35.
- 36. A typical submission Title Abstract Moreinfo About you First impression / sticky Convincing the committee The final punch You’re a great presenter
- 37. The Title Let’s writea submission
- 38.
- 39. Burnout at theWorkplace Try 2
- 40. Try 3 Keep yourselfalive Stopping the Effects of Burnout
- 41. The Abstract Let’s writea submission
- 42. I will talkabout why burnout culture takes away from inclusion and how to identifying burnout within yourself and your teams.
- 43. The tech communityputs a warped badge of honor around burnout. It’s often seen as an indicator of success and working hard when it’s actually harming the growth of our developer communities and teams. By helping to recognize the signs in yourself and others, we can solve one of the least talked about and most dangerous problems in tech -- and hopefully save some lives. I will talk about why burnout culture takes away from inclusion and how to identifying burnout within yourself and your teams.
- 44. The tech communityputs a warped badge of honor around burnout. It’s often seen as an indicator of success and working hard when it’s actually harming the growth of our developer communities and teams. By helping to recognize the signs in yourself and others, we can solve one of the least talked about and most dangerous problems in tech -- and hopefully save some lives. I will talk about why burnout culture takes away from inclusion and how to identifying burnout within yourself and your teams. You'll learn how to bring a healthy work and growth ethic to your team, no matter if you’re the newcomer or the tech lead.
- 45. The tech communityputs a warped badge of honor around burnout. It’s often seen as an indicator of success and working hard when it’s actually harming the growth of our developer communities and teams. By helping to recognize the signs in yourself and others, we can solve one of the least talked about and most dangerous problems in tech -- and hopefully save some lives. I will talk about why burnout culture takes away from inclusion and how to identifying burnout within yourself and your teams. You'll learn how to bring a healthy work and growth ethic to your team, no matter if you’re the newcomer or the tech lead.
- 46.
- 47.