Hacker News new | past | comments | ask | show | jobs | submit login

By definition, the bottom of the org chart is people who don't manage other people. If you want to devote your career to engineering, the only good place to be is the bottom of the org chart. Anywhere else, and you're starting to spend more time managing people instead of engineering products.

What's really sad that many companies have pay scales that all but force engineers to move up the org chart, and therefore out of engineering positions. But there's nothing sad about being happy to not have any direct reports.




If you place all leaf nodes at the "bottom", then yes. But in many companies you will find some engineers reporting in to very high ranking people - including the CEO some places - and still be "leaf nodes".

Those guys can be paid as normal, or they can be paid according to execs at similar slots in the chart, depending on why they are there. The latter will often be accompanied with a suitably important sounding title to justify it, but still be effectively engineering positions with some advisory capacity tacked on, often with wide latitude in picking and choosing what projects they want to work on.

A reasonable number of organizations also explicitly have "grades" associated with people and have parallel non-managerial grades for engineering that goes fairly high. E.g. when I was at Yahoo a decade ago, there were engineering grades that went up equivalent to 3-4 managerial levels - near director or VP level if I remember correctly. They'd still be leaf nodes, but in the more critical teams.


> What's really sad that many companies have pay scales that all but force engineers to move up the org chart

This hasn't been my experience.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: