Should I become a team lead?

17 questions, 3 minutes. Verdict: ready now, 6 to 12 months out, or stay IC. Plus your top 2 gaps and one concrete move for each.
Built from 3,400+ mentoring sessions since 2019. 52% of the leaders I mentor started exactly here: first lead role, promoted for engineering skill, left alone with the people part.
0/17
Answer all 17 to get your verdict
People appetiteLetting go of codeOwnership beyond your ticketsTranslation & saying noWhy you want thisOrg reality
People appetite
Do 1:1s, feedback, and conflict give you energy or drain it?
Monday morning, your calendar shows four 1:1s this week. Honest reaction:
A teammate’s work has been slipping for three weeks. What have you actually done?
Two engineers on your team disagree hard about an approach and the thread is turning sour. You:
Letting go of code
Coding drops to ~50% with the title, then keeps dropping.
Your coding time drops to 50% next quarter. In a year, maybe 20%. How does that read?
The hardest ticket of the sprint comes up. As a lead, you would:
One hour left today. A full review queue, and a growth conversation a teammate asked for. You pick:
Ownership beyond your tickets
Doing parts of the job before the title.
Who ran your team’s last sprint planning?
A dependency on another team is about to slip your release. You:
The most junior person on your team. What is your actual relationship?
Translation & saying no
Tech decisions explained to non-engineers. Boundaries held.
Your PM asks why the migration takes three weeks, not three days. You:
A stakeholder asks for “one small extra thing” mid-sprint. You:
Explaining a technical decision to sales, support, or the CEO usually goes:
Why you want this
Service and impact age well. Salary-only does not.
Be honest. The biggest pull toward the lead role is:
A teammate you helped grow ships something great and gets the public praise. You feel:
If leading paid the same as your senior IC path for the next two years, would you still want it?
Org reality
A readiness verdict needs a seat to be ready for.
Is there an actual team lead opening in reach?
Does your manager know you want this?
Your verdict

Your top 2 gaps
Want a second opinion on the verdict? The intro session is free: book 30 minutes.

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.

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 actually exists. 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 are closer than the missing title suggests if you already run planning, unblock teammates, and mentor juniors. That is the pattern: start doing parts of the job before the title, then make the ask explicit. 52% of the leaders I mentor started exactly here, in their first lead role.

Is staying a senior engineer instead of becoming a team lead a failure?+

No. It is a track choice, not a demotion. Staff and principal engineers multiply through influence instead of authority, and the pay ceiling is comparable. The worst outcome is not staying IC. It is leading a team you never wanted to lead.

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, not vibes: 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.

One email from Marian. No newsletter, no sales sequence. See our privacy policy.