Teams & Orgs at QCon San Francisco 2026

Most "AI for engineers" content is about typing faster. That's IC-level work. Staff engineers have a different question to answer. When AI raises the floor on what every engineer can ship, what is the staff engineer's job, and where does the leverage actually come from now?

Code review was built for a world where humans wrote all the code.

In 2009, every big enterprise said "continuous delivery won't work here." In 2026, the same rooms say "the dark factory won't work here." It was never about the technology being ready. It's about the organization being ready. Readiness is a socio-technical problem, not a technical one.

Scaling a complex technology can get messy without a clear north star or a shared technical strategy. Product strategies from different functions can each deliver impact but may lead to disconnected solutions or inadvertently introduce various forms of technical debt.

Successful Staff+ engineers build alignment across organizational and technical boundaries, including domains where they aren't the deepest expert.

What you need to succeed in a startup with zero customers is different from what you need when you have a few thousand, and this changes many times as the company grows. Some of these changes are code and architectural changes, some are organizational changes, and some are mindset shifts.