You joined TCS or Infosys as a fresher, got that ₹3.6 LPA package, and now it's been 2-3 years. Your friend at Razorpay just crossed ₹28 LPA. You're still on ₹6.5. And you're wondering — is it too late to switch to a product company? It's not. But the playbook is very specific, and most people get it wrong.
Let me be honest with you. The jump from a service company (TCS, Infosys, Wipro, Cognizant, Accenture, Capgemini) to a product company (Razorpay, Zepto, PhonePe, Swiggy, Flipkart, Atlassian, Adobe) is the single biggest career upgrade an Indian engineer can make in their first 5 years.
The salary jump? Often 2-4x. From ₹6 LPA to ₹22 LPA is not rare. From ₹9 LPA to ₹32 LPA happens every week on LinkedIn.
But here's the thing nobody tells you: recruiters at product companies have a quiet bias against service company resumes. Not because you're bad. Because 90% of TCS/Infosys engineers can't clear their interview loop. So they filter aggressively.
This post is the exact playbook to flip that bias. Let's get into it.
Why Product Companies Hesitate to Hire from Service Companies
Before you fix the problem, understand it.
Service companies optimize for billable hours, not engineering depth. You might have "3 years experience" on paper but only touched:
- A 10-year-old Java 8 codebase
- One internal tool with 50 users
- Manual testing dressed up as "QA automation"
- A ticket-based workflow where you fix bugs assigned by an offshore lead
Meanwhile, an SDE-2 at Razorpay with the same 3 years has:
- Shipped features to 5M+ users
- Owned a microservice end-to-end
- Done on-call rotations
- Made architecture decisions
When recruiters see "TCS, 3 years" on your resume, they assume the first profile. Your job is to prove you're the second.
The Skills You Actually Need (Not What LinkedIn Influencers Say)
I'm going to give you the real list. Not "learn 17 technologies." Three categories, focused.
Core Engineering (Non-negotiable)
- One strong language: Java (Spring Boot), Python (FastAPI/Django), Go, or Node.js. Pick one. Get deep.
- Data Structures & Algorithms: Yes, still. Around 150-200 LeetCode problems focused on Medium difficulty. Patterns matter more than count.
- System Design basics: How to design a URL shortener, a rate limiter, a chat app, a payment gateway. Even for SDE-1 roles at most product companies, you'll get a low-level design (LLD) round.
- SQL: Joins, window functions, indexing. Almost every product company tests this.
- Git, REST APIs, Docker basics: Bare minimum hygiene.
What Product Companies Specifically Look For
- Ownership stories: "I owned X, shipped Y, measured Z." Service company work is often shared — find your individual contribution and frame it.
- Production thinking: How do you handle a service going down? What's your debugging approach? What's an SLA?
- Cloud fundamentals: AWS basics — EC2, S3, RDS, Lambda. You don't need a cert. You need to know what these do.
Skip These (Despite the Hype)
- Blockchain (unless applying to a blockchain company)
- 12 different JS frameworks
- That AWS Solutions Architect cert (nice-to-have, not a tiebreaker)
- Kubernetes if you've never used it
The Resume Rewrite: From "Resource" to "Engineer"
This is where 70% of service company engineers lose the game before the interview even starts.
Here's a typical TCS resume line:
"Worked on enhancement and bug fixing of client application using Java, Spring, and Oracle."
Here's how it should read:
"Reduced API response time by 40% on the order-management service (8M monthly requests) by introducing Redis caching and optimizing N+1 query patterns in the Spring Boot codebase."
Notice the difference?
- Specific number (40%, 8M)
- Specific technology (Redis, Spring Boot)
- Specific problem (N+1 queries)
- Specific outcome (response time reduction)
The 3-Bullet Formula
For every project, write exactly 3 bullets:
- What you built / changed (with the tech stack)
- The measurable impact (latency, users, revenue, time saved)
- The hard problem you solved (the one thing that makes you sound like an engineer, not a ticket-closer)
If you can't find a measurable number, ask your team lead. Or estimate honestly. "Reduced manual effort by ~6 hours/week for the support team" is better than "improved efficiency."
Run your final resume through CareerLens to get an ATS score and see which keywords product company recruiters are filtering for — it catches stuff like missing "Spring Boot" when you only wrote "Spring."
The Side Project That Makes You Stand Out
Here's an uncomfortable truth: your TCS work probably won't impress a Zepto recruiter. NDAs, generic client work, no GitHub link to show.
So you need one solid side project. Not five. One.
What works:
- A small SaaS tool you actually deployed (even with 10 users)
- A clone of a real product with a non-trivial twist (a Razorpay-like payment flow with idempotency, a Swiggy clone with surge pricing logic)
- An open-source contribution to a library you actually use
What doesn't work:
- Todo apps
- Tutorial-following projects with zero deviation
- "E-commerce website" with three hardcoded products
Host it. Add a live demo link. Write a README that explains the trade-offs you made. Recruiters love trade-off discussions.
How to Get the Interview: The Referral Game
Cold-applying to product companies from a TCS email ID is rough. The conversion rate is brutal — often under 2%.
Referrals change everything. Here's how to actually get them.
The Outreach Template That Works
Don't message: "Hi sir, please refer me."
Try this instead on LinkedIn:
"Hi [Name], I saw you work on the payments team at Razorpay. I've been building a side project around idempotent payment flows and ran into the same retry-storm problem your engineering blog described last month. Quick question — did you handle this with a distributed lock or with a state machine? Also, are you open to referring for the SDE-2 role (ID: 4421)? Happy to share my resume."
This works because:
- You showed you read their content
- You asked a smart technical question
- You named the specific role
- You made it easy to say yes
Send 20-30 of these per week. Expect 3-5 referrals. That's enough.
Salary Expectations: What You Can Actually Get
Here's a realistic 2026 snapshot of what TCS/Infosys engineers are getting when they switch:
| Current Role (Service) | Current CTC | Target Product Co. Role | Realistic New CTC | |---|---|---|---| | 1.5 yr exp, System Engineer | ₹4.5 LPA | SDE-1 | ₹12-18 LPA | | 2-3 yr exp, Sr. System Engineer | ₹6-8 LPA | SDE-1 / SDE-2 | ₹18-26 LPA | | 3-5 yr exp, Tech Lead (service) | ₹9-13 LPA | SDE-2 | ₹26-38 LPA | | 5-7 yr exp, Module Lead | ₹14-18 LPA | SDE-2 / SDE-3 | ₹35-55 LPA |
Two warnings:
-
Don't quote your current CTC. Quote your expected CTC based on market. Product companies don't anchor to your TCS package — they anchor to their internal band. If you say "I make ₹7 LPA," they'll offer ₹13. If you say "I'm looking at ₹22 LPA based on my interview performance," they'll offer ₹20.
-
Negotiate the variable + stocks. Product companies often have ESOPs or RSUs. A ₹28 LPA offer with ₹5L stocks is real money over 4 years. Service companies almost never give equity.
You can sanity-check offers on CareerLens to see role-specific bands at companies like Razorpay, Swiggy, and PhonePe before you accept.
The Interview Process: What to Expect
Most product companies follow some version of this loop:
- Online Assessment — 2 DSA questions, 90 minutes. HackerRank or CodeSignal.
- DSA Round 1 — One Medium + one Hard, live coding. 60 minutes.
- DSA Round 2 — Same format. Sometimes optional.
- Low-Level Design (LLD) — Design a parking lot, splitwise, BookMyShow. OOP-heavy.
- High-Level Design (HLD) — Only for 3+ years exp. Design Instagram, design Uber.
- Hiring Manager / Behavioral — "Tell me about a conflict," "Why are you leaving?"
- Bar Raiser / Director Round — Culture fit + curveball.
For a service-to-product transition with 2-3 years exp, expect 4-5 rounds. Total time from first call to offer: 3-6 weeks.
The One Behavioral Question You Must Prepare
"Why do you want to leave [TCS/Infosys]?"
Wrong answer: "Because they pay less and the work is boring."
Right answer: "I've gained strong fundamentals in [X domain] over the past 3 years, but I want to work on systems that I own end-to-end with direct user impact. I've been following [company]'s engineering blog, especially the post on [topic], and the kind of problems your team works on is exactly the depth I'm looking for."
Practice this until it sounds natural, not rehearsed.
The Timeline: Realistic Roadmap
Here's how a typical service-to-product switch looks across 6 months:
- Month 1: Audit skills, pick stack, start LeetCode (75 problems). Rewrite resume.
- Month 2: 75 more LeetCode problems. Start side project. Read system design basics (Designing Data-Intensive Applications, or Hello Interview free content).
- Month 3: Finish side project. Mock interviews on Pramp / with friends. Apply to lower-tier product companies first (warm-up).
- Month 4: Start LinkedIn outreach. Apply broadly. Target 5-10 applications/week.
- Month 5: Interview loops in full swing. Expect 1-2 rejections before you get traction.
- Month 6: Final rounds, offers, negotiation, resignation.
Don't rush this. People who try to switch in 4 weeks usually fail and burn out.
Common Mistakes That Kill Your Switch
- Applying before you're ready. You only get one shot at most companies. They have a 6-12 month cooldown after rejection. Don't apply to Razorpay in week 3.
- Quitting before you have an offer. Never. The "I'll focus on prep full-time" plan sounds great until month 4 with no income.
- Ignoring smaller product companies. Series B/C startups (Yellow.ai, Hasura, Rippling India, Postman, Browserstack) pay great and have faster interview loops than FAANG.
- Bad-mouthing your current company in interviews. Even if you hate it. Stay neutral and forward-looking.
- Negotiating poorly. Always counter the first offer. Always. Even a 10-15% bump on the initial number is normal.
FAQ
Q: I have 5 years at Infosys but only worked on legacy mainframes. Is it too late? No, but you'll need 4-6 months of focused upskilling on a modern stack. Aim for SDE-1 or SDE-2 roles, not Senior. Don't anchor on your 5 years — anchor on the skills you'll demonstrate in interviews.
Q: Do product companies care about my college tier? For freshers, yes — heavily. For 2+ years experienced engineers, almost no. Your interview performance and current work matter 10x more than whether you went to a Tier-3 college.
Q: Should I do a Master's or Scaler/MaaNG-prep course first? Skip the Master's unless you want to relocate abroad. Paid prep courses can help if you lack discipline — but the free content (Striver's DSA sheet, NeetCode, Hello Interview) is genuinely enough. Don't spend ₹1.5L if you can spend 6 months and ₹0.
Q: What if my notice period is 90 days? Will product companies wait? Most will, especially at SDE-2 level and above. Mention it upfront. Some companies offer buyout (they pay your notice period salary). Negotiate this — it's normal.
Bottom Line
- The TCS/Infosys to product company switch is absolutely doable — thousands make it every year. The path is well-paved, you just have to walk it.
- Focus on one strong stack, 150-200 LeetCode problems, one solid side project, and a rewritten resume. That's the core.
- Referrals beat cold applications 5-to-1. Spend equal time on outreach as on prep.
- Expect 2-4x salary jumps, but only if you negotiate properly. Don't anchor to your current CTC.
- Give yourself 6 months, not 6 weeks. The people who succeed treat this like a serious project, not a weekend side quest.
You're not stuck. You just need the right playbook. Now you have it.