When senior engineers move away from hands-on coding, their understanding of the system becomes abstract. This leads to designs disconnected from reality, and they lose the trust of their team, who see them as out-of-touch architects without "skin in the game."

Engineers moving into leadership shouldn't see it as abandoning their technical identity. Instead, they should reframe their role as "elevating engineering." They can stay connected to their roots by using their experience to constructively challenge their teams, brainstorm solutions, and help others solve problems faster and more effectively.

The role of a designer on a developer-focused AI product has fundamentally changed. Ed Bays from OpenAI reports spending 70-80% of his time coding, indicating that design execution at the frontier is now primarily a software engineering discipline.

To prevent management from becoming a detached layer, Arista ensures its leaders are "coach players." This means even senior executives, like the CTO and founder, still contribute by coding. This "leading by example" approach proves to employees that management is connected to the core work, reinforcing a strong, authentic engineering culture.

A critical career inflection point is moving from solely executing tasks (writing code) to influencing strategic decisions about what problems to solve. True value and impact come from being in the room where decisions are made, not just being the person who implements them.

It's nearly impossible to hire senior product or engineering leaders who are also fluent in AI. The advice for experienced managers is to step back into an Individual Contributor (IC) role. This allows them to build hands-on AI skills, demonstrating the humility and beginner's mindset necessary to lead in this new era.

After a certain point, becoming a more senior engineer isn't about writing better code. In fact, coding skill may decline. The key differentiator is the ability to zoom out and apply technical judgment to increasingly larger scopes—from a team, to a department, to the entire company's long-term strategy.

AI models will dutifully try to fix reported bugs, even in a poorly architected system. A true senior engineer provides value by stepping back, identifying the root cause (e.g., flawed architecture), and pushing for a necessary, albeit difficult, system rewrite.

To avoid becoming an "ivory tower" manager, engineering leaders should use side projects as a playground for new technologies. This practice ensures they understand the limitations of new tools like AI and can provide credible, concrete, hands-on guidance to their teams.