Career guide
How to become a Tech Lead: the transition guide
Published
You become a Tech Lead the day you are accountable for what the team ships, and no longer only for your own code. The title often comes later. You need to be technically credible first, then learn three new jobs: making decisions and writing down why, helping others grow, and speaking product and business.
What really changes
As a developer, you were judged on your tickets. As a Tech Lead, you are judged on the team’s ability to ship, often and without breaking things, for years.
Your calendar changes too. Fewer long stretches of focus, more reviews, questions, trade-offs and conversations with product. Many new Tech Leads struggle with this fragmentation for the first few months; that is normal, and it can be organised.
The code stays the reference, since it is what runs in production. A Tech Lead who stops reading the code quickly loses track.
Related principles
The foundation: staying technically credible
Nobody follows a Tech Lead who does not understand the system. Before taking the role, aim for an end-to-end view: where the data comes from, who consumes it, what breaks when a service goes down.
Knowing production matters as much as knowing the code. Being able to deploy, read the logs and understand an alert is what makes you useful the night everything is on fire.
Learning to decide, and to write down why
The Tech Lead settles technical choices: database, framework, how to split services, which debt to pay back and which to keep. Most of these choices have no universal right answer; they have a right answer in your context.
A decision made out loud gets distorted in people’s memories, then disappears. Write down the context, the options you ruled out and the reason for the choice. Six months later, that document is what stops the debate from reopening.
Technical debt is part of the decisions. There is the debt you inherit and the debt you choose on purpose to ship faster. The job is to make the second explicit and keep the first under control.
Growing the team instead of doing everything yourself
The new Tech Lead’s reflex is to take the hard tasks back “because it will be faster”. That works for a week. Then you become the team’s bottleneck, and nobody else grows.
Delegate the topics that help people grow, review without rewriting, leave room for mistakes on anything reversible. Regular one-on-ones catch weak signals before they turn into resignations.
Match the amount of structure to the team’s maturity. A young team needs clear rules, an autonomous team needs room.
Speaking product and business
A Tech Lead spends part of their time with product, sales or leadership. They translate technical constraints into timelines, risks and costs, and do the reverse for their team.
Keeping the balance between product vision and technical vision is ongoing work. And the company has to make money: an elegant architecture that delays the launch helps nobody.
Where to start
You do not need to wait for an open position to practise. Take on these responsibilities one by one in your current team:
- write the next architecture decision with its rationale;
- prepare the onboarding of the next newcomer;
- turn an unwritten convention into a rule checked by CI;
- trace a recurring problem back to its cause instead of working around it once more.
Once in the role, start by listening and mapping before changing anything. The first weeks are for understanding why things are the way they are.
Common pitfalls
- Staying the best developer on the team and keeping the key tasks for yourself: the team stalls and you burn out.
- Deciding alone and out loud: every newcomer reopens the topic.
- Keeping context to yourself: most friction between people who share the same goals comes from an information gap.
- Wearing yourself out: the role lasts for years, so treat it as a marathon.
Frequently asked questions
- How do you become a Tech Lead?
- By gradually taking on the role’s responsibilities in your current team: documenting technical decisions, onboarding newcomers, reviewing other people’s code, working with product. The title usually comes once the team already sees you in that role.
- Do you need a degree or certification to become a Tech Lead?
- No. The role is earned through practice and the team’s trust. Reading, mentoring and other people’s experience help you get there faster; no degree is required.
- Does a Tech Lead still write code?
- Yes, but less, and preferably off the critical path. Writing code keeps your credibility and your knowledge of the system; taking the blocking tasks makes the Tech Lead the team’s bottleneck.
- Is Tech Lead a management position?
- It is a technical leadership role, often with no reporting line. People management (careers, hiring, performance reviews) usually belongs to the Engineering Manager. The Tech Lead vs Engineering Manager guide covers the difference.
- How do you prepare when your company has no open Tech Lead position?
- Start with the parts of the role your team is missing: a written architecture decision, an onboarding path, an automated convention, a root-cause analysis after an incident. They are concrete evidence to show when the time comes.
Other guides
The 60 principles, in one book
Every principle cited in these guides is covered in NoBullshit Tech-Lead: 240 pages for developers, Tech Leads, architects and CTOs (in French).