Software Engineer
QA
Business
Notes
- The team ladder helps us to get some structure and clarity and measure progress
- The team ladder is discussed during 1-1s with your team members. For newcomers, reviews take place after 6 weeks and 3 months. Then aim for reviews every 6 months
- Technical Skills and Get Stuff Done are the primary drivers of promotions at lower levels. At higher levels, the importance gradually shifts to Influence and Communication and Leadership
- Not everyone will progress in each column in lockstep
- Moving up the team ladder is not decided in a top-down way, but by a committee of peers
- Seek as much feedback as possible from different parts of the team. The goal is to grow not just on technical aspects, but as an overall member of the team. Someone not directly related to your everyday work may have some valuable feedback to give you, aim for 360 feedback
- When you give feedback: describe the situation, the behaviour, the impact observed, don't make it personal (don't "you are wrong, I am right")
- Be direct, constructive and mindful at the same time
- Take the time to explain well, be pedagogic
Bump process
- Step 1: following the team ladder reviews by your peers, you should feel confident that you fit in the new role
- Step 2: fill out the bump questionnaire
- Step 3: ask 4 people in the team to be sponsors of your bump. At least one founder and one member from an unrelated domain. The reviews are visible to everyone in the company
- Step 4: the bump presentation is open for everyone to attend, but at minima the 4 sponsors should be there