Should I Become a Team Lead? A 6-Dimension Answer

52% of the 300+ leaders I mentor came to mentoring while already in their first lead role. The most common opening line of a first session, almost word for word: “I became a team lead and nobody told me what the job is.”

They did not fail. They accepted a job nobody described to them.

I helped run that machine myself. At Mews we built one new team per month in 2022. Every new team needed a lead, and the pool was always the senior engineers already in the room. The default promotion path fills seats fast. It does not check whether the person wants the job.

So should you become a team lead? Only if the people work gives you something back. That answer is measurable. After 3,400+ sessions I can name the six things that predict whether the role will fit you, and I turned them into a free 17-question readiness test. This post is the reasoning behind it.

The promotion nobody describes before you accept it

Here is what the title actually changes, and what almost no offer conversation covers.

The pattern my first-time lead mentees report: coding drops toward 50% in the first quarter, and a year in it is often closer to 20%. The calendar fills with 1:1s, planning, and conversations with people who cannot read your code and should not have to. The success metric quietly flips too. It stops being your commits and becomes other people’s output.

None of that is a complaint. For the right person it is a bigger lever. But the role is a different job wearing your old job’s badge, and most companies hand it over with a pay bump and a shrug.

I wrote the full team lead vs tech lead vs engineering manager breakdown separately. The one-line version: team lead is where you find out whether you want the management track. Engineering manager is where the switch becomes hard to reverse.

The question is not “can I do it?” Most senior engineers can, mechanically. The question is whether the job will give you energy or eat it.

Six dimensions predict it. Vibes don’t.

Every readiness conversation I run eventually walks the same six dimensions. The test asks 17 scenario questions across them, not “rate your leadership from 1 to 10” fluff. Concrete Monday-morning situations with honest answer options.

What the first four look like when they surface in sessions:

• People appetite is the one people misjudge most about themselves. A teammate’s work slips for three weeks; the honest question is not “could you address it” but what you actually did. “Helped with their tickets and dropped hints” is avoidance wearing a helpful costume.
• Letting go of code shows up as the hardest-ticket reflex. Taking it yourself because you are fastest is the right answer for a senior engineer and the wrong answer for a lead.
• Ownership beyond tickets is the strongest positive signal I know. Who ran your team’s last sprint planning? If the answer is “me, it drifted to me and I kept it,” you are already doing the job.
• Translation and saying no decides whether the org trusts your team. “It’s complicated” plus a link to the epic is not an explanation, and quietly absorbing mid-sprint requests in your evenings is not a boundary.

The last two dimensions deserve their own sections, because they are the two the career-advice industry gets wrong.

“Stay IC” is a verdict, not a consolation prize

Indeed’s career guide tells you that “becoming a team leader is a great way to grow professionally and experience increased responsibility.” Most of the top-ranking advice says a version of the same thing. Growth equals title, title equals leadership, declining equals stagnation.

I disagree. One of the most damaging patterns that walks into my sessions is the engineer three years into leading a team they never wanted to lead. They took the title because refusing felt like failure. Their team feels it every day, usually before they admit it to themselves.

The senior IC track is not the runner-up prize. Staff and principal engineers multiply through influence instead of authority, and the pay ceiling is comparable: run your own numbers in my developer salary calculator and the EM version side by side. I wrote up what a Staff Engineer role is all about separately. A “stay IC” outcome from an honest self-assessment is a career decision working exactly as intended.

The worst outcome is not staying IC. It is leading a team you never wanted to lead.

That is why the test’s third verdict is “Stay IC. And that is fine.” No promotion process will hand you that verdict. Promotion processes are pipelines; they are built to fill seats, not to protect you from the wrong one.

Salary-only motivation does not survive the first bad quarter

The second dimension worth a spotlight: why you want this.

There is a thought experiment in the test that does more work than any other question. If leading paid the same as your senior IC path for the next two years, would you still want it? Sit with that one honestly.

Wanting the money is not shameful. But when the salary bump is the only pull, the first bad quarter exposes it. A struggling teammate, a slipped release, a conflict that takes three conversations to untangle. Service-and-impact motivation survives that week. Title-and-money motivation starts drafting the “maybe management isn’t for me” message.

If the raise is the actual goal, raise your market value and negotiate directly. It is a cheaper way to get money than a job you do not want.

If the verdict is “6 to 12 months out”: do the job before the title

Half the value of a readiness verdict is the gap list that comes with it. The test names your two weakest dimensions and gives you one concrete move for each. The general playbook, the one I hear described in past tense by mentees who got the title on their own terms:

• Run the next sprint planning end to end. Not “help with.” Own it, including the awkward scope conversation.
• Mentor the most junior person on the team. Their growth becomes partly your problem. That sentence is the whole job in miniature.
• Have the feedback conversation you have been postponing. One honest conversation teaches you more about your people appetite than a month of reading.
• Tell your manager you want the lead path. Out loud, with a date. “I never said it out loud” is one of the most common answers in the org-reality dimension, and it is the cheapest gap to close.

Do these for two quarters and one of two things happens. Either the title conversation becomes a formality, or you discover you hated every minute, which is the same verdict at a much lower price.

Take the test. It is 3 minutes and brutal on purpose.

The Team Lead Readiness Test is free, 17 questions, no email needed to see your verdict. You get one of three answers: ready now, 6 to 12 months out, or stay IC and that is fine. Plus your two weakest dimensions and one concrete move for each.

If you live in an AI editor or agent instead of a browser, the same assessment runs as the assess_team_lead_readiness tool on my MCP server; point your client at marian.coach/mcp and ask it whether you are ready.

And if the verdict surprises you, in either direction, that conversation is exactly what a mentoring session is for.