DEV Community

[Comment from a deleted post]
Collapse
 
daniel13rady profile image
Daniel Brady • Edited

It's especially helpful if your organisation has a pretty clear definition of what's expected in order to climb that ladder.

Absolutely ❤️ A year or so ago at my company, a few of the engineering leads got together and created a progression map that feels like something you'd see in the rulebook for a table-top RPG 😆 but it's amazing, and has been incorporated into the engineer hiring process at this point as a reference for evaluating candidates applying for certain roles.

Basically, they broke down what they think it means to be a "good engineer" at every level on the company's "individual contributor" career track, and organized the resulting skill sets, abilities, attitudes and behaviors into a logical progression matrix. Then, they color-coded cells in the matrix according to whether expectations of competency changed between levels for that particular skill: green for "first expected at this level", orange for "growth expected from previous level", and no color for "no change".

Here is an example of the progression for a trait they termed "Growth Minded":
Example IC progression matrix for "growth mindset"

I love it. It served me well in one-on-one's with my manager and peer reviews.