Short answer
Tech lead is accountability without authority. You own the technical outcome but cannot direct anyone, which means every result is produced by persuasion - so the quality of your disagreements, your reviews and your pushback is the entire job.
Tech lead is the most structurally awkward role in engineering. You are responsible for whether the project lands, the design holds up and the team stays unblocked - and you cannot tell anybody to do anything. Every outcome has to be produced by persuasion, and nobody trains you for that part.
Accountability Without Authority
Managers have levers: assignment, performance reviews, headcount. Tech leads have exactly one - being someone whose judgement people want to follow. This makes credibility the scarcest resource in the role, and it is why tech leads who try to substitute authority for persuasion tend to fail quickly and publicly.
The four things the role actually is
- Setting the technical direction and getting genuine agreement rather than silent compliance, which is the failure mode that surfaces three weeks later as a rewrite.
- Owning review culture. The tone you use in review becomes the team's tone within about a month, whether you intend it or not.
- Protecting scope. You are the last line between an optimistic roadmap and a team working weekends.
- Growing the people around you without the formal mechanisms a manager has.
Start here
Code review feedback without the fight is the highest-leverage page for a new tech lead, because review is where your influence is most visible and most easily damaged. The blocking/suggestion/nit convention alone removes most team friction within a week.
Pushing back on unrealistic deadlines is the other core skill: you will be the one asked whether the date is possible, and the three-option frame is what keeps that conversation collaborative rather than adversarial.
Disagreement is the job, not an interruption
A tech lead who is never disagreed with does not have consensus - they have a team that has stopped bothering. Actively invite the objection: "What's the strongest argument against this?" is a question that gets better answers than "any concerns?", because it gives explicit permission to push.
When you are the one disagreeing upward, the same rules apply to you: argue consequences rather than preferences, and commit properly once the decision is made.
Where tech lead leads
The role forks. Some tech leads move toward staff engineer, widening technical influence across teams without taking on people management. Others move to engineering management, trading technical depth for organisational leverage.
Tech lead is genuinely good preparation for both, and it is also a legitimate place to stay. Being the person who makes projects land is valuable indefinitely.
Frequently asked questions
What does a tech lead actually do?
Sets technical direction, owns the design and review culture, protects the team's scope from unrealistic commitments, and unblocks people - all without formal authority over anyone, which means every outcome comes from persuasion.
Is tech lead a management role?
No. Tech leads usually have no direct reports, no performance review responsibility and no headcount. They hold accountability for technical outcomes without the authority that normally accompanies it.
How do I lead a team without authority?
Through credibility and reasoning. Explain the why behind decisions, invite the strongest counter-argument explicitly, and be visibly willing to change your mind when someone is right. Teams follow judgement they trust far more reliably than instructions.
Should a tech lead still write code?
Yes, but off the critical path. Staying hands-on preserves technical judgement, while owning a deadline-bound feature means your lead responsibilities will constantly preempt it and the feature will slip.