Skip to content

Tech Lead (Years 5–10) — Deep Dive

Hybrid role: technical leadership, mentoring, and coordination without necessarily having formal people-management authority.


What "Tech Lead" Actually Means

A Tech Lead is:

  • ~70% IC work — designing, coding, reviewing (an illustrative split, not a standard)
  • ~30% people work — mentoring teammates, unblocking the team, coordinating
  • Technical authority — people respect your expertise
  • A leader without required formal authority — hiring, firing, and compensation usually stay with the manager
  • Team representative — speak to management on behalf of technical team
  • Not automatically a manager — a Tech Lead Manager (TLM) is a different role with formal reports

Typical scope: Small team (3–8 engineers) + technical domain.

Note: "Tech Lead" is a role, not a level, at many companies — it's often held by a Senior or Staff engineer. Some companies also have a TLM (Tech Lead Manager) role that adds formal reports.

Duration: Often a multi-year developmental role, but there is no mandatory tenure or forced next step. You can move toward Staff IC, management, or another Tech Lead scope.


Why Tech Lead Role?

Before You Commit to Management

  • Try people interactions without full commitment
  • See if you like coaching vs. executing
  • Develop leadership muscles
  • Keep technical skills sharp

Before You Commit to Pure IC

  • Test if you want broader influence
  • Understand what management looks like
  • Build leadership skills you might need later

Unique Value

  • You understand both technical and people sides
  • You build consensus through technical authority, not hierarchy
  • You can bridge engineers and management

Your Role & Responsibilities

The split below is a typical week; the "~70% IC" above includes technical work plus design docs and reviews.

~50% Technical Work

  • Design systems and architecture
  • Write code (maybe 30% of time)
  • Propose technical improvements
  • Participate in architecture reviews

~30% Mentoring & Developing

  • Mentor 2–3 engineers on your team
  • Help them own features
  • Code review their work (teaching, not gatekeeping)
  • Celebrate wins and learn from failures

~20% Meetings & Communication

  • Sync with your manager
  • Participate in planning meetings
  • Represent team's technical concerns
  • Write design documents

Tech Lead vs Manager vs. Senior Engineer

Responsibility Tech Lead Manager Senior IC
Technical decisions Primary Advisory Primary
Mentoring Direct mentoring Growth/coaching Thought leadership
Hiring Input, no final call Full responsibility Input, no call
Performance feedback Informal only Formal, official Informal only
People's manager No (someone else is) Yes No
Coding 40–50% 10–20% 30–50%
Meeting load Medium High Low
Scope 1 team 1–3 teams 1 team / service

The Unique Challenges of Tech Lead

Challenge 1: Ambiguous Authority

You're not their manager, but you lead them. Confusing.
Fix: Be clear. "I'm not your manager, but I'm helping you grow technically."

Challenge 2: Overcommitment

You say yes to too much tech work AND people work.
Fix: Set boundaries. You can't do both 100%.

Challenge 3: Bottlenecking on Technical Decisions

Nothing ships until you review it.
Fix: Set clear standards. Teach people. Let them run.

Challenge 4: Unclear Path Forward

People don't know if you're stepping toward management or IC.
Fix: Talk to your manager. Have a 2–3 year plan.

Challenge 5: Not Feeling Like 'Real' Management

You don't hire, don't fire, don't set comp.
Fix: You're testing. This is intentional. Use it to learn.


Decision Point: IC or Management?

Reassess your path after you have enough evidence about the role; there is no mandatory deadline.

Signals you may prefer the IC track:

  • You love solving technical problems more than people problems
  • Code and design excite you more than organizational dynamics
  • You want deep expertise
  • Technical exploration energizes you more than organizational coordination

Signals you may prefer management:

  • You love helping people grow
  • Coaching and mentoring excite you
  • You want broader organizational impact
  • People and organizational dynamics energize you

What to do:

  1. Talk to Staff Engineers and Managers you trust
  2. Reflect on which parts of the Tech Lead role energized you
  3. Choose your next focus and clarify expectations with your manager
  4. Review that choice periodically; you can change direction again later

Books to Read as Tech Lead

  1. The Staff Engineer's Path — understand the IC path (has a strong Tech Lead section)
  2. The Manager's Path — understand the management path (covers the Tech Lead role explicitly)
  3. Radical Candor — feedback and mentoring
  4. The Phoenix Project — systems thinking
  5. Designing Data-Intensive Applications — deepen technical knowledge

Success Metrics (As Tech Lead)

✅ Your team ships on time and with quality
✅ Engineers you mentored grow and ask your advice
✅ Your technical decisions improve the system
✅ Other teams respect your opinion
✅ You're not bottlenecking anything
✅ You still write code and stay current


Should I become Tech Lead if I'm not sure about management?

Yes. That's exactly the point. 2–3 years of testing saves 10 years of wrong choice.

How do I know when to switch from Tech Lead to IC vs Manager?

Ask your manager for guidance. Be honest: "Which path do you think fits me?" Get 360 feedback.

Is Tech Lead a real level or a role?

Usually it is a role held by a Senior or Staff engineer, not a separate level. Make sure your scope, decision rights, and evaluation criteria are explicit; a Tech Lead Manager role is different because it adds formal reports.


Next: Director of Engineering or return to IC vs Manager Track.