What helps your proposal get accepted?

• Make sure your abstract is sufficiently long and detailed.
• Hint not only at the problem, but also at the solution.
• Touch on why your experience matters and give data points where helpful.
• Hearing what worked is great and hearing what didn’t work and what you learned from it is even better.
• If you have spoken before, include links. If you have never spoken publicly, tell us that, too. We’re looking for a mix of new and experienced speakers.

Some factors we consider when we assemble the final program includes (but is not limited to):

• Broad appeal: How will your talk play out in a room of people with a variety of backgrounds? Remember that DevOpsDays is a single track conference. Not everyone in the room will use your specific tool.
• Original content: content not yet presented at other conferences, or a new angle to an existing problem
• New presenters: people who are new to space and have insightful stuff to say; we want to hear everybody's voice
• Local presenters: We like to include stories about challenges and successes experienced in our local area.
• Under-represented voices: We want to hear all voices, including those that may speak less frequently at similar events.
• No vendor pitches: we value vendors and sponsors, but this is not the right forum
• No third-party submissions: If a PR firm or your marketing department is proposing the talk, you’ve already shown that as a speaker you’re distant from the process. This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees.