11 Comments
User's avatar
Srinivas Harihar's avatar

Great article. I especially loved the depiction of ambiguity lifecycle.

Catalina Villouta's avatar

Your article was great! I loved reading it!

Mohiuddin Abdul Kader's avatar

Very informative article. Thank you for sharing.

Sudhansu's avatar

I really enjoyed reading your article. Looking forward for future posts.

Caleb Mellas's avatar

Great read Irina! When becoming a senior it’s really important to become one of the key contributors on the team in terms of coding and running projects.

So often times we think it’s just doing that better to become a staff engineer. But that’s not true.

I love how you shared three keys to moving yo staff - including the one about delegation. That’s always been a hard one for me.

Great read, and looking toward to future articles on this as well.

Jason's avatar

For job families that require all the leadership skills you mentioned already at a junior level ( for instance, TPM, PM), do you have any advice or insight as to how they can progress beyond senior?

Petr Zaparka's avatar

I wonder how large the organisation/team has to be to go beyond junior, mid, senior. I have been working in small to medium organisations and never come across the term "staff". Skills and approach you describe is something I expect "real senior" developer to have. Thank you.

Alex Cirstea's avatar

Great article! I'm not working in software development, but I was very interesting to read

Hari's avatar

Clear depiction of the tools needed for progression. Fabulous read! Well articulated. Thank you for this.

Meng Li's avatar

Great insights on progressing from Senior to Staff Engineer! Scaling yourself, navigating ambiguity, and influencing without authority are crucial skills for career growth. Thanks for sharing your experience!

Amirjuve's avatar

Thanks for all those informations