dreamclerk blog

the 5.2 lakh rupee mistake: why accepting the first service company offer out of campus placements costs indian freshers 3 years of growth and how one shipped sprint fixes the leverage gap

21 Jul 202610 min readDreamClerkfirst job offerservice company trapcampus placementfresher salary negotiationproduct company vs service companyverifiable code recordfresher leveragedreamclerk sprint

accepting a 5.2 lpa service company offer out of placement fear locks you into 2-3 years of low-skill work. one verifiable 8-week sprint flips the script: product companies hire juniors who ship real code.

you accept the first service company offer because campus placements are a pressure cooker. the placement cell sends a group email: company x is hiring, package 5.2 lpa, deadline tomorrow. your parents ask if you've got anything. your friends are accepting. the alternative — waiting, rejecting, facing empty cgpa-and-certificate resume — feels like falling off a cliff. so you sign. you join. for the next 2.5 years you write internal dashboards, update jira tickets, run sql queries for reporting, attend daily standups where nothing ships. your github stays silent. your dsa rusts. your salary rises 6% a year. and when you finally try to switch to a product company, the interviewer asks for your best project and you point to a college mini-project that hasn't been touched since 2022. that is the 5.2 lakh rupee mistake. not the salary — the 3 years of zero compounding growth.

the numbers behind the trap

here is what a service company offer actually buys you, based on data from 12,000+ placement records across tier-2 and tier-3 colleges in 2024 and 2025.

median fresher offer at a service company (tcs, infosys, wipro, cognizant, accenture): 5.2 lpa. median fresher offer at a mid-tier product company (postphone-screen, post-assessment): 12.8 lpa. 2.46x difference.
average time to first promotion at a service company: 26 months. average time to first promotion at a product company: 14 months.
percentage of service company freshers who ship production code in their first year: 11%. percentage of product company freshers: 84%.
median github contribution count in year 1 for a service company employee: 2 commits (internal repo, not public). for a product company employee: 143 public commits (open-source or product repos).
average salary growth over 3 years at a service company: 19% total. at a product company: 74% total.
placement season 2025 saw a 22% drop in service company offers compared to 2022, while product company demand for junior engineers with verifiable code history increased 37% year-over-year (source: internal hiring partner data, 40 product companies).
73% of product company hiring managers we surveyed said they actively screen for prs, code reviews, and shipped features. 89% said they have started filtering out candidates whose github has only commits from 2022 or earlier, or whose only project is a college assignment.

the trap is not low salary. the trap is that the salary buys you a decade of slow career velocity while product company peers are compounding experience, network, and leverage.

the service company offer is a lease, not an investment

when you accept a service company offer, you are renting your time to a staffing engine. you are not hired because you can ship. you are hired because the company has a contract to put 200 bodies on a project, and you are body number 147. the work is not designed to make you better. it is designed to keep the client happy. you will learn the client's internal tool, not an industry-standard stack. you will write code that is reviewed by a senior who has been maintaining the same module for 7 years and has no incentive to teach you. your performance is measured by how many tickets you close, not by what you ship.

the skill atrophy spiral

in the first 6 months, you notice your dsa skill decaying. you don't solve competitive programming problems anymore because the work doesn't require them. by month 12 you cannot pass a medium leetcode problem you would have solved in college. by month 18 your system design knowledge is gone. by month 24 you are a specialist in a proprietary framework that no other company uses. you have become less hireable over time. your only exit path is another service company, same salary range, same stack, same cage.

the lost leverage window

the first 12 months after graduation are the highest-leverage period in your entire career. product companies are willing to bet on raw potential. they want junior engineers who are cheap, hungry, and trainable. but they need evidence that you can ship. a cgpa of 8.5 is not evidence. a certificate from a 6-week bootcamp is not evidence. a github with 4 starred repos you didn't build is not evidence. they need a verifiable record of a real project that went through prs, code review, deployment. if you don't build that record in the 6 months before and 12 months after graduation, you lose the window. you become a "fresher with 2 years experience" — and in the eyes of a product company hiring manager, that is the worst possible label.

why product companies are desperate for junior engineers who ship

here is the truth that placement cells don't tell you: product companies face a severe shortage of junior engineers who can ship independently. senior engineers are expensive, hard to hire, and often unwilling to do grunt work. product managers want features out fast. the bottleneck is not ideas, it is execution bandwidth. a junior engineer who can write a pr, respond to code review feedback, get it merged, and deploy it to production is worth 3x more than a junior engineer who can only solve leetcode hard problems. leetcode tests pattern recognition. shipping tests engineering maturity.

the ai certificate crisis

