Tech lead, engineering manager and senior IC are three different jobs. Choose by what energises you day to day: solving hard technical problems, guiding a team's technical direction, or growing people. Try the work before the title, through small leadership tasks, and remember the choice is reversible.
What people tell me
I am a few years into my career and my manager has asked whether I want to move towards leadership. I enjoy coding and solving difficult problems, but I also like helping newer people and sometimes planning work for the team. Everyone seems to assume management is the only way up. I am worried that if I say no I will stall, and if I say yes I will stop coding and regret it.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- A tech lead guides the technical direction of a team and usually still codes. A manager's main job is people: hiring, growth, performance.
- Many companies have an IC track that goes to staff and principal levels, so management is not the only way up.
- Choose by the daily work that energises you, not by title, pay or what others expect.
- Test before committing: lead a project, mentor someone, run a planning session.
- Moving between tracks is common and reversible, especially early on.
Three different jobs
People often talk about "going into leadership" as one thing. It is at least three different jobs, and they feel very different day to day.
| Senior or staff IC | Tech lead | Engineering manager | |
|---|---|---|---|
| Main focus | Hard technical problems, architecture, quality | Technical direction and delivery of one team | People: hiring, growth, performance, team health |
| Coding time | High | Medium, often reduced | Low or none |
| Success looks like | Systems that work and scale, strong technical decisions | The team ships the right thing well | People grow, the team is healthy and effective |
| Hardest part | Influence without authority | Balancing own coding with unblocking others | Difficult conversations, slow feedback loops |
| Typical day | Deep work, design reviews, debugging | Planning, reviews, pairing, some coding | One-to-ones, meetings, hiring, planning |
A tech lead is often still an IC on paper, with extra responsibility. A manager is a change of profession. The essay The Engineer/Manager Pendulum describes this well.
Management is not the only way up
At many product companies, the IC track continues to staff and principal engineer, with pay comparable to management. In smaller companies or service-based companies, the IC track may stop earlier, and "senior" may be the highest non-management title. Find out what exists where you work before deciding the choice is forced.
What energises you?
For two weeks, note at the end of each day what gave you energy and what drained you. Then look for patterns:
- Solving a tricky bug or designing a system gave energy. Lean IC.
- Unblocking others, planning, reviewing and deciding direction gave energy. Tech lead may fit.
- Helping someone grow, resolving a conflict, improving how the team works gave energy. Management might suit you.
- Meetings drained you almost every time. Be careful with management.
Try before you commit
You can test all of these without a title change:
- Lead one project. Break it down, assign parts, run the check-ins, own the delivery.
- Mentor a newer engineer for a few months. Notice whether their progress feels rewarding.
- Run a planning or retro session.
- Write a design document and drive it through review. See whether influencing others feels natural.
- Sit in on interviews if you are interested in hiring.
How do I become someone teammates can trust? covers the trust that every leadership role depends on.
A 60-day experiment
| Weeks | Experiment | What to notice |
|---|---|---|
| 1 to 2 | Keep the energy log | Which tasks lift you, which drain you |
| 3 to 5 | Lead one small project end to end | Do you enjoy coordinating, or miss coding? |
| 6 to 7 | Mentor one person weekly | Is their growth satisfying to you? |
| 8 to 9 | Talk to one tech lead, one manager, one staff IC | What they wish they had known |
At the end, talk to your manager with specifics: "I enjoyed leading the migration, but I found I missed hands-on work when meetings took over. I think tech lead fits better than manager for now."
Things to be honest about
- Management means less coding, often very little. Your technical skills can fade if you are not deliberate.
- Feedback loops get slower. Code gives you results in minutes. People grow over months.
- You will have hard conversations: performance issues, rejections, sometimes layoffs.
- Staying IC means building influence without authority, which is also hard.
It is reversible
Plenty of engineers try management for a couple of years and return to IC work, often better at it. Others go back and forth. The choice is less permanent than it feels, especially early in your career.
Questions to ask before you say yes
If your manager offers a lead or manager role, ask these before answering:
- "What exactly would change in my week? How much time would I still spend coding?"
- "Who would report to me, and what are their current challenges?"
- "What support or training would I get in the first six months?"
- "How will success be measured in this role after a year?"
- "If it does not suit me, can I move back to an IC role without it counting against me?"
- "Is there an IC path to staff level here, and what does it look like?"
The answers tell you whether this is a real, supported role or simply extra work with a new title. A good manager will be glad you asked. If the answers are vague, it is reasonable to ask for a trial period, for example leading one project for a quarter before any formal change.
Common mistakes
- Taking management because it is the only promotion offered, then being unhappy.
- Becoming a tech lead who still tries to write most of the code, so the team never grows.
- Turning down all leadership tasks, which also limits senior IC growth, because senior ICs lead too.
- Deciding based on title or pay alone.
If you are still stuck
The Staff and leadership roadmap and An Elegant Puzzle go deeper into both paths. If you want to think it through with someone, join Sefism: learning is free, and joining gives you credits. Members can ask their own question or book a 1:1 session about their specific offer.
Was this answer helpful?
Read next
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.