Team Lead CV 2026: People-Manager or Still-Codes Engineer

Open ten Team Lead job ads in 2026 and you will find ten different roles. One wants a senior engineer who happens to run weekly 1-on-1s. The next wants a full people manager who has not opened a PR in two years. The third wants both, full-time, and pays for one. So when you sit down to rewrite your CV, the first honest question is "which kind of Team Lead am I, and which kind is this company actually buying?" Most candidates skip that step and lose the role to someone less experienced but better positioned.

This post is for the Team Lead who got passed over for an EM role last quarter, opened the CV, and realised it reads like a confused mix of "I led people" and "I shipped features" with no anchor. We will fix the anchor, the bullets, and the answer to the question that decides every TL interview: "what percentage of your time is coding?"

The most ambiguous role on the market

Backend, frontend, QA, designer, even PM, all have a relatively stable shape across companies. Team Lead does not. In a 12-person startup, a Team Lead writes half the codebase, hires three people a year and runs payroll conversations. In a 400-person scale-up, a Team Lead with the same title does zero coding, owns headcount planning, and reports into an EM. Same title, two unrelated jobs.

Because of this, recruiters set the trap on purpose. The job ad will list both "hands-on coding" and "people management responsibilities" because they themselves do not yet know which lead they want. The first sentence of your CV summary has to make the choice for them: are you a player-coach Lead, a delivery-focused Lead, or a people-first Lead on the path to EM. Pick one. The other two qualities can still appear in the bullets, but the summary has to anchor.

The "still ships code" myth

Every second Team Lead writes some version of "hands-on lead who still ships code" in their summary. In 2022 it sounded like a flex. In 2026 it sounds like denial. Hiring managers have seen the pattern too many times: the Lead writes "still codes", joins the team, and three months later cannot remember the last PR they opened that was not a doc tweak. The phrase has lost almost all signal.

If you do still ship code, prove it with one specific 2026 bullet, not an adjective. "Owned the auth refactor in Q1 2026, 14 PRs over 6 weeks, dropped login p95 from 1.4s to 380ms" ends the argument. "Hands-on lead" starts an argument you will lose. Adjectives age badly; a dated, numbered PR set does not.

And if you no longer ship code, that is also fine. Write it honestly: "Coding share dropped from 40% to 10% in the last 12 months as the team grew from 4 to 9." That sentence costs you nothing and tells the recruiter you understand your own role. Pretending you still code at 50% when you do not is the fastest way to fail the technical screen.

Bullets that prove you grew or protected the team

The single weakest area in Team Lead CVs is the bullets. They sound like a job description, not a track record. "Managed a team of 6 engineers" is not a bullet, it is a fact. A real Team Lead bullet has to do one of two things: prove you grew the team, or prove you protected the team from something. Anything else is filler.

Growth bullets are easier. They take the form action + headcount or grade move + timeframe. "Promoted 2 mid-level engineers to senior in 14 months through structured growth plans, both still on the team a year after promotion." The second clause is what sells it: a promotion that stuck is worth ten promotions that triggered a resignation 90 days later.

Protection bullets are harder to write but read stronger because most candidates skip them. "Pushed back on a deadline the team flagged as unrealistic, negotiated a 3-week extension with the PM, shipped on time without weekend work." Or: "Held the team headcount during the company-wide Q3 freeze by reframing two open roles into internal moves." These bullets show the part of the job nobody outside leadership sees, and hiring managers know that and weight them heavily.

• Always pair team size with timeframe: "team of 8 for 18 months" beats "team of 8"
• Attrition numbers land hard if you have them: "attrition dropped from 22% to 6% in 12 months" is a hire-on-sight bullet
• Mention hires that survived probation, not just headcount added. The first number is honest, the second is theatre
• Include one cross-functional bullet (PM, design, data) to show you do not live only inside the team
• If you let someone go, you can mention it in interview, not in CV. Bullets are for outcomes, not stories

