Google Internship Guide for IIT and Tier 3 College Students

Yes, Google is possible from a tier 3 college. Here's the honest guide for both no gatekeeping, no false promises.

"Is Google Even Possible For Me?"

Let's answer this upfront because it's the first thing everyone thinks.

If you're from an IIT yes, Google is very much on the table. Google comes to campus at IITs, your resume gets seen, and with the right preparation you have a real shot. But "IIT student" is not a free pass. People from IITs get rejected at Google all the time because they under-prepare or don't understand how Google specifically evaluates candidates.

If you're from a tier 3 college yes, it is possible. But let's be honest: it's harder, the path is longer, and you'll have to work around systems that weren't designed for you. Students from tier 3 colleges have gotten Google internships. It happens every year. But it requires you to build a profile strong enough that your resume gets noticed without the brand name doing any of the work.

The good news: Google cares more about how you solve problems than where you studied. Their interview process is designed to evaluate thinking, not credentials. That's actually good news for anyone who is willing to put in the work.

This guide is written for both of you honestly, with different strategies where the path diverges.

Google's Internship Programs What Actually Exists

Before anything else, understand what programs you can actually apply to.

Google STEP Internship

STEP stands for Student Training in Engineering Program. This is Google's internship for first and second-year undergraduate students.

In India, STEP is specifically targeted at students from underrepresented groups in tech historically this has meant women and students with disabilities. If you're a first or second year student and fit this criteria, STEP is your primary Google internship target.

• Duration: 10–12 weeks, May to August
• Location: Bengaluru, Hyderabad, or Pune
• Eligibility: 1st or 2nd year BTech/BE students from underrepresented groups in tech
• When to apply: Applications open in August–September for the following summer

Google SWE (Software Engineering) Internship

This is the main Google internship that most people are targeting the one that can convert to a full-time offer.

• Duration: 10–12 weeks, May to August
• Location: Bengaluru, Hyderabad, or Pune (for India)
• Eligibility: Pre-final year or final year BTech/BE or MTech students
• When to apply: Applications open August–October for the following summer

This is what the rest of this article focuses on.

The Reality Check IIT vs Tier 3

Here's the honest picture of where you're starting from.

If You're From an IIT

Google comes to your campus. That means your resume goes into a separate, smaller pool not the general off-campus pile that gets thousands of applications. This is a significant advantage.

But here's what IIT students get wrong: they assume the brand does more work than it does. Google's interviews are the same whether you come on-campus or off-campus. The bar doesn't lower for IIT students. People from IITs who haven't done serious DSA prep get rejected in round one all the time.

