I think part of the problem is how companies fail to define boundaries for their roles, and it's probably on purpose to get the most productivity from an indivi

I think part of the problem is how companies fail to define boundaries for their roles, and it's probably on purpose to get the most productivity from an individual. There is no ceiling or max number of responsibilities, it is always more and more and never enough. Roles are ultimately defined to "add business value", but this is like writing a blank check. For engineering, I want to exchange code for money... as a full time position. But this does not exist as far as I know. Full time salaried basically means you own a slice of the business, and your responsibilities have more to do with business profit then exercising expertise in your technical field. As a result the expectations range from managing people to making presentations and coordinating meetings, all in the name of "engineering" except it's just running the business under the disguise of an engineering role. To me this is what has led to burnouts and dissatisfaction in my career, at times doubting it, but ultimately I concluded that I still like programming, I just don't like how the industry treats programmers.