How to Prepare for Google STEP: When It Opens, How to Apply and What the Interviews Ask
Prepare for Google STEP intern interviews with reported assessment patterns, interview questions, and preparation advice.
On this page
Last reviewed November 10, 2026.
For first- and second-year undergraduates.
Check this first: STEP may not run in 2027. On 10 November 2026, Google's STEP page redirected to the Google Careers home page, and a search of Google's job board for STEP and for "Associate Software Developer" returned no matching role. Google has not announced that STEP ended. Treat the dates below as what happened in past cycles, and watch the Google Careers students page for the next posting.
The 30-second version. In past cycles STEP was a paid 12-week summer internship for first- and second-year computer science students. In India, applications opened around mid-November to early December, shortlist emails came about a month later, then a 15-minute recruiter call, a prep session, and two 45-minute DSA interviews in a Google Doc. Questions are easier than the SWE intern loop but told as stories, with a follow-up each.
How STEP differs from the SWE intern role
| STEP intern | SWE intern | |
|---|---|---|
| Who it was for | First- and second-year undergraduates; in India, a 2024 account describes it as open to women students in their second year | Students in their penultimate year, usually third-year B.Tech |
| Online assessment | Not described in STEP accounts; shortlisting was by resume | Usually 2 hard coding questions in 60 minutes |
| Interviews | Two 45-minute DSA rounds, often one main problem plus a follow-up | Two 45-minute DSA rounds with two questions each, sometimes a Googleyness round |
| Difficulty | Easy to medium, story-based | Medium to hard |
| Name in India | Candidates say it was renamed Associate Software Developer intern in 2025 (not confirmed by Google) | Software Engineering Intern |
For the SWE intern loop, see the Google SWE intern guide.
Round-by-round breakdown
Stage 1: Application, where and when candidates applied
How it works. Candidates applied on the Google Careers site with a resume, and in North America and EMEA an unofficial transcript. One candidate added an optional cover letter. Some heard about it through their college placement cell; one applied through an alumni referral.
When it opened (past cycles):
| Cycle | What was reported |
|---|---|
| India, STEP 2024 | Applications opened around mid-November to the first week of December; shortlist email in mid-February |
| India, STEP 2025 | Applied at the end of November, received a rejection email at the end of December, then a recruiter got in touch in mid-January |
| EMEA, summer 2025 | Application deadline 25 October 2024; internship ran 30 June to 26 September 2025 |
Eligibility in past postings: first- or second-year bachelor's students in computer science or a related field. North American postings asked first-years for at least one college CS course and second-years for at least two, and programming experience in C, C++, Java, JavaScript or Python.
Stage 2: Shortlisting, how candidates moved forward
At a glance
- Length: 10 to 20 minutes
- Questions per round: 4 to 6 conversational questions
- What was asked: your introduction, projects, coding-practice progress and preparation, CGPA and backlogs, interview availability
- Most common: projects and coding practice
How it works. A recruiter emails to book a short phone or Google Meet call. It checks your background and schedules the interview. One candidate then attended an interview prep session. The gap to the first technical interview was short: 5 days in one report and 1 to 2 weeks in another.
Stage 3: Online assessment
None of the STEP accounts we read describe an online assessment. Shortlisting was by resume and the recruiter call.
Stage 4: The technical interviews
How it works. Two 45-minute DSA interviews on Google Meet, coded in a Google Doc with no syntax highlighting or auto-indent. Interviewers often describe the problem as a real-life story and add one follow-up.
Round 1
At a glance
- Length: 45 minutes
- Questions per round: 1 main problem plus 1 follow-up
- What was asked: sliding window and two pointers, graphs with hash maps, Kadane's algorithm
- Most common: sliding window problems
Questions candidates reported:
| Question (our summary) | Follow-up reported |
|---|---|
| Most friends who can sit together on a beach where some seats are taken (Max Consecutive Ones) | Allow up to k people between them (Max Consecutive Ones III) |
| A graph and hash map problem on chemical polymer data | A follow-up solved without major blockers |
| Maximum subarray (Kadane's algorithm) | A harder extension; brute force only |
Round 2
At a glance
- Length: 45 minutes
- Questions per round: 1 main problem plus 1 follow-up
- What was asked: recursion and class design, two pointers with bitwise operations
- Most common: none repeated
Questions candidates reported:
| Question (our summary) | What it tests |
|---|---|
| Model files and folders as classes and traverse them | Recursion, class design |
| A 1D array problem using two pointers and bitwise operations; the follow-up first looked like DP | Two pointers, bits |
More questions: Browse Google questions.
Stage 5: Result
How it works. Results arrived 10 to 12 days after the interviews in one report. One candidate was rejected by phone call; another heard nothing positive from HR after both rounds. Two candidates who felt both rounds went well were still not selected.
The Codinzhub Next-Round Playbook
What STEP candidates who moved on did. Put together by the Codinzhub team from the STEP experiences in this guide.
To get shortlisted
- Apply as soon as the posting opens, with a clean one-page resume. A cover letter is optional.
- Ask your placement cell or seniors for a referral; one candidate applied that way.
To get past the recruiter call
- Have a short introduction ready, and be ready to talk about your projects, coding-practice practice, CGPA and backlogs.
To get past the technical interviews
- Expect a real-life story. Turn it into the underlying problem out loud before coding.
- Explain why you chose each data structure and data type.
- List edge cases such as all zeros, all ones and k = 0 before you finish.
- Go from brute force to the optimised version step by step.
How to prepare in four weeks
- Week 1: Arrays, two pointers and sliding window. These came up in more STEP accounts than any other topic.
- Week 2: Hashing and strings. Frequency maps and grouping.
- Week 3: Recursion, trees and simple class design. File-and-folder structures, traversals.
- Week 4: Graph basics and mock interviews. BFS and DFS, then timed 45-minute mocks in a plain Google Doc, explaining out loud.
Candidates also advised: explain why you chose each data structure and data type, list edge cases such as all zeros, all ones and k = 0, and go from brute force to the optimised version step by step.
If STEP does not open
Google's regular internships are listed on the Google Careers students page. Most SWE internships target penultimate-year students, so first- and second-years should use the time to build projects and practise the topics above.
About this guide
This guide is researched and written by the Codinzhub team. We read every Google interview experience we could find, kept only what candidates actually described, and rewrote it in our own words. Questions are our own short summaries; the practice links point to similar problems, not the exact interview questions. Found something out of date? Share your own experience on Codinzhub and we will update the guide.
Keep track of what you’ve learned.