Everyone is a Staff Engineer Now

The article says coding agents have made execution cheaper, so engineering work is shifting toward higher-level judgment. Planning, architecture, review, and context management are becoming more important earlier in a career, while the hardest part is knowing what to build, where it belongs, and how to design it.

Reading notes

#

• Senior and staff-level skills are moving earlier in engineers’ careers as agents handle more implementation work.
• The role shifts toward planning, architecting, reviewing, and steering AI systems.
• The article compares this shift to search, which did not remove thinking but rewarded people who learned to search well.
• Engineers need to maintain rich context across multiple domains and projects.
• A “correct” refactor can still break downstream systems if it ignores an implicit contract that lives in shared team knowledge.
• Engineers need to understand how components interact and notice subtle side effects across services.
• Long-running agents make focus harder because time spent waiting can turn into distracted context switching.
• The article recommends batching agent requests, planning follow-up work in advance, and treating agent runtime as intentional gaps.
• As agents improve, clarity of intent becomes the bottleneck rather than execution speed.
• Breaking work into parallelizable tasks and defining clean boundaries can multiply output.
• Different engineers may prefer different AI workflows, such as heavy planning first or prototype first and cleanup later.
• Reviewing and reading code become more expensive as code generation gets cheaper.
• AI can help with summaries and reviews, but humans should remain the main line of defense.
• The engineers who thrive will be the ones who manage their own contexts well and adapt their workflow to the tooling.