aicodinginterview Waitlist

Google AI coding interview: 5 candidate reports

What candidates say the round looked like, summarised in our words, each linked to where it came from. Google hasn’t confirmed these details unless the source says “Official page”.

Background on the format: our Google guide.

Had this round? Add your report →

At a glance

Stage
Onsite (3 of 5 reports)
Where it runs
CoderPad (1 of 2 reports)
The AI
Built-in AI chat (3 of 5 reports)
The task
Mixed (1 of 3 reports)
The AI could
write code, read the files (at least half of 2 reports)
Length
about 60 min (median of 1 reports)

The reports

Onsite · October 2026

Didn’t pass

Cloud AI engineer role: the role-related knowledge round was spoken questions on AI terms, with most interest in prompt injection and how system instructions affect a model. The onsite coding round was a single array problem; the candidate solved it but wasn’t selected because of bugs in the code.

AI: No AI · Source: LeetCode Discuss post

Phone screen · October 2026

Senior · CoderPad

For a senior AI/ML role at L5, round 1 used Google’s newer format, in two parts. Technical Communication and Collaboration: a deep discussion of one past project, covering design choices, trade-offs, ambiguity, AI tools used and collaboration, with no slides. Then AI-assisted Code Comprehension on CoderPad: debug, extend and optimise a given codebase with an AI assistant.

AI: Built-in AI chat · Task: Mixed · Source: Reddit thread

Onsite · October 2026

Mid-level

Replying in a thread about Google’s AI-assisted rounds (the poster was interviewing for L4), a candidate who had one the week before said it was two LeetCode problems, a medium then a hard. The interviewer asked for pseudocode first and said not to touch the AI until it was written. They wrote the whole solution as pseudocode and had the AI translate it to Python in one shot, and felt coding it themselves would have been faster.

AI: Built-in AI chat that could write code · Task: Build from a spec · Source: Reddit thread

Phone screen · August 2026

Intern · 60 min

First intern round, about an hour: one tree problem with an N-ary follow-up, then the last few minutes on 3 or 4 AI fluency questions. These were spoken questions, not a coding task with AI: how they use AI in their normal workflow, whether they give the AI full ownership of a project, and how they use it for tasks like debugging.

AI: No AI · Source: LeetCode Discuss post

Onsite · May 2026

Junior · Other

Business Insider reviewed an internal Google document describing a pilot ‘code comprehension’ round: candidates ‘read, debug and optimize’ an existing body of code with Gemini as the only approved assistant. Interviewers assess ‘AI fluency’, described as prompt engineering, output validation and debugging skills. It’s a pilot for junior and mid-level roles on select US teams from the second half of 2026, and Google’s VP of recruiting confirmed it. Candidate posts describe a multi-file codebase of roughly 100 to 500 lines.

AI: Built-in AI chat that could read the files, write code · Task: Fix bugs · Source: Press report