Somewhere around five to eight years in, most people in India are offered a team. It arrives as a promotion — more money, a title with "Lead" or "Manager" in it, recognition that you are good at your job — and it is usually accepted in about four days.
That framing hides the actual decision. Management is not a more senior version of your current work. It is a different job, with different daily activities, a different definition of success, and a different set of things that make it satisfying. Some excellent engineers, analysts and designers are miserable in it. Some are far better at it than they were at the craft. Very few can predict which they will be without looking closely.
What actually changes
Your output becomes other people's output. You are no longer measured on what you produced. You are measured on what your team produced, which you influence indirectly, slowly, and through other people's decisions. For people who get their satisfaction from finishing things, this is the hardest adjustment and the one they are least warned about.
Your calendar stops being yours. One-to-ones, planning, reviews, hiring, cross-team coordination, escalations. A first-time Indian tech manager with a team of six typically has fifteen to twenty-five hours of meetings a week. The deep work you used to do in blocks now happens in fragments, or after hours, or not at all.
Your feedback loop lengthens from days to quarters. A shipped feature gives you a result on Friday. A hiring decision, a restructured process, a person you invested in — those tell you whether you were right in six months.
You inherit problems that have no clean solution. Two people who cannot work together. A rating cycle where you have five good performers and a curve that permits two top ratings. A layoff you did not decide and have to deliver. This is the part nobody previews, and it is a real part of the job.
Your craft decays. Slowly at first. Most managers who stay in the role for three years cannot return to hands-on work at their previous level without a period of catching up. Some accept this; some are blindsided by it.
What you gain
Stated fairly, because the honest case for management is strong:
- Leverage. A good manager makes six people meaningfully more effective, which is more impact than one person can produce directly.
- Scope. Decisions about what gets built, and by whom, sit on this side of the line.
- A clear ladder. In most Indian companies the management track has more rungs, more visible progression, and less ambiguity about how to advance.
- Building people. For a certain kind of person this is genuinely the most satisfying work available, and it does not exist on the IC track.
- Transferability. Management skills move between industries more easily than a specific technical stack does.
The money, honestly
Two claims circulate and both are half true.
At the first rung — team lead or engineering manager against senior engineer — pay in the Indian market is broadly comparable, often within 10–20%, and at product companies the senior IC is sometimes ahead. Taking a first management role for the money is usually a mistake, because the money is not the difference.
Higher up, the picture diverges. At most Indian companies — particularly services companies, banks, manufacturing and traditional enterprises — the ceiling on the management track is considerably higher, and beyond a point the only route to senior compensation is headcount. At product companies, MNC captives and well-funded startups, a genuine senior IC track exists with staff and principal levels that pay at or above the equivalent manager.
Which category your company falls into is not a matter of what the career-ladder document says. It is a matter of who actually holds the senior IC titles today. Which brings us to the test.
Does the senior IC track exist where you work?
Almost every company claims a dual ladder. Far fewer have one. Three questions settle it:
- Name the people at your company two levels above you on the IC track. If you cannot name any, the track is aspirational.
- Are they in the rooms where decisions get made? A principal engineer who is not consulted on direction has a title, not a track.
- What did the last three promotions at that level require, and how long did they take relative to the management-track equivalents?
If the answers are discouraging and you want to stay hands-on, the conclusion is not necessarily that you should take the management role. It may be that you should change companies. Product companies and captives are structurally better at this than services companies, and that is a real reason to move.
Testing the decision before committing
You can get a surprisingly good preview without accepting anything.
Mentor someone properly for two quarters. Not answering questions — owning whether they improve. This isolates the core of management better than any other single experience.
Run a project with three or four people on it. You will do planning, coordination, and the uncomfortable conversation when someone is behind. Notice how you feel on Friday.
Do the hiring work. Screen resumes, run interviews, sit in the debrief. A large part of a manager's job is this, and people are startled by how much of it there is.
Ask a manager you respect what their last week actually contained, hour by hour. Not the good version — the real one. Most will tell you, and the answer is frequently clarifying in the direction of "I do not want this".
If those experiences leave you energised, that is real evidence. If they leave you counting the hours until you can get back to your own work, that is also real evidence, and it is worth more than a title.
Choosing badly, and recovering
Two things worth saying plainly.
Declining a management offer is not career-limiting at a company with a real IC track, and it is at a company without one. Know which you are in before you decide, and if you decline, say what you do want instead — larger technical scope, architecture ownership, a specific problem — so it registers as ambition rather than reluctance.
Going back is possible and it is not a demotion, although it is often experienced as one. The people who make this move well tend to do it early, before their craft has decayed too far, and to be explicit about the reason: "I'm more useful and considerably happier building than coordinating." Companies that handle this badly exist; so do companies where it is routine.
If the return requires changing employers — which it sometimes does, because internal perception is stickier than internal policy — the framing is the same as any pivot. Changing careers mid-level without starting over covers how to write and explain that move.
The question that usually settles it
Not "do I want to be a manager", which is really a question about status and pay, but this:
Would you rather be the person who solved the hard problem, or the person whose team solved it?
Answer that honestly, in the language of what makes a good week for you, and the decision is usually already made. The people who thrive in management genuinely prefer the second answer — not out of selflessness, but because building the conditions for other people's work is the thing they find interesting.
There is no correct answer, only a correct fit. What is not defensible is drifting into management because it was offered and declining felt awkward, then spending four years in a job you never chose. That is the outcome worth avoiding, and thirty minutes of honest thought avoids it.
Whichever way you go, the skills that make the next step credible are the ones an employer can verify — which is a narrower set than most people assume. That is covered in upskilling that employers actually verify.