Staff promotion packets.

August 8, 2020. Filed under staff-plus 11

Some folks think of their promotion packet as the capstone of reaching a Staff-pus role, but I’ve seen many folks succeed by taking an opposite approach: starting to write their first Staff promotion packet long before they think they’re likely to be promoted to Staff, much the way they might use a [brag document]( Used this way, your packet becomes the map to accomplishing your goal.

Create space for others.

July 26, 2020. Filed under staff-plus 11

One of the best measures of your long-term success as a Staff-plus engineer is that the organization around you increasingly benefits from, **but doesn’t rely upon**, your contributions. Because many folks reach their first Staff-plus role by being the “go to” person for the organization, it can be a difficult transition from essential to adjacent.

Staff-plus interview processes.

July 12, 2020. Filed under staff-plus 11interviewing 4

When we talk about designing a Staff-plus engineer interview loop, the first thing to talk about is that absolutely no one is confident their Staff-plus interview loop works well. Many loops end up looking for a senior engineer who’s _really_ fast at solving problems, which doesn’t reflect the actual role. Others focus on communication skills, which _are_ a key part of the role but certainly not the entirety of it. A few companies even construct their process to assess whether the candidate _feels_ like a member of their existing senior engineering team, conflating excellence with familiarity.

Does the Staff title even matter?

June 28, 2020. Filed under career 13staff-plus 11

If you’re safely nestled within the comfortable clutches of the Senior Engineer career level, you might wonder if you ought to pursue the Staff title. It’s a considerable investment of time and energy, along with requiring a good amount of luck, is that investment worth your time?

Where do Staff-plus engineers fit into the org?

June 28, 2020. Filed under management 113staff-plus 11

When I work on the organization design of an engineering organization, I think a lot about "organizational mathematics", the guideline that each team should have one manager and six to eight engineers, and each manager of managers should support four to six managers. From those numbers you can rapidly determine an appropriate structure for your organization that’ll work fairly well. It might not be perfect, but it’ll work.