Should I become a team lead?
What this test measures, and what it does not
This is a fork-in-the-road test, not a salary calculator. It measures the six things that decide whether the move from engineer to team lead works: appetite for people work, letting go of code, ownership beyond your own tickets, translating tech decisions to non-engineers, your real motivation, and whether your org has a seat for you at all. If you want the money answer instead, that is the EM salary calculator.
One position baked into the scoring, so you can disagree with it consciously: "stay IC" is a legitimate verdict, not a consolation prize. The staff engineer track multiplies through influence instead of authority, and it pays. The verdict logic treats salary-only motivation as a signal to stay IC, because a lead role taken for the bump alone hurts the lead and the team.
The role itself, and how it differs from tech lead and engineering manager, is covered in the team lead role guide. The full reasoning behind the six dimensions is in should I become a team lead.
How the verdict is computed
Each of the six dimensions scores 0 to 10 from its own questions. The five core dimensions, everything except org reality, average into a core score. Core 7.0 or higher with an org score of at least 5 reads ready now; core 7.0 or higher without a visible seat, or core between 4.5 and 7.0, reads 6 to 12 months out; core under 4.5 reads stay IC. One override sits on top: motivation at 3 or lower combined with people appetite at 4 or lower reads stay IC no matter what the rest says, because a lead role taken for the salary bump alone hurts the lead and the team. Published so you can check the verdict instead of trusting a black box.
FAQ
Should I become a team lead?+
Only if the people work gives you something back. The test measures six things: appetite for 1:1s and conflict, letting go of code, ownership beyond your own tickets, translating tech to non-engineers, your real motivation, and whether an opening exists at all. If the honest answer to "why" is only salary and title, stay IC. The senior IC track pays too, without the meetings.
Am I ready to be a team lead?+
You’re closer than the missing title suggests if you already run planning, unblock teammates and mentor juniors. That’s the pattern: do parts of the job first, then make the ask explicit. 52% of the leaders I mentor started in exactly that position.
Is staying a senior engineer instead of becoming a team lead a failure?+
No, it’s a track choice rather than a demotion. Staff and principal engineers multiply through influence instead of authority and the pay ceiling is comparable. The outcome worth avoiding isn’t staying IC, it’s running a team you never wanted.
What is the difference between a team lead and an engineering manager?+
A team lead usually keeps about half their time in code and carries a lighter people load. An engineering manager owns performance, careers, hiring, and delivery, with little or no coding time. The EM step is where the switch becomes permanent; the team lead step is where you find out if you want it.
How do I prepare for a team lead role in 6 to 12 months?+
Close specific gaps: run the next sprint planning end to end, mentor the most junior person on the team, have one honest feedback conversation you have been postponing, and tell your manager you want the lead path. The test names your two weakest dimensions so you know where to start.
Not ready for a call? Get pinged when a slot opens.
Mentoring slots free up every few weeks. Leave your email and you get one message from me when the next one opens.
Not sure yet? Build the inquiry with my AI first. Under 16 minutes, no email needed until the end, and the pack comes out at €2,166 instead of €2,580.
One email from Marian. No newsletter, no sales sequence. See our privacy policy.
You're on the list.
One email from marian@marian.coach when the next slot opens. In the meantime, let's connect on LinkedIn.