@ulrike I definitely know who those people have been on my teams. when I think of people that I'd like to work with again, they're always top of the list because I could see how critical their work was.
I expected the first thing the author would talk about is changing the role itself rather than the engineer moving to a different role, etc. Leadership and management is baked into the criteria for advancement at my company, so you can be a software engineer who also manages people and that's valued. Maybe--and really I am just guessing--it's because we're an actual engineering organization and not a "tech company"? There are so many engineering roles just on one project that privileging "writing code" or even drawing up designs on its own for promotion seems bizarre. It's all about meeting customer needs and minimizing costs.
(side note: when did "IC" become an abbreviation we're expected to just know what you mean?)