Engineering team levels at Wise

We’re sharing our Engineering team levels to give you an idea of where you might fit, what’s expected at each level and how you can progress at Wise. 

While career map frameworks are a useful guideline, they should never replace one-to-one career development and coaching conversations. All our employees go through an annual 360 feedback review, where we refine our individual development plans. This framework helps our Engineering Leads have more structured conversations with their team members about progression and understand what they need to do to increase their impact on our mission.

When you’re thinking about your skills in relation to these levels, always remember it’s not a tick box exercise, but rather a guide to show the kind of impact we expect from our people as they progress in their journey at Wise. Different roles and teams have varying expectations on certain areas, but on the whole these expectations are common across all roles.

The two Wise Engineering tracks: Individual Contributor and Engineering Lead

There are two Engineering tracks at Wise – the Individual Contributor track and the Engineering Lead track.

1. The Individual Contributor track consists of our Software Engineers who are focused on personal contribution to our product, rather than team or people leadership. There are a number of levels (from Junior Software Engineer to Principal Software Engineer) that reflect the increasing impact, scope and responsibilities with each level. 
2. The Engineering Lead track is made up of Engineering Leads who act as team leads and focus on making an impact at a team level. There are a number of levels (from Software Engineering Lead to Director of Engineering) that reflect the increasing impact, scope and responsibilities with each level. It’s important to note that our Engineering Leads are still very hands-on with our Engineers, so we expect them to have good soft skills and strong coding and technical abilities too.

Important to note: The Engineering Lead track isn’t necessarily better than the Individual Contributor track. Although we don’t expect Engineering Leads to be the best Engineer in their team, they’re expected to be technically hands-on. So there’s a minimum requirement that they hit Senior Software Engineer level before moving on to Engineering Lead positions so they’re better able to contribute meaningfully and guide others in the team alongside other new responsibilities. 

Both tracks run in parallel and the compensation packages are of similar level. We strongly recommend our employees decide which path to go down based on the type of work they enjoy rather than basing their decision on perceived external validation.