Mention "free internship" to a student and the usual reaction is suspicion. With fair reason: fake internship offers that ask for a "registration fee", "training charge" or "certificate fee" are everywhere.
But the scam and the unpaid internship are two different things, and lumping them together hurts freshers. It pushes them away from real opportunities at small firms that can offer mentoring and real project work, just not a stipend. To understand when a free internship is genuine, it helps to start somewhere most articles skip: the employer's side of the table.
First, a clear line: "free" vs "fee"
There are really three things being sold under the word "internship":
- A free internship doesn't pay you, but doesn't charge you either. You trade time and effort for experience, mentoring and proof of work. Whether that's a fair trade depends on what you actually get.
- Paid training labelled as an internship. You pay a training institute, learn in a batch, build a classroom project and receive an "internship certificate". The training may be good, but it isn't an internship.
- A scam asks you to pay for a job or internship that doesn't exist. Registration fees, "placement assurance" charges, kit or certificate fees with nothing real behind them.
The grey zone: training sold as an "internship"
This is the version freshers run into most often. A training institute advertises a "paid internship programme" or "internship with certificate" for a fee. In practice it is a course: you attend sessions, work on a sample project with other trainees, and get a certificate that says "intern".
There is nothing wrong with paying for good training. Structured training is often exactly what a fresher needs, and many institutes do it well. The problem is the label.
Why the label matters
- An internship means working for an employer. You contribute to a real business, inside a real team, under someone who would hire people like you. A training batch, however good, is a classroom.
- Recruiters know the difference. A hiring manager who sees "Intern, XYZ Training Institute" on a CV and finds out it was a paid course will discount it, and may start doubting everything else on the CV.
- It blurs the line with outright scams. Once "pay for an internship" sounds normal, the fake offers become harder to spot.
How to tell which one you're looking at
| Real internship | Training sold as an internship |
|---|---|
| The company pays you, or at least doesn't charge you | You pay the fee |
| You work on the company's own product or client work | You build a sample project, often the same one as the rest of the batch |
| One mentor, small number of interns | Batches of 20, 50 or 100 "interns" |
| Selected through an interview | Anyone who pays is enrolled |
| Certificate from the company that employed you | Certificate from the institute that trained you |
What to do if you've done one: Put it on your CV honestly, under Training or Projects rather than Work Experience. Lead with what you built and what you can do. Honest training, well described, is an asset. Training dressed up as experience becomes a liability the moment an interviewer asks a follow-up question.
Good training paired with real placement is far more valuable than a certificate with the word "internship" on it.
Why most employers resist hiring interns
For most startups and small IT firms, the real reasons for not hiring interns are not about the stipend, but about the practical issues in running an internship.
1. Interns cost senior time, not just money
The biggest cost of an intern isn't the stipend. It's the hours a senior developer spends explaining the codebase, reviewing pull requests and fixing mistakes. In a 10-person team, one engineer spending 5–8 hours a week on an intern is a significant chunk of delivery capacity. Many small firms say no to interns because they can't spare that time.
2. The payoff often walks out the door
An employer invests most heavily in the first few weeks, and the intern becomes useful just as the internship ends. Then the intern leaves, often for a bigger brand. The return on that onboarding effort goes to someone else.
3. No-shows and drop-outs are real
India's PM Internship Scheme pilot shows the problem at scale. In its first two rounds, companies made over 1.5 lakh offers, but only around 34% were accepted, and by the end of 2025 only 3,417 interns had completed the programme.
4. The skill gap makes interns hard to deploy
Most candidates aren't even internship-ready, let alone job-ready. In a TeamLease EdTech survey, 38% of companies said they struggle to find interns with the right skill sets. If an intern can't yet work with Git, write a basic API or debug on their own, the employer has to train before the intern can contribute.
5. Risk around code, clients and data
Client projects come with NDAs, production access and security requirements. Many firms don't want a short-term, lightly vetted person near client data or production systems, and carving out a safe internal project takes planning they may not have done.
6. Unclear rules and reputational fear
Some employers worry that a low-paid internship will be read as exploitation, or are unsure what paperwork and obligations apply. Doing nothing feels safer than being called out on LinkedIn.
7. There's no job to convert into
If the company isn't planning to hire freshers in the next few months, an intern has no future there. Without a hiring pipeline, there's no return on the investment, paid or unpaid.
Still, some companies pay ₹1 lakh a month while others won't take you even for free
Internship stipends in tech vary enormously. Going by candidate-reported ranges for 2026, big product companies such as Google, Microsoft and Amazon pay interns roughly ₹1–2.5 lakh a month. Funded startups like CRED, Razorpay and Swiggy pay ₹40,000–1.5 lakh. Large IT services firms are typically in the ₹8,000–30,000 range. And many small firms won't take an intern at all, even for free.
That looks contradictory until you see what the stipend actually is. For the companies that pay well, a stipend isn't a wage for the intern's work. It's a hiring cost.
Why do some companies pay huge stipends?
- The internship is the hiring process. For big product companies, a summer internship is a two-month interview. Interns who perform well get a pre-placement offer (PPO) for a full-time job. Compared with the cost of a bad full-time hire, or of hiring through months of interviews and recruiters, a generous stipend is cheap.
- They're competing for a small pool of talent. These companies recruit heavily from a limited set of top campuses, where every other big employer is also recruiting. The stipend works like a bid in an auction: offer less, and the strongest students go to a competitor and probably join them full-time too.
- They've built the systems that make interns productive. Large companies have documented codebases, sandbox environments, structured intern programmes and engineers whose role includes mentoring. So the senior time per intern is lower, and interns can ship real work within weeks. The cost that stops small firms (point 1 above) has largely been solved.
- Scale makes the cost small, and the brand payoff large. For a company with thousands of engineers, a few hundred interns barely register in the budget. Meanwhile, interns who have a good experience go back to campus and talk, which strengthens the employer's brand for next year's recruiting.
The large IT services firms follow the same logic at a different scale. They hire freshers in volume, so internships feed a mass-recruitment pipeline. Unlike big tech, they aren't trying to win the top few hundred students from elite campuses. They're looking for trainable candidates at scale, and they don't need to pay top stipends to find them.
The pattern
It isn't about generosity. Companies pay well when an intern is a likely future employee they're competing for, and they have the systems to make interns productive quickly.
Most startups and small IT firms sit in between: they could use extra hands and would like to hire freshers eventually, but they can't afford big stipends or heavy mentoring. That middle ground is exactly where genuine unpaid or low-stipend internships come from, and where reducing onboarding time makes the biggest difference.
For candidates, the lesson is the same as for employers: the closer you look to a ready-to-deploy future hire, the more a company is willing to invest in you. Skills that cut the employer's onboarding time, such as knowledge of frameworks, Git, debugging, reading an unfamiliar codebase and communicating clearly, are what move you up the stipend ladder.
When a free internship is genuine
Here are the setups where an unpaid internship can be a fair deal for both sides.
- Early-stage startups with mentors but no budget. A founder or senior engineer personally mentors you on a real feature that ships. You get production experience you couldn't get from a course. The test: is there a named mentor with regular time blocked for you?
- Short, project-based internships (4–8 weeks). A clearly scoped deliverable, such as a dashboard, an internal tool or a test suite, with a start and an end. Short duration limits the cost to you, and a finished project is something you can show in interviews. TeamLease's survey found 73% of companies themselves consider 1–6 months the right length.
- Academic-credit internships. Many engineering and diploma courses make an internship compulsory to graduate. Here the main value is the credit and the structured evaluation, and the college partly acts as a safeguard. In theory, the college approves a company, your mentor there evaluates you, and the college reviews your report. In practice, a lot of colleges meet the requirement by tying up with training institutes, where students pay a fee, attend a batch programme, and get an "internship certificate". If that's what your college offers, treat it as training, not an internship.
- Non-profits and open-source projects. Contributing to an NGO's tech stack or a recognised open-source project builds a public, verifiable track record. The work is visible on GitHub for any future recruiter to check.
- "Try before hire" with a written conversion path. The internship is explicitly an extended interview, with criteria for converting to a paid role stated upfront in writing. This is the strongest version for both sides: the employer reduces hiring risk, and the candidate has a clear target.
A quick checklist: is this free internship genuine?
| Genuine | Red flag |
|---|---|
| No fee of any kind | Asks for a fee and still calls it an "internship" |
| Offer letter from a company email domain | Gmail/WhatsApp-only communication, Google Forms, link shorteners |
| Named mentor and defined deliverables | Vague "work on live projects" with no details |
| Interview-based selection for a small number of places | Everyone who pays gets in |
| Fixed duration (ideally 1–3 months if unpaid) | Open-ended, or "unpaid for 6 months, then we'll see" |
| You can show the work in your portfolio (within NDA limits) | Nothing you can show or reference afterwards |
| Experience letter and reference on completion | Certificate is the only "deliverable", and it costs money |
| Conversion or stipend criteria in writing | Verbal promises of a job "if you perform" |
The bottom line
"Free internship" shouldn't be a dirty word.
- It's a scam when you pay for something that doesn't exist.
- It's training, not an internship, when you pay to learn in a classroom.
- It's exploitation when you work without learning anything.
But when an employer gives you real mentorship, a real project and a clear outcome, an unpaid internship can be the bridge from training to a first job.
Judge the offer by what it gives you, not only by the stipend line.
