It depends VERY much about the content and invitees of the meetings.
If you’re there to give your expert engineering feedback, awesome. If you’re there to receive the information you need in order to provide expert engineering feedback, awesome.
So often, I find, meetings are too broad and end up oversubscribed. Engineers are in a 2 hour meeting with 10 minutes of relevance.
There are serious differences in meeting culture, with vast implications oh the amount of efficacy you can juice from the attendees.
I’ve worked in a few places, all with senior engineers, including myself as a senior engineer, all of which the senior engineers spent most of their time actually engineering. If I went somewhere as a senior and was told I was going to be in meetings all day, I would quit because that’s management, not engineering.
No it isn’t - a senior engineer should be a technical track professional that’s excellent at their job - it’s likely there will be a fair amount of mentorship but that can take many forms including PR reviews and pair programming.
A technical lead, architect, or a front line manager is the one that should be eating meetings four to six hours a day. And absolutely nobody should be in eight hours of meetings a day - even bullshit C level folks should be doing work outside of meetings. Eight hours of meetings means that you’re just regurgitating the output of other meetings.
I’d clarify that having occasional eight hour meeting days isn’t bad, there might be occasional collaboration jam sessions that everyone prepares for… but if your 8-5-52 is solid meetings then nothing productive is happening.
Where I work, Senior Engineer is an IC role. They attend the same meetings as other engineers. Its the Staff+ Engineers and managers that attend more meetings (in ascending order)
Yes, that’s generally the job of a senior engineer.
Agreed. Use your experience to shape the direction your teammates are moving in. Be an architect, and let them handle your light work.
It depends VERY much about the content and invitees of the meetings.
If you’re there to give your expert engineering feedback, awesome. If you’re there to receive the information you need in order to provide expert engineering feedback, awesome.
So often, I find, meetings are too broad and end up oversubscribed. Engineers are in a 2 hour meeting with 10 minutes of relevance.
There are serious differences in meeting culture, with vast implications oh the amount of efficacy you can juice from the attendees.
I’ve worked in a few places, all with senior engineers, including myself as a senior engineer, all of which the senior engineers spent most of their time actually engineering. If I went somewhere as a senior and was told I was going to be in meetings all day, I would quit because that’s management, not engineering.
No it isn’t - a senior engineer should be a technical track professional that’s excellent at their job - it’s likely there will be a fair amount of mentorship but that can take many forms including PR reviews and pair programming.
A technical lead, architect, or a front line manager is the one that should be eating meetings four to six hours a day. And absolutely nobody should be in eight hours of meetings a day - even bullshit C level folks should be doing work outside of meetings. Eight hours of meetings means that you’re just regurgitating the output of other meetings.
I’d clarify that having occasional eight hour meeting days isn’t bad, there might be occasional collaboration jam sessions that everyone prepares for… but if your 8-5-52 is solid meetings then nothing productive is happening.
Fully agree. Not every high paying job has to end up with management duties. That’s the Peter Principle.
Anti Commercial-AI license
I mean I’m a senior engineer and I mostly handle escalations and high priority client issues, but my work is mostly break/fix
Where I work, Senior Engineer is an IC role. They attend the same meetings as other engineers. Its the Staff+ Engineers and managers that attend more meetings (in ascending order)
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.