RepostedGoogle logo

Google · Phone screen → Onsite

In process

Google Intern Host Call Updates: 10 Experiences (Part 8 of 8)

Software engineer · InternshipReported Oct 28, 2026
Shared byjanebeingjane

Google Summer 2027 SWE intern updates, Sep 24–Oct 29, 2026: two coding rounds, then Project Search and host calls; unfinished code was not always a no.

At a glance

  • Process: two technical rounds of LeetCode-style coding with no separate behavioral or resume section (82, 86), then Project Search: a project questionnaire and host calls before any offer (80, 81, 83).
  • Asked recently: only one report named topics: a greedy question with a binary-search-on-the-answer follow-up, then a class with methods and attributes (80). Others described medium main problems with harder follow-ups (82, 88).
  • Difficulty: the second round was where candidates needed hints or ran out of time (80, 82, 86, 87). Outcomes split: 80 advanced with unfinished code, 86 was rejected after several corrections.
  • After the interviews: positive replies came two days (83) to four days (80) later; one candidate already had three host calls booked (81).

Coverage: Google Summer 2027 SWE intern, U.S. and Canada where stated. Ten reports, entries 79–88, posted September 24 to October 29, 2026. Entry 82 continues a Part 5 account.

In this series

  • Part 1: graphs, intervals and OOD from the first wave of 2027 intern loops.
  • Part 2: paths, grids and trees.
  • Part 3: prefix sums and heaps.
  • Part 4: full loops and team matching.
  • Part 5: grids, DP, OOP and AI.
  • Part 6: trees and knapsack.
  • Part 7: PhD and return offers.
  • Part 8 (current): updates and host calls.

What came up

This update is mostly about what happens after the interviews. Only one candidate named topics, so the table is short.

Topic Reports Last seen
Greedy, with binary search on the answer 1 of 10 Oct 2026
Class-based data-structure implementation 1 of 10 Oct 2026
Status at last update Reports
Project Search or team matching (one with host calls) 5 of 10 (80, 81, 83, 85, 88)
Waiting for feedback or the next step 3 of 10 (79, 82, 84)
Rejected 1 of 10 (86)
Not reported 1 of 10 (87)

No report named a specific coding problem, so there is no question table here.

10 detailed candidate timelines, loops, and screens

79: An October 27 interview, no portal change

Interview date: Oct 27, 2026 · Report date: Oct 29, 2026 · Role: U.S. Summer 2027 SWE Intern · Status: Waiting for feedback

  1. The interview moved from the week before because of a recruiter conflict.
  2. Afterward the portal still showed only the scheduling change, not a submitted interview. No questions or decision were shared.

80: An unfinished class still led to Project Search

Interview date: Oct 23, 2026 (a Friday, inferred) · Report date: Oct 28, 2026 · Role: Summer 2027 SWE Intern · Status: Project Search

  1. Round 1: a prompt given aloud: a greedy question with a binary-search-on-the-answer follow-up.
  2. Round 2: build a class with methods and attributes in Python, without running code. Hints showed the way, but the code was still wrong at time. They compared the format to LRU-cache problems; it was not said to be one.
  3. Expecting another round at best, they had raised concerns with recruiting. The next Tuesday a recruiter moved them to Project Search, with matching from November and a team required before an offer.

81: Two host calls became three

Report date: Oct 23, 2026 · Role: U.S. Summer 2027 SWE Intern · Status: Host calls scheduled

  1. Two host calls were booked for the next week: one team and location looked promising, the other less so. Both were in the northeastern U.S., not their preferred Bay Area.
  2. The recruiter asked for their impressions after each call. A third call was added later. They were in the general pipeline, not direct consideration. No match or offer yet.

82: Optimal main answers, an unfinished follow-up

Report date: Oct 23, 2026 · Role: Summer 2027 SWE Intern · Location: Canada · Status: Waiting for feedback

  1. Round 1: optimal solution, coded and dry-run, with five minutes left for questions and none for follow-ups.
  2. Round 2: improved to optimal time; explained the optimal follow-up, then struggled to code it in the last ten minutes. Main problems felt medium, follow-ups a bit harder.
  3. This is the candidate whose coding pad stopped accepting input in Part 5 (entry 42). On Oct 29 they were still waiting about a week for feedback.

83: A two-day reply and a submitted questionnaire

Report date: Oct 22, 2026 (follow-up Oct 23) · Role: Canada Summer 2027 SWE Intern · Status: Project Search

  1. They heard they passed two days after the two rounds.
  2. Their project questionnaire drew on two earlier internships in backend, data engineering, cloud and security, while keeping interests open. They asked about Toronto and Waterloo matching. No technical questions were shared.

84: Two good rounds, and only a scheduler to ask

Report date: Oct 9, 2026 · Role: 2027 SWE Intern · Status: Next step unknown

  1. Two technical rounds that felt very good. They wondered whether team matching or another round came next.
  2. Their contact was a scheduler, not a personal recruiter. No questions or decision were shared.

85: Team matching with a robotics background

Report date: Oct 7, 2026 · Role: Summer 2027 SWE Intern · Status: Team matching

  1. Reached team matching for the general SWE internship with experience in real-time firmware, motion planning, perception and a vision-language-action model, not web or backend.
  2. They were deciding whether to stay close to robotics on the preference form, and asked others what hosts focus on. No host call was reported yet.

86: Several corrections, then a rejection

Report date: Oct 6, 2026 · Role: Summer 2027 SWE Intern (bachelor's) · Result: Rejected

  1. Round 1: a warm-up became the main question once a constraint was added. Their first working answer was not optimal; two or three hints, plus another during coding, got them there. They missed an edge case, tried a wrong fix, then corrected it. The follow-up was in the right direction but incomplete.
  2. Round 2: an approach accepted, then quiet coding. The dry run surfaced a bug and a missed edge case, both fixed. Asked for another solution, they offered one they later felt was slower than the one being hinted at.
  3. LeetCode-style coding only, no behavioral or resume section. Rejected.

87: A strong first round, a hint-led second

Report date: Oct 5, 2026 · Role: 2027 Intern · Result: Not reported

  1. Round 1: main question and follow-up, both with optimal time and space.
  2. Round 2: brute force in about ten minutes; the optimization came only with direct guidance. Time ran out before the follow-up; the interviewer said they understood what the candidate would have written.

88: Another offer while Google matching was open

Report date: Sep 24, 2026 · Role: Summer 2027 SWE Intern (sophomore) · Status: Team matching

  1. Applied with a referral through normal consideration. The OA came about a month later, and the interview invite the next day. Questions felt medium, with one easy one.
  2. Holding another company's internship offer, they asked if Google could move to fall. The other company would not move, so they planned to try Google. No Google offer yet.

Patterns across the reports

  1. Team matching is a long middle stage. Five candidates had reached it (80, 81, 83, 85, 88); one had host calls booked (81); none had a match or offer yet.
  2. Unfinished work, different results. 80 advanced with an incomplete class; 86 was rejected after hints and fixes; 82 and 87 ran out of time with no result yet.

Common questions

How long does Google take to reply after the intern interviews?

Two days (83) and four days (80) for those who moved forward; others were still waiting after a week (82).

What happens in Google intern host calls?

One candidate had two, then three, calls booked with teams in the northeastern U.S., and was asked to send impressions after each (81).

Can you pass the Google intern interview without finishing the code?

One candidate did: 80 reached Project Search with an unfinished round-two class. Another with several fixes was rejected (86).

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.