Half of those meetings are business MBAs asking “Why isn’t more getting done on this project?”
The job is defending people who get work done from people who don’t get work done.
LOL. So true.
No, this is incompetent management.
Senior engineers write enabling code/scaffolding, and review code, and mentor juniors. They also write feature code.
Lead engineers code and lead dev teams.
Principal engineers code, and talk about tech in meetings.
Senior Principal engineers, and distinguished technologists/fellows talk about tech, and maybe sometimes code.
Good managers go to meetings and shield the engineers from the stream of exec corporate bs. Infrequently they may rope any of the engineers in this chain in to explain the decisions that the engineers make along the way.
Bad managers bring engineers in to these meetings frequently.
Terrible managers make the engineering decisions and push those to the engineers.
Good managers go to meetings and shield the engineers from the stream of exec corporate bs
Was lucky enough to work with one… once.
I wanted to write code with more authority and higher wage, not sit in endless meetings and explain to somebody why it’s 8 story points instead of 5 🙄
Of course there’s no point in trying to rationalize this 'cos these people use meetings to try justify their usefulness to the company (HR does the same with random activities), so you end up drawing red lines with invisible ink…
Yes, that’s generally the job of a senior engineer.
Engineer should still be an IC position and not have that many meetings. It should be a project or team lead that does the majority of meetings.
This is largely semantic, and highly subjective, but to me “Engineer” implies more design, architecture, and planning (ie, meetings).
A Senior “Developer” would imply more day-to-day coding to me. Not that companies care what I think, of course.