The manager-vs-IC trap recruiters set

There is a question that comes up in almost every Team Lead screen and most candidates answer it wrong: "so, are you more of a manager or more of an IC?" The recruiter is not asking out of curiosity. They are testing whether you understand that for this specific role they need one or the other, and whether you can read which one and answer accordingly. The wrong move is to say "I am both". That answer is a no-signal and the recruiter has heard it 200 times this year.

The right move depends on three signals you read before the call: the company size, the team size you would inherit, and whether there is already an EM above the Lead. Small company, small team, no EM above, they want player-coach. Larger company, team of 8+, EM above, they want people-first on the path to EM. If you cannot tell from the ad, ask in the recruiter call directly: "what split between coding and management does the team need from this lead today?" Asking that question alone often moves you to the next round, because it shows you know the role has two shapes.

Handling "what percentage of your time is coding?"

This is the question that derails Team Lead candidates more than any other in 2026. The trap is that whatever number you give, the interviewer has a follow-up. Say 60% and they ask why you are even applying for a lead role. Say 5% and they ask if you can still review architecture decisions. Say "it depends" and they file you under non-committal.

The answer that works has three parts in this order: the honest number, the trend, and the reason. "Right now about 15%, mostly architecture reviews and a couple of critical bugs per quarter. It was 35% a year ago, but the team grew from 4 to 8 and I traded coding time for hiring and 1-on-1s. I plan to keep it around 15 because that is the minimum I need to stay credible in code reviews." Three sentences. Honest, trended, defended. The interviewer has nothing to ambush.

If you have not thought through your own number before the interview, you will improvise it on the spot and it will sound improvised. Write the three-part answer down before the screen, out loud, twice. The version you say to yourself in the mirror is always 30% sharper than the one you type.

Summary line: what to put, what to delete

A Team Lead summary that works has four pieces in this order: years leading + current team size + the anchor (player-coach / delivery / people-first) + the kind of system or domain you work in. Example: "4 years leading, currently 8 engineers, people-first lead with a backend background, payments and fintech". The recruiter knows your scope, your style, your stack and your domain by the end of one line.

Things to delete from a Team Lead summary today: the words "servant leader", any mention of "passion for people", the phrase "hands-on lead who still codes" without a number behind it, and the laundry list of methodologies (Scrum, Kanban, SAFe, XP) in the first line. Methodologies belong in the skills block. The summary is for positioning.

Common Team Lead CV mistakes I keep seeing

• Inflated team size: "led 20+ engineers" when really 4 reported to you and 16 sat in the same room. Recruiters check on the screen
• Listing technologies the team uses, not what you personally still work in. Stack inventory is not leadership signal
• Zero numbers around people work: no attrition, no promotions, no headcount delta. Manager bullets without numbers age like milk
• Same project mentioned under both "leadership" and "technical" sections. Recruiters notice and discount both halves
• No mention of who you report into. Lead under a Director and Lead under an EM are two different jobs, and the CV should make it clear

Salary ranges for Team Lead in 2026

Useful as a sanity check before you fill in expected compensation. These are 2026 market bands specifically for Team Lead with a team of 5 to 10, not for engineering management in general.

• Ukraine: $3,500-5,500 mid lead, $5,500-8,500 senior lead per month
• EU (Western): 6,000-8,500 mid lead, 8,500-12,000 senior lead EUR per month
• USA: $160,000-200,000 mid lead, $200,000-260,000 senior lead per year base, plus equity

Two notes. US bands are base only, equity at product companies often adds another 25-40% on a senior Lead. If your number lands in the bottom of the band but you have one strong retention bullet (attrition under 10%, promotions that stuck), you are almost certainly under-asking by 10-15%.

Last thing. If you got passed over for an EM role this year, the gap is almost never "more technical depth". It is almost always either an unclear summary anchor or zero retention numbers in the bullets. Both are fixable in an afternoon. The next role you apply to should see a sharper CV than the last one did.