I'm pulling together a list of criteria for the various levels of software engineers. I know some are public. What are the public definitions that you like the most/feel are accurate with your experience?
Unfortunately, what I see the most is:<p>An increase in seniority comes with (A) a decrease in hands-on time with technical problems and (B) an increase in time spent on project management, team organization, and people problems.<p>None the less, there are some possibly interesting resources regarding levels at Honeycomb [1], Netflix [2], and Gitlab [3]. There's a whole book if you're going to venture into "staff" [4]. Last but not least, don't forget the Peter Principle [5].<p>[1] <a href="https://www.honeycomb.io/blog/engineering-levels-at-honeycomb/" rel="nofollow">https://www.honeycomb.io/blog/engineering-levels-at-honeycom...</a><p>[2] <a href="https://blog.pragmaticengineer.com/netflix-levels/" rel="nofollow">https://blog.pragmaticengineer.com/netflix-levels/</a><p>[3] <a href="https://about.gitlab.com/job-families/engineering/development/" rel="nofollow">https://about.gitlab.com/job-families/engineering/developmen...</a><p>[4] <a href="https://staffeng.com/guides/staff-archetypes" rel="nofollow">https://staffeng.com/guides/staff-archetypes</a><p>[5] <a href="https://en.wikipedia.org/wiki/Peter_principle" rel="nofollow">https://en.wikipedia.org/wiki/Peter_principle</a>
If we’re talking about “favorite” definitions: the more senior the less time one spends at their “desk” - whatever that means now with everyone being remote
Posted a comment about this just the other day: <a href="https://news.ycombinator.com/item?id=32826054" rel="nofollow">https://news.ycombinator.com/item?id=32826054</a>