Tech Lead CV in 2026: IC++, Not Engineering Manager

Tech Lead is the role recruiters understand least. Half of them read it as "junior manager", the other half as "senior engineer who runs meetings", and your CV is the only thing that decides which bucket you land in. If you write it as a vague hybrid, you get neither Staff IC interviews nor EM ones. You get filtered.

The trick in 2026 is to position yourself as IC++: still an engineer at the core, but with a multiplier effect on the team. No formal direct reports, but real ownership of tech direction. Done right, the same CV opens doors to Staff IC and to EM, depending on which role you decide to chase that month. Let's go through what that actually looks like on paper.

Tech Lead is not Engineering Manager, and your CV has to say that

EM owns people. Hiring, firing, 1-on-1s, performance reviews, comp. If you've never run a perf cycle or had to put someone on a PIP, you're not an EM yet, no matter how many standups you facilitated. Tech Lead owns the technical direction of a team: what we build, how we build it, what we don't build, and which trade-offs we accept on the way. The team's manager handles the people side. You handle the system.

Write that distinction into your summary in one line. Something like: "Tech Lead, 6 engineers, owning architecture and delivery direction; line management with the EM". Recruiters scan summaries first. If they can't tell in five seconds what you own and what you don't, they assume you're inflating the title and move on.

• Team size you technically lead, even without HR reports
• Scope: which services, which surface area, which product domain
• Where your authority ends, hiring, comp, performance
• How long you've been in the lead seat for this team
• One line on what the team shipped because of decisions you made

Architectural decisions you owned, the part most CVs skip

Most Tech Lead CVs list features shipped and team metrics, then go quiet on the actual decisions. That's the gap a Staff IC interviewer wants to see filled. They're not asking "did your team ship?", they're asking "would I want you in the room when we redesign payments?". Bullets need to name the decision, the alternatives, and the consequence.

Bad version: "Designed and led migration to microservices". Reader learns nothing. Good version: "Argued against a full microservices split for the billing domain; kept it as a modular monolith with extracted async workers, saving 4 months of cross-team work and cutting p95 by 18% in the same quarter". The good version proves you can choose not to do the trendy thing. That's senior signal.

Multiplier-effect bullets without claiming you manage people

The smartest move on a Tech Lead CV is to show you made the team faster, safer or sharper, without writing verbs like "managed", "led 1-on-1s" or "owned performance". Those words trigger the EM filter and the recruiter starts asking about people questions you can't answer. Instead, use verbs that belong to a senior IC who happens to lift the team.

• "Drove" the architecture, not "managed" the project
• "Unblocked" three engineers a week through pair-debugging on a critical service
• "Authored" the API contract used by 4 squads, removing 2 months of back-and-forth
• "Set" the team's testing baseline; flake rate dropped from 11% to 2% in 8 weeks
• "Mentored" 2 mids into the senior interview loop without owning their reviews

Notice the last one. "Mentored" is fine. "Promoted" is not, because promotion is the manager's call. If you write "Promoted 2 mids to senior" on a Tech Lead CV, a careful interviewer will catch the lie in five minutes. Stay precise. Senior people read precise CVs as senior.

The "did you actually code?" question, killed at the CV stage

Every Tech Lead interview eventually arrives at: "how much do you still code?". If your CV is all architecture and roadmaps, the interviewer assumes the answer is "barely" and starts grading you on EM signal. If you want the Staff IC track too, you need at least 2-3 bullets that are unambiguously hands-on, with a real artifact behind them.

Hands-on bullets look like: "Wrote the rate-limiter library now used by 5 services; 800 LOC of Go, 92% test coverage" or "Owned the incident playbook for the payments path and authored the rollback tool we used in 3 prod outages this year". They name a thing you typed, not a thing the team built. One or two of these tell the reader you didn't lose the muscle.

Writing one CV that flexes into Staff IC or EM

You don't need two CVs. You need one CV with two adjustable knobs: a summary line and a top-of-bullets section per role. Keep the body identical across applications, swap the framing. For a Staff IC role, the summary leans on architecture, system thinking and the hands-on artifacts. For an EM role, the same summary leans on team outcomes, hiring help and the mentoring story. The bullets underneath don't change.

• Staff IC framing: "Tech Lead with 6 years owning architecture for high-traffic systems"
• EM framing: "Tech Lead growing a 6-engineer team and the senior pipeline behind it"
• Same skills section, reordered: architecture first for IC, people-adjacent first for EM
• Same bullets, different verbs at the front ("designed" for IC, "led" for EM)

Design reviews and tech reviews on the CV without sounding ceremonial

Running design reviews is one of the highest-leverage things a Tech Lead does, and one of the easiest things to write boringly. "Facilitated weekly design reviews" says nothing. Anyone with a calendar invite can claim that. What signals real ownership is the shape of decisions that came out of those reviews and the bar you set for what gets in.

Rewrite it: "Set up a lightweight design-review template (problem, options considered, trade-offs, blast radius); after 3 months, 9 of 11 proposals shipped without a rework loop". Now the reader sees a process you authored and a measurable outcome. Same with tech reviews: name what you blocked from shipping and why, not just that you ran the meeting.

If you blocked something with consequences, write it. "Pushed back on a third-party search vendor swap; estimated 6-week migration vs 9-day in-house index rebuild; the in-house path shipped on time and saved $42k/year". That single bullet does more for your CV than ten lines of meeting hygiene.

A quick checklist before you send the CV out

• Summary line names team size, scope, and where your authority stops
• At least 3 bullets that name a decision, an alternative, and a consequence
• 2-3 hands-on bullets with a real artifact you typed, not the team's output
• Zero use of "promoted", "hired", "fired", "ran perf reviews" unless you really did
• Design and tech reviews framed as decisions and blocked work, not meetings
• One CV, two summaries on file, swap depending on whether the job is IC or EM

Tech Lead is the hardest title to write a CV for because the role itself has no industry-standard definition. The good news is that gives you room. Write it precisely, separate the IC work from the people work, name decisions instead of activities, and you'll get callbacks from both tracks. Then pick the one you actually want.