How to Get a Software Engineering Internship in India (Even from a Tier-3 College)

An internship is the single biggest lever a CSE student has on their first job. A good internship gives you real engineering experience, a resume line recruiters recognise, and often a pre-placement offer that makes final-year placements irrelevant. The problem is that the best internship processes start much earlier than most students expect, and students outside top campuses rarely get them through the placement cell.

This guide is a year-by-year plan that works from any college. It covers the internship calendar, where students actually get hired, how to write a resume and cold email when you have no experience, and how to prepare for internship interviews specifically, which are noticeably different from full-time interviews.

Types of Software Internships in India (and Which Ones Matter)

"Internship" covers very different experiences. Some will transform your resume; some are a certificate and not much else. Know what you are targeting.

Program names, eligibility and dates change from year to year. Treat every program name here as a pointer to its official page, and confirm the current cycle's rules there.

Internship Timeline by Year of College

The most common regret I hear from final-year students is "I started too late". Here is what each year should accomplish, assuming a four-year B.Tech. BCA/MCA and B.Sc students can compress years 1–2 into the first year of their program.

First year: fundamentals and curiosity

• Learn one language properly (C++, Java or Python). Write lots of small programs. See Java vs Python vs C++ for DSA if you're undecided.
• Start basic problem-solving: 50–100 easy problems on arrays, strings and loops-based logic.
• Learn Git and push everything to GitHub. A GitHub account with a year of activity is a quiet signal later.
• If your institution is eligible, apply to first-year-focused programs (Google STEP is the best-known one). Read our Google STEP guide for the process.

Second year: one real project and core DSA

• Cover core data structures and algorithms: arrays, hashing, two pointers, recursion, linked lists, stacks, queues, trees, basic graphs, sorting and binary search.
• Build one project that real people use, even 20 classmates. A deployed app beats three tutorial clones.
• Start contributing to open source: documentation fixes, small bugs, then features. This sets you up for GSoC-style programs.
• Apply for a summer internship after second year at startups, research labs or open-source programs. Big product companies rarely hire second-years outside dedicated programs, so don't be discouraged by that.

Third year: the main internship season

• This is the year that matters most. Many large companies run their summer internship hiring for pre-final-year students roughly from July to October, nearly a year before the internship.
• Your DSA must be at interview level by the start of third year: comfortable with medium problems, including trees, graphs, DP basics and heaps.
• Have two strong projects and a one-page resume ready by June–July after second year.
• Apply widely: on-campus if available, plus off-campus to product companies, startups and contests.

Fourth year: six-month internships and conversion

• Many companies offer six-month internships in the final semester (January–June), which often convert to full-time offers. Check whether your university allows a final-semester internship.
• If you had a summer internship, focus on converting it to a PPO; if not, final-year internships are an excellent second chance.

A broader year-by-year plan beyond internships is in our B.Tech CSE year-wise roadmap.

The Internship Hiring Calendar

The calendar is the most underestimated part of internship hunting. A student who starts applying in March for a May internship will find most large company programs already closed. Use this as an approximate guide, and confirm exact dates each year on official pages.

Where to Apply for Software Internships

Company careers pages

Every big tech and well-known product company lists internships on its careers page, usually under "Students" or "University". Search for "SDE intern", "Software Engineering Intern", "Summer Intern 2027". Bookmark 30–50 target companies and check them weekly during the season.

Internship and job platforms

• Internshala: very large volume of internships, especially startups and smaller firms. Quality varies a lot; filter by stipend and read the role description carefully.
• LinkedIn: filter Jobs by "Internship". Also follow recruiters who post intern openings and set alerts.
• Wellfound (formerly AngelList Talent): startup roles, often with transparent pay; good for remote internships.
• Unstop, HackerEarth, HackerRank: hiring challenges and hackathons with internship outcomes. These are skill-first, which makes them especially valuable for tier-2/3 students.

Programs with their own applications

• Open source: Google Summer of Code, LFX Mentorship, Outreachy (for people from underrepresented groups, with its own eligibility rules), MLH Fellowship. See our GSoC guide.
• Research: summer research programs at IITs and IISc (for example, IIT Kanpur's SURGE and the Indian Academy of Sciences' Summer Research Fellowship), and abroad programs such as MITACS Globalink and DAAD WISE. Deadlines are often months ahead.
• Company-run challenges and hackathons that award interview opportunities to top performers.

