Somewhere around year five or six of an engineering career, a question starts showing up quietly. "Should I become a manager?" Sometimes it's prompted by a manager who mentions it in a one on one. Sometimes it comes from watching a peer take the leap. Sometimes it's pure ambition. However it shows up, it's worth treating it carefully, because the move from individual contributor to manager isn't a promotion. It's a job change.
Most people realize that too late. They accept the title, enjoy the compensation bump, and then spend six months wondering why they're so tired and why none of their old skills feel useful anymore. The shift is real, and it's worth doing on purpose.
Here are the signs you're genuinely ready, the signs you're not, and how to prepare properly.
You find yourself more interested in outcomes than code. This is the most reliable signal of all. When you start caring more about whether the team shipped the right thing than whether the PR you opened has elegant abstractions, something has shifted. That shift is the seed of managerial thinking.
You already do the work informally. You mentor junior engineers without being asked. You help your manager shape the roadmap. You unblock people across teams. You run the standup when your manager is out. If a quarter of your current impact comes from multiplying others, you're already doing a slice of the job.
You can sit with ambiguity without panicking. ICs often operate in well defined problem spaces. Managers operate in unclear ones. If your first instinct when something gets messy is to force clarity by making decisions with incomplete information, that's manager wiring.
You care about people as people, not just as resources. This sounds obvious, but the difference is enormous. The managers who thrive are the ones who genuinely want to see the people on their team grow, even when that means they eventually leave for bigger roles elsewhere.
You're okay with indirect impact. ICs get a dopamine hit from shipping. Managers rarely get that. Their satisfaction is slower, quieter, and dependent on other people doing the thing. If you need the fast feedback loop of direct work, the switch will be painful.
You want to be a manager because it's the next step. In most companies, there's a dual ladder. Staff and Principal engineer paths exist for a reason. If you're looking at management because you think it's the only way up, stop and look again. The IC path often pays as well or better at senior levels, and it's a much better fit for people who love the craft.
You want the title, not the work. The title is one percent of the job. The other ninety nine percent is difficult conversations, planning cycles, performance management, and being the last line of defense when things break.
You dread one on ones. If the idea of back to back meetings with individuals makes you want to hide, the job will grind you down.
You avoid conflict. Managers have to hold difficult positions, give hard feedback, push back on leadership, and sometimes fire people. If conflict avoidance is your operating mode, it becomes a serious liability.
You haven't been a senior IC yet. Becoming a manager before you've earned the technical respect of your team makes the job significantly harder. Not impossible, but harder. You'll be managing people on work you haven't fully done yourself, and that gap shows up quickly.
The worst time to start learning management is on day one. The best time is six to twelve months before you step into the role. Here's what to actually do.
Shadow your manager. Ask them what's on their mind each week. Ask how they decided a promotion case. Ask what they'd do differently about the last reorg. You'll learn more in three months of this than in a year of books.
Lead without authority. Volunteer for cross team initiatives. Run a hiring loop. Mentor two or three junior engineers formally. Drive a postmortem. These are real management reps without the title.
Have honest conversations about your readiness. Your current manager is the first source, but a second opinion from someone outside your company often reveals blind spots. Working with an experienced engineering manager mentor who has made this transition and watched dozens of others make it can help you see both the opportunities and the warning signs in your situation.
Study the failure modes, not the success stories. Read about managers who burned out, who lost their teams, who regretted the switch. Every one of those stories contains a lesson that the celebratory ones don't.
Whether you're going for an internal promotion or an external move, the interview process for first time managers is very different from an IC loop. You'll face people scenarios, difficult conversation roleplays, strategy questions, and tradeoffs between short term and long term outcomes.
A dedicated first time manager prep track, paired with realistic technical leadership interview practice, is the fastest way to sharpen this specific muscle. A structured IC to manager transition plan that covers the months before, during, and after the switch is even better.
Once you have the role, the first ninety days are where most first time managers either set themselves up for success or create debts they'll carry for years.
Resist the urge to change things fast. Spend the first month listening, really listening. Every one on one is an interview. Every roadmap review is a chance to understand what matters to the team versus what matters to leadership.
Do less IC work than you think you should. The hardest habit to break is reaching for the keyboard when a bug appears. Your job now is to make the team faster, not to be the fastest person on it.
Get a coach. The single highest leverage investment a new manager can make is ongoing engineering manager coaching with someone who has run teams at the level you aspire to. What takes a year alone takes three months with the right guide.
If you do make the switch and it works, you'll eventually become the person a younger engineer looks at and asks the same question you once asked. That's one of the best parts of the job, and it's part of why platforms like BeTopTen encourage experienced engineering leaders to become a mentor for the next generation, so fewer people stumble into this transition blind.
Being a manager is not a better version of being an engineer. It's a different thing. Some of the best engineers out there should never be managers. Some of the best managers were average engineers. Figure out which kind of career you actually want, and the decision becomes easier to live with for the long haul.
How a Mentor Can Help You Stop Drowning in Stressful Workdays.
How a Mentor Can Help You Switch From Developer to Engineering Manager.
What Your Mentor Would Tell You Before a System Design Interview.