How do you go from junior to staff engineer when AI writes the code?
Summary
The article addresses the evolving path for junior software engineers to advance to senior and staff roles in an era dominated by AI code generation. Adam Berry, a Staff Engineer at Netflix, argues that while AI changes the "interface" of engineering, the core mentoring methodology remains consistent. He proposes that the agentic world simplifies providing bounded tasks and feedback, emphasizing three foundational skills: asking the agent, correcting and codifying agent errors, and discerning when AI output is flawed. Berry advocates for staged learning, moving from well-specified tasks to ambiguous problems, and suggests pair programming where juniors drive interactions with an interrogative AI. The piece also highlights a concern that juniors might outsource critical thinking to AI, hindering judgment development, and discusses the short-sighted industry trend of reduced entry-level hiring, citing a 25 percent drop from 2023 to 2024 according to SignalFire.
Key takeaway
For engineering leaders and mentors developing junior talent, recognize that AI shifts the learning interface, not the fundamental path to senior roles. You must actively guide juniors to engage critically with AI-generated code, fostering judgment by requiring them to articulate options and understand agentic processes, rather than passively accepting AI outputs. Prioritize structured mentoring and codify AI interactions to ensure continuous skill development, counteracting the risk of juniors outsourcing critical thinking and preserving the long-term pipeline of experienced engineers.
Key insights
Advancing engineers in the AI era requires adapting mentoring to agentic tools while preserving core judgment-building principles.
Principles
- Mentoring methodology is constant; AI changes details.
- Judgment grows by handling increasing ambiguity.
- Codify agent corrections to prevent recurrence.
Method
Guide junior engineers through staged tasks, starting with well-specified prompts and gradually increasing ambiguity. Use pair programming with an interrogative AI, focusing on asking for options and understanding agentic processes.
In practice
- Set up AI to interrogate juniors during pairing.
- Attach prompts to pull requests for context.
- Direct AI tools to expert sources like "Working with Legacy Code".
Topics
- AI in Software Engineering
- Engineering Mentoring
- Staff Engineer Path
- Code Review
- AI Adoption
- Talent Development
Best for: CTO, Software Engineer, Director of AI/ML, VP of Engineering/Data
Related on AIssential
See Counsel's argued verdicts on the open AI decisions leaders are weighing →
Editorial summary, takeaway, and curation by AIssential. Original article published by CIO.