RoundHound
Get accessSign in
Prepare
HomeHomeJobsJobsPractice historyHistoryProgressProgress
Get full access?Sign in
Jobs/Google

STEP Intern

Google · Intern (first- and second-year students)

Research from Oct 93 rounds, none tried

This is how Google interviews for STEP Intern, from our research: 3 rounds, what each one looks for, and how to prepare. Pick any round and an AI interviewer runs it with you out loud, by voice or by typing. Afterwards you’ll see what went well and what to work on next.

Your first 60 minutes of practice are free. No card needed.

Next: your first full round

Do the Recruiter or HR Screen round.

One full round, as long as theirs, shows where you stand before you work on anything specific.

Set up this round →Practice the full interview day
Length50 min · Intern (first- and second-year students) level

The rounds

3 rounds · 2 h 20 min

Pick a round to see what it asks of you and where you stand on it.

Recruiter or HR Screen

Confirm communication, project ownership, academic context, and foundational programming readiness.

Behavioral · 50 minSet up this round →
Not tried yetNo attempt yet.

What strong sounds like

  • Gives a structured introduction covering study, interests, skills, and interest in STEP.
  • Explains personal contribution, key choices, and one concrete result or learning from a project.
  • Accurately describes preferred programming language, relevant skills, and recent preparation.

Expect to be pushed on

Ask for personal contribution, project decisions, or preparation details.

Shapes of problem you may get

  • Self-introduction and study path
  • Project contribution and result
  • Programming language, skills, and preparation

How to prepare

  1. Choose three short screen stories

    Select one study example, one project example, and one preparation example. For each, note your personal contribution, one choice you made, one result or lesson, and the programming language or skill involved.

    Reports describe questions about study, projects, skills, preparation, academic context, and preferred programming language. The exact screen format is not consistent across reports.

    Company researchGoogle STEP Internship Interview Experience (India, 2025)My Google STEP Internship Interview ExperienceMy Google STEP Journey + Tips for First-Timers

  2. Shape a concise introduction

    Write a short introduction that connects your current study, technical interests, recent preparation, and interest in STEP. Rehearse it once without giving a full biography.

    A structured introduction is directly named in the round criteria and matches reported STEP screening topics.

    Company researchGoogle STEP Internship Interview Experience (India, 2025)My Google STEP Internship Interview ExperienceMy Google STEP Journey + Tips for First-Timers

  3. Separate your work from group work

    For each project story, mark what you designed, coded, tested, or learned yourself. Prepare one sentence about a group decision and one sentence about your own contribution.

    This prevents broad project claims and gives the interviewer specific material about ownership, choices, and results.

    Suggested approach

Then try the round

You have three selected stories, a short introduction, and a clear statement of your preferred language and recent preparation.

Resources to focus on
  • Interviewing at Google: Best practices, advice, and tips

    Focus on “Interview prep,” especially self-introduction, skills, projects, interests, and questions for the interviewer. It is general Google guidance, not STEP-specific.

    Use its communication guidance to edit your introduction and project stories before trying this round.

Do

  • Give a concise introduction linked to current study and STEP.
  • Describe personal project choices, contribution, and one result.
  • State a preferred programming language and recent preparation.

Avoid

  • Do not give a long chronological biography.
  • Do not describe group projects without separating personal work.
  • Do not claim skills without a specific example.

Your first try takes the full 50 minutes, like the real one.

What they look for

Researched today

Recent Google STEP reports describe a 10–15-minute recruiter or human-resources screen followed by two 45-minute coding interviews. Candidates report shared-document coding, data-structures and algorithms problems, verbal reasoning, complexity, edge cases, and follow-up changes. The current platform, location-specific loop, and elimination rules are not confirmed.

They reward

  • Clear verbal reasoning during coding
  • Simple solutions followed by useful optimization
  • Specific project ownership and preparation details

What to avoid

  • Do not give a long chronological biography.
  • Do not describe group projects without separating personal work.
  • Do not claim skills without a specific example.
  • Do not code before stating inputs, outputs, and constraints.
  • Do not hide complexity or edge cases until prompted.

How sure we are

Worth redoing if you hear something from the recruiter that contradicts this.

Confirmed · 9
  • Multiple 2025 STEP candidate reports describe a recruiter or human-resources screen followed by two technical interviews.
  • Several exact STEP candidates reported two 45-minute technical interviews.
  • Two exact STEP reports state that both technical interviews were eliminatory.
  • Exact STEP candidates reported coding in a shared Google Docs-like document during technical interviews.
Likely · 1
  • The exact STEP reports and the reposted EMEA listing support an expectation of foundational programming and data structures and algorithms coding, rather than a dedicated system-design interview.

Worth asking them

Questions that fill in what the research couldn’t tell us.

Will both technical rounds use a shared Google document or another coding editor?
Are the two technical rounds each 45 minutes in my location and current cycle?
Does the current process include a preparation session before technical interviews?

Research status

Collected Oct 9. If the recruiter tells you something this brief contradicts, correct it after the interview and the brief updates.

Correct this brief

Attempts

Every round you’ve done for this job, newest first.

All attempts in History →

Recruiter or HR Screen, Technical Coding Interview 1, and Technical Coding Interview 2 have no attempts yet.