After 10 EXCELLENT YEARS of DevOps DAYS, this year we are scaling down to a single day event, with an additional community event in partnership with AWS in April (so we’re allowing ourselves to keep the DevOpsDays name).

FOLLOWING FEEDBACK FROM PREVIOUS EVENTS, WE WOULD LIKE TO OPTIMIZE FOR ADVANCED TECHNICAL SESSIONS THIS YEAR.

At this year's DevOpsDays Tel Aviv we would like to see the diversity of our TLVCommunity groups represented:

• DevOps Israel  
• Cloud Native & OSS Israel 
• Statscraft 
• Serverless Nights 

What you should think about before you submit.

Ask yourself questions like:

• Why this talk? What makes it a must see for those attending the audience?
• Is this talk related to the subjects the conference covers?
• Have I proofread the content and done a grammatical review?
• Does this content already exist online? (DevOpsDays makes an effort to bring new content to its audience).
• Does this talk focus on a specific tool? We are of the opinion that the tooling changes and implementation details evolve. Therefore, the higher order the concept of the talk, the better. (Demos with a specific stack are welcome - however, specific tooling talks will likely be passed over, unless for an ignite session, which they are more relevant for).
• Is the topic of the talk directly related to a product or service my company offers? (Hint: If you answered yes, it probably is not the right fit.)

~/ talk language

For inclusivity purposes the main track will be in ENGLISH, as we often have attendees from all over the globe, however, we are open to having HEBREW talks in our SECOND TRACK.

~/ talk formats

We are planning on being dynamic with the talks that are submitted this year, allowing the program team to decide the ideal talk length based on the information provided in the abstract.

• We will be accommodating VERY FEW long-form talks.
• If you choose a long-form talk, please make sure it is very clear to the program team WHY you chose this length, and practically what this session will cover–these slots are reserved for advanced technical talks of 300+ proficiency levels (not thought leadership).
• Since there is a very LOW submission to ACCEPTANCE ratio, if you select long-form, and it could have been a short-form talk - IT WILL BE DECLINED.
• Be deterministic about the talk length, level, and anything else in the form.

~/ talk level

In an effort to be able to provide attendees with a better classification of talks, we are requesting both a Track categorization and proficiency - so folks can choose sessions to attend based on their knowledge and level. There will be a preference for advanced technical sessions of 200-300 proficiency levels this year.

~ / suggested topics

DEVOPSDAYS TEL AVIV covers the intersection between development and operations, with a focus on the culture, core technologies, systems, protocols & principles that are the backbone of scalable, resilient, robust, and secure systems. 

CLOUD NATIVE DAY TEL AVIV is the mirror image of DevOpsDays Tel Aviv, where the focus is indeed on modern cloud native tool chains, open source projects that power the cloud native world, containers, networking, service mesh and more. 

STATSCRAFT is focused on helping engineers understand how to make monitoring easier for humans with content that dives into the tools & methods, insights on how to derive more from your data, and ensuring systems are built to empower and enable the humans behind them to have a good quality of life. 

SERVERLESS NIGHTS is focused on topics that fall in the serverless operations domain. This includes practitioner stories related to operational excellence, unique edge cases, war stories and any other unique tales that relates to managing serverless systems.

~/ guidelines - The Finer Print

Like every year we are looking to include:

• Diversity: We embrace diversity and encourage proposals from people in underrepresented parts of our community
• Original content: content not yet presented at other conferences, or a new angle to an existing problem
• New presenters: people who are new to the space and have insightful stuff to say; we want to hear everybody’s voice
• No vendor pitches: we value vendors and sponsors, but vendor promotional talks won’t be accepted.