Career track
The Software Engineering track in India, and how it typically plays out.
Every company runs the ladder a little differently. This is the pattern most product-first Indian and global companies broadly follow, and where the real friction points show up.
One honest caveat before you read further. The bar and the compensation vary massively between top-tier product companies and mid-tier or services companies. Titles do not travel well across that boundary. A Senior Engineer at Google and a Senior Engineer at a mid-market services shop are not doing comparable work. If you plan to move between those worlds, expect a de-facto re-level.
The ladder, level by level
1. SDE-1 / Software Engineer
Entry level. Ship code within a scoped area, learn the codebase, join the on-call rotation.
- Who ends up here
- Fresh grads from tier-1 CS programs, bootcamp graduates with a solid portfolio, or self-taught engineers who cleared a systems + DSA interview.
- Typical day
- Picks up tickets from the sprint board, pairs with a senior on design questions, spends real time reading existing code before writing new code.
- Signal for the next level
- Consistent shipping without hand-holding, taking on the first small ownership of a component, catching production issues before an SDE-2 has to.
2. SDE-2 / Software Engineer II
First step where design decisions are yours. Owns a service or a meaningful module end to end.
- Who ends up here
- Engineers with 2 to 4 years of shipping experience who have already owned something in production and been on-call for it.
- Typical day
- Splits time between writing code, reviewing junior PRs, and participating in design discussions for the next quarter's work.
- Signal for the next level
- Owning a full system across its lifecycle, mentoring at least one SDE-1 through their first year, being the go-to person for at least one non-trivial technical area.
3. SDE-3 / Senior Engineer
Owns a bigger system or multiple related systems. Mentorship becomes a formal part of the job.
- Who ends up here
- Engineers with 4 to 7 years, ideally with prior exposure to production incidents that they debugged, fixed, and wrote a postmortem for.
- Typical day
- More architectural review, less individual coding. Sits in cross-team design meetings, unblocks juniors, still writes code for the hardest parts.
- Signal for the next level
- Cross-team influence without formal authority. Other teams start pinging you for input on their designs.
4. Staff Engineer
Technical leadership across multiple teams. Not a manager, but has the reach of one.
- Who ends up here
- Engineers with 7 to 12 years who have consistently shipped, mentored, and made technical calls that others agreed with in retrospect.
- Typical day
- Design docs, RFCs, unblocking teams, occasionally shipping a hard critical-path piece of code. Very few sprint tickets.
- Signal for the next level
- Company-wide impact. Systems you designed are load-bearing beyond your original team.
5. Principal Engineer
Company-wide technical direction. Rare enough that most Indian companies below Series C do not have one.
- Who ends up here
- Engineers with 12 or more years of consistently high-leverage work, usually specialists in a domain the company depends on.
- Typical day
- Mostly design, mostly writing, mostly meetings with founders and directors. The code they still write goes in for very specific reasons.
- Signal for the next level
- Distinguished-level roles are so rare in India that there is no reliable path. Ends up being about domain, company, and timing.
6. Manager track (parallel)
EM to Senior EM to Director. Not above or below the IC ladder, just a different craft.
- When to consider it
- If you find yourself already spending more time unblocking others than coding, and enjoy it. Not as a promotion when you feel plateaued as an IC.
- Compensation
- Broadly parallel to the IC ladder at the same level. EM matches SDE-3, Senior EM matches Staff, Director matches Principal.
- Reversibility
- Going back to IC from EM is harder in India than in the US, both culturally and structurally. Assume the switch is one-way and pick accordingly.
Approximate salary ranges
Cash compensation at tier-1 product companies in India. Stock and bonus are on top and vary widely. Services companies typically run 30 to 50 percent lower.
| Level | Range (LPA) |
|---|---|
| SDE-1 / Software Engineer | 15 to 30 LPA |
| SDE-2 / Software Engineer II | 30 to 55 LPA |
| SDE-3 / Senior Engineer | 55 to 90 LPA |
| Staff Engineer | 90 to 150 LPA |
| Principal Engineer | 150 to 250 LPA |
| Distinguished / Fellow | 250 LPA and up (often equity-heavy) |
| Engineering Manager | roughly parallel to SDE-3 through Principal |
Common pivots
SDE to PM
Common. Engineers with 3 to 6 years of experience often move into APM or PM roles at their own company or one they know well. Works best when you already own product decisions in practice.
SDE to Founding Engineer at a startup
Popular with SDE-2s and SDE-3s who want scope, equity, and speed. The tradeoff is worse compensation now for a shot at meaningful upside later.
SDE to ML Engineer / Data Scientist
Requires a real investment in ML theory and applied practice, not just cloud-course certificates. Easier if your company has an ML platform team you can rotate into.
SDE to Developer Advocate / DevRel
For engineers who genuinely like writing and speaking. Compensation is comparable to IC roles, career ladder is narrower.
Let Hiro pick the roles worth your Saturday.
Tell Hiro what stage of the ladder you are at, what you are ready to own next, and the kind of company that fits. Every Saturday morning you get a short list of 5 roles with an honest note on each. No firehose, no recruiter DMs, no scrolling.
Meet HiroCommon questions
Is SDE-1 the same everywhere in India?
The band is similar but the bar differs a lot. At the top-tier product companies (Google, Microsoft, Amazon, Adobe, Uber, Meta, Atlassian, Stripe) SDE-1 typically expects a strong CS foundation, 4 to 6 rounds of interviews, and comfort owning a small module inside a bigger system. At mid-tier product or services companies the same title often means executing well-scoped tickets under close supervision. Same label, different expectations.
How long does it take to go from SDE-1 to SDE-2 in India?
Two to three years is the honest range at most top-tier companies. Some fast-movers do it in 18 months if they take on ownership of a service or module end to end and can point at a concrete production impact. Others take four or five years because they never step outside the exact scope handed to them. The single biggest lever is scope, not tenure.
Is there a real ceiling as an IC in India, or do you have to become a manager?
There is no hard ceiling anymore. Staff and Principal roles exist at Google, Microsoft, Adobe, Amazon, Uber, Atlassian, Stripe, Cred, Razorpay, PhonePe and a handful of others in India. The compensation is often equivalent to or higher than the parallel manager track. That said, IC-track roles above Staff are genuinely rare, and if you want more of them you either need to be at a very large product company or specialize in an area with almost no market supply.
What is a realistic SDE salary in India?
For an SDE-2 with 3 to 5 years of experience at a tier-1 product company, cash compensation typically lands between 30 and 55 LPA, with stock and bonus on top. To land at the upper end you usually need at least two of: a tier-1 institute degree, prior tier-1 product-company experience, a strong systems or DSA interview performance, and negotiation nerve. Compensation at services companies for the same title runs 30 to 50 percent lower.
Should I stay a specialist or become a full-stack generalist?
Specialize once you have three or four years in. Deep specialization (distributed systems, ML infra, security, developer tools, iOS at a serious scale, front-end architecture) is what unlocks Staff and Principal. Full-stack breadth is valuable early because it lets you move between teams inside a company, but as roles get more senior, hiring decisions get made on depth, not breadth.