How to actually land a tech internship in India in 2026

There are four distinct pools of internships in India, and they behave completely differently. Treating them as one undifferentiated list is the single most common mistake we see.

The first pool is applicant tracking systems used by product companies and funded startups — Greenhouse, Lever, Ashby, Workday and Oracle Recruiting. These are the canonical source: if a role exists at a company running one of these systems, it exists on that board first, often days before it appears anywhere else. They are also the least crowded, because most students never look at a company's own board.

The second pool is government and institutional portals, above all the AICTE National Internship Portal, along with ministry, PSU and defence programmes. These have fixed windows, formal eligibility criteria, and far less competition per seat than their visibility suggests, largely because the application flow is unpleasant enough that people give up halfway.

The third pool is campus and program-specific intakes — Google STEP-style programmes, Microsoft Engage-style cohorts, Amazon and Adobe campus tracks, and university-mediated drives. These open on a calendar, not on demand, so the winning behaviour is to know the month rather than to search continuously.

The fourth pool is aggregators and community boards. Useful for discovery, unreliable as a source of truth. Always trace the listing back to the company's own page before you spend an hour on the application.

• Company ATS boards: freshest, least competitive, requires knowing the company list.
• Government portals: fixed windows, formal process, low effective competition.
• Campus programmes: calendar-driven, high volume, high prestige.
• Aggregators: good for discovery, always verify at the source.

Applying is a search problem before it is a writing problem. Spend one evening constructing a list of eighty to a hundred and twenty companies that plausibly hire interns in your domain and in your region, and store their careers URLs. Include the obvious large employers, but weight the list toward Series A to Series C startups, which hire interns with far less ceremony and convert them to full-time offers at a much higher rate.

Once the list exists, checking it takes minutes per week rather than hours. Most students invert this: they spend hours per week searching and minutes per week applying, which produces a small number of late applications to heavily contested roles.

A useful heuristic for the Indian market: for every well-known company on your list, add three companies you had not heard of a month ago. Recognition is inversely correlated with your odds.

Stipend language in India is deliberately vague, and decoding it saves weeks. 'Performance-based stipend' with no number almost always means either nothing or a token amount contingent on targets. 'Certificate and letter of recommendation' listed as compensation means unpaid. A stated monthly range in rupees, with a duration, is a real offer.

Unpaid internships are not automatically bad — a genuinely unpaid research assistantship with a named professor and a publishable output can be worth more than a paid data-entry role labelled 'software intern'. But you should know which one you are applying to before you invest, which is why we mark every internship on Ovyro as paid, unpaid or unstated rather than leaving it ambiguous.

Treat any request for money as disqualifying. No legitimate employer in India charges a candidate a registration fee, a security deposit, a training fee or an equipment deposit. This is the most common fraud pattern targeting students and it is worth being absolute about.

• Stated monthly amount + duration = real.
• 'Performance-based' with no figure = assume zero.
• 'Certificate + LOR' = unpaid.
• Any fee requested from you = fraud, report and move on.

One page. Not two, not a designed multi-column artefact that shreds in a parser. A single column, standard fonts, black text, no photographs, no skill bars, no rating stars. Applicant tracking systems read text; anything that makes the layout interesting makes the text harder to extract.

Structure it as: name and contact, one-line summary, projects, experience, skills, education. Projects go above education for a student with real work to show. Every project line should say what the thing does, what you built, and what happened as a result — 'built X using Y, which did Z' beats a list of technologies with no verbs.

Include links that resolve. A GitHub profile with three well-documented repositories beats twenty abandoned forks. A deployed URL that loads in two seconds beats a demo video. Reviewers spend well under a minute per application, and a broken link consumes the entire budget.

Write the cover note only when there is a field for it, and keep it to four sentences: what you are applying for, the single most relevant thing you have built, why this specific company, and your availability window. Anything longer is not read.

Freshness dominates. An application submitted within forty-eight hours of a posting going live is read in a substantially smaller pile than one submitted two weeks later, when the role is often already in final rounds. This is why checking a fixed list weekly outperforms searching sporadically.

On volume: forty carefully targeted applications with tailored project ordering will beat four hundred identical submissions, but ten will not be enough. Plan for a sustained rate — five to ten well-made applications a week for eight weeks — rather than a single burst of effort followed by silence.

Follow up once, seven to ten working days after applying, by email, in three sentences, with the role title and a link to the most relevant thing you have shipped. Follow up a second time and you become noise. Never follow up by connecting with recruiters on social platforms and messaging them repeatedly; in India this is common enough now that it actively counts against candidates at several employers.

Track everything in a simple sheet: company, role, date applied, source URL, status. Without it you will re-apply to the same role, forget which version of your resume you sent, and miss deadlines that were entirely in your control.

The conversion rate from intern to full-time hire is the single highest-leverage number in an early career, and it is largely determined in the first two weeks. Interns who ship something small and visible early are remembered; interns who spend three weeks reading the codebase before touching it are not.

Ask for a written definition of success in week one — literally, 'what would make this internship a clear success from your side?' Almost nobody asks, and the answer converts a vague assignment into a checklist.

Document what you did as you go and produce a one-page summary at the end with the measurable outcome of each piece of work. This is what your manager forwards when the conversion conversation happens, and it is also the basis for your next resume.