You have been a strong individual contributor for years. You ship features, solve hard problems, and your tech skills are solid. And now, someone has asked the question: "Have you thought about management?"
Or maybe nobody asked. Maybe you have been watching your manager handle one-on-ones, sprint planning, and stakeholder meetings, and you have thought to yourself, "I could do that, and maybe do it better."
Either way, the transition from IC to people manager is one of the most significant career shifts in tech. It is also one of the most misunderstood. The skills that made you an excellent engineer are not the same skills that will make you an excellent manager. Some of them transfer. Many do not.
This guide is for people who are either considering the switch, actively preparing for it, or have recently made the jump and are trying to figure out what just happened.
Let us be direct about this. Becoming a people manager means your primary output is no longer code or technical architecture. Your primary output is now the effectiveness and growth of other people.
That sounds obvious, but the implications are deeper than most people realize.
Your calendar will look completely different. Instead of long blocks of focus time, you will have a patchwork of one-on-ones, team meetings, cross-functional syncs, and planning sessions. Your dopamine hits will change too. Instead of the satisfaction of merging a clean PR, you will get your wins from watching a team member have a breakthrough, or from unblocking a project that was stuck because of a people or process problem.
If that does not sound appealing to you, that is worth paying attention to. Not everyone is wired for management, and there is no shame in choosing to stay on the IC track. Many companies now have senior, staff, and principal engineer tracks that offer equivalent growth, scope, and compensation.
But if the idea of building and growing a team excites you, keep reading.
The most jarring part of the transition is how unstructured your days become. As an IC, you typically have clear tasks, clear deliverables, and a clear definition of done. As a manager, most of your work is ambiguous, ongoing, and hard to measure.
Here is what your core responsibilities will look like.
People development. Running meaningful one-on-ones, giving constructive feedback, writing performance reviews, identifying growth areas, and creating development plans. This is probably 30 to 40 percent of the role.
Team health and dynamics. Building psychological safety, resolving interpersonal conflicts, maintaining team morale, and ensuring everyone feels heard and valued. This is the invisible work that makes or breaks a team.
Execution and delivery. Ensuring the team is delivering on commitments, removing blockers, managing scope, and communicating progress to stakeholders. You are not writing the code, but you are accountable for the output.
Hiring and talent. Sourcing candidates, running interviews, making hiring decisions, and onboarding new team members. This becomes a significant time investment, especially if your team is growing.
Strategy and alignment. Working with product, design, and leadership to ensure the team is working on the right things. Translating company priorities into team goals.
None of these come with a tutorial. You learn by doing, and often by making mistakes.
Some of your IC skills will serve you well. Technical judgment helps you make better decisions and earn credibility with your team. Problem-solving applies, just to different types of problems. Attention to detail helps with things like performance reviews and project planning.
But several critical management skills are entirely new.
Active listening. As an IC, you are trained to jump into problem-solving mode. As a manager, sometimes the most important thing you can do is listen without immediately offering solutions. Your team members often need to feel heard before they are ready for advice.
Giving difficult feedback. This is uncomfortable for almost everyone, but it is non-negotiable. Avoiding hard conversations does not make problems go away. It makes them worse. Learning how to deliver feedback that is specific, timely, and compassionate is one of the most important skills you will develop.
Delegation. This is where many new managers struggle the most. You know you can do the task faster yourself. But doing it yourself defeats the purpose. Your job is to grow your team's capacity, not to be the bottleneck.
Managing up. You are now the bridge between your team and leadership. You need to communicate effectively in both directions, translating executive priorities into actionable work for your team while advocating for your team's needs to leadership.
Emotional regulation. Your team will look to you for cues. If you are stressed, they will be stressed. If you are calm during a crisis, they will be calmer. Your emotional state is now a leadership tool, whether you like it or not.
If you are still in an IC role but considering management, there are concrete steps you can take right now to prepare.
Start leading without the title. Volunteer to lead a project, mentor a junior engineer, or run a team retrospective. These experiences give you a taste of what management involves without the full commitment.
Find a mentor who has made the transition. Talking to someone who has been through the exact same shift is invaluable. They can share what surprised them, what they wish they had known, and what mistakes to avoid. Platforms like BeTopTen connect you with experienced engineering managers and senior leaders who can provide this kind of guidance.
Read, but not too much. Books like "The Manager's Path" by Camille Fournier and "An Elegant Puzzle" by Will Larson are great starting points. But do not fall into the trap of thinking you can learn management from books alone. It is a practice-based skill.
Have an honest conversation with your manager. Let them know you are interested in the management track. Ask what opportunities exist on your current team. Many managers are happy to give aspiring leaders more responsibility if they know you are interested.
If you have already made the jump, the first three months are critical.
Do not change anything immediately. Observe, listen, and learn. Understand the team's existing dynamics, processes, and pain points before trying to fix anything. Coming in with sweeping changes on day one signals that you do not respect what already exists.
Set up regular one-on-ones. Weekly, 30 minutes minimum, with every direct report. Use these to understand what each person is working on, what is blocking them, and what their career goals are. These meetings are the foundation of your relationship with each team member.
Build relationships across functions. Your effectiveness as a manager depends heavily on your relationships with product managers, designers, other engineering managers, and leadership. Invest time early in understanding their priorities and building trust.
Be transparent about your learning curve. Your team knows you are new to management. Pretending you have it all figured out will backfire. Instead, be open about the fact that you are learning, ask for feedback, and show that you are committed to getting better.
A few patterns show up repeatedly among first-time managers.
Staying too hands-on technically. It is tempting to keep coding because it feels productive and familiar. But every hour you spend writing code is an hour you are not spending on people development, team health, or strategic thinking. Some new managers stay involved in code reviews or architecture discussions, which is fine. But if you are spending more than 20 percent of your time on technical work, something is off.
Avoiding conflict. New managers often want to be liked, which leads to avoiding difficult conversations. This creates bigger problems down the line. Address issues early and directly, but with empathy.
Trying to make everyone happy. You cannot. Management involves tradeoffs, and sometimes those tradeoffs mean someone is disappointed. Your job is to make fair, well-reasoned decisions, not to achieve universal approval.
Not asking for help. Management can feel lonely, especially in the early days. Do not hesitate to lean on your own manager, peer managers, or external mentors. Practice sessions like mock interviews can also help if you are preparing for a management role at a new company, since manager interviews require demonstrating both technical and leadership competencies.
A question many people ask: what if I try management and do not like it? Can I go back?
The answer is generally yes, though it depends on the company. Many organizations allow managers to move back to IC roles, especially if they have maintained their technical skills. The experience of having managed a team often makes you a better IC as well, because you understand the broader context of how teams operate.
That said, the longer you stay in management, the harder it becomes to return to deep technical work. If you are unsure, give it at least a year before deciding. The first few months are rough for almost everyone, and it takes time for the role to start feeling natural.
One of the most rewarding aspects of moving into management is the opportunity to help others navigate their own careers. Whether it is mentoring junior engineers on your team or helping professionals outside your organization who are facing similar transitions, sharing what you have learned is one of the best ways to solidify your own understanding while making a real impact.
The IC to manager transition is not easy, but it is one of the most growth-intensive experiences in a tech career. If you approach it with humility, curiosity, and a genuine desire to help others succeed, you will find it deeply fulfilling.
