Beat the rush and join us early for complimentary barista-made coffee and breakfast.

The teams pulling ahead in AI are not just using better models. They are making different infrastructure decisions underneath them, and the gap between AI-native and AI-retrofit is widening fast.

This keynote walks through what AI-native infrastructure actually looks like in 2026, where the patterns are converging, and what the rest of the industry will have to confront.

We'll cover:

• The infrastructure choices AI-native teams make differently from day one
• Where established cloud-native patterns break under AI workloads
• What this means for teams trying to retrofit existing infrastructure

Most AI prototypes work. Most AI systems serving real users are harder than they look. The gap between the two is where most of the engineering work that matters actually gets done.

This panel brings together engineering leaders who have taken AI from prototype to production at scale, to discuss what broke and what they had to retrofit under pressure.

We'll cover:

• The architectural decisions that turned out to matter once real traffic arrived
• What teams underinvested in early and paid for later
• How the engineering bar for AI is different from traditional software

A live scenario where a major model provider announces an EOL on the model powering your most important product feature. Attendees vote through their phones on migration strategy, capability regression, and engineering trade-offs, with the scenario evolving as the room decides.

A real-world version of a dependency risk problem most senior engineering teams now face and few discuss openly.

Agent demos work because the path is clean. Production workflows are messy. Tools fail, context drifts, permissions get tangled, retries duplicate actions, and the system needs to know when to stop.

This session walks through how one team designed agentic workflows that could operate safely with real users, where they drew the line on autonomy, and what broke first when the demo became a product.

We'll cover:

• Where agents were given authority to act and where humans stayed in the loop
• How tool calls, retries, state, and memory were managed under pressure
• What broke first when the workflow moved from demo to real users

Once AI systems start taking actions on behalf of users — calling tools, moving data, triggering workflows — the engineering bar shifts. Prompt injection, tool misuse, data leakage, eval failures, and silent reliability regressions all become live operational concerns, and most teams are figuring out the patterns in real time.

This panel brings together engineering leaders working on the safety, control, and reliability of production AI to discuss what is actually working and where the open problems still sit.

We'll cover:

• How teams are deciding what an AI system is allowed to do and where humans review
• What's working against prompt injection, tool abuse, and data exposure
• How reliability and observability practices are being rebuilt for systems that take action

Delegates choose from a list of peer-to-peer discussion topics covering the engineering challenges that aren't getting solved in public.

Topics include:

• Inference performance — runtime, batching, caching, quantization
• Model-layer decisions — API, fine-tuning, distillation, training
• Context engineering — retrieval quality, grounding, feedback loops
• Eval engineering — harnesses, LLM-as-judge calibration, eval-driven development
• Training infrastructure at scale — clusters, checkpointing, failure recovery
• Data engineering for AI — pipelines, synthetic data, labeling
• AI observability — what to track beyond latency and errors
• GPU and accelerator strategy — when custom silicon starts to make sense

A fast-paced quiz covering real-world AI engineering trivia, key concepts, and emerging trends. Compete for bragging rights — and a travel voucher — as the top scorer takes the crown.

AI is rewriting what it means to be a software engineer faster than most leaders are willing to say publicly. Junior engineers are doing work that used to require five years of experience. Senior engineers are spending more time reviewing AI output than writing code. Some teams are getting smaller while output expectations climb.

This keynote takes an honest look at where the craft of engineering is going, what's happening to team composition and career paths, and what leaders should be thinking about now.

We'll cover:

• How the day-to-day work of engineering is actually changing
• What's happening to junior roles and the career ladder beneath them
• How team composition is shifting and what skills are becoming valuable

Some AI products live or die on latency. Voice systems, real-time copilots, and conversational interfaces all have latency budgets that fundamentally shape what's possible underneath.

This session walks through how one team built an AI product where latency was a first-order constraint, the choices that flowed from it, and what changed about how they operated.

We'll cover:

• How latency requirements shaped the underlying architecture from day one
• What the team tried that didn't work and what delivered the wins
• What changed about how they operate once latency became release-blocking

The AI stack is moving fast enough that decisions being made today will look obvious or wrong in 18 months, and nobody is sure which is which. Self-hosting versus managed APIs. Hyperscalers versus dedicated AI clouds. Agent platforms versus building it yourself. Custom silicon versus established GPUs.

The audience votes live on a series of contested questions, the panel argues each result out, and the room votes again at the end to see whether anyone shifted position.

We'll cover:

• Which parts of the stack are converging and which are still genuinely contested
• Where the build-versus-buy line should sit on inference, agents, and evals
• Which bets are most likely to look wrong in 18 months and why

Unwind with your peers for a couple of drinks on us.