The Socio-Technical Staff+ Engineer: Architecture, Culture and Organisational Change

Interview:

What is your session about, and why is it important for senior software developers?

This session explores the role of the socio-technical Staff+ engineer, an engineer who understands that software systems do not exist in isolation but evolve within complex organizational and societal environments.

Architecture is influenced not only by technical choices, but also by incentives, culture, leadership, business priorities, and external forces such as AI, regulation, and global events. In this talk, I explore what it means to practice holistic engineering: designing and evolving technology while understanding the full socio-technical system it lives in.

For senior engineers, the impact of their work increasingly comes not just from writing code or designing systems, but from shaping the environment in which those systems grow.

Why is it critical for software leaders to focus on this topic right now, as we head into 2026?

We are entering a period where execution is becoming increasingly automated and accelerated, particularly with the rise of AI-assisted development.

As building software becomes faster, the real differentiator shifts toward human capabilities: understanding context, navigating ambiguity, making ethical decisions, aligning teams, and framing the right problems.

At the same time, the systems we build are becoming more embedded in society and more influenced by global forces, from geopolitical tensions to regulatory pressures and changing expectations around responsible technology.

In this environment, senior engineers and leaders need to move beyond purely technical thinking and develop the ability to read and influence the broader socio-technical system in which their technology operates.

What are the common challenges developers and architects face in this area?

One of the most common challenges is focusing on technical solutions without fully understanding the environment in which those solutions must operate.

Architects often design what looks like the “perfect architecture” on paper, only to see it struggle in practice because organizational incentives, team structures, culture, or leadership priorities were not aligned with it.

Another challenge is that many engineers are promoted into senior roles because of strong technical expertise but are not always equipped to handle the organizational and human dimensions of engineering, things like influencing without authority, coaching teams, or making implicit assumptions visible.

Finally, many engineers underestimate how much external forces, such as market shifts, new technologies like AI, or societal expectations, shape the systems we build.

What's one thing you hope attendees will implement immediately after your talk?

I hope attendees start looking at engineering problems through a wider lens.

The next time they encounter a technical challenge, instead of asking only “What architecture should we build?”, I hope they also ask questions like:

• What incentives are shaping this system?
• What organizational constraints are influencing our decisions?
• What assumptions are implicit but not being discussed?

Often the most impactful improvements come not from adding more technology, but from making the surrounding system more visible and better aligned.

What makes QCon stand out as a conference for senior software professionals?

QCon stands out because it focuses on real-world experience and practical insights from people operating at scale, rather than abstract theory.

The audience is composed primarily of staff+ engineers, architects, and technical leaders who are dealing with complex systems and organizational challenges in their daily work. That creates a space where discussions go beyond basic technical topics and address the deeper realities of building and evolving software systems in complex environments.

It’s one of the few conferences where conversations naturally happen at the level of architecture, organizational dynamics, and long-term engineering strategy.

What was one interesting thing that you learned from a previous QCon?

One of the most valuable aspects of QCon is how often the most interesting insights come from informal conversations with other attendees.

In a previous QCon discussion, I was struck by how many staff+ engineers across very different companies described similar challenges: not technical limitations, but misalignment between architecture, organizational structures, and incentives.

It reinforced the idea that many of the hardest engineering problems today are socio-technical problems, and that sharing experiences across organizations is one of the best ways to learn how to navigate them.