2026 Google AI Coding Interview and HackerRank AI OA, Experienced Hires: 2 Experiences
- Company
- Reports
- 2 interview reports
- Level
- Full-time
- Stages
- OA
The two candidates met Google's AI coding in different places: one in an online assessment with an assistant built into HackerRank, the other in a live round on a multi-file project where using AI was up to them.
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
- 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
- The task was a code project spread across several files, with features that were missing, buggy, or both. The candidate had to fix them.
- AI was optional. The candidate could use it whenever they chose.
- The AI tool, platform, language and length of the round weren't mentioned.
Result
- 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 | Frequency | All last seen dates |
|---|---|---|
| Google Docs Mobile Feature Rollout: features that turn on only once their prerequisite features are satisfied | 1 report | Reports: Jan–Mar 2026 (report date Apr 21, 2026); Additional FastPrep history: May 17, 2026; Apr 19, 2026; Apr 6, 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
- Problem 1 was a classic difference-array or prefix-sum style problem. The candidate finished it quickly, and no AI was mentioned for it.
- 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.
- An AI assistant came with problem 2. The candidate found it weak, about what they'd expect from the GPT-3 era.
- 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.
Keep practicing
- Google Docs Mobile Feature Rollout: the feature-dependency codebase task from report 02's OA.
- Google project coding questions: Google's codebase-style practice projects. Sign-in required.
- AI coding OAs at 15 companies: a cross-company roundup that includes this Google OA problem.
- Google interview guide: Google's interview process and question list.
- Google hiring insights: hiring data for Google.
- Experience feed: more candidate reports from every company.
AI coding rounds at other companies
- Meta: Meta AI coding interview: two onsite rounds where you finish a hard algorithm inside a mostly written codebase with an AI model, then face stress-test suites.
- Stripe: Stripe AI coding interview: experienced engineers kept getting the same transaction rule parser, built step by step with a built-in model.
- Stripe interns: Stripe intern AI coding round: ten intern accounts of the same AI-assisted round.
- Rippling: Rippling AI coding interview: HackerRank's built-in AI on Rippling's familiar problems, plus an HR codebase at the onsite.
- DoorDash: DoorDash AI coding interview: AI CodeCraft: build and run several small services live with your own AI tool.
- LinkedIn: LinkedIn AI coding interview: one long, multi-part task in an IDE whose agent edits files directly.
- Shopify: Shopify AI coding interview: pair programming with your own AI on Shopify's well-known question set.
- Datadog: Datadog AI coding interview: bring any AI tool and share your screen; the tasks are easy, and the follow-ups decide the round.
- Capital One: Capital One AI coding interview: new grad Power Day agentic round: fix a bug, then add a feature to a large full-stack app with Claude Code.
- Bloomberg: Bloomberg AI coding interview: intern rounds that start in a small file and move to a large codebase, debugging with AI help.
- xAI: xAI AI coding interview: new grad take-homes and onsites where you build with AI.
- Adobe: Adobe AI coding interview: AI showed up as one step in a director round and in a take-home; the rest stayed classic.
- Snowflake: Snowflake AI coding interview: design and build a rate limiter or a retrying task queue while the AI writes the code; one AI Engineer onsite was in person with your own laptop.
- Snap: Snap AI coding interview: a backend-only chat service from an empty Python project with Claude or Codex, or a feature in an existing codebase.
- Ramp: Ramp AI coding interview: build inside a repo Ramp provides; one repo logged every prompt for the interviewer to read.
- Anthropic: Anthropic AI coding interview: review four pull requests, then improve one with Claude Code.
- Apple: Apple AI coding interview: CoderPad with a sidebar agent, alongside Apple's other recent interviews.
More companies with AI rounds on FastPrep:
- Amazon: Amazon interview report: an AI-assisted debugging OA (1 experience).
- Atlassian: Atlassian interview report: project coding and AI tool use (11 experiences, two parts).
- Circle: Circle interview report: three AI rounds: building, debugging and PR review (1 experience).
- Volta: Volta interview report: a deliberately vague data task with a token budget (1 experience).
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.
Comments
0No comments yet — be the first to share what you know.