AI systems are rapidly moving from experimental tools into components of critical infrastructure embedded in products, platforms, and decision-making processes. As adoption accelerates, the consequences of poorly designed AI systems are becoming more visible—from discriminatory outcomes to security vulnerabilities and unsustainable computational costs.

We are at a stage similar to other major technological transitions in history, where new engineering practices must emerge to make systems safe and reliable at scale. Software leaders play a key role in shaping those practices. As we head into 2026, organizations that treat ethical AI as an engineering discipline—rather than an afterthought—will be better positioned to build trustworthy, resilient, and at the end of the day better AI systems.

One of the biggest challenges is that many ethical risks in AI systems are difficult to detect using traditional software engineering approaches. Bias may originate in training data, explainability can be limited by model architecture, and security vulnerabilities can arise from new attack vectors such as prompt injection or model extraction.

Another challenge is translating high-level principles—such as fairness or transparency—into concrete engineering practices. Teams often lack clear architectural patterns, evaluation metrics, or operational tools to implement these principles throughout the AI lifecycle. As a result, ethical considerations are frequently addressed too late, when systems are already in production.

I hope attendees start treating ethical properties of AI systems the same way we treat reliability, performance, or security—as engineering requirements that must be designed, measured, and continuously monitored.

In practice, this means incorporating fairness evaluation, explainability checks, security testing, and resource efficiency considerations directly into the development lifecycle. By embedding these practices early in system design and architecture, teams can build AI systems that are not only powerful, but also trustworthy and responsible.

I also hope people leave with a stronger curiosity about the risks and limitations of AI: following the growing body of research in the field, questioning assumptions, and becoming more aware of the societal and technical implications of the systems they build.

QCon stands out because it focuses on real-world engineering challenges and lessons learned from building systems at scale. The conference brings together experienced practitioners who share practical insights rather than theoretical ideas, creating an environment where senior engineers and architects can learn directly from peers facing similar problems.

This emphasis on practitioner-driven knowledge makes QCon particularly valuable for professionals responsible for designing and operating complex systems, especially as new technologies like AI reshape the software landscape.