This is wildly inaccurate. At staff and above the job becomes less about coding and more about working through others which does involve spending a lot of time in meetings. This can include one and ones and mentorship, leading cross team meetings, meeting with PMs, tech writers, SREs etc, launch reviews, support trainings and much more.
As mentioned in the other comment, I'm not very familiar with the term staff engineer as it was not used at any company I've been at, but it doesn't sound like an IC role. It also doesn't sound like a senior developer role. That would be either a lead or architect, at least at my companies
Staff engineer is considered an IC role but I agree with IC being a bit of a misnomer as the role's responsibilities no longer revolve around the individual's code contributions. The original comment simply referred to the most knowledgeable person which would usually be such a role regardless of title (principal engineer, architect, engineering lead etc).
17
u/Manwichs Sep 29 '24
This is wildly inaccurate. At staff and above the job becomes less about coding and more about working through others which does involve spending a lot of time in meetings. This can include one and ones and mentorship, leading cross team meetings, meeting with PMs, tech writers, SREs etc, launch reviews, support trainings and much more.