It is the most attempted switch in Indian tech, and the one most often attempted twice. The first attempt usually fails at the second interview round, and the candidate concludes that product companies are gatekeeping. Sometimes they are. More often the candidate walked in expecting their years to be counted and discovered they were being audited instead.
The short version: a service based to product based company move is not a domain change and it is not a function change. It is a change in what counts as evidence. Delivery discipline and client management transfer. Years, titles and the number of projects you have touched largely do not. Budget roughly 200 hours of preparation, ₹2.25 lakh of notice buyout on a typical structure, and the real possibility of being mapped one level below your current title.
What transfers, and what gets quietly discounted
Be honest with yourself about this before you start applying, because it determines what you spend the next six months doing.
Transfers well. Delivery under a deadline with real consequences. Client and stakeholder communication, which most product-company engineers are worse at than they think. Working inside a process rather than around it. Debugging systems you did not write, which is a genuinely rare skill and a services person's strongest card. Documentation habits.
Transfers partially. Technical breadth. Having touched eight technologies reads as adaptability in a services interview and as shallowness in a product one, and the difference is entirely in whether you can go three questions deep on any of them.
Barely transfers. Years on a résumé. Certifications. The number of clients. Team size managed, if the team was executing rather than deciding. And the service company experience discount everyone complains about is mostly this: five years of implementing someone else's decisions evidences execution, not judgement, and product interviews test judgement.
The uncomfortable framing, which is also the useful one: they are not discounting your experience because of your employer's logo. They are discounting it because the interview is designed to find decisions you made and owned, and a delivery role often does not generate many.
The interview is a different exam entirely
This is where most first attempts end. The rounds test things a services career does not systematically build.
Data structures and algorithms. Whether or not you think this is a good filter, it is the filter. It is trainable in a way that judgement is not, which is why it is the easiest gap to close and the most common reason people are rejected before anyone looks at their real skills.
System design. Not memorised architectures. The ability to hold requirements, name trade-offs and defend a choice while someone pushes back. If you have never chosen between two options and lived with the consequences, this round is where that shows.
Depth on your own résumé. The most predictive round and the one nobody prepares for. An interviewer picks one line from your CV and goes four questions deep. "You mention you improved performance; what was the bottleneck, how did you find it, what did you try that did not work, and what was the number before and after?" A services CV listing responsibilities collapses here. A CV listing decisions survives.
Behavioural rounds about ownership. Every question is a variant of "tell me about something you decided." Not something you delivered, something you decided.
Budget the preparation honestly
Assume 200 hours to be competitive, split roughly: 100 on DSA to a comfortable medium level, 60 on system design, 40 on rebuilding one project you can defend in depth. At eight hours a week that is about six months. At two hours a week it is two years, and you will forget the early material before you finish, which is exactly how people end up preparing indefinitely and never applying.
Two failure modes to avoid. Preparing forever set an application date before you start and hold it, because your first three interviews will teach you more about the gap than three more months of practice. And preparing only DSA, which gets you past the first round into a system design conversation you cannot hold.
If you want the structure rather than assembling it yourself, our technical training tracks are built backwards from live postings and end with two capstones designed to survive the depth round.
The 90-day notice problem
Longer notice periods are standard at large service firms, and they cause two concrete problems.
Offers expire. A product company with a role approved this quarter may not hold it for three months. This is the most common way a successful interview process still ends in nothing.
The buyout costs real money. Since the labour codes pushed basic pay toward 50% of CTC, buyouts computed on basic got more expensive. On an ₹18,00,000 CTC with basic at ₹75,000 a month, a three-month buyout is ₹2,25,000, up from about ₹1,35,000 under an older 30%-basic structure.
Three things that work. Ask the new employer to fund the buyout, in writing, before you resign; many will, and it is far more negotiable than base pay. Negotiate a staggered start where you join at 60 days with the balance bought out. And check your contract for a training bond or service agreement recovery clause if you joined as a fresher, because that is a separate liability from notice pay and people discover it at the worst moment.
The full mechanics of the transition Form 12B, the gratuity date, the provident fund transfer, the relieving letter are in switching jobs mid-year in India.
The level mapping conversation
Expect it. A five-year services title frequently maps to a lower product-company level, because levels there are defined by scope of ownership rather than by years served. It feels like an insult and it is usually just a different measuring instrument.
What not to do: fight for the title. What to do instead:
- Ask what the next level requires, specifically, and get it in writing. If nobody can articulate it, that is a red flag about the company, not about you.
- Negotiate an early review at six months rather than the annual cycle. This is the highest-value concession available and it costs them nothing today.
- Negotiate fixed pay rather than level. Pay and level are separate levers, and pay is often the more flexible one.
- Accept the level if the scope is real. A lower title with genuine ownership rebuilds your CV in eighteen months. A higher title with execution-only work leaves you in the same position, one switch later.
Three things to build before you apply
Not a checklist for the CV. Actual evidence.
One artefact with depth. A single project you built end to end and can defend for twenty minutes, including what you chose not to do. This is worth more than five tutorial projects, and it is the thing the depth round is looking for.
One system design you have actually reasoned about. Take something you worked on and write up how you would rebuild it at ten times the load, naming the trade-offs. Two pages. It converts a delivery story into a judgement story.
A résumé rewritten around ownership. Every bullet that begins with "responsible for" or "involved in" should be rewritten as a decision with a number attached. "Reduced regression cycle from two days to four hours by moving suite execution into CI" is the same work as "responsible for regression testing," aimed differently. A résumé for a product company is read for decisions; a services CV is usually written for scope.
When this switch is the wrong move
Worth saying, because the assumption that product is strictly better costs people real money.
If you like managing clients, scoping work and running delivery, the services track pays well for exactly that and product companies have fewer such roles. If you are two quarters from a promotion that would change your band, the maths of waiting often wins. If your five-year gratuity date is within a quarter, leaving early forfeits a little over ₹2 lakh on a ₹75,000 basic. And if the only reason for the switch is the pay differential, check the number properly against the structure: a headline CTC difference can shrink substantially once variable pay and provident fund treatment are compared, which we broke down in CTC vs in-hand salary.
The broader question of which variable you are actually changing the function, the domain, or both is worth settling first: change one variable, not both.
A six-month plan
- Month 1. Collect thirty postings for the exact role and level you want. Build the skill tally. Rewrite your résumé around decisions rather than responsibilities.
- Months 2–3. DSA, daily, small doses. Start the depth artefact in parallel. Read your contract for notice terms and bond clauses.
- Month 4. System design. Write up one system you know at ten times scale. Finish the artefact and publish it with the decision log.
- Month 5. Apply to fifteen roles in one wave, not one at a time. Three will interview you and teach you what is missing.
- Month 6. Second wave, corrected. Negotiate buyout funding and the review date before you resign, not after.
Fifteen applications in a wave matters. Sequential applications spread your rejections over a year and you learn nothing from each one in isolation.
Frequently asked questions
How do I switch from a service based to a product based company in India?
Close the DSA and system design gap, build one project you can defend in depth, rewrite your résumé around decisions rather than responsibilities, and apply in waves. Budget about 200 hours of preparation and expect the notice period to be the hardest logistical problem.
Is product company experience better than service company experience?
Different rather than better. Product work builds depth and ownership; services work builds delivery discipline, client skills and breadth. Product interviews happen to test the first set, which is why the switch is asymmetric in difficulty.
Will I get a pay cut moving to a product company?
Usually not on fixed pay, but you may be mapped a level lower than your title. Compare the fixed component and the actual variable payout rather than headline CTC, and negotiate an early review if the level is the sticking point.
How much DSA is enough for a product company interview?
Comfortable, unhurried medium-difficulty problems with clean reasoning out loud. Depth of pattern recognition beats volume of problems solved, and hard problems are a poor use of limited hours for most mid-level roles.
Can I buy out a 90-day notice period?
Usually yes, if the contract permits, and the cost is typically three months of basic pay around ₹2.25 lakh on an ₹18 lakh CTC with basic at half. Ask the new employer to fund it in writing before you resign.
Do product companies reject candidates for their current employer's name?
The rejection is almost always about demonstrated depth and ownership rather than the logo. The fix is evidence you can defend, which is why one deep artefact changes outcomes more than another year of experience does.