Speaker
Abstract
Most "AI for engineers" content is about typing faster. That's IC-level work. Staff engineers have a different question to answer. When everyone has AI, what does a 10x engineer look like, and where does a staff engineer's leverage come from now?
A year ago I gave a talk on using AI to turn a four-hour task into four minutes. I was shipping about as much as my whole team. That isn't a staff engineer. That's a strong executor. AI didn't change what a staff engineer is for. It changed where the leverage is. It used to be one code review, one mentee at a time. Now it's your judgment, in the tools and agents your whole team uses every day.
This talk is the year that followed, drawn from platform DevEx work at Pinterest, in three moves.
- Multiply yourself: go first. Try things on your own work, hit the dead ends, and notice what others are likely running into too.
- Multiply your team: turn the corrections you keep making into the default for everyone, and make it easy for others to add theirs. Over a thousand people at Pinterest now use our skills, about half our engineers. One command that takes a task to a ready-for-review PR was used across 28 teams.
- Multiply the system: move up a level, and build what handles any case, instead of doing each one faster. For us, that meant going from doing each migration faster to a system that runs any migration on its own. The same AI tools as every other team, and my team now ships about four times as much per engineer.
Key takeaways:
- Go first, and notice what others will run into too.
- Make your corrections the default, and let others add theirs.
- Move up a level, and build for any case, not each one.
- Let agents propose, and keep humans deciding.
Some of the job can't be written down, like an honest conversation with a teammate who's struggling. That part is still yours. A 10x engineer isn't ten times faster. They're the reason ten other people are.
Topics
$3,250, Conference (3 days). Current pricing ends November 20th. All pass options.
QCon San Francisco 2026 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.
Part of the track
Staff+ Engineering Skills Hosted by Javier Fernandez-Ivern Staff Software Engineer @Netflix with Over 24 Years in Software EngineeringFrom the same track
Tuesday 17 November
10:35 Ballroom BC Session Staff Plus Engineering Nobody Knows Everything (and That's OK): Building Alignment in Complex, Rapidly Changing Environments Kaye Mason Senior Staff Software Engineer @Meta, Previously @Google and @EA, 20+ Years in Real-Time Rendering, Spatial Computing, and Developer Platforms Successful Staff+ engineers build alignment across organizational and technical boundaries, including domains where they aren't the deepest expert. 11:45 Ballroom BC Session Staff Plus Engineering Use AI to Multiply Your Team as a Staff Engineer Jordan Cutler Senior Staff Engineer and Web Tech Lead @Pinterest, Author of High Growth Engineer Newsletter Most "AI for engineers" content is about typing faster. That's IC-level work. Staff engineers have a different question to answer. When everyone has AI, what does a 10x engineer look like, and where does a staff engineer's leverage come from now? 13:35 Ballroom BC Session Staff Plus Engineering Scaling Tech by Aligning Humans Scott Behrens Principal Security Engineer @Netflix, Providing GenAI Technical Leadership and Upleveling Engineers on The Engineer Setlist Blog 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. 14:45 Ballroom BC Session Staff Plus Engineering Transitioning From a Startup to a Mature Platform Joy Ebertz Principal Engineer @Imprint, Blogger, and Speaker, Previously @Harness, @Split, & @Box 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. 15:55 Ballroom BC Session Onboarding Learning What’s Already There: A Breadth-Based Approach To Onboarding Laura de Vesine Senior Staff Engineer @Reddit When onboarding to a new organization, it's vital to bootstrap your network and context quickly. 17:05 Seacliff D Unconference Unconference: Staff+ Engineering Skills