You are looking at a posting titled “Junior Analyst.” The requirements say two to three years of experience. You have none, so you close the tab and move on.
That instinct costs freshers more opportunities than any skill gap does. Job descriptions in India are frequently written by copying an old one, or by a hiring manager listing everything they would ideally like rather than what they will actually hold out for. The number in the requirements is a preference far more often than it is a gate.
This is not an argument for applying to senior roles you cannot do. It is an argument for treating “2+ years” on an entry-level listing as a soft signal, and spending your effort on the things that genuinely move a fresher application forward.
Work out what actually counts as experience
Most freshers have more than they list, because they apply an unnecessarily narrow definition. All of the following are legitimate experience, and all belong on your resume:
- Internships, paid or unpaid, however short. A six-week internship where you shipped something real is worth more than a six-month one where you watched.
- Freelance work. Three logos for a local restaurant, a WordPress site for your uncle's clinic, editing someone's thesis for a fee. This is client work. Name the deliverable and the outcome.
- Substantial college projects, especially anything with a user other than your evaluator.
- Open-source contributions, even small merged pull requests. A merged PR is a public record of your code passing someone else's review, which is rarer on a fresher resume than you might think.
- Running something. A college fest budget, a 150-member society, a campus ambassador programme with targets you hit. Coordination and accountability transfer directly.
- Family business work. Managing inventory, handling GST filings, running the shop's accounts. Many candidates leave this off out of embarrassment. It is often the most operationally real thing on the page.
- Tutoring and teaching. Explaining hard things to people who do not want to hear them is a professional skill.
Write these up the way you would write up a job: what you did, at what scale, what changed. Do not apologise for them and do not label them “just” anything.
Build one thing that is real
The fastest way to close an experience gap is to produce evidence that does not depend on anyone having employed you.
One genuine project beats a certificate stack, and the distinguishing feature of a genuine project is that it has users, or data, or a constraint that was not handed to you. A to-do app from a tutorial is not evidence. A scraper that tracks fee changes across the twenty colleges you applied to, with a small dashboard, is — because you chose the problem, hit real messy data, and made decisions.
Aim for something you can talk about for fifteen minutes, covering:
- Why you built it and who it was for.
- One decision you made and the alternative you rejected.
- One thing that broke, and how you found out why.
- What you would do differently now.
That last set of answers is what interviewers are actually probing for, and it is the part that cannot be borrowed.
Non-technical roles have the same logic. Marketing: run a small campaign for a local business and report the numbers. Finance: build a full three-statement model for a listed company and write the one-page thesis. Design: redesign a real Indian app's worst flow and document your reasoning, not just the screens. HR: nothing stops you from writing a proper JD and a structured interview scorecard for a role you have studied.
Twenty considered applications, not two hundred sprayed ones
Mass applying feels productive because it produces volume, and volume is the only thing you can measure while you are waiting. But the response rate on an untailored application to a role you barely match is close enough to zero that two hundred of them is still roughly nothing.
A better ratio is twenty to thirty applications a week, where each one gets ten minutes: read the posting properly, reorder your resume bullets so the relevant ones are at the top, match the vocabulary, and — if there is any human name attached — send one short note.
Keep a simple tracker. Company, role, date applied, source, contact, status. Not for motivation, but because after four weeks it will tell you something you cannot otherwise see: which channels produce replies. Nearly everyone finds their replies are concentrated in one or two, and then they can stop spending time on the others.
Referrals, and how to ask a stranger
A referred application is read. That is the whole advantage, and it is enormous. You do not need to know the person.
Find someone in a role adjacent to the one you want at that company — not the HR head, not the CEO. Someone two to four years in, who remembers being where you are and has some standing. Then send something that takes them under thirty seconds to read and one minute to act on:
Hi Priya — I'm applying for the Junior Data Analyst role at Acme (JR-2481). I'm a 2026 B.Sc. Statistics grad; last month I built a dashboard tracking Bengaluru water tanker prices from municipal data, which is the closest thing I have to the work in the JD — repo here. Would you be willing to refer me, or tell me if I'm not a fit yet? Either answer is genuinely useful. Resume attached.
Why this works, when almost nothing else does:
- It names the exact role and requisition number, so there is nothing to look up.
- It offers one piece of concrete evidence, not a self-assessment.
- It makes a single, specific request and explicitly permits a no. That removes the social cost of replying, which is the actual reason most such messages are ignored.
- It is short. Nobody owes you five paragraphs of attention.
Send ten of these a week. Expect one or two replies, and do not follow up more than once — after seven days, one line, then let it go.
Your own batch is an underrated source. Seniors from your college who graduated one or two years ago are the single most likely group to help you, and the least likely to be asked.
Certifications: which ones are worth the money
Certificates have a specific and limited job. They get you past a keyword filter and they signal that you have covered a defined syllabus. They do not substitute for evidence of work, and recruiters discount them heavily because they know how little some of them require.
Worth considering, if the target role genuinely asks for them:
- Vendor certifications that are actually examined and named in postings — cloud platform associate-level credentials, for instance, in infrastructure roles.
- Regulated qualifications where the certificate is the requirement: NISM modules for capital markets roles, CA or CS intermediate stages, actuarial papers.
Rarely worth the money:
- Expensive “placement guarantee” bootcamps. Read the guarantee's fine print carefully — the placement promise is frequently conditional in ways that make it unenforceable, and some are funded by an income-share or loan agreement you sign on day one.
- Any course whose completion needs nothing but watching the videos. The market knows.
If you have limited money, spend it on the exam that is externally invigilated rather than the course that is not.
Answering the question you will always be asked
“We were looking for someone with experience. Why should we consider you?”
The failing answers are the two obvious ones: apologising, or overclaiming. What works is acknowledging the gap plainly and then redirecting to evidence.
You're right that I haven't done this in a paid role. What I can point to is the inventory tool I built for my father's distribution business — it's been running fourteen months and cut stock-out incidents from about six a month to one. I know that's smaller than what you deal with. But the reason I'm confident is that I've already had to debug something other people depended on.
Concede the point, then move to something specific and true. Interviewers are not looking for you to pretend the gap is not there — they are checking whether you can be honest about a weakness without collapsing.
The weeks in between
Job hunting as a fresher involves long stretches of no news, and the damage that does to your interviewing is real: by week six people start sounding defeated on calls, which reads as a lack of ability.
Two things help concretely.
Keep building. A project you shipped last month gives you something current to talk about and keeps the conversation about your work rather than your unemployment.
Debrief every rejection you can. When you are turned down after an interview, reply once, briefly, and ask what would have made the difference. Most will not answer. Perhaps one in five will, and that feedback is more accurate than anything you can guess at — several candidates discover their problem was something mechanical, like rambling past the four-minute mark on every answer, which is fixable in an afternoon once someone tells you.
Your first job is disproportionately hard to get and then rapidly stops mattering. Two years in, nobody will ask how you got it — only what you did once you were there.