Google AI Coding Interview and AI OA: 2 Experiences

Shared by janebeingjane ·
Company
Google
Reports
2 interview reports
Level
Full-time
Stages
OA

Google's AI coding in 2026 showed up as a HackerRank OA with a built-in assistant and a live round on a multi-file project where AI use was optional.

At a glance

  • Process: an early-career OA on HackerRank with its built-in assistant (02) and, for an experienced candidate, a live AI-assisted round (01).
  • Asked recently: a multi-file project with missing or broken features, where the candidate chose when to use AI (01).
  • Outcome: 02 passed the OA; 01 was rejected and blamed the timing of their AI use.

Coverage: Two experienced full-time candidates. One is a currently employed engineer on their third try at Google, whose role and level weren't given; their AI-assisted round took place between late September and early November 2026. The other is a software engineer whose post's header lists them as switching jobs, although the test they took was Google's early-career assessment; that OA happened in January–March 2026. The reports went up on April 21, 2026 and around November 2, 2026. No locations were given.

Formats in this article

  • AI-assisted interview round, role not given, 1 report: a multi-file project with missing or broken features.
  • Software engineer OA with an AI assistant, 1 report: a feature-dependency codebase task on HackerRank.

Google's AI-assisted coding interview round (1 report, role not given)

What came up

The single report here describes a multi-file project with features that were missing or broken, where the candidate decided when to bring in AI. The candidate put the rejection down to getting that timing wrong. No specific task was named.

01: Third Google attempt, rejected after the AI-assisted round

Report date: around Nov 2, 2026 · Interview period: between late September and early November 2026 · Role: not given · Experience: currently employed engineer, third Google attempt · Result: Rejected

Before the round

  1. In late September, the candidate asked other engineers what the new AI-enabled interview measures and how much of the work to hand to the AI. Nobody answered.

AI-assisted round

  1. The task was a code project spread across several files, with features that were missing, buggy, or both. The candidate had to fix them.
  2. AI was optional. The candidate could use it whenever they chose.
  3. The AI tool, platform, language and length of the round weren't mentioned.

Result

  1. Rejected. The candidate blamed this round, and by their own account the mistake was not knowing when to use AI.

Google's OA with an AI assistant (1 report, software engineer)

What came up

One HackerRank OA with two problems in 90 minutes. The AI assistant was only available for the second problem, a feature-dependency task, and the candidate found it weak and quick to refuse.

Questions we found

AI Coding

Question Reports Last seen
Google Docs Mobile Feature Rollout: features that turn on only once their prerequisite features are satisfied 1: 02 Jan–Mar 2026

The first OA problem was described only as a difference-array or prefix-sum style problem, so it has no row here.

02: Early-career OA on HackerRank, passed

Report date: Apr 21, 2026 · Interview period: Jan–Mar 2026 · Role: Software engineer (the post's title says SDE2) · Cohort basis: the post's header lists the author as switching jobs, while the test itself was Google's early-career assessment · Experience: referred · Result: Passed

Online assessment: 2 problems, 90 minutes, HackerRank

  1. Problem 1 was a classic difference-array or prefix-sum style problem. The candidate finished it quickly, and no AI was mentioned for it.
  2. Problem 2 was a business simulation. Several features depend on each other, and a feature only switches on when its prerequisite features are satisfied. The practice version is Google Docs Mobile Feature Rollout.
  3. An AI assistant came with problem 2. The candidate found it weak, about what they'd expect from the GPT-3 era.
  4. As soon as the candidate asked it about the problem's actual logic, it hit a guardrail and wouldn't help.

Experienced Google loops with no AI round (fall 2026, 1 report)

This report isn't counted in the title or in the sections above. It's one experienced loop from that autumn with no AI round at all.

  • L4 software engineer, Kirkland, Oct–Dec 2026 season (onsite the week before the report), changing jobs. The phone screen was a coding problem plus Googleyness questions. The onsite had coding and a "Solution Design" round that turned out to be a deep dive into a past project rather than a design exercise. No AI-assisted round came up. The full account is in 2026 Google Experienced L4 SWE Phone Screen and Kirkland Onsite.

Common questions

Does Google use AI in coding interviews?

In these reports: a HackerRank OA with a built-in assistant (02) and a live round on a multi-file project with optional AI (01).

Keep practicing

AI coding rounds at other companies

More companies with AI rounds on FastPrep:

Across companies: 2026 AI Coding OAs at 15 Companies: 32 Reported Problems and 2025–2026 AI Coding Phone Screens and Onsites at 43 Companies: 76 Reported Problems.

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.

Comments

0

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