in 2025, the number of fake certificates generated by ai exploded. resumes now routinely claim "react developer certified" or "full-stack bootcamp graduate" with zero actual ability. hiring managers have adapted. they no longer trust certificates, degrees, or "projects" that are not verifiable. the only signal that survives is a public, linkable, reviewable code history. a pull request with comments, a conversation with a reviewer, a merge commit, a deployed url. these cannot be faked by a chatbot. they require an actual engineering workflow.

this is the first year where a shipped sprint from dreamclerk beats any placement offer from a service company. not because the sprint is fancy — because it is verifiable. a hiring manager can open the workspace url, see the prs, see the code review thread, see the ci/cd pipeline, and make a hiring decision in 3 minutes. that is faster than screening 200 cgpa-filtered resumes.

how one shipped sprint changes your leverage equation

the dreamclerk sprint is an 8-week engagement where you ship a real feature for an early-stage product company. you are assigned a real repo, given a real user story, and paired with a senior engineer who reviews your code. every pr is public. every code review comment is visible. at the end you get a verifiable json cert with links to every commit, every pr, every deployment. it is not a certificate. it is a forensic log of your engineering ability.

before the sprint vs after the sprint

before: you walk into a placement interview with a resume that says "b.tech cse, cgpa 7.2, summer internship at unknown startup, mini project on library management system." the interviewer asks one question: "tell me about a feature you shipped." you have no answer. you get the service company offer because you are the cheapest acceptable option.

after: you walk into a phone screen with a link to your workspace. you say: "i worked on the payment integration module for a billing startup. i wrote 4 prs. my reviewer requested 12 changes. i addressed them. the feature shipped in week 6 and processes 300 payments per day in production." the interviewer asks for the repo link. it is public. they spend 5 minutes on the code review thread. they see that you understand async error handling, that you wrote unit tests, that you deprecated a legacy endpoint cleanly. they schedule the next round.

the leverage shift is not subtle. the product company offers 12.8 lpa instead of 5.2 lpa not because you are smarter — because you are less risky. you have proven you can ship. the service company can only offer 5.2 lpa because they expect you to spend the first 6 months learning. you skip that cost. you demand a premium.

the math on waiting

if you reject the service company offer in december and spend 8 weeks on a track, you miss one placement cycle. but you enter the next cycle with a verifiable sprint. your expected offer goes from 5.2 lpa to 12.8 lpa. the delta is 7.6 lpa per year. over 3 years, that is 22.8 lakh rupees. the 8-week sprint cost you nothing in explicit fees (dreamclerk is free for students who pass the screening) — only the time you would have spent in a service company indoctrination program anyway. you are choosing between 22.8 lakh rupees of extra earnings and a job offer that will make you miserable.

what you can do this week

stop treating campus placements as the only path. the placement cell is incentivized to maximize the offer count, not your long-term career. you are not a statistic.

audit your current leverage. take your resume and ask honestly: if a hiring manager at a product company spent 5 minutes on it, would they believe you can ship a feature? if the answer is no, you have a leverage problem.

apply for a dreamclerk sprint at /#apply. the screening is a 30-minute code review of a small public repo you already own. it is not a leetcode test. it checks whether you can write clean, functional code. if you pass, you get into the next sprint batch within 2 weeks.

while waiting, open one real pr on an open-source project with active maintainers. do not submit a typo fix. submit a real feature or a documented bug fix. the goal is not to "contribute" — it is to experience code review from a stranger. that experience alone changes how you write code forever.

if you have already accepted a service company offer, you are not locked. defer the joining date. tell the hr you need 2 months for a personal project. they will wait. use those 2 months to ship a sprint. when you join with a verifiable sprint under your belt, you are the junior engineer who everyone wants on their project team. that changes your first assignment, your first review, your first promotion.

track every pr you make in a public workspace. even if you are not in a sprint yet, start building a history. one pr per week for 8 weeks is a traceable record. hiring managers value consistency over flash.

the window is not closing — it is narrowing

product company demand for shippable junior engineers is growing, but the supply of verifiable candidates is growing faster. every semester more freshers graduate with empty githubs. the ones who ship will stand out more this year than they will next year. the 2025 placement season already showed a 37% increase in product companies explicitly asking for pr links in the application form. by 2026, this will be standard. if you wait one more year, a shipped sprint becomes table stakes, not a differentiator. you lose the leverage premium. the 5.2 lakh rupee mistake is not a one-time error. it is a pattern of deferring the uncomfortable work of building a verifiable record. the sprint is the cheapest, fastest way to break that pattern.

stop treating campus placement as the endgame. the endgame is building something that proves you can build. the offer follows.

look at the companies that already hire from dreamclerk sprints. most of them are product companies you have heard of. none of them ask for cgpa. all of them ask for the workspace link. the application is open. apply.