Direct outreach

Cold emails to startup founders and engineering managers, and referral requests to alumni. This is covered in detail below because it is the channel students underuse most.

Internship Resume When You Have No Experience

For an internship, nobody expects work experience. Recruiters screen for evidence that you can write code and learn quickly. Your resume should prove exactly that, on one page.

Section order for an internship resume

1. Header: name, phone, email, LinkedIn, GitHub, LeetCode/Codeforces (only if decent).
2. Education: college, degree, expected graduation year, CGPA (include if it is 7.5+ or the company asks for it).
3. Projects: two or three, with bullets that describe what you built, how and with what result.
4. Technical skills: languages, frameworks, tools. Only what you can be interviewed on.
5. Achievements: contest ratings and ranks, hackathon results, open-source merges, scholarships.

Turning weak bullets into strong ones

The pattern: action verb + what + stack + a concrete outcome or scale. Be ready to explain every number. Our full fresher resume guide has a template and more before/after examples.

Cold Emails for Internships That Actually Get Replies

Startups are the most responsive audience for cold outreach because founders and early engineers read their own inboxes and many don't post every opening publicly. The email needs to be short, specific and show you've looked at their product.

Subject: Backend intern (Summer 2027) - built a delivery-slot scheduler in Go

Hi Priya,

I'm a third-year CSE student at [College]. I've been using [Product] to order
groceries and noticed you schedule delivery slots per pincode - I built
something similar as a side project: a slot scheduler in Go + PostgreSQL that
handles overbooking with row locks (repo: github.com/you/slotter, live demo
linked in the README).

I'd love to intern with your backend team for 8-10 weeks this summer (May-July),
remote or in Bangalore. I'm comfortable with Go, Python, SQL and Docker, and
I've solved 400+ DSA problems.

Resume attached. Would you be open to a 15-minute call?

Thanks,
Rohan | +91-XXXXXXXXXX | github.com/you

Why it works: the subject line contains the role, the season and proof; the first line shows genuine interest; the project is directly relevant to their business; the ask is small and specific. Writing 5 emails like this beats sending 100 generic ones.

Finding emails: many founders list theirs on their personal site or social profiles; otherwise LinkedIn messages work fine. Follow up once after about a week. For more variants, including referral requests and follow-ups, see our cold email and LinkedIn message templates.

Emailing professors for research internships

The same principles apply, with one difference: professors want evidence that you've read their work. Mention a specific recent paper, what you understood, and a concrete skill you bring ("I've implemented graph neural network baselines in PyTorch"). Mass-mailing an identical email to dozens of professors is common and easy to spot; tailored emails to a few well-matched labs do better.

How to Prepare for Software Internship Interviews

Internship interviews are a lighter version of new-grad interviews. The bar on DSA is real, but the scope is narrower: almost no system design, less depth on CS theory, more weight on whether you can solve a clean problem and explain your projects.

The DSA topics that cover most intern questions

• Arrays, strings and hashing (frequency maps, prefix sums)
• Two pointers and sliding window
• Binary search, including on answer space
• Linked lists and stacks (including monotonic stack basics)
• Binary trees: traversals, height, LCA, level order
• Graphs: BFS, DFS, connected components, simple shortest paths on grids
• Recursion and basic backtracking (subsets, permutations)
• Introductory dynamic programming (1-D DP, simple 2-D grid DP)

The top DSA patterns guide goes through each one with problems. For a fixed list, either Blind 75 or NeetCode 150 is enough for most internship processes if you genuinely understand each problem.

Project questions to prepare

For each project on your resume, prepare answers to: Why did you build it? What was the hardest bug? Why this database or framework? How would it behave with 100x users? What would you change now? Interviewers use projects to check that you actually built what you listed, so be precise about which parts you wrote. More on this in how to explain projects in an interview.

A 6-week internship interview prep plan

