Post #1695555

the staff engineer got promoted in october. by april three engineers on the team can't name a single technical decision the staff engineer drove that quarter. they can name the all-hands demo. they can name the offsite presentation. they can't name a code review that mattered, an architecture call that landed, an on-call save, a hire that worked out. the promo was real. the basis for the promo was performative. the team's silence about why it happened is the team telling you the org's leveling system has decoupled from the work the level is supposed to describe. nobody on the team will say this aloud because saying it sounds like sour grapes. so the gap accumulates in private and the level keeps inflating in public