An IC7 engineer found the senior staff role was mostly meetings and docs. He preferred coding, debugging, and mentoring, which aligned better with an E5/E6 level. He actively requested a demotion to improve his job satisfaction, challenging the conventional "up-or-out" career mentality in tech.
Related Insights
An engineer recalled being an IC4 and thinking IC7 was an undesirable level of intensity. This fear shifted upward with each promotion; at IC6, he became open to IC7 but then felt the same about IC8. This shows how our perception of the "next level" changes as we grow and our ambitions evolve.
Climbing the corporate ladder isn't always the ultimate goal. As professionals become more senior, they often move away from the hands-on, creative work they are passionate about. Leaders advise cherishing mid-career roles where you can be "in the weeds" of the actual work.
The speaker identifies the L5 (Senior Engineer) role as having the highest quality of life. At this level, an engineer is shielded from upper-management pressure by their Tech Lead (L6) and manager, allowing them to focus on hands-on technical work without the burdens of Staff+ roles.
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.
Intentionally accepting a lower level than you qualify for reduces immediate pressure to deliver massive project impact. This creates the space and freedom to explore, learn the systems, and build innovative side projects that establish a strong reputation from the ground up.
Despite being on a clear track to Director, Ilya Grigorik chose a lateral, likely down-leveled move to an IC role. He traded guaranteed career progression for greater control over his time, the freedom to pursue deep technical interests, and the ability to work on problems he was passionate about.
Both Meta and Google lacked a formal process for an employee to voluntarily take a lower-level role. The speaker's request was a challenge for recruiters and HR because systems are designed for upward mobility. It required special exceptions and created suspicion, as it's an unconventional career move.
Unlike at smaller companies like Cruise where scope is abundant, the speaker felt Meta's senior IC ranks were "crowded." This created an environment where finding impactful, level-appropriate projects required significant effort, making it harder for new senior hires to demonstrate their value quickly.
Mike Perry's grandfather declined a top executive promotion, choosing to remain a VP of sales where he excelled and was happy. This embodies an inversion of the Peter Principle: intentionally stopping at one's peak level of competence and satisfaction, rather than striving for the next, potentially ill-fitting, rung on the ladder.
The leap from Senior to Staff Engineer is a major mindset shift. It's not just about solving harder problems, but about autonomously owning the entire lifecycle: identifying the right problems to solve, pitching their value to stakeholders, and then leading the execution end-to-end.
