Google STEP & SWE Internship India: Eligibility, Process and Preparation

A Google internship is one of the most sought-after outcomes for Indian CSE students, and for good reason: it's a strong resume signal, the work is real, and it can lead to a return offer. It's also a process with its own specific shape: an early application window, an online challenge, two technical interviews, and a host-matching step that surprises many first-time applicants.

This guide explains the two main Google engineering internships open to students in India, who is eligible, the commonly reported timeline and process, a fully solved Google-style problem, and a ten-week preparation plan. Google adjusts its programs every year, so treat this as a map and check the current listings on Google Careers for exact rules.

STEP vs SWE Internship: Which One Is for You?

If you're in first or second year, STEP is your target. If you're in pre-final year, you're applying for the SWE internship. Master's students apply for SWE internships as well, often with a broader range of teams available. Google may also run other student programs (research internships, specific university or diversity-focused programs) in some cycles; they'll appear on the same careers site.

Google Internship Eligibility in India

Every posting has an explicit "Minimum qualifications" section. Read it word by word, because applications that don't meet these are typically filtered automatically.

STEP: what to check

• Year of study and graduation window. Postings specify the graduation years they accept, which effectively limits the program to first- or second-year students in that cycle.
• Degree and field. Typically a bachelor's in Computer Science or a closely related technical field.
• Enrollment. Usually currently enrolled full-time in a degree program in India.
• Programming experience. Experience in at least one general-purpose language such as C++, Java or Python.
• Cycle-specific criteria. Some years have had additional eligibility criteria. Don't rely on last year's rules or a senior's memory; read the current posting.

SWE internship: what to check

• Currently pursuing a bachelor's, master's or PhD in CS or a related field, with the graduation year window stated in the posting.
• Experience in one or more general-purpose languages, and familiarity with data structures and algorithms.
• Ability to complete the internship in the stated period and location (and return to your degree program afterwards).
• Preferred qualifications often mention projects, internships, open-source or competitive programming, but these aren't hard filters.

Google Internship Application Timeline (Typical)

The timeline is the part students most often get wrong. Google's summer internship applications typically open well before the summer, often in the second half of the previous year, and some postings close once enough applications arrive. Use this as an approximate pattern only.

Practical rule: be application-ready (resume, transcript, DSA level) by the middle of the year before your target summer, and check Google's careers site weekly from July. Apply within days of a posting going live.

How to Apply for Google STEP and SWE Internships

1. Create a Google Careers profile and set job alerts for "intern" roles in India (search "STEP Intern" and "Software Engineering Intern" with location India).
2. Prepare a one-page resume. For STEP: education, 1–3 projects (course projects count), programming languages, any contests or clubs. For SWE: projects with results, previous internships, contest ratings, open-source. Our fresher resume guide has the bullet formula and template.
3. Keep an unofficial transcript ready as a PDF in case the application asks for it.
4. Apply through the official posting. Some campuses also have on-campus Google processes; if yours does, follow the placement cell's instructions too.
5. Seek a referral from a Google engineer if you know one, ideally an alumnus. A referral typically ensures a recruiter reviews your application; it doesn't skip any interview. See how to get referrals at Google, Microsoft and Amazon.
6. Answer any application questions (preferred languages, availability) accurately.

Google Internship Selection Process, Stage by Stage

The online challenge

The online challenge is the first real skill filter. Expect problems in the easy-medium to medium-hard range: arrays and strings, hashing, sorting with a twist, greedy, BFS/DFS on grids or graphs, and some DP. Each problem is scored on hidden test cases, so efficiency and edge cases matter. Our guide on clearing online coding assessments covers constraint reading, partial scores and time management.

The technical interviews

Google's interviews are known for emphasising problem-solving process over memorised answers. A typical 45-minute interview for an intern:

• ~2–5 minutes: introductions.
• ~35 minutes: one problem, sometimes with a follow-up that extends it (for example, "now what if the input doesn't fit in memory?" or "what if there are updates?"), or two smaller problems.
• ~5 minutes: your questions for the interviewer.

What interviewers commonly evaluate:

STEP interviewers calibrate to what a first- or second-year student should know. They care more about how you reason and respond to hints than about advanced algorithms. For SWE interns, expect the full range of standard topics, including graphs and DP. Communication matters enormously in both; read how to think out loud in coding interviews.

A Solved Google-Style Interview Question

This is the kind of problem that fits a 45-minute intern interview: a clear statement, a brute force that's easy to find, an optimal solution that requires a pattern, and a natural follow-up.

Problem. Given a string s and an integer k, return the length of the longest substring that contains at most k distinct characters.

How a strong candidate talks through it

