The team structures that worked yesterday need rethinking for AI adoption

You have a team culture that ships. You understand ownership, coordination, and how to maintain quality under pressure. That foundation holds – but AI adoption introduces friction in places you did not expect. Ownership blurs when agents act across boundaries. Architectural discipline erodes when generation replaces deliberation.

Engineering Teams in the Age of AI

Learn from Industry Leaders about:

  • AI Literacy for Software Engineers: What engineers need to understand about AI systems – and what they need to stay skeptical about
  • Team Structures for Modern Development: Organizing teams around system boundaries and reducing coordination overhead
  • Human–AI Collaboration: Effective working relationships between engineers and intelligent systems
  • Engineering Culture & Discipline: Maintaining quality and architectural thinking when delivery pressure is constant
  • Governance & Responsible Technology Use: Policies, guardrails, and accountability for AI-augmented systems
  • Developer Experience in Modern Environments: Designing workflows and toolchains that support effective, sustainable engineering work

Track Speakers 2025

Track Program 2025

Track Sessions on Jax London

Track Sessions on Jax London

View all sessions

Frequently Asked Questions

What is the focus of the track?

The focus is on the evolution of engineering leadership and team dynamics during AI adoption. It addresses how to rethink team structures, maintain ownership, and preserve engineering discipline when traditional coordination and quality-control methods are challenged by the speed and nature of AI systems.

How do we handle "blurred ownership" when AI agents act across different team boundaries?

The track explores Team Structures for Modern Development, focusing on organizing around system boundaries. You’ll learn how to redefine ownership and coordination so that even when agents are involved, the responsibility for system integrity remains clear and human-led.

What does "AI Literacy" mean for a software engineer in this context?

It’s not just about knowing how to write prompts. It’s about understanding the underlying behavior of AI systems so engineers can identify unreliable outputs and architectural risks. The track emphasizes teaching engineers what to trust and, crucially, what to stay skeptical about.

How can we maintain our engineering culture if AI is doing the heavy lifting?

A major topic is Engineering Culture & Discipline. You’ll learn how to prevent "architectural erosion"—where generation replaces deliberation. The track provides a framework for keeping human judgment and quality at the center of the development process, even under constant delivery pressure.

What kind of governance is required for AI-augmented systems?

You will explore Governance & Responsible Technology Use, focusing on the policies and accountability models needed for AI systems. This includes building guardrails that ensure AI-generated results align with organizational standards and that there is a clear path for human intervention when systems deviate.

STAY TUNED!

JOIN OUR NEWSLETTER

[mc4wp-simple-turnstile]

Explore other Tracks

Engineering Teams in the Age of AI

The team structures that worked yesterday need rethinking for AI adoption
DevOps, CI/CD & Platform Engineering

The platform is what makes AI systems trustworthy in production
Software Architecture for Intelligent Systems
Designing systems that stay coherent as intelligent capabilities enter the architecture.
Software Engineering Practices
Engineering judgment is what gives AI-generated code its quality.
AI in Development & Agentic Systems
The engineer who understands systems is the one who can direct AI
Enterprise AI: Security, Scale & Performance
Keeping AI systems secure, cost-efficient, and stable under real-world conditions.