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 hadn’t failed. They’d accepted a job nobody described to them, which is a different problem.
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, and it doesn’t check whether the person actually 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
What does the title actually change? Almost none of it comes up in the offer conversation.
The pattern my first-time lead mentees report: coding drops toward 50% in the first quarter, and a year in it’s often closer to 20%. The calendar fills with 1:1s, planning, and conversations with people who can’t read your code and shouldn’t 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’s a bigger lever. But it is a different job than the one you were promoted for, 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.
In practice, “can I do it?” is the wrong question, most senior engineers can, mechanically. The better question is whether the job will give you energy or eat it.
The six dimensions that predict the fit
Every readiness conversation I run eventually walks the same six dimensions. The test asks 17 scenario questions across them, no “rate your leadership from 1 to 10” fluff, just concrete Monday-morning situations with honest answer options.
| Dimension | The question underneath | The red-flag answer |
|---|---|---|
| People appetite | Do 1:1s, feedback, and conflict give you energy or drain you? | Quiet dread at four 1:1s in a week |
| Letting go of code | Can you hand the hardest ticket to someone slower than you? | ”Hard tickets are my thing” |
| Ownership beyond tickets | Do you already run planning, unblock others, mentor juniors? | ”My tickets are on track, so not my problem” |
| Translation and saying no | Can you explain three weeks of migration to a PM in risk and money? | ”If they can’t read code, that’s their gap” |
| Why you want this | Would you still want it at the same pay for two years? | ”The money was the point” |
| Org reality | Is there an actual seat, and does your manager know you want it? | Flat org, role does not exist, nobody told |
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 isn’t “could you address it” but what you actually did. “Helped with their tickets and dropped hints” means you avoided the conversation, and it felt helpful the whole time.
- Letting go of code shows up as the hardest-ticket reflex. Taking it yourself because you’re 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’re already doing the job.
- Translation and saying no decides whether the org trusts your team. “It’s complicated” plus a link to the epic isn’t an explanation, and quietly absorbing mid-sprint requests in your evenings isn’t a boundary.
The last two dimensions deserve their own sections, because they’re 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 isn’t 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.
That’s why the test’s third verdict is literally “Stay IC. And that is fine.” No promotion process will hand you that verdict, because promotion processes are pipelines, built to fill seats, as opposed to protecting you from the wrong one.
Salary-only motivation doesn’t survive the first bad quarter
The second dimension worth a spotlight: why you want this.
There’s 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 isn’t 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. If service and impact pull you, that week is hard and survivable. If the title and the money were the whole pull, that’s usually the week the “maybe management isn’t for me” message gets drafted.
If the raise is the actual goal, raise your market value and negotiate directly. It’s a cheaper way to get money than a job you don’t 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, which is the whole job in miniature.
- Have the feedback conversation you’ve 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’s 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’s 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’s 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’re ready.
And if the verdict surprises you, in either direction, that conversation is exactly what a mentoring session is for.