| > Profit at any cost Yes, but I think you're overlooking a hugely important factor in all this... You boss is just some average manager that very often could even be below average. Your boss is under their own pressure to perform and most of them will similarly struggle because they're not that good. Most workers at any roles are just average by definition. And the higher up you go, the more timing and luck plays a role, and the less good meritocracy is at filtering people. As luck becomes a bigger factor up the management chain, leaders tend even more towards being average at their job. Even founders, they often have never done this before, leading a fast growing company is all new to them and they learn as they go. What makes a good founder is the guts to be one, and than having the luck of timing and right idea. Plus being able to sell a narrative. What I mean by that is, they'll want to optimize profits, that's literally the charter of any company, and as an employee you should also be focused on that as your goal. But optimizing for profit often aligns with engineering well being, a robust, productive team, an environment conductive to innovation and quality with high velocity, etc. Those are good both for the employed engineers and profit. Often if you can't get that, it's not so much because of maximizing profit, but that your boss just isn't good. Think about it, it's super easy to, as a manager, do nothing but tell people to work harder, do better, and ask why this isn't done, why this isn't good, etc. This is what being bad at leading a profit maximizing company looks like. It's much harder to motivate people to work their hardest, to properly prioritize and make the hard trade off to focus the resources on the best ROI, to actually unblock blockers, to mentor and put processes that actually help quality go up and velocity go up. Etc. |
I agree with this 100%. I may add a tidbit here simply because I'm thinking about it. There is a real agency problem in leadership.
I've been a staff engineer[0] for just over half a decade now. I've noticed, particularly in the last few years, there's been more dustups over executive[1] authority of the role. Traditionally, what I've experienced is having latitude to observe, identify, and approach engineering problems that affect multiple teams or systems, for example. I've contributed a great deal to engineering strategy, particularly as it relates to whatever problem domain I am embedded in. Its about helping teams meet their immediate sprint goals, not working on strategy or making sure upcoming work for teams is unblocked by doing platform work etc.
The only thing I can surmise about this shift is that engineering managers (and really managers going up the chain) don't want to feel challenged by a "non manager". They didn't like that we didn't have a usual reporting structure that other ICs do (we all rolled up the same senior director or VP rather than an EM) and previously had similar stature that of a director.
[0]: for a general sense of what this entails, see this excellent website: https://staffeng.com
[1]: As in having the power to put plans and/or actions into effect