DevRel Summit 2016 is now accepting proposals for talks. 

The conference will take place at Seattle Armory Lofts, August 11th 2016.

Proposals will be accepted between Monday, May 23rd, 2016 and Monday, July 4th, 2016 at 11:59pmPST (Pacific Standard Time UT-8:00)

Talks will be 25-30 minutes in length with no segment for questions.

Submit your proposal that includes an abstract, details, and pitch

Abstract will be included on the website program. This is for audience and includes a high-level overview of the talk. (600 characters or less)

Details section gives us more insight into the talk. Please include an outline of the talk, any demonstrations that you plan on doing, etc. This will not be public if your talk is accepted, allowing edits within reason until the day of the talk. No character limitation.

Pitch section is where we want to hear about why you think this talk is important. What makes you excited about this topic? Why does the audience need to hear about this?


How it works

You can edit your proposal after submission. Please submit your proposal as early as possible to allow us to provide feedback if necessary. Everything is considered a draft until the call for proposals closes. Not all submissions will receive feedback.

The DevRel Summit team is committed to a diverse, unbiased and inclusive selection process.

If your talk is selected, you'll receive:

  • A free ticket for you and your companion to the conference

  • Invitation to Speaker meet-and-greet event prior to the conference

  • Edited video of your talk

  • Anonymized feedback from audience

  • Photo of you speaking

If you've already purchased a ticket by the time you are selected as a speaker, we will refund your purchase completely—so, don't wait to buy a ticket. Also, if your company or employer is able to cover your travel and lodging, we'll happily list them as a speaker sponsor on our conference website.

DevRel Summit abides by our Code of Conduct and expects all speakers and attendees to do the same.


Questions? Email


*Thank you to Dinosaurs.js for providing a great example of CFP documentation