1. Clarify. "Is the string ASCII or Unicode? Can k be 0? Can the string be empty? Should I return the length or the substring?" (Assume: any characters, k ≥ 0, return length.)
2. Brute force. "Check every substring and count distinct characters: O(n²) substrings, and with an incremental set per start index it's O(n²) overall. Fine for small n, too slow for 10⁵."
3. Optimise. "If a window has more than k distinct characters, any larger window containing it does too. So I can use a sliding window: extend the right end, and when the distinct count exceeds k, shrink from the left. A hash map tracks counts."
4. Complexity. "Each index enters and leaves the window at most once, so O(n) time. Space is O(min(n, alphabet size)), bounded by k + 1 keys in the map."

from collections import defaultdict

def longest_at_most_k(s, k):
    freq = defaultdict(int)
    left = best = 0
    for right, ch in enumerate(s):
        freq[ch] += 1
        while len(freq) > k:              # too many distinct: shrink
            freq[s[left]] -= 1
            if freq[s[left]] == 0:
                del freq[s[left]]
            left += 1
        best = max(best, right - left + 1)
    return best

int longestAtMostK(const string& s, int k) {
    unordered_map<char, int> freq;
    int left = 0, best = 0;
    for (int right = 0; right < (int)s.size(); right++) {
        freq[s[right]]++;
        while ((int)freq.size() > k) {
            if (--freq[s[left]] == 0) freq.erase(s[left]);
            left++;
        }
        best = max(best, right - left + 1);
    }
    return best;
}

Dry run: s = "eceba", k = 2

Answer: 3 ("ece"). With k = 0, every character immediately triggers shrinking, so the window stays empty and the answer is 0, which is correct.

Likely follow-ups

• "Return the substring itself." Track the start index when you update best.
• "What if the string is a stream and you can't store it?" You still need the characters inside the current window, so store only the window (for example in a deque) rather than the whole stream.
• "Exactly k distinct?" Use atMost(k) − atMost(k − 1) for counting substrings, a classic trick worth knowing.

For more on this pattern, see sliding window problems explained.

Practice Question Themes for Google Internships

Rather than hunting for "leaked" questions (which Google actively retires), practise the themes that come up repeatedly in candidate reports. For each theme, a few representative practice problems:

Our explainers for several of these are a good place to start: Number of Islands, Merge Intervals, and Coin Change.

A 10-Week Preparation Plan for Google Internships

This plan assumes 10–12 hours a week alongside college. STEP aspirants can stop after week 7 and spend the remaining time on mocks; SWE aspirants should do all ten weeks.

Practise like the real interview

• Solve in a plain text editor or a shared doc, not an IDE with autocomplete. Many candidates are surprised how much they rely on it.
• Explain out loud, even when practising alone. Record yourself occasionally.
• Always finish with a manual dry run and complexity analysis.
• Do at least 3–4 mock interviews with someone who'll interrupt and give hints, so taking hints gracefully becomes natural. See mock interview strategy.

Host Matching and the Offer

Host matching is the stage most specific to Google, and it causes the most anxiety. After you clear the interviews, your profile (resume, interview feedback, preferences) is shared with teams that have intern projects. A team interested in you may set up a short conversation, often called a host matching call.

How to handle a host matching call

• It's a two-way conversation, not another coding interview. The host wants to know whether you'd be a good fit for their project and whether you're excited about it.
• Prepare a crisp introduction of yourself and your projects. Our guide to answering "tell me about yourself" has samples for students.
• Ask about the project: what you'd build, the tech stack, what success looks like, how mentoring works.
• Show genuine interest and willingness to learn unfamiliar technologies. Interns often work in stacks they haven't used before.

Matching can take a while, and timing depends on how many projects and candidates are in the pool. Some candidates who clear interviews aren't matched in a given cycle, especially late in the season. If it's taking long, a polite check-in with your recruiter is fine.

Stipend and logistics

Google doesn't publish intern stipends. Based on student reports and public sources such as Glassdoor and AmbitionBox, Google's India intern stipends are among the highest in the market, often reported above ₹1 lakh per month, with exact figures varying by year and program. Treat these as approximate; the offer letter is what counts. Offers may also include relocation or travel support depending on the cycle and location.

If You Don't Get a Google Internship

Google internships are extremely competitive, and many strong students don't get one. That's not a verdict on your ability, and there are excellent paths forward.

• Apply again next cycle. STEP applicants can apply for the SWE internship later. Interview experience from one cycle makes the next one much easier.
• Get an internship elsewhere. A strong internship at a product startup or another large company makes your next Google application more competitive. See our internship guide for CSE students for the full landscape.
• Do open source. Programs like Google Summer of Code (an open-source program, not an internship at Google) give you public, reviewed work.
• Aim for new-grad roles. Many Google engineers in India joined as new grads or after a few years elsewhere. The Google India SDE interview guide covers that path.

Google's internship process rewards students who start early, apply the week postings open, and practise solving problems out loud in a plain editor. Do those three things consistently, and you'll give yourself a real shot 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.