The Short Answer: Start Doing the Job
Tech lead is usually a role you take on, not a title you are handed. In most companies it is a hat, not a rung on the ladder, which means you rarely need permission to start. You become a tech lead by owning the technical direction of a project and the team's ability to deliver it: you break the work down, make the design calls, unblock people, and keep the effort coherent. The core shift is from your personal output to the team's throughput. Your job stops being to write the most code and starts being to make sure the right code gets shipped by the whole team. Demonstrate that a project goes better when you are quietly doing that coordination, and the role becomes yours in practice before it is ever official.
I am Mahmoud Zalt, an AI architect who has led engineering teams for over a decade. Through Sista AI I mentor engineers stepping into their first lead role.
What a Tech Lead Is, and Is Not
The title confuses people because it sits between three different jobs. Getting the distinction right tells you what to actually work on.
| Role | Owns | Primary focus |
|---|---|---|
| Tech Lead | A project's technical delivery and the team's execution on it | Ship the right thing, well, with the team |
| Engineering Manager | People: careers, performance, hiring | Grow and support the humans |
| Architect | Cross-system technical design | Long-horizon technical coherence |
A tech lead is not a mini-manager. You are not doing performance reviews or owning someone's career. You are the person accountable for whether the project is technically sound and actually ships. You are also not an ivory-tower architect who hands down diagrams. A good tech lead is in the code, close to the team, making the plan real. The role is where deep technical work and light leadership meet, which is exactly why it is the most common on-ramp to both staff engineering and management.
How to Earn the Role
Since it is a role you grow into, the path is a set of behaviors you can start this week, on your current project.
- Own the plan, not just your task. Volunteer to break an ambiguous project into a sequence of pieces the team can pick up. The person who writes the plan quietly becomes the person leading it.
- Unblock other people first. Make yourself the one who clears dependencies, answers questions, and reviews promptly. Throughput improves when the team is not stuck, and everyone notices who did the unsticking.
- Communicate up and out. Give your manager and stakeholders a clear read on status, risks, and tradeoffs. Being the reliable source of truth for a project is half of leading it.
- Make design decisions visible. Write short design docs, weigh two options, and record the call. This builds the trust that lets people follow your technical direction.
- Protect the team's focus. Absorb interruptions, push back on scope creep, and keep the group pointed at the goal. This is invisible work that has enormous impact.
The Hard Part: Letting Go of the Keyboard
The genuine difficulty of becoming a tech lead is emotional, not technical. For years your value came from being the person who wrote the most and the best code. As a lead, some of your value now comes from not writing that code, and instead enabling three other people to write it. That trade feels like a loss at first. You will watch a teammate solve a problem more slowly than you would have, and you will have to let them, because your job is to grow the team's capacity, not to be its bottleneck. The engineers who thrive as leads make peace with this: they still code, usually on the riskiest or highest-leverage parts, but they measure themselves by what the team shipped, not by their personal commit count. If you cannot let go of the keyboard at all, the individual-contributor staff track may fit you better than lead, and that is a legitimate choice, not a failure.
Frequently Asked Questions
Is tech lead a promotion?
Usually not by itself. At most companies it is a role or hat you can hold at your current level, often senior. It is one of the clearest on-ramps to a staff engineer or engineering manager promotion, because it gives you visible leadership evidence, but the title change and the role are separate events.
Do tech leads still write code?
Yes, usually, but less of it and more deliberately chosen. A tech lead often takes the riskiest, most ambiguous, or most architecturally important parts, and leaves the rest to the team. A meaningful share of the week goes to planning, unblocking, and communicating instead of coding.
Tech lead or engineering manager, which should I choose?
Tech lead keeps you close to the technology with lighter people responsibility, while an engineering manager owns careers, performance, and hiring. Many engineers try tech lead first, because it lets you test your appetite for leadership without giving up the technical work entirely.
How do I become a tech lead if no one appoints me?
Start doing the job on your current project. Offer to own the technical plan, break down the work, unblock teammates, and be the status source of truth. When a project visibly goes better because you did that, the role tends to become official.
Grow Into the Role Deliberately
Becoming a tech lead is less about a promotion decision and more about a deliberate change in how you spend your time and where you find your value. The engineers who make the shift cleanly usually have someone to talk it through with, because the hardest parts, delegating, communicating up, and measuring yourself by the team's output, are exactly the parts you cannot learn from a documentation page.
That is what my Engineering Mentorship helps with: making the shift from strong individual contributor to trusted lead, with real feedback on the leadership and communication reps. It starts at $80 for a single session, with a $400/month track of four sessions plus accountability, or a $1.2K three-month Career Accelerator. If you are ready to lead your first project, start here.
