DevConf.CZ has always welcomed first-time speakers as well as seasoned pros. If you're a first-time speaker or just want to make sure you learn as much as possible before submitting a proposal, you're at the right place! We're going to cover all you need to know to get your proposal accepted at DevConf.CZ 2023.

Don't miss the deadline

First and foremost, make sure you submit your proposal on time and sooner rather than later. The DevConf.CZ 2023 Call for Proposals ends on March 17, 2023 EOD. We always remind the date on our social media channels and you can also make sure you have the latest information on our website.

Make it relevant and engaging

DevConf.CZ 2023 is built around a list of themes we believe are attractive for attendees as well as speakers but we're also open to other high-quality talk suggestions. We are interested in technical sessions and speakers who are not afraid to dive deep into details of the area of their interest. Sessions with a lot of audience interactions and demos are highly encouraged. We're not looking for an overview or high-level topics. Make sure to avoid product pitches and marketing presentations.

Those with a keen eye for detail might have noticed the crystal ball in DevConf.CZ logo. The motto of the conference is “#define future” and the future is what we're interested in. We'd like to see emerging topics that might hit mainstream engineering in 1-2 years. Talking about new and upcoming work generally increases your chance of acceptance.

There is a range of questions about the speaker and content in the CfP form. The title and abstract are the most important aspects of your submission as they are the primary focus of the Reviewing Committee and they become the most prominent part that will attract attendees during the conference. In case the Reviewing Committee needs further clarification, they will reach out to you during the reviewing period (after the CfP is closed).

Select the right session type

While we plan DevConf.cz 2023 as a hybrid event, please note that all sessions will be delivered in person. We plan to stream content online and make sure in-person as well as online audiences can participate in Q&A and chat. We want to make sure the content is focused, tells the whole story, and is structured in a way that allows engagement for both in-person and virtual audiences.

• Talk (35 minutes) - A talk is where you present with slides and demos to an audience. We recommend reserving some time in the end for Q&A, e.g. a 25-minute talk and a 10-minute Q&A. Feel free to recruit your colleagues to interact with people in chat while you are talking. A talk has one primary speaker, optionally another (secondary) speaker. It should be bite-sized and focused on a certain topic. This means that you should not expect to be able to cover multiple broad areas in one talk. You can submit more than one proposal, to cover a set of topics, but we cannot guarantee their final scheduled order. Therefore, we recommend you submit topics that are independent and do not need to be presented in a specific order.
• Discussion (35 minutes) - A discussion is where you lead/moderate a conversation with a group of knowledgeable panelists who answer prepared questions or questions from the audience as selected by you for appropriateness to your topic and session goal. A discussion has a dedicated moderator and up to 3 active speakers. It is an interactive session and you’re asked to engage with the audience during the session.
• Lightning talk (15 minutes) - A lightning talk is a short presentation focused on getting people interested in something new. The goal of the lightning talk is to convey key information in a clear and concise manner. Smaller technical topics, project introductions, and research/thesis topic introductions are great topics for lightning talks. Lightning talks are presented back-to-back, do not require slides and do not include Q&A.
• Two-part session (35+35 minutes) - If you require more than 35 minutes to cover a certain topic, there is an option to submit a two-part session (two 35-minute time slots with a 10-minute break in between) where we guarantee the order in the schedule. You should consider that different audiences may join each part and tailor the content accordingly. This option is recommended for deep technical dives that include a demo. You will be asked to specify why you require more time, each case will be evaluated individually.
• Workshop (80 minutes) - A workshop is a hands-on demo where you and other workshop leads interact with the audience with the goal to share your knowledge and experience on a particular bite-sized topic. The goal of a workshop is to teach or practice a skill. As a result, workshops should be actionable and goal-oriented. We allow up to 3 active presenters in a workshop.
• Meetups (80 minutes) - Meetups are organized as in-person meetings. They are open to all participants, and they serve as a place for open discussions during the dedicated time, sharing the latest project developments and interaction with contributors and attendees. We allow up to 3 active presenters in a meetup.
• Booths (all day) - A booth is a staffed table at the event. Booths are open to all participants at all times, and they serve as a place for conversations about the project and interaction with contributors, users, and attendees. There must be at least one person at the booth at all times. Preference is given to booths that will run all three days.

Do you need help with your submission?

If you still aren't 100% certain about your proposal we invite you to the DevConf.CZ 2023 CfP office hours on Friday, March 3 from 2 - 3 PM CET. (Google, Yahoo, Outlook, Office365). You can discuss your proposal or get some tips from session reviewers and past DevConf.CZ speakers.

You can also watch the recording of DevConf.cz talk 'Let's get your conference talk accepted' or take a look at the slide deck containing tips on submiting proposals.