u/EricLowItsMe

I've heard about senior level behaviors, and even have some of them, such as ownership. But during my 20 year career, no mentor, manager, or coach has ever taken the time to walk through behaviors that I needed to display to be at the staff+ level. Instead, I have collected a few examples, below.

While watching interviews with top Meta engineers on the Ryan Peterman podcast, I found a hidden gem: Behaviors and examples of behaviors.

Staff+ Behaviors

1. Influence without Authority
   1. talk in person - when in person, it is easier to relate to them and quicker to respond
   2. code reviews - it is easier to engage an engineer when you speak directly about task they are working on right now
   3. technical depth and breadth - demonstrating your technical mastery is important to earn the respect of fellow engineers
   4. technical writing - written communication is an under utilized skill that allows you to scale your influence broadly.
2. Ownership
   1. own all the things - you are responsible for more than the coding, you are responsible for the results of the project.
   2. own your failures - step up and help with the cleanup, when you are responsible for a failure.
   3. disagree and commit - even if you disagree with the path, it is important for the org to move in the same direction to an imperfect solution.

now, if you are curious about my post about Staff+ Projects, the post can be found on this other reddit post