Career progression in engineering has traditionally followed a predictable path: junior tasks teach fundamentals, mid-level work builds judgment, senior roles require synthesis across systems. AI has disrupted this by eliminating the learning opportunities at each rung while simultaneously enabling people to perform above their experience level.

The result is juniors who ship like mids but can't debug like them. Mids who architect like seniors but lack the battle scars. Seniors wondering what their role even is when AI handles the implementation. Our progression frameworks—built for a world of gradual skill accumulation—no longer match reality.

This talk shares lessons from rebuilding engineering ladders during rapid team growth. We'll examine what competencies actually differentiate levels now, how to create learning opportunities when AI handles the traditional training ground, and whether the IC/management split still makes sense when AI shifts what individual contribution means.