Three Tuesdays into being a manager, I closed my laptop at 5pm, walked to the kitchen, and realized I had not opened my code editor once that day. I had not opened it Monday either. I checked my calendar: 11 meetings on Monday, 9 on Tuesday. Two 1:1s I had to prep for. A performance-cycle calibration meeting where I argued for a teammate's promotion. A hiring debrief where I disagreed with a colleague about a candidate's leveling. A skip-level with my own manager. A 30-minute slot I had blocked for "focus time" that got steamrolled by a customer escalation. The work I had done was important. None of it had produced a line of code, a written design, or anything I would normally call output.
I sat with that for the rest of the week. I had been promoted into management the previous quarter, partly because the team needed it and partly because I had been told it was the next rung. Two months in, I knew I had agreed too quickly. I went back to my manager and asked to step back to IC. He said "give it six months, then decide". I gave it six months, decided I wanted to go back to IC anyway, and did. Three years later I crossed back to a different management role at a different company, on purpose this time, with a clear sense of what I was signing up for.
This article is what I learned across that round trip. It is not the universal truth about management vs IC. It is the specific differences in the two days, the trade I did not see coming, and the question that decided it for me both times.
What the two roles actually do, day-to-day
The pictures of the two roles in the abstract are easy. "Managers manage people; ICs build things." The reality is that the day-to-day mix is the part that decides whether the role suits you, and the abstract description does not capture it.
A real Tuesday for me as a senior IC, before management:
That day produced about 250 lines of merged code, two PR reviews, one debugged test, one finished feature in flight. I went home tired in the way that focused work is tiring.
A real Tuesday for me as a manager (the same skill level, same company, same team):
That day I touched five engineers' careers, one hiring decision, one architectural call, and zero lines of code. I went home tired in the way that emotional and conversational work is tiring, which is a different kind of tired. The first kind I could refresh from with a beer and an evening of reading. The second kind required a full evening of doing nothing and an undisturbed weekend.
This is not a complaint. It is the description of the job. The IC day has a tangible artifact and a clean stop point. The manager day has a thousand small inputs and outputs and no clean stop point. If you do not enjoy that texture of work, the calendar I just showed you will look exhausting, not energizing.
The trade I did not see coming
Here is the trade nobody told me about, and that I now warn anyone considering the jump.
As an IC, my day's success was largely under my control. If I focused, I shipped. If I was blocked, I unblocked myself or asked. The output was mine. The bad days came from external interruptions, ambiguous specs, or my own off-days, but the control was mine.
As a manager, my day's success was almost entirely not under my control. The team's output was the team's, not mine. If an engineer had a bad week, my week reflected that. If a project was blocked because two teams were arguing, my fix was a 2-hour conversation that might or might not work. If someone on my team was unhappy, my entire week was that conversation. The control over outcomes I had as an IC went to roughly zero. What replaced it was influence, which is slower, less reliable, and works at a different timescale.
This trade was the thing I had not internalized when I took the manager role the first time. I assumed I would be doing IC work plus some additional management work. The reality was that I was doing different work, on a different rhythm, with a different feedback loop, and I missed the IC rhythm so much that I went back. The second time I crossed, three years later, I knew that going in, and the same role felt completely different because I had stopped expecting it to feel like IC.
If you take one thing from this article: the management role is not IC plus some people stuff. It is a different job with a different reward shape. Going in expecting one thing and getting another is the most common reason I see managers be unhappy.
What is rewarding about each role, in my experience
For IC, the reward is craft. Building something that did not exist yesterday and works today. Solving a hard problem and seeing the metric move. Reading a piece of code two months later and recognizing the elegance of the solution. Closing a tab on a finished project. The reward loop is fast and tangible, and over a career it produces a body of work you can point at.
For management, the reward is people. Watching someone you mentored get promoted. Building a team that runs without you. Helping someone navigate a hard decision in their career. Being trusted with a problem that is not technical and getting through it. The reward loop is slow and intangible, but the cumulative effect over a few years is a track record of careers you have meaningfully helped.
The rewards are real on both sides. I have experienced both. The question is which one energizes you. The reward you find energizing is the one that pulls you through the unsexy parts of the job. If you do not find management's reward energizing, the unsexy parts (the difficult 1:1s, the political navigation, the writing of performance reviews on a Sunday) will grind you down.
The question that decided it for me
My manager, the second time I was considering the jump, asked me a question that decided it: "in five years, do you want to be the engineer the team turns to for the hardest technical problems, or the manager the team turns to when they don't know what to do?" Both are good answers. They are different lives.
My answer the first time, when I crossed too quickly, was "I think I want both". Wanting both is fine, but the role I was crossing into could only deliver one. The role I should have stayed in delivered the other one I cared about.
My answer the second time was "I want the manager one". I had spent three years deepening as a senior IC and I had hit the limit of how much I wanted that to be the entirety of the work. I wanted the second axis. I crossed, and the second time stuck.
If you cannot answer the question honestly, the safe move is to stay where you are. Crossing into management because the IC track "looks like a dead end" is the worst reason. Crossing because you genuinely want the work, even on the bad days, is the right reason.
Is the IC track really a dead end?
A quick aside on the most common reason I have heard people consider the cross: they think the IC track tops out at senior, and they see management as the only growth path.
In most companies I have worked at recently, this is not true. The IC ladder above senior is real: staff, principal, distinguished, sometimes more. Comp on the senior IC ladder caught up to and in some cases surpassed equivalent management comp around 2018-2020 and is still there. The notion that you have to manage to grow has not been accurate at most well-funded engineering organizations for several years now.
If you are at a company where the IC ladder genuinely caps out at senior and the only path to higher comp or scope is through management, the question is whether to change companies before changing tracks. I would seriously consider the move. A senior+ IC at a company with a real ladder is, in my experience, often happier than a low-experience manager at a company with no IC ladder.
What I wish I had asked before crossing the first time
In retrospect, here are the questions I wish I had answered honestly before crossing the first time. Each of them gets at a different aspect of the job that I underestimated.
- How do I feel after a day with seven hours of meetings? (Energized or drained?)
- When a teammate is unhappy with their project, do I find the conversation engaging or exhausting?
- Do I read books about leadership for fun, or does the genre bore me? (Honest answer for me: bored me at first.)
- When a project I am not on goes sideways, do I want to step in and help, or do I want to focus on my own work?
- Have I done some of the work-shaped versions of management already? (Tech-leading a project, mentoring multiple juniors, owning a hiring loop?)
The last question is the most useful one. Tech-leading without the title is the closest thing to a try-before-you-buy for management. If you have done a six-month tech-lead stint and you enjoyed it, the manager role will probably not surprise you. If you have not, it almost certainly will.
A path that worked for me the second time
When I crossed into management the second time and it stuck, the path was: I did a six-month tech-lead stint inside my IC role first. I owned the team's planning, ran the standups, did the project allocation, and did 1:1s with three of my teammates (without performance authority; my manager kept that part). At the end of that six months, I knew whether I liked the work, and my manager and I had real evidence about whether I was effective at it. The cross was a low-drama formal step at the end of an experiment that had already played out.
If your company supports this pattern (most do, even informally), I would strongly recommend it over the more common path of "get promoted to manager and figure it out on the job". The cost of finding out you do not like management while you are already responsible for a team's careers is real, and a tech-lead stint surfaces the same information without the irreversible commitment.
Pick the one whose bad days you can stomach
The last frame, the one that has stuck with me through both crossings, is that every job has bad days, and the question is which job's bad day you can stomach. The IC's bad day is a debugging session that lasts eight hours and ends in defeat, or a code review that flames the design. The manager's bad day is a teammate quitting on a Friday afternoon, or a calibration meeting where you fail to get a teammate the promotion they earned. Both are real, and both are weekly, depending on the team. You will have one or the other. Pick the one whose texture you can show up for on Monday morning, and the rest of the choice mostly works itself out.