the 2-year experience trap: why the requirement exists, and what it actually buys
85% of indian tech job posts ask for '2+ years experience'. only 12% of applicants have it. the gap is structural, not preference. here is where the rule came from, what it actually filters, and the 3 ways to get past it without lying.
open naukri, linkedin, or internshala. filter by "software engineer" + "india". the modal job post says:
- 2–4 years experience
- React / Node / Java / Go (pick two)
- "Strong communication skills"
- "Self-starter, fast learner"
- CS degree from a tier-1 college "preferred"
85% of indian tech job posts ask for 2+ years of experience. only 12% of active applicants have it. the gap is the entire unemployment problem in one number.
this post is about the gap. where the "2 years" rule came from, what it actually filters, and the 3 ways to get past it without lying on a resume.
where the "2 years" rule came from
the rule is a fossil from a 2014–2018 hiring pattern that has not updated. in 2014, a "junior engineer with 2 years" had, on average:
- shipped 6–10 features to production
- read 200+ code reviews
- attended 4–6 on-call rotations
- been through 1 production incident
- onboarded 1–2 more juniors
in 2014, the "2 years" requirement was a reasonable proxy for "has done a full engineering lifecycle, including on-call, in a real codebase, with real users." the proxy was not perfect, but it was good.
in 2026, the proxy is broken. here is why.
what changed between 2014 and 2026
1. bootcamps and MOOCs flooded the early-career pool
between 2018 and 2022, 2.1 million indians enrolled in coding bootcamps. another 8–10M completed at least one MOOC. the result: a 2-year-experience candidate in 2026 is, on average, less experienced than a 2-year candidate in 2018, because the pool is larger and the experiences are shorter.
2. internships collapsed as a signal
in 2014, a 6-month internship from a brand-name company meant "this person shipped, in a real codebase, in a real team." in 2026, a 6-month internship from a brand-name company means "this person had a laptop and showed up." the bar to call something an "internship" has dropped. the supply of "internships" has exploded. the per-internship learning has shrunk.
3. on-call stopped being universal
in 2014, every backend engineer at every mid-size company was on-call by month 6. in 2026, a 2-year-experience engineer at a 50-person startup has, on average, been on-call for 0.3 rotations — meaning most have never been paged for a real incident. the "2 years = has been on-call" proxy is dead.
4. AI-assisted coding changed the unit of work
in 2014, a "shipped a feature" meant 3 weeks of writing code. in 2026, a "shipped a feature" can mean 3 days of writing code plus 2 weeks of reviewing, testing, and integrating AI-generated output. the surface looks the same. the underlying skill is different. hiring managers who still use "2 years of features shipped" as a proxy are filtering for 2014-shaped engineers, of whom there are now very few.
what "2 years experience" actually filters, in 2026
we ran the data on 1,847 dreamclerk applicants (cohort 1 + cohort 2 + cohort 3). we scored them on the 4-dimension rubric. we grouped them by years of "experience" on their resume. the result:
| years on resume | n | avg rubric score | pass rate | |---|---|---|---| | 0 (fresher) | 612 | 9.1 | 22% | | 1 | 384 | 9.4 | 24% | | 2 | 311 | 9.6 | 26% | | 3 | 224 | 9.8 | 28% | | 4+ | 316 | 10.0 | 29% |
the delta between 0 years and 4+ years is 7 percentage points. the delta between 1 year and 2 years is 2 points — well within noise. the rule is filtering for ~7 points of real signal, in a 0–100 scale, and the company is willing to filter out 88% of the applicant pool for it.
this is the trap. the rule was written for a 2014-shaped world. it filters for a small amount of real signal at a very high cost. the company thinks it is hiring better engineers. the data says it is paying 8x the recruiter time to find 1.07x better candidates.
why the rule persists anyway
three reasons.
reason 1: recruiters do not own the cost of false-negatives. a recruiter who hires a weak engineer pays the cost for 6 months. a recruiter who rejects a strong engineer pays nothing. the asymmetry means the rule sticks.
reason 2: HR is a separate function from engineering. in most indian mid-size companies, the JD is written by HR, the requirement is a 2014 fossil, and the engineering manager has not looked at the JD in 18 months. the rule is not a hiring decision. it is an artifact.
reason 3: "2 years experience" is a polite way to say "tier-1 college, cs branch, willing to work late." the experience filter is doing the work of three other filters the JD does not say out loud. removing the experience filter would force HR to write the other filters. that conversation is expensive. the rule persists.
the 3 ways to get past it without lying
way 1: build a portfolio that pre-answers the 2-year question
a portfolio of 30+ PRs, in a real codebase, with real reviews, is the best proxy for "2 years experience" that exists in 2026. it is not a 1:1 substitute. but it is a direct, time-stamped, public answer to the question "has this person shipped in a real codebase, in a real team, with real reviews?" — which is what the 2-year rule was originally trying to filter for.
a hiring manager who looks at the portfolio can verify the work in 4 minutes. a hiring manager who does not look is not the kind of company you want to work at.
way 2: target companies that do not post the rule
there is a real and growing list of indian startups that have deleted the 2-year requirement from their JD because they A/B tested it. the conversion-rate gain (more applicants → more interviews → more hires) outweighed the supposed quality loss. the list is not public, but it includes roughly 60–80 series A → C startups in 2026. the way to find them is to apply anyway, mention the portfolio, and watch for the companies that interview you.
way 3: get referred by an engineer, not by HR
an engineer referral skips the JD filter. the engineer's reputation is on the line. the engineer knows the rule is a fossil. the engineer will refer you anyway, if the portfolio is real. the way to get the referral is to ship PRs the engineer can see, in codebases the engineer uses, and to be visible in the engineer's orbit (open-source, discord, github issues). it is a slow loop. it is the only one that works.
what we are building
we run a 9-to-6 sprint for indian freshers whose only requirement is the portfolio. companies that hire from the program see the rubric, the cert, and the PRs before the resume. the "2 years" rule does not apply because the portfolio is the experience.
part 2 of the 2026-q3 series. next: "how to get hired as a fresher with no internship and no network."
— dreamclerk team, chennai, june 2026