Convinced he was underleveled as an IC4, Ryan Peterman explicitly asked his director to be promoted two levels to IC6 in one cycle. While HR policy prevented the double jump, the bold request successfully anchored his manager's perception of his performance at a higher level, leading to two consecutive promotions.
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.
For his Principal Engineer promotion, the work alone wasn't enough. He identified critical leaders (VPs, Directors), proactively sought their mentorship, and held monthly check-ins. By the time the promotion cycle began, all key decision-makers were already aligned and supportive, making it a formality.
The path to senior engineering levels is tied to the scope of your work's influence. Rather than explicitly seeking promotions, focus on projects with natural potential to grow from solving a team's problem to solving an organization's. The promotions will follow the impact.
Tying SDR promotions to time-in-seat fosters stagnation. Instead, create a clear, multi-level roadmap where advancement is based solely on hitting performance thresholds. This model rewards high-achievers, provides constant motivation, and gives reps control over their career trajectory.
At Menlo, peer-driven promotion decisions hinge on a crucial question: "Does the rest of the team perform better when you are part of that project?" This evaluates an individual's value based on their ability to elevate others, prioritizing team amplification over solitary excellence.
To assess an internal candidate's readiness for promotion, give them the responsibilities of the higher-level role first. If they can succeed with minimal coaching, they're ready. This approach treats promotion as an acknowledgment of proven performance rather than a speculative bet on future potential.
When his promotion was blocked by external factors, an engineer didn't scale back his efforts. He continued to take on work well above his level (IC4 doing IC5/IC6 work). This proactive approach during a frustrating period led to a top-tier rating and promotion once the freeze lifted.
Instead of asking managers for a checklist to get promoted, focus on delivering significant impact. This approach is more effective and viewed more favorably by leadership. Genuine impact is what gets recognized and rewarded, while simply 'checking boxes' can backfire.
A Meta engineer was denied a promotion despite a "Greatly Exceeds" rating due to a behavioral gap in cross-functional collaboration. This shows that lagging promotions hinge on consistently demonstrating the behaviors of the next level, not just delivering high impact at the current level.
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.