From answers to questions
Stop being the person with every answer. Start being the person who asks the question that unlocks the room. Influence grows when you make others smarter.
Free Guide
How to become a tech leader
The move from individual contributor to leader is one of the hardest transitions in a technology career — and one almost no one is trained for. Here is the honest version: the mindset shift, the skills that matter, the traps to avoid, and a 90-day plan to start.
Leadership is a change of job, not a reward for a good one
Most engineers are promoted into leadership because they were excellent engineers. Then they discover the thing no one warned them about: the new job barely resembles the old one. The skills that made you a great individual contributor — going deep, shipping the hardest code, being the person with the answer — are not the skills that make a great leader. Leadership is measured by what your team produces and how its people grow, not by your personal output.
That single reframe — from “How much can I build?” to “How much can I help this team build, and how much better can each person get?” — is the foundation everything else rests on.
The five shifts that turn an engineer into a leader
You don’t need a title to start. You need to start behaving like a leader where you already are.
From doing to multiplying
Your leverage is no longer your keyboard — it’s mentorship, unblocking, and clarity. One hour spent making five people better beats one hour of your own code.
From tasks to outcomes
Care less about which ticket is done and more about whether the team is moving the metric that matters. Connect daily work to why it matters.
From certainty to judgment
Leaders decide with incomplete information. Build the emotional steadiness to make a call, own it, and adjust — rather than waiting for certainty that never comes.
From self to service
The job is now to care for people while unlocking their best work. The teams that win are the ones that feel both supported and stretched.
From coding to communicating
Writing, framing, and listening become your highest-value skills. Most leadership failures are communication failures in disguise.
Common traps for new tech leaders
- Staying the best engineer. Hoarding the hard work feels productive and quietly starves your team of growth.
- Avoiding the hard conversation. The feedback you postpone compounds into a much harder problem later.
- Leading former peers as if nothing changed. The relationship has changed; name it and reset expectations early.
- Confusing being busy with being effective. A full calendar is not a strategy.
- Forgetting you set the weather. Your mood, standards, and reactions become the team’s culture, whether you intend it or not.
A 90-day plan to start
Days 1–30 — Listen. Meet every person one-on-one. Ask what’s working, what isn’t, and what they want to grow toward. Learn how the team actually operates and what you’re accountable for. Resist the urge to prove yourself by doing the engineering.
Days 31–60 — Clarify. Set a small number of clear priorities and a simple operating rhythm — how you plan, how you make decisions, how you give feedback. Start mentoring deliberately, not accidentally.
Days 61–90 — Multiply. Delegate something you’d rather keep. Give one piece of direct, kind feedback you’ve been avoiding. Measure your success by the team’s momentum and the growth of the people on it.
Go deeper
The whole blueprint is in the book.
This guide is the first step. Tech Leadership gives you the frameworks, real stories, and tools to make the leap — and lead well once you have.
Frequently asked questions
How do you become a tech leader?
It’s less about a promotion and more about a shift in where you create value — from writing the best code yourself to multiplying the output and growth of a team. Start by taking ownership beyond your tasks, mentoring peers, communicating decisions clearly, and learning the fundamentals of strategy, execution, and people development.
Do you need to be the best engineer to lead engineers?
No. You need enough technical depth to earn trust and make sound judgment calls, but the job changes from being the strongest individual contributor to making the whole team stronger.
What skills do tech leaders need?
Communication, mentorship, technical strategy, prioritization and execution, hiring and developing people, and the emotional steadiness to decide under uncertainty. These are learnable skills, not innate traits.
What should you do in your first 90 days as a manager?
Listen first, then clarify priorities and an operating rhythm, then start multiplying through delegation and feedback. Don’t try to prove yourself by doing the engineering work yourself.