> They instead encourage them to focus fully on process and sprint management.
Thats literally the point. Its totally fucking batshit that somewhere like meta still uses spreadsheet to plan. This is why properly trained people should be doing management.
Project management at scale is not something you "dip into" its a full time job to project manage and people manage. Its not something most ICs should be doing.
A consultant[1] surgeon leads a team, but they don't manage the timesheets of the juniors, nurses and assistants. Meta very much expects that a consultant surgeon not only does surgery, but fills rostas, recruits nurses, does some marketing and works on the legal policy for negligence.
The issue at meta is that with the growth there is no "leadership". What is a lowly IC supposed to work on? "create consensus" and "drive from the bottoms up". That doesn't work when you have 11 layers of management, all pissing about talking about impact, but not actually driving projects.
> I would think that the role of an "Engineering Manager" or "Tech Lead" or "Team Lead" etc. should all be pretty interchangeable, or at least have very high overlap.
You should try it. Its pretty clear you've not managed people at any level of scale or formality. Not everything is code, babes.
(No. I'm not a manager at meta, thank fuck, it sounds pretty shitty.)
[1]https://www.rcseng.ac.uk/careers-in-surgery/surgical-care-te...
edit I meant uk consultant surgeon, thank you to commentor for pointing out my mistake