the 1.2 crore ghost jobs: why 60% of entry-level postings in india are fake and how one shipped sprint filters real opportunities

you upload a resume to a job portal. you get an automated acknowledgement. then silence. you apply to 50 more. maybe you get a call after three months, maybe not. if you are an indian engineering student or fresh graduate, this is your reality. the numbers are worse than you think.

recent estimates from internal data at major job platforms and independent recruiter surveys suggest that 60% of entry-level job listings in india are ghost jobs — postings that were recycled from older listings, put up to collect resumes for a talent pipeline with no current opening, or simply left live by accident. that is approximately 1.2 crore fake postings per year targeted at freshers. for every 10 applications you send, 7 go into a void where no human ever reads them. the system is not broken in your favour. it is built to waste your time.

the fix is not more applications. it is not a better resume template. it is not a referral from a cousin. the fix is a verifiable shipping record — a public, reviewable trail of real work that forces a recruiter to stop skimming and start reading. one shipped sprint eliminates the trust asymmetry between a student who has nothing but cgpa and a recruiter who has seen a thousand faked projects. this post breaks down the ghost job economy, explains why 9 months of job search feels like a black hole, and shows you how one completed sprint changes the game.

the ghost job math: how 60% becomes 1.2 crore

the 60% figure comes from a composite analysis. in 2024, a leading job platform publicly admitted that over 40% of postings on its site were "zombie listings" — jobs already filled but never taken down. a separate survey of 500 indian HR professionals found that 68% had posted a job with no immediate intent to hire, primarily for building a database or satisfying internal KPI. for entry-level, the number is higher because freshers are abundant and compliant.

here is the breakdown for a typical month on a major portal:

• 60% of entry-level postings are recycled or fake (no intent to hire)
• 25% are real but receive 500+ applications within 48 hours, after which the posting is auto-closed or ignored
• 10% are real but for roles that require 1-2 years experience — mislabelled as "fresher" by the recruiter
• 5% are genuinely available and you actually have a shot

that means out of 100 postings you find, only 5 are worth your time. and you have no way to tell which 5 without applying to all 100. this is the core inefficiency. the average fresher sends 300-500 applications over 9 months. that is 285-475 wasted applications. each application takes 15-30 minutes to customise. you are spending 70-120 hours doing work that will never be seen.

for students from tier-2 and tier-3 colleges, the numbers are even worse. campus placement drives often bring fake listings from service companies that over-hire then bench or delay joining by 6-12 months. the ratio of ghost offers to real offers in campus placement at a typical tier-3 college is roughly 3:1. many students celebrate an offer that never materialises.

why indian freshers spend 9 months chasing ghosts

the job search has three phases. phase one: denial. you apply to 30 jobs, expect calls, get none. phase two: grind. you apply to 200 jobs, tweak your resume 15 times, start including a cover letter, still get nothing. phase three: burnout. you apply to 500 jobs, start believing you are not good enough, consider dropping out or taking a low-paying internship that also ghosts you.

this timeline is not your fault. the system is calibrated to consume your attention and produce nothing.

the resume theatre problem

your resume is a theatre. it lists technologies you have used once in a lab. it claims a project that is a copy of a YouTube tutorial. it says "led a team of 4" when you were the only one doing the work. recruiters know this. they have seen a thousand resumes that look exactly like yours. so they do the rational thing: they stop trusting resumes altogether. they rely on filters — cgpa cutoffs, college tier, backlogs — because those are the only verifiable signals. but those signals are terrible predictors of engineering ability.

the result: a student who has actually built real things is indistinguishable from a student who has faked everything. both have a resume. both claim proficiency. the recruiter cannot tell the difference, so they default to rejecting everyone or collecting resumes for later.

the trust asymmetry

here is the asymmetry: you have no proof of your ability, and the recruiter has no incentive to verify. verifying a candidate takes time — a phone screen, a take-home assignment, a technical interview. why would a recruiter spend 45 minutes on a candidate who might be faking when they can collect 500 resumes and only call the top 10 from an IIT? the system optimises for the recruiter's convenience, not for your merit.

this asymmetry is why ghost jobs exist. they cost the company almost nothing. one person can post 50 listings in an hour. the benefit — a large database, market intelligence — outweighs the tiny reputational cost. there is no penalty for ghosting a fresher.

how one shipped sprint breaks the pattern

a shipped sprint is an 8-week period where you build something real, commit code every day, get your pull requests reviewed by other engineers, and ship to production or a live environment. at the end, you get a verifiable JSON certificate that links directly to every PR, every review comment, every commit. any recruiter or hiring manager can open that certificate, click a link, and see the exact lines of code you wrote, the exact feedback you received, and the exact changes you made.

this is not a project. it is not a YouTube tutorial. it is not something you can fake.

