Speak at Code Europe.
Poland’s leading tech conference attracting CEE’s engineers, architects, and tech leads building modern software in the age of AI. Each track curated by practitioners in that field.
The room you’ll be speaking to.
Architects, engineers, and tech leads from CEE’s leading technology companies - people who ship systems for a living. When you present, you’re speaking to peers who’ll recognize the trade-offs without needing the basics explained.
The company you’d be keeping.
Past Code Europe editions have featured creators and core contributors to the languages and tools your audience uses every day - alongside practitioners from Google, Microsoft, Anthropic, AWS, CNCF, GitHub, Netflix, NVIDIA, and Harvard.
We invest more in headline speakers each edition than the previous one. Most accepted speakers don’t fall in that bucket - but if your background and proposal fit, we’ll reach out directly.
Pick the audience you most want in the room.
Code Europe runs deep tracks with tight clusters. The bullets below each track are indicative - examples of what tends to land well, not a fixed list. If your talk genuinely fits more than one track, it’s probably too generic - pick the audience it serves best.
AI Engineering & Data
For ML, AI, and data engineers shipping production systems.
Cloud, DevOps & Platform Engineering
For platform engineers, SREs, cloud architects.
Software Architecture & Engineering Excellence
For staff+ engineers, tech leads, architects.
Embedded across every track.
We don’t run a separate security track - security belongs where engineers and operators actually meet it. Each track owns a clear slice. Submit to the audience you most want in the room.
AI security
Prompt injection and realistic defense patterns. LLM output validation against PII leaks and exfiltration. Securing agents with tool access to production systems. AI supply chain - model provenance, dataset integrity.
Infrastructure security
Zero trust architecture in real adoptions. Secrets management at scale (Vault, cloud KMS, SOPS). Kubernetes security posture and runtime. CI/CD supply chain - Sigstore, SLSA, signed builds.
Developer-side security
Threat modeling engineers actually do. OWASP Top 10 for modern stacks - it’s different from 2017. Dependency security beyond npm audit. Secure-by-design API patterns.
Engineering careers, trends, and personal practice.
Code Europe’s spine is hard technical content. These topics run alongside - talks attendees value between deep technical sessions. Submit to whichever track frames your takeaway best, or use the “doesn’t fit” option in the form.
Where senior engineers go from here.
Staff+ trajectories. Engineering management transitions. Compensation realities at senior bands. Building reputation outside your employer through OSS, writing, and public work.
Where the field is going.
Where engineering teams are heading in 2026 and beyond. What AI assistants change about org structure and IC work. Honest retrospectives on the trends people called inevitable.
20-year engineering careers.
Learning practices that scale with seniority. Burnout patterns and what holds across decades. Specialization versus generalist bets. Mental models that hold up across stack rewrites.
Pick the format that fits what you have to say.
Five formats. Stage Talk and Workshop are what the program is built around. Online Talk, Panel, and Lightning Talk fill specific slots. Submit to the format that matches your material - not the one with the most prestige.
Stage Talk
The main format. Bring a system you shipped, a decision you defended, a result you measured. Stage Talk is for engineers who can carry a senior room for 40 minutes with substance - not slides, not war stories without a takeaway.
Workshop
Hands-on. Attendees leave having built something, not just heard about it. Workshop submissions need a clear flow, prerequisites, and a description of what people will have working by the end.
Online Talk
Same depth as Stage Talk, no travel. Available live and on-demand. Right format if your audience is global and your story doesn’t need a room.
Panel
Facilitated conversation between 3–4 practitioners. Submit with a panel theme and your co-panelists already on board. We help finalize the lineup.
Lightning Talk
One sharp insight, one production lesson, one tightly-bounded story. The format for engineers who’d rather make one point land than cover three loosely.
What you request isn’t always what we assign. We sometimes propose a different format because your material is stronger at a different length - that’s a conversation, and you’re welcome to push back.
Reviewed by engineers, on engineering merit.
Every submission is read by senior engineers and architects from the Code Europe program. We rate on technical depth, originality, and audience fit, and respond to every submission - accept or decline.
You submit through the form
Takes 15–20 minutes. Limit of 3 submissions per speaker - we de-duplicate manually after the deadline.
First-pass filter
Submissions are filtered on the title and abstract alone - anything that signals the wrong audience is removed before deeper review. Hype framing, vendor demos, and beginner content don’t make it past this step.
Track-level review
Senior practitioners from each track rate submissions on depth, originality, and audience fit. Borderline cases are evaluated against past speaking experience - links and recordings help.
Program shape
We balance across clusters within each track to avoid topic-clustering. A strong talk can be declined if four other strong talks already cover the same ground.
Decision by email
Accepts include the assigned format and slot. Declines include a one-line reason - typically the cluster was full or the framing didn’t land.
Signal the result, point at a system.
- ▹A concrete first paragraph that signals the result you’ll deliver.
- ▹A system or measurable outcome you can point at.
- ▹Links to past talks or recordings, especially for borderline submissions.
- ▹Specific numbers over general claims.
- ▹A single track that genuinely fits - focused beats scattered.
Focused beats polished.
- ▹Pick the track whose audience you most want in the room.
- ▹First paragraph promises something specific; the rest delivers detail.
- ▹If you’ve given a version of this talk before, link the recording.
- ▹15–20 minutes of focused time is enough - we don’t need polished prose.
What you get if you’re in.
Code Europe covers travel, accommodation, and event fees for every accepted speaker. The benefits below apply to everyone in the program.
Travel covered
Economy flights, up to 3 nights international, 2 nights domestic. Booked through our travel desk after acceptance.
Accommodation covered
Hotel near the venue, arranged by us. You don’t book anything.
Full event access
Event fee waived. Full access to both conference days, including the partner zone, sessions across all tracks, and the afterparty.
Speaker dinner
The night before the on-site day. Speakers and program team only. The conversation you came for happens here.
Recording & distribution
Your talk is published on the Code Europe YouTube channel after the event. Reach extends well past the conference room.
Direct contact with sponsors
Speakers get the kind of access to engineering teams at our partner companies that attendees don’t - useful if you’re hiring, looking, or building.
Common questions before submitting.
If your question isn’t here, write to [email protected]. We respond within a few days.
01What language are talks delivered in?+
02Can I submit more than one talk?+
03Can I co-present with other speakers?+
04Do you accept pre-recorded talks?+
05When is the submission deadline?+
06When will I hear back?+
07Do you pay speaker fees?+
08What if my talk doesn’t fit any of the tracks?+
09Will my talk be recorded?+
Submit your talk.
The submission form takes 15–20 minutes. We respond to every submission - accept or decline. If you’re not sure your talk fits, write to [email protected] first.