Your strategy: use the on-campus opportunity (don't miss the registration deadline), but prepare as seriously as you would if you had no brand advantage. Because in the interview room, you don't.

If You're From a Tier 3 College

Google does not come to your campus. You're applying off-campus, which means you're in a pool with thousands of other applicants, and your resume has to pass an initial filter without a recognizable college name helping it.

This is the hard truth: resume screening at Google is real, and college name does matter at that stage. This doesn't mean you can't get in it means you need to make the rest of your profile strong enough that a recruiter looks twice.

What makes a recruiter look twice:

• Competitive programming achievements (ICPC, Codeforces, LeetCode contest ratings)
• Open source contributions to well-known projects
• Strong projects with real impact and a good GitHub
• Referrals from Google employees

Of these, referrals and competitive programming are the two things that most reliably get tier 3 students past the initial filter. We'll cover both in detail.

Your strategy: you're playing a different game. You need to build proof of ability that's visible and verifiable things a recruiter can point to and say "this person clearly knows what they're doing regardless of where they went to college."

Building the Profile What Google Actually Looks For

Google's bar for internships is genuinely high. Here's what matters, in order of importance for Google specifically.

DSA This Is Non-Negotiable

Google's interviews are almost entirely DSA and problem-solving. Unlike some companies that test system design even for interns, Google's intern interviews are focused on algorithms and data structures.

The topics Google hits most often:

Arrays and Strings Sliding window, two pointers, prefix sums. These show up constantly.

Trees and Graphs BFS, DFS, binary search trees, lowest common ancestor, cycle detection. Google loves graph problems.

Dynamic Programming 1D and 2D DP, memoization vs tabulation. Not always in every interview but common enough to be essential.

Recursion and Backtracking Permutations, combinations, N-queens type problems. Google uses these to test clean thinking.

Sorting and Searching Binary search in all its variations, merge sort, quicksort.

Heaps and Priority Queues Used in scheduling, top-K problems, Dijkstra's.

Hashing HashMap-based solutions, frequency counting, anagram detection.

What matters at Google isn't just solving the problem it's how you solve it. Google interviewers pay close attention to:

• Can you arrive at an optimal solution or do you need hints?
• Can you identify the time and space complexity of your solution?
• Can you handle edge cases without being prompted?
• Can you explain your thinking clearly?

A candidate who codes a working but suboptimal solution and clearly explains it will often score better than one who codes the optimal solution but can't articulate why.

Competitive Programming Especially for Tier 3 Students

For IIT students, competitive programming is helpful but not strictly required if your DSA is strong.

For tier 3 students, it's significantly more important because it's one of the most visible signals that a recruiter without context about your college can immediately understand.

A Codeforces rating, ICPC result, or strong open-source contribution can show problem-solving ability beyond your college name. Focus on achievements you can link to and explain; no contest result guarantees a recruiter response.

Projects Quality Over Quantity

Google doesn't care about the number of projects on your resume. They care about depth.

One strong project that:

• Solves a real problem
• Has a clean, well-documented codebase on GitHub
• Shows technical decision-making (why did you choose this database? why this architecture?)
• Has some scale or complexity to it

...is worth ten tutorial clones.

For Google specifically, projects that involve algorithms, data processing, or backend systems tend to land better than pure frontend projects. Not because frontend doesn't matter but because Google's intern interviews are algorithmic, and a project that shows algorithmic thinking gives you better interview stories.

Open Source Contributions

Contributing to well-known open source projects especially Google-run ones like TensorFlow, Kubernetes, or Flutter is one of the strongest signals a tier 3 student can have on their resume.

It's also genuinely hard to fake. A merged pull request to a major open source repo means real engineers reviewed your code and approved it. That carries weight.

You don't need to fix the hardest bugs. Start with documentation improvements, test coverage additions, or small bug fixes. The goal is to get a few merged contributions to recognizable projects.

Where to start:

• GitHub’s “good first issue” label on active projects
• Google Summer of Code (GSoC) is a mentored, stipend-supported open-source program for eligible adult students and open-source beginners. It is not a Google internship or recruitment program.

Referrals The Most Underused Path for Tier 3 Students

A referral from a Google employee gets your resume into the referred candidates pool which is reviewed by a human, not just a filter. For tier 3 students, this can be the difference between your resume getting seen and it disappearing.

How to get a referral:

LinkedIn Search "Google Software Engineer India" and filter by 2nd-degree connections. A shared connection makes outreach much warmer. Send a short, personalized message. Not "please refer me" "I've been preparing for Google for X months, here's my profile, would you be open to a quick chat?"

Alumni networks Check if any alumni from your college work at Google. Even one or two people from your college at Google is enough. They're more likely to respond to someone from the same place.

Competitive programming communities People you've interacted with on Codeforces, in ICPC teams, or in coding communities. These are warm connections, not cold outreach.

Google Developer Student Clubs (GDSC) Being active in your college's GDSC or attending Google-run events puts you in spaces where you meet Google employees and developer advocates. These connections are valuable.

For a more detailed guide on how to ask for a referral professionally, check out our LinkedIn Referral Guide.

How Google Recruits The Full Picture

On-Campus (IITs and Select NITs)

Google visits a small number of campuses in India primarily the IITs and a handful of NITs. The process:

1. Resume submission through your placement cell
2. Online Assessment (OA) typically 3 DSA problems in 90 minutes
3. 2–3 technical interview rounds

The OA is the first filter. It's harder than most company OAs. Expect medium to hard LeetCode-level problems with tight time constraints.

Register early. Placement cells have registration deadlines, and missing them means missing the opportunity entirely for that year.

Off-Campus Applications

Go directly to careers.google.com and search for "Software Engineer Intern India." Apply online with your resume.

The honest reality: off-campus cold applications from unknown colleges have a low conversion rate at Google. This doesn't mean don't apply always apply. But don't rely on it as your only strategy. Pair it with referrals and competitive programming visibility.

When to apply: The moment the listing goes live, which is typically August–October. Google internship roles fill fast and sometimes close before the listed deadline.

Google Summer of Code (GSoC)

Google Summer of Code is a mentored open-source contribution program that provides a stipend to accepted contributors. Participants work with a mentoring organization; they are not Google interns or employees. The experience can strengthen an open-source portfolio, but it does not provide a direct route into Google hiring.

• Who can apply: eligible contributors aged 18 or older who are students or open-source beginners; check the official rules for all conditions
• No college-tier requirement; proposals are evaluated by participating mentoring organizations
• Stipend: amount varies by project size and country
• When to apply: check the official annual timeline; the 2026 contributor application window was in March

For students from colleges with limited recruiting access, GSoC can be a valuable way to build public open-source work and mentorship relationships. Describe your contribution accurately on your resume; it is not part of Google’s hiring pipeline.

Apply at: summerofcode.withgoogle.com

The Interview Process What to Expect

Google's intern interview process in India typically looks like this:

Online Assessment → 2 Technical Rounds

Sometimes there's a third round. Rarely more than that for internships.

Online Assessment

3 problems, 90 minutes. Difficulty: medium to hard.

Unlike some companies where the OA has easy-medium problems, Google's OA is genuinely hard. If you're not consistently solving medium LeetCode problems in under 20 minutes, the OA will be a wall.

Prepare specifically for the OA by doing timed practice not just solving problems, but solving them within strict time limits.

Technical Interview Rounds

Each round is 45–60 minutes with one Google engineer. The format:

• 5 minutes: introductions
• 35–40 minutes: problem solving (1–2 problems)
• 5–10 minutes: your questions for the interviewer

What the interviewer is evaluating:

Google uses a rubric internally. The things they score you on:

Problem Solving Do you arrive at a working solution? Do you optimize it?

Coding Is your code clean, readable, and correct? Do you handle edge cases?

Communication Do you explain your thinking? Do you ask clarifying questions before diving in?

Analytical Ability Can you analyze the time and space complexity of your solution? Can you compare approaches?

The biggest thing that separates Google interviews from other company interviews: Google cares a lot about the process, not just the answer. A candidate who starts with a brute force, explains why it's suboptimal, and then improves it to an optimal solution while narrating their thinking will score well. A candidate who silently codes the optimal solution and says "done" will not.

How to Approach a Problem in the Interview

1. Read the problem carefully. Ask 1–2 clarifying questions input size, edge cases, constraints. This shows you think before you code.
2. Think out loud from the start. "My first instinct is a brute force O(n²) solution let me think if there's something better."
3. Start with the brute force. Get a working solution first, even if it's slow. Then optimize.
4. Walk through your approach before coding. "I'm going to use a hashmap to store frequencies does that approach make sense?" Get the interviewer's buy-in.
5. Code cleanly. Use meaningful variable names. Don't write spaghetti code under pressure.
6. Test your code. Walk through a test case manually after writing. Catch bugs before the interviewer has to point them out.
7. Analyze complexity. Always state the time and space complexity of your final solution.

Preparation Roadmap Topic by Topic

Here's a structured plan based on how long you have.

If You Have 6+ Months

This is the ideal scenario. Use it.

Months 1–2: Foundations

• Complete a full DSA course (see resources below)
• Solve easy LeetCode problems by topic 5 per topic minimum
• Start participating in weekly LeetCode contests

Months 3–4: Core Google Topics

• Focus on: Trees, Graphs, DP, Sliding Window, Binary Search
• Move to medium problems aim to solve mediums in 20–25 minutes
• Start Codeforces Div. 3 contests

Months 5–6: Interview-Level Practice

• Solve relevant algorithm problems and review your mistakes
• Do timed mock assessments under realistic conditions
• Practice explaining solutions out loud with a friend or recording

If You Have 3 Months

Month 1: High-frequency topics only

Arrays, strings, trees, graphs, binary search, hashmaps. 150–200 problems, all mediums.

Month 2: DP and advanced topics

Dynamic programming, backtracking, heaps. Push to hard problems for practice even if you can't solve them reading the solution builds pattern recognition.

Month 3: Mock interviews and Google-specific prep

LeetCode Google tag problems. Timed OA practice. Mock interviews with peers. Behavioral prep for the intro portion.

If You Have Less Than 1 Month

Be honest with yourself: you can't fully prepare for Google in under a month if you're starting from scratch.

What you can do: focus on the 75 most important problems (Blind 75 is a well-known list), practice talking through your solutions, and apply anyway. Getting to the interview with under-preparation is still better than not applying. You'll learn what the real bar feels like, and next cycle you'll be ready.

Resources What to Actually Use for Google

For DSA Foundations

Striver's A2Z DSA Sheet

The most comprehensive free DSA roadmap for Indian students. Covers every topic with curated problems in the right order. Start here if you're building from scratch.

LeetCode

Non-negotiable for Google prep. Use the "Google" company tag to filter problems that have appeared in Google interviews. Focus on mediums.

Neetcode.io

Free video solutions for the most important LeetCode problems, explained clearly. When you're stuck on a problem and don't understand the editorial, Neetcode's explanation is usually the best one.

For Competitive Programming

Codeforces

The best platform for competitive programming practice. Start with Div. 3 contests, move to Div. 2. Aim for a rating of 1400+ as a baseline, 1600+ as a strong signal.

CP-Algorithms

Free, comprehensive reference for competitive programming algorithms and data structures. Use it to understand topics deeply, not just memorize implementations.

For Google-Specific Interview Prep

LeetCode Google Tag

Filter LeetCode problems by "Google" under company tags. These are problems that candidates have reported seeing in Google interviews. High-signal practice.

Blind 75

A curated list of 75 problems that cover the most important patterns. If you have limited time, this is the list to do.

→ Search "Blind 75 LeetCode" available on NeetCode and multiple other sites

interviewing.io

Anonymous mock interviews with engineers from FAANG companies, including Google. Expensive but the most realistic Google interview practice available. Worth it if you can afford it for 2–3 sessions.

For Open Source and GSoC

Google Summer of Code official site

Check the official timeline each year for the list of mentoring organizations and the contributor application window. In 2026, contributor applications opened in March.

First Contributions (GitHub)

A beginner-friendly guide to making your first open source contribution. Good starting point before contributing to larger projects.

For Non-CS Students Your Path to Google

Let's address something that almost nobody talks about honestly.

Google does hire non-CS students for SWE internships. ECE, mechanical, electrical, even civil engineering students have gotten Google internships. But the path looks different, the prep looks different, and the realistic options are slightly different too.

Here's everything you need to know.

First What Google Actually Looks For in Non-CS Students

Google doesn't care about your degree title. They care about whether you can solve algorithmic problems at their bar. A mechanical engineer who has solved 400 LeetCode problems and can think through a graph problem clearly will get the same fair shot as a CS student in the interview room.

What you're fighting is the resume filter getting past the initial screening without a CS degree on your resume. Once you're in the interview, the playing field levels out entirely.

So the entire game for non-CS students is: build a profile that gets you past the filter, then prepare for interviews the same way any CS student would.

What's Actually Different for You

Your starting point for DSA is further back. CS students have typically seen data structures and algorithms in their curriculum trees, graphs, sorting, recursion. You may not have. This means you need to budget more time for foundations before you start doing interview-level practice. Expect to spend 4–6 weeks on pure fundamentals before touching LeetCode mediums. That's not a disadvantage it's just a different starting point.

Your resume needs to work harder. Without a CS degree, a recruiter looking at your resume needs other signals that you can code at Google's level. The three things that do this most effectively:

• Competitive programming: a verifiable Codeforces, LeetCode, or ICPC result can show algorithmic skill regardless of your degree
• Strong GitHub projects: publish real code, clear READMEs, and meaningful commits
• Open-source work: documented contributions or a GSoC project can demonstrate collaboration and engineering skill, but neither guarantees Google recruitment

Referrals matter even more. For a non-CS student applying off-campus, a referral is arguably your most powerful tool. It bypasses the resume filter entirely and gets a human to look at your application. Invest time in finding Google employees through LinkedIn, alumni networks, or competitive programming communities and asking genuinely, not desperately.

The Roles Available to Non-CS Students

SWE Intern Yes, non-CS students can and do apply. You'll be evaluated on the same algorithmic bar. If you can clear it, your degree doesn't matter.

Hardware Engineering Intern Relevant for ECE and EEE students. Google's hardware teams work on custom chips (like the TPU), data center infrastructure, and devices. This track is more aligned with your background and less purely algorithmic in nature.

Technical Program Manager (TPM) Intern Open to students from any engineering background. TPMs sit between engineering and operations coordinating technical projects, managing timelines, working across teams. Less DSA-heavy, more systems thinking and communication. Google does hire interns for TPM roles.

Google STEP If you're in your first or second year and from an underrepresented group in tech, STEP is open to you regardless of your branch. This is worth pursuing early.

For ECE Students Specifically

You have a genuine advantage in certain Google teams hardware, silicon, networking infrastructure. Don't default to assuming you have to compete on the same SWE track as CS students. Research what Google's hardware and infrastructure teams do and see if your background maps to it. You might find a more natural fit and a less crowded path.

Your Preparation Path

Step 1 Build the CS foundations first (4–6 weeks)

Before touching LeetCode, get solid on:

• Basic programming in Python or Java (if you're not already)
• Arrays, linked lists, stacks, queues, trees, graphs what they are and how they work
• Basic sorting algorithms bubble sort, merge sort, quicksort
• Big O notation understanding time and space complexity

Best resource for this starting point:

CS50 by Harvard (Free)

The best free introduction to computer science for someone coming from a non-CS background. Covers programming, algorithms, data structures, and more in a genuinely beginner-friendly way. Watch this before anything else.

Step 2 Move into structured DSA practice

Once foundations are solid, follow the same path as any CS student Striver's A2Z sheet, LeetCode by topic, starting with easy and moving to medium.

The timeline is just longer. Give yourself 2–3 months of consistent daily practice (1–2 hours a day) before you'll feel comfortable with mediums.

Step 3 Build visible proof of ability

Pick one of these and pursue it seriously:

• Participate in active Codeforces contests and track your progress over time
• Consider Google Summer of Code if you meet its current eligibility rules and want to contribute to open source; it is not a Google internship
• Build one strong project in an area that interests you and document it properly on GitHub

Step 4 Apply and get a referral

Apply on careers.google.com the moment internship listings open (August–October). Simultaneously work on getting a referral check our LinkedIn Referral Guide for exactly how to do this.

Don't apply and wait. Apply and keep building.

Honest Expectations

Non-CS students breaking into Google is real but statistically harder, especially for SWE roles. Here's a realistic picture:

If you start early (2nd year), build competitive programming skills seriously, do GSoC or have strong open source contributions, and get a referral your chances are genuinely competitive.

If you start in your final year with no coding background, no projects, and no competitive programming history Google SWE is probably not the right target for this cycle. In that case, target companies with lower algorithmic bars first, build 6–12 months of real engineering experience, and revisit Google after.

There's no shame in sequencing your goals. A lot of people who eventually get into Google didn't get in on their first try they built their profile over time and came back stronger.

The Mindset Shift

Stop thinking "I'm from ECE, can I even apply to Google?" and start thinking "what do I need to build in the next 6 months to make my application competitive?" The first question keeps you stuck. The second one gives you a plan.