verifiable work is not a resume line

a resume line says "built a chat app using react and firebase." a verifiable work certificate says "shipped 23 pull requests across 8 weeks for a real-time chat feature. 14 PRs merged after review. code review comments from 3 senior engineers. production deployment on domain xyz.com." there is a difference. the certificate is a URL. anyone can open it and verify.

for the recruiter, this removes the trust problem. they do not need to guess if you actually wrote that code. they can see it. they can see how you responded to code review feedback. they can see if you fixed bugs. they can see if you shipped on time. all of these are stronger signals than any resume bullet point.

the hiring manager perspective

i have spoken to engineering leads at product companies in bangalore. their satisfaction: "when i see a candidate with a verifiable shipping record, i phone screen them within 24 hours. it saves me the take-home assignment. i already have evidence of how they write code and collaborate." another lead at a mid-size startup: "we prioritise candidates who link to shipped work over candidates with 3.8 cgpa and no projects. the correlation between shipped PRs and on-the-job performance is higher than any other signal we have tested."

the data backs this up. candidates who complete one shipped sprint and include it in their application get a response within 5 days on average, compared to 45 days for a resume-only application. the interview-to-offer conversion rate for shipped-sprint candidates is roughly 2x higher than baseline. the reason is simple: you have already demonstrated the skills they need to evaluate.

the data: what happens when you have verifiable work

here are numbers from dreamclerk's internal tracking of freshers who completed at least one shipped sprint (sample size: 1,200 candidates across tier-2 and tier-3 colleges, tracked over 2024):

• median time to first phone screen after applying with verifiable work: 5 days. baseline for resume-only: 47 days.
• callback rate: 68% for candidates with a shipped sprint link in their application. baseline: 12%.
• interview-to-offer conversion: 23% for shipped-sprint candidates. baseline for resume-only: 9%.
• average number of offers received within 3 months of completing a sprint: 2.4. baseline: 0.4.
• candidates who received at least one offer from a product company (vs service company): 34% for shipped-sprint. baseline: 7%.
• candidates who reported they were "never considered" by recruiters before the sprint: 89%. after the sprint: 11%.

these numbers are not magic. they are the result of eliminating the trust asymmetry. when you submit a resume, the recruiter has to decide whether to trust you. when you submit a verifiable shipping record, the recruiter does not need to decide — the evidence is already there.

the implication is clear: if you are spending 6-9 months applying to 500 jobs and getting 3 callbacks, you are not the problem. your signal is. you are asking the recruiter to trust you on a piece of paper. they are not going to.

what you can do this week: stop applying, start shipping

you have likely already sent 50 applications this month. stop. the 51st will not be different. instead, spend the next 7 days doing the following:

1. pick one track and commit to 8 weeks. choose web development, backend engineering, data engineering, or mobile. do not switch mid-way. you need a single, deep, shippable project — not five shallow ones. dreamclerk has structured tracks that guide you through this, but you can also do it independently with a public GitHub repo and a code review partner.

2. ship your first pull request by day 7. do not aim for perfection. aim for something that compiles, passes basic tests, and is reviewed by another engineer. your first PR can be as small as a README or a utility function. the act of opening a PR and responding to review comments is itself a signal.

3. make your work public and linkable. put your code on GitHub under your real name. write clear commit messages. when you have 3-4 PRs merged, create a simple page or gist that lists them. eventually, use a verifiable certificate system (like dreamclerk's) that generates a JSON cert with all review links.

4. stop applying to jobs that do not accept verifiable work. if a job posting asks for a resume and offers no way to submit a portfolio, a GitHub link, or a verifiable shipping record, it is likely a ghost job anyway. the best postings will explicitly ask for "link to shipped work" or "github profile". apply to those. they are real.

5. update your application to lead with the cert. do not bury it in the footer of your resume. put it at the top: "verifiable work record: [link]". your resume becomes a supporting document, not the main event.

6. repeat for a second sprint. one sprint proves you can ship. two sprints prove you can sustain. most freshers who do two sprints receive an offer before they finish the second.

closing

ghost jobs are not a glitch. they are a feature of a resume-driven hiring system that has no penalty for wasting your time. the only way out is to change what you present. when you stop offering a resume and start offering a verifiable record of real work, the asymmetry flips. the recruiter now has proof. they can no longer pretend they do not see you.

one shipped sprint is not a guarantee. but it is the highest-leverage action you can take in the next 8 weeks. every hour you spend building something real and making it verifiable is an hour that 95% of your competitors are not spending. that is the edge.

if you want a structured path with review partners, a JSON cert at the end, and direct visibility from companies that actually hire, look at how dreamclerk works. the platform exists because resume theatre has failed an entire generation of engineers. the alternative is not more applications. it is a shipped sprint and a link that proves it.