Your Best Engineers Should Design Your Organization

The most effective senior engineers don't just choose technology; they design the organization and culture required for that technology to thrive.

In a recent InfoQ presentation, engineering leader Vanessa Formicola argued that the most effective senior technical leaders must move beyond “wishful architecture” and practice holistic socio-technical engineering. She frames the Staff+ engineer role not as someone who just picks the best tools, but as a designer of the organizational conditions that allow technology to thrive. According to Formicola, many ambitious technical projects fail not because the technology was wrong, but because the organization wasn't set up to support it. The key insight is that technology and the human organization that builds it are a single, interconnected system, and senior engineers must be empowered to influence both parts.

Socio-technical engineering involves analyzing factors far beyond code and infrastructure. It requires a deep understanding of the organization's maturity, its reward structures, team dynamics, and even the broader geopolitical climate. For example, a Staff+ engineer might advise against adopting a complex microservices architecture not because it's technically unsound, but because the company’s incentive system rewards individual “hero” developers over the cross-team collaboration required to maintain it. Similarly, they might analyze how communication patterns between teams (a concept known as Conway's Law) will inevitably shape the software architecture. This approach treats organizational friction, political capital, and team skill gaps as first-class problems to be solved, just like a software bug or a performance bottleneck.

The idea of connecting organizational structure to technical outcomes has been a cornerstone of software development theory for decades, most famously through Conway's Law. However, Formicola’s perspective represents a growing trend that formalizes this responsibility within the Staff+ engineer role. Traditionally, these senior individual contributors were seen as deep technical specialists who solved the hardest coding problems. The modern view, driven by the immense complexity of cloud-native systems and distributed teams, recognizes that the biggest risks are often human and organizational. This shifts the focus from pure technical brilliance to a more holistic ability to diagnose and influence the entire system of people, processes, and technology.

For engineering leaders and CTOs, the practical takeaway is to redefine and empower the Staff+ engineer role. These individuals need the mandate to influence team structure, hiring processes, and project roadmaps, not just technical blueprints. For developers aspiring to senior roles, this means cultivating skills beyond coding, such as systems thinking, negotiation, and organizational psychology. Companies should start evaluating senior candidates not just on their ability to design a system, but on their ability to diagnose why a previous project failed due to non-technical reasons. As this trend continues, expect to see more companies explicitly including responsibilities for organizational design and cultural change in their Staff+ engineer career ladders.

This reframes the Staff+ engineering role from a purely technical expert to a strategic organizational designer. For senior ICs and engineering leaders, it highlights that technical excellence alone is insufficient; success depends on navigating and influencing the complex human systems within which technology is built.

Companies that empower Staff+ engineers to address organizational issues can avoid costly projects that fail due to cultural or structural misalignments. This approach leads to more sustainable technical strategies, better team retention, and a higher probability of successful project delivery.