Guides › Career
How to Get Your First Internship (Without a Referral)
Pick a track, build proof, apply in the right places, write cold messages that get replies, ace assignments and spot fake internships — a 6-week plan.
Most students think internships come only through referrals or top colleges. In reality, plenty of students from every kind of college get their first internship by applying smartly and showing proof of skill. This guide is a practical plan: what to prepare, where to apply, how to write messages and how to handle the interviews.
Step 1: Pick one direction
"I can do anything" gets nothing. Choose one track for the next three months:
| Track | Core skills to show |
|---|---|
| Web development (frontend / full stack) | HTML, CSS, JavaScript, React, Node.js, a database |
| Backend (Java / Python) | Java + Spring Boot or Python + Django/Flask, SQL, REST APIs |
| Android / Flutter | Kotlin or Dart, one published or demo app |
| Data analysis | SQL, Excel, Python (pandas), one dashboard tool |
| SDE intern (product companies) | DSA + one language + CS basics |
Follow a roadmap for your track so you know what to learn in what order.
Step 2: Build proof (this replaces the referral)
Recruiters for internships don't expect experience — they want evidence you can build things.
- 2 solid projects in your track, deployed with a live link and a clean GitHub README. See project ideas and projects by role.
- DSA basics if you're applying to SDE roles: 100–150 problems across arrays, strings, hashing, two pointers, recursion, trees (Codify DSA Sheet).
- A one-page resume (fresher resume guide).
- A clean LinkedIn and GitHub.
Step 3: Where to apply
| Where | Why it works |
|---|---|
| Internshala | Huge number of internships, many open to all colleges, many startups |
| LinkedIn Jobs (filter: Internship, Past week) | Startups and mid-size companies; apply early |
| Wellfound (AngelList) | Startups that hire for skills, not college name |
| Company career pages | Many larger companies post internships only here |
| Hiring challenges / hackathons | Some companies hire interns directly from coding challenges |
| Your college placement cell & seniors | Seniors often know when their team is hiring |
| Cold emails/DMs to startups | Very effective when done well (below) |
Apply consistently: 5–10 good applications a day for a few weeks beats 100 rushed ones in a day.
Step 4: Make every application count
- Apply within the first 2–3 days of a posting — later applications are often never seen.
- Answer the screening questions properly ("Why should we hire you?" → mention a relevant project with a result).
- Adjust the top of your resume to the role (put the most relevant project first).
- Keep a simple sheet: company, role, date, link, status. Follow up once after a week.
Step 5: Cold messages that get replies
Founders and engineers at small startups often reply to short, specific messages.
LinkedIn message / email template:
Hi Ankit, I'm a 3rd-year CSE student. I really liked how [product] handles [specific feature].
I build full-stack apps with React and Node.js — most recently a real-time chat app (live link) and an expense splitter (live link).
Are you open to taking an intern for the next 2–3 months? I'd be happy to do a small task first to show my work. Resume attached.
Thanks, Asha
Why it works: short, about them first, proof with links, a clear ask, low risk ("small task first").
Avoid: "Respected sir, kindly provide me opportunity", long life stories, the same message pasted to 200 people.
Step 6: Assignments and interviews
Many startups send a take-home assignment:
- Finish it on time and deploy it — a live link stands out.
- Write a short README: how to run it, what you'd improve with more time.
- Clean code beats extra features.
Interviews usually cover:
- Your projects in depth — every technology you listed
- Basic DSA (arrays, strings, hash maps) or a small coding task
- Fundamentals of your stack (React hooks, REST, SQL joins, OOP)
Practise explaining your project out loud, and use the AI mock interview to rehearse.
Step 7: Paid vs unpaid, and red flags
- Prefer paid internships, but a good unpaid one at a real company with real work can be worth it for a short time.
- Red flags: asking you to pay a "training" or "registration" fee, no clear work description, no company website or LinkedIn presence, offer letters with no company details. Never pay to get an internship.
A 6-week plan
| Week | Focus |
|---|---|
| 1–2 | Finish and deploy 2 projects, write READMEs, update resume |
| 3 | Fix LinkedIn & GitHub, start applying (5/day) |
| 4–6 | Apply daily, 3 cold messages a day, practise interviews, do assignments well |
Rejections and silence are normal — most applications get no reply. Keep a steady pace, improve your projects as you go, and the first "yes" usually comes within a few weeks.
More guides
- How to Use Codify: A 7-Day Start Plan — New here? Pick a roadmap, make a study plan, start the DSA sheet, revise with notes, practise for placements and test yourself — one step a day, then a daily routine.
- Infosys Preparation Guide: Online Test, Pseudocode and Interview — Roles (SE, DSE, SP), what each section of the Infosys online test checks, how to crack pseudocode and reasoning, a 4-week plan and the interview.
- Wipro Elite NLTH Preparation: Aptitude, Essay and Coding — The Wipro fresher test round by round — quant, logical and verbal, the written essay, two coding problems — plus a 3-week plan and interview tips.
- Accenture Preparation Guide: Cognitive, Technical, Coding and Communication — Every Accenture round explained — cognitive, MS Office/networking/cloud technical MCQs, pseudocode, coding and the spoken-English test — with a 4-week plan.