Call for Papers GuidelinesEvery 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 technical professionals, practitioners 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 tools and primitives that are changing how we build and operate software
- Cutting-edge research and experimental approaches
⚠️ 101/introductory content about mainstream technologies will NOT be accepted. We received a large number of AI/ML and AI Agents introductory proposals in our previous editions that couldn't fit the schedule. Please ensure your content is truly advanced and relevant.
📍 Topic Priorities
- AI/ML (AI for software development, AI systems)
- Software Engineering & Architecture
- Cloud & DevOps
- Cybersecurity
Selection Criteria
Preference will be given to proposals of sessions:
- Mid-advanced level content
- Not previously performed at other conferences in Italy
⚠️ 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 content that do not hold a hidden marketing pitch
Any example?
✅ DO submit:
- AI/ML: How AI-assisted development changed our engineering workflow - velocity, quality and what we lost
- AI/ML: Evaluating LLMs in production - metrics, tradeoffs and hard lessons
- AI/ML: Local-first AI agents - architecture tradeoffs between privacy, capability and control
- Software Engineering: Technical debt at scale - how we paid it back without stopping feature delivery
- DevOps: How we cut deployment time by 80% without rewriting anything
- Security: How we detected and contained a supply chain attack in production
- Architecture: Why we went back to the monolith - and what we'd tell our past selves
❌ DON'T submit:
- Introduction to [Any Technology]
- What is [Basic Concept]?
- [Technology] 101
- Getting Started with [Framework]
- My first project with [Tool]
- What are AI Agents? (introductory AI content will not be accepted)
- Introduction to RAG (see above)
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 1 month before the conference date (28 October 2026).
- Not accepted: You will receive an email informing you that your proposal is rejected. You may receive this up to 1 month 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 1 month before knowing the outcome of their proposal. The organisers are open to providing feedback on rejected proposals if contacted.