bombardier6789

Coolblue has been amazing for my electronics needs and it's customer support.

If you ever have been in leadership interviews then you will know that firing people is one of the quality one needs to evaluate or prove.

This is just business as usual for these roles and a lot of people shy away from these roles due to "responsibilities" such as this.

What would be your definition of distributed?

Although this is a generalisation of overall population in few buckets, it helps people understand what it is really.

You can assume different archetypes at different times. That's the best thing about being staff. The staff engineer is a clear leadership role with expectation to perform each of these archetypes at varying degrees. The person might prefer to be one of these archetypes but doesn't shy away to pick up others if the situation demands. Of course, they and people in their vicinity would want to play their strengths.

Yes and no.

I have been asked if staff engineers are around so that they can pick up projects noone wants to do. This entirely defeats the point of staff engineers.

I would want my staff engineering bunch to either pave the path or mentor the teams to do it themselves. Making it easier for the teams and future engineers could be a better strategy and effective multiplier.

If there is organisational mission critical software lacking any of this then it is a p0 and I would count it under high impact work rather than gardening. Besides depending on company size, some of those responsibilities should belong to platform teams.

Indeed this is what I thought after reading the article. While there is a point to the article, it misses the basics entirely.

Internet makes a lot of things easier, losing money included.