1. Weeks 1–2: Core patterns. Arrays, hashing, two pointers, sliding window, binary search. 3 problems a day, mostly easy rising to medium. Write the complexity of every solution.
2. Weeks 3–4: Trees and graphs. Traversals, BFS/DFS, recursion and backtracking. Start one timed 90-minute set every weekend to simulate an OA.
3. Week 5: DP basics + CS fundamentals. 1-D and grid DP. Revise OOP pillars, SQL joins and indexes, process vs thread, and deadlock conditions.
4. Week 6: Mocks and projects. Two mock interviews with a friend or senior, explaining aloud. Prepare project deep dives. Redo problems you got wrong.

Choosing Between Internship Offers (Stipend, Brand, Work, Remote)

If you get more than one offer, or you are deciding whether to accept an early startup offer while waiting on a bigger company, compare on what actually affects your next step. Stipend matters, but for most students it is not the most important factor.

On stipends, ranges are wide and change every year. As approximate 2026 ranges from public sources such as AmbitionBox, Glassdoor and student reports: small and early-stage startups often pay roughly ₹10,000–₹40,000 a month, funded mid-size product companies more, and large product and big tech companies frequently pay well above ₹1 lakh a month for SDE interns, sometimes with relocation or housing support. Treat these as rough orientation, not benchmarks; the offer letter is the only number that matters.

Remote internships: good and bad versions

Remote internships at startups are common and can be excellent, especially for students outside metro cities. A good remote internship has a named mentor, regular calls, code review on every pull request and access to the real codebase. A bad one is a list of tasks over chat with no review, which teaches little. Before accepting, ask: "Who will review my code, and how often will we talk?" The answer tells you which kind it is.

Should you accept an early offer and keep interviewing?

Students often get a startup offer in December and a big company interview in February. Accepting and then backing out damages your relationship with that company and sometimes your college's relationship too, and some colleges have rules on this for on-campus offers. If you're still interviewing elsewhere, it is reasonable to ask the first company for a short extension on the decision deadline, and to be honest that you're completing another process. Many startups will agree. If they won't, decide based on the table above, not on fear of having nothing.

The Tier-3 College Playbook for Internships

If your college doesn't bring product companies for internships, your strategy changes in emphasis, not in kind. You need channels where your skills are evaluated before your college name is.

• Coding contests and hiring challenges. A good rank in a company's hiring contest or a strong Codeforces/CodeChef rating gets you noticed regardless of college. This is the most college-blind channel there is.
• Open source. Merged pull requests in a well-known project are public proof that experienced engineers have reviewed your code. GSoC selection in particular is a strong signal to recruiters.
• Alumni referrals. Your college has alumni at product companies even if it has few. Search LinkedIn by college and company; one referral beats dozens of cold applications.
• Startups first, then big tech. A startup internship after second or third year makes the next application far stronger. Many engineers reach big tech through two steps rather than one.
• Visible work. Writing about what you build (a blog, a LinkedIn post with a demo) helps recruiters find you.

The tier-3 to MAANG guide covers the longer-term version of this strategy.

During the Internship: How to Turn It into a PPO

Getting the internship is half the job. A pre-placement offer can take placement-season pressure off entirely. Conversion decisions usually depend on your project outcome, your mentor's and manager's feedback, and sometimes a final presentation or interview.

1. Clarify success in week one. Ask your mentor: "What would a great outcome for this project look like by the end?" Write it down and confirm it.
2. Ship something early. A small merged change in the first two weeks (even a bug fix) builds trust and teaches you the codebase and deployment flow.
3. Send a short weekly update. What you did, what's next, where you're blocked. Managers remember interns who make their progress easy to see.
4. Ask good questions, after trying. Spend a reasonable amount of time on a problem, then ask with context: what you tried and where you're stuck.
5. Document impact. Measure before and after if your work allows it. Your final presentation should state the problem, what you built and the result.
6. Build relationships. Join team meetings, talk to engineers outside your project. These people become your referrers later.

Our dedicated PPO guide covers conversion in depth, including what to do if a PPO doesn't come through.

An internship isn't a lottery. Start in second year, align with the calendar, use channels that judge skill over pedigree, and treat the internship itself as a long interview. That sequence works from any college.

Frequently Asked Questions

Pranjal Jain

Ex-Microsoft SDE · IIT Kanpur · Founder of Prepflix. Helps engineers crack startup and product company interviews across India.