Article

Every internship season, the same pattern repeats on Internshala and Unstop: a listing goes live and collects 300+ applicants within two days. On the other side is one busy recruiter who spends maybe ten seconds per profile before deciding "shortlist" or "skip." Getting picked is rarely about being the most brilliant person in the pile — it is about being the clearest and most relevant one in those ten seconds. Here is how to do that even with zero formal experience.

Decode the role before you write anything

Most students skim a listing, see the word "intern," and hit apply. That is exactly why they get filtered out. Read every listing twice and pull out three things:

• The core deliverable — what you will actually produce (code, content, social media posts, research, spreadsheets, designs).
• The must-have skills — usually two or three named tools or concepts (React, Excel, Canva, Python, SEO).
• The hidden signals — phrases like "fast-paced," "self-starter," or "will talk to customers" tell you what the team quietly values.

A listing that says "assist with content and basic design in Canva" is not looking for a future novelist. It wants someone who can turn out clean social posts quickly. Once you know the deliverable, you can prove you have done that exact thing before — and that is the entire game.

Spend five minutes on the company too. Open their website, LinkedIn, and Instagram. Note what they actually sell and one recent thing they did. You are not doing this to flatter them; you are doing it so your application references something real instead of sounding like a mass-forwarded template.

Build a resume that survives a seven-second scan

For a no-experience student, the resume's job is not to look impressive — it is to be instantly scannable and believable. Keep it to one page, use a clean single-column layout, and save it as a PDF named Firstname-Lastname-Resume.pdf, never "resume_final_v2.pdf".

Order the sections by strength, not by tradition. If your projects are stronger than your marks (they usually are), put projects above education. A typical winning order for a fresher is: a two-line summary, skills, projects, education, then positions of responsibility or certifications.

The single biggest upgrade you can make is to quantify everything. Compare these:

• Weak: "Made posts for the college fest Instagram."
• Strong: "Ran the fest Instagram for 6 weeks, published 24 posts, grew followers from 400 to 1,900."

You do not need a job to have numbers. Club events, a YouTube channel, a freelance gig, a Kaggle rank, GitHub stars, quiz scores — all of it counts. Numbers signal that you finish things and measure outcomes, which is exactly what a manager is afraid an intern cannot do.

Let your projects carry the application

When you have no work history, projects are your experience. Two or three real, finished projects beat a long list of half-watched courses every time. A strong student project has three qualities: it solves a small real problem, it is actually usable (a live link, an APK, a working sheet, a published article), and you can explain every decision inside it.

• For developers: put it on GitHub with a clear README, and add a live link (Vercel, Netlify, Streamlit).
• For designers: a Behance or Figma link, or a simple portfolio site.
• For content and marketing: a Google Drive folder or Notion page with samples, plus any real reach numbers.
• For data roles: a Kaggle notebook or a short write-up of what you found and why it matters.

Do not submit the "To-Do App" and "Weather App" that everyone else also submits. Pick something slightly specific to you — a fee-splitting app for hostel roommates, a scraper that tracks internship stipends, an Instagram page for your hometown's food spots. Specific projects start conversations; generic ones get skimmed past.

Write a cover note that sounds like a person

On Internshala, the cover-letter box is where most applicants either paste a robotic template or write "I am hardworking and a quick learner." Both are invisible. A good cover note is short — four to six sentences — and follows a simple shape:

1. One line on why this role, referencing something specific about the company or product.
2. Two lines of proof — your most relevant project or result, with a number.
3. One line on availability and fit (hours per week, WFH-ready, start date, duration).
4. A warm, confident closing line.

Here is the difference in practice.

Before: "Respected Sir/Madam, I am a hardworking and dedicated student looking for an opportunity to learn and grow in your esteemed organization. I am a quick learner and a team player."

After: "Hi team — I noticed you're pushing more short-form video on the page lately, and that's exactly what I've been doing. Over the last two months I ran my college placement cell's Instagram, took Reels from ~500 to 12,000 average views, and wrote every caption myself. I'm free 25 hrs/week, fully set up for WFH, and can start immediately."

The second version is specific, numeric, human, and confident. It answers the only question the recruiter has: can this person do the actual work?

Avoid the mistakes that trigger instant rejection

Recruiters reject on signals, not essays. These are the ones that end applications in seconds:

• A generic, un-tailored application blasted to 50 listings at once — it always shows.
• Typos in the first line, especially the company's name spelled wrong.
• Skills you cannot defend. If "Python" is on your resume, expect a Python question. List only what survives one follow-up.
• Fake or inflated numbers. Experienced recruiters smell "managed a team of 20" from a first-year.
• Applying late. For popular WFH listings, applying in the first 24–48 hours meaningfully raises your odds, because recruiters often shortlist before the deadline closes.
• Overwriting. A wall of text in the cover box gets skimmed to zero. Keep it tight.

Follow up without being annoying

Following up is not desperate — done right, it signals genuine interest that most applicants are too shy to show. The rules are simple.

If you applied and have a contact (a LinkedIn connection at the company, a recruiter's email), send one short, polite message about 5–7 days after applying. Reaffirm your interest in a line, restate your single strongest proof point, and re-link your work so they don't have to dig. Then stop — one nudge, not five.

A referral changes everything, so build them before you need them. Politely message a current employee or a college senior on LinkedIn: keep it to two lines, mention the specific role, and attach your resume. A warm referral often moves your profile straight to the top of a pile the platform's algorithm would otherwise bury.

Finally, treat every application as a rep. Save the projects and cover notes that got replies, reuse those patterns, and drop whatever got silence. Getting shortlisted is a skill you build across a season — and the students who treat it that way are the ones holding offer letters by the end of it.