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?

Staff engineering is still about leverage. That hasn't changed. What's changed is the medium it operates on, more in the last few years than in the last two decades. Engineers who internalize this are multiplying their teams. Engineers who don't are competing with a senior IC plus an AI agent and losing the comparison.

This talk is for engineers who want to multiply their team, not just themselves. Five behaviors, drawn from a year of platform DevEx work at Pinterest, each paired with an artifact. A personal skills marketplace that turned ad hoc judgment into installable plugins. A doc-sharing platform I built when AI made HTML cheap to author, now hosting 500+ technical write-ups across the engineering org in its first two weeks. A teaching loop where shadow sessions with my pod became, via AI, a playbook I shipped to a 1000-person engineering channel, so the work I did with four people compounded across a thousand.

Key takeaways:

1. Codify your judgment so it's loadable by someone else.
2. Raise the team's AI floor, not your AI ceiling.
3. When AI capability gets reliable, build the platform, not the script.
4. Set the standard others ship against.
5. The parts that don't codify stay yours. The artifact is you, and there's no fork of that.