Call for Papers Guidelines

Every year we receive hundreds of proposals for our Conference and we have to make a selection based on a number of reasons:

• How it fits in the agenda
• Relevance of the topic/technology
• Expertise of the speaker
• Description of the proposal

Our audience consists of developers and technical leaders looking for advanced insights and real-world experiences.

You can find useful tips from Codemotion’s Technical Committee in this article.

✅ We WELCOME introductions to:

• Emerging technologies
• New frameworks and tools just entering the ecosystem
• Cutting-edge research and experimental approaches

⚠️ 101/introductory content about mainstream technologies will NOT be accepted. We received dozens of AI/ML introductory proposals last year that couldn't fit the schedule. Please ensure your content is truly relevant.

📍 Topic Priorities for 2026

• AI/ML (advanced implementations)
• Backend & Software Architectures
• Cloud & DevOps
• Data Engineering & Analytics
• Cybersecurity

Selection Criteria

Preference will be given to proposals of sessions:

• mid-advanced level content
• not previously performed at other conferences

⚠️ Please note: To avoid frustration, check if your topic fits our priorities before investing time in your proposal. If uncertain about the track fit, feel free to contact us for guidance.

What do our attendees look for?

• Showcase of technical excellence, latest research and cutting-edge technologies
• Hands-on knowledge that could be useful for their job
• Best practices and case studies that can help them become better developers
• Code! Remember to show some lines of code and some demos
• Inspirational talks and visions on how technology is shaping the future
• Advanced implementations, real production cases
• Lessons learned from actual production deployment
• Talks with great contents, which do not hold a hidden marketing pitch

Any example?

✅ DO submit:

• AI/ML: How we scaled ML to 1M users at [Company]
• DevOps: Lessons from migrating 500 microservices to [Technology]
• Security: Real-world security incidents and how we handled them
• Data: Building a real-time data pipeline processing 1TB/day
• Architecture: From monolith to microservices: 2 years later

❌ DON'T submit:

• Introduction to [Any Technology]
• What is [Basic Concept]?
• [Technology] 101
• Getting Started with [Framework]
• My first project with [Tool]

When will we contact you?

There are 3 possible outcomes for your proposal(s):

• Approved: You will receive an email confirming your talk is selected. The organisers may contact speakers in 3 rounds as they announce new speakers on their website.
• Waiting for approval: Your proposal is still under review. This process can last up to 2 months before the conference date.
• Not accepted: You will receive an email informing you that your proposal is rejected. Again, you may receive this up to 2 months before the conference.

The organisers try to contact speakers as soon as the Call for Papers closes but finalising the agenda and scheduling backup talks can take time. Speakers should expect to wait up to 2 months before knowing if their proposal is approved, waiting for approval or not accepted. The organisers are open to providing feedback on rejected proposals if contacted.

Travel expenses refund will be considered as part of the selection process.