2026 Snowflake AI Coding Interview, Experienced SWE and AI Engineer Onsite: 3 Experiences
- Company
- Snowflake
- Reports
- 3 interview reports
- Level
- Full-time
- Stages
- Onsite
Two of these three candidates, a software engineer and an AI Engineer, got the same task in Snowflake's AI coding round: design and implement a rate limiter, and let the AI write the code.
Coverage: Three experienced hires who were changing jobs: two software engineers (one at IC1, one whose level wasn't given) and one machine learning engineer interviewing for Snowflake's "AI Engineer" title. All three describe the onsite, and two also mention the rounds before it. The interviews took place in July–September 2026, and the reports went up between September 17 and October 23, 2026. One onsite was in person at the office and one was virtual; the third didn't say.
The candidates called the round by different names: "AI-enabled coding," "AI Augmented coding," or just "AI coding." In every case it was a single round of the onsite where the candidate could use an AI assistant to write the code.
Roles in this article
- Software engineer, 2 reports: a rate limiter and a retrying task queue in the AI coding round, plus a key-value store, two system design questions and behavioral questions about using AI.
- AI Engineer (machine learning), 1 report: the same rate limiter in an in-person AI coding round, then a design round on agent skills and agent memory.
Software engineer: Snowflake AI coding onsite (2 reports)
What came up
Both engineers had one AI coding round at the onsite, and in both the AI produced the code while the candidate worked out the design. Neither called the task hard. One thought the round went well and was still rejected; the other found the task simple but only learned at the very end what the interviewer was grading.
| Topic | Reports | Most recent report |
|---|---|---|
| One AI coding round at the onsite | 2 of 2 | Oct 23, 2026 (interview Jul–Sep 2026) |
| AI wrote the code while the candidate handled the design | 2 of 2 | Oct 23, 2026 (interview Jul–Sep 2026) |
| System design, at the phone screen or the onsite | 2 of 2 | Oct 23, 2026 (interview Jul–Sep 2026) |
| Behavioral round at the onsite | 2 of 2 | Oct 23, 2026 (interview Jul–Sep 2026) |
| Rate limiter | 1 of 2 | Oct 23, 2026 (interview Jul–Sep 2026) |
| Key-value store with transactions at the phone screen | 1 of 2 | Oct 23, 2026 (interview Jul–Sep 2026) |
| Project deep dive | 1 of 2 | Oct 23, 2026 (interview Jul–Sep 2026) |
| Task queue with backoff retries and a dead-letter queue | 1 of 2 | Sep 17, 2026 (interview Jul–Sep 2026) |
| Graded on prompting and trade-off judgment | 1 of 2 | Sep 17, 2026 (interview Jul–Sep 2026) |
| Behavioral questions about using AI at work | 1 of 2 | Sep 17, 2026 (interview Jul–Sep 2026) |
A report can count toward several rows.
Questions we found
AI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Design and implement a rate limiter (Sliding-Window Rate Limiter) | 1 report | Reports: Jul–Sep 2026 (report date Oct 23, 2026); Additional FastPrep history: Sep 22, 2026; Aug 10, 2026 |
| Queue plus worker that retries failed tasks with exponential backoff and moves them to a dead-letter queue after the limit (Design a Fault-Tolerant Cloud Queue Service) | 1 report | Jul–Sep 2026 (report date Sep 17, 2026) |
The Sep 22 date in the rate limiter's FastPrep history is the AI Engineer report further down.
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Key-value store with transactions, at the phone screen (Key-Value Store with Transactions) | 1 report | Jul–Sep 2026 (report date Oct 23, 2026) |
System Design
| Question | Frequency | All last seen dates |
|---|---|---|
| Load data from S3 into a database, at the phone screen | 1 report | Jul–Sep 2026 (report date Oct 23, 2026) |
| Task scheduler (Design a Scheduled Job Execution System) | 1 report | Jul–Sep 2026 (report date Sep 17, 2026) |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| How do you use AI in your work? | 1 report | Jul–Sep 2026 (report date Sep 17, 2026) |
| How do you check that what the AI gives you is right? | 1 report | Jul–Sep 2026 (report date Sep 17, 2026) |
2 detailed candidate timelines
01: A rate limiter the AI mostly wrote, and a rejection anyway
Report date: Oct 23, 2026 · Interview period: Jul–Sep 2026 · Role: Software engineer, level not given · Experience: changing jobs, referred · Result: Rejected
Phone screen
- System design: load data from S3 into a database. No further detail was shared.
- Coding: a key-value store that supports transactions. The practice version is Key-Value Store with Transactions.
The onsite was booked very soon after the phone screen.
Onsite: AI-enabled coding
- Design and implement a rate limiter. Practice version: Sliding-Window Rate Limiter. That exercise fixes one algorithm; the report doesn't say which one this candidate chose.
- The candidate added later that the round was mostly about design, and that the AI wrote all of the basic code.
- They felt they answered the rate limiter well.
The report doesn't say whether the rate limiter had to run as a service called over HTTP or only as core logic.
Onsite: project deep dive and behavioral
- A deep dive into one of their past projects.
- A behavioral round. No questions were named.
02: IC1, a retrying task queue, and an AI that took three minutes per answer
Report date: Sep 17, 2026 · Interview period: Jul–Sep 2026 · Role: Software engineer, IC1 · Experience: changing jobs, referred · Format: virtual onsite · Result: Not known when posted; the candidate expected a rejection
Onsite format
- Three rounds back to back: AI coding, behavioral, then system design.
- The candidate called the AI round the hardest of the five rounds in their process. The other two weren't described.
Onsite: AI coding
- Build a queue and a worker that takes tasks from it. A failed task is retried with exponential backoff, and once it goes past the retry limit it moves to a dead-letter queue (a separate queue that holds tasks that keep failing). The practice version is Design a Fault-Tolerant Cloud Queue Service, a design exercise built on the same queue.
- The interviewer spent most of the time on the retry strategy and asked directly about jitter (adding some randomness to each wait) and a cap on the delay.
- Later the interviewer added that client jobs can have a priority. The candidate compared two layouts: one priority queue where the client passes a number, or separate queues for three fixed levels where the client picks one of the three.
- They had the AI write the code but ran out of time to test it.
- The task itself felt simple. What the candidate couldn't work out was what the interviewer wanted. Only at the end did the interviewer explain it: they look at how you ask the AI questions, how you write prompts, and how you judge trade-offs.
- The AI was the one built into CoderPad, and it was very slow, about three minutes per answer. The interviewer kept asking the candidate to query it anyway, so there were long, awkward waits.
Onsite: behavioral
- Mostly questions about AI: how they use it at work, and how they check what it produces.
- Very little about their resume.
Onsite: system design
- A task scheduler. Practice version: Design a Scheduled Job Execution System.
- Not many follow-ups on scaling. The candidate said the interviewer was good.
AI Engineer (machine learning): Snowflake AI-augmented coding onsite (1 report)
This role has one report, an in-person onsite. Its AI coding round was the same rate limiter as report 01, followed by a design round about AI agents and a behavioral round with the hiring manager.
Questions we found
AI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Design and implement a rate limiter (Sliding-Window Rate Limiter) | 1 report | Reports: Jul–Sep 2026 (report date Sep 22, 2026); Additional FastPrep history: Aug 10, 2026 |
System Design
| Question | Frequency | All last seen dates |
|---|---|---|
| Pipeline that automatically extracts and distills reusable agent skills for enterprise users | 1 report | Jul–Sep 2026 (report date Sep 22, 2026) |
| Common components of agent memory (Design Memory for an AI Assistant) | 1 report | Jul–Sep 2026 (report date Sep 22, 2026) |
1 detailed candidate timeline
03: AI Engineer who passed, then turned the offer down
Report date: Sep 22, 2026 · Interview period: Jul–Sep 2026 · Role: Machine learning engineer; the title at Snowflake is AI Engineer, on an agent-focused team that hires directly · Experience: changing jobs, applied online · Result: Passed; declined the offer
Before the onsite
- An ordinary algorithm coding round. The candidate no longer remembers which problem it was.
- An ML fundamentals round.
Onsite format
- In person at the office, which the candidate said was rare in their own experience. Three rounds.
Onsite: AI Augmented coding
- Candidates were asked to bring their own laptop with any AI tools already installed. This candidate uses Codex and Claude. It turned out they could also use the interviewer's laptop, so they did, to save their own tokens.
- The recruiter mentioned two possible formats, refactor-and-debug and design-and-build. They first said it would be the first one, then later said the second.
- The task: design and implement a rate limiter, the same task as report 01. Practice version: Sliding-Window Rate Limiter.
- The AI was allowed to write the code. The candidate had to explain which algorithm they picked and why, what the other options were, and the trade-offs between them.
- Then they demoed the AI-written code live and walked the interviewer through how they had talked to the AI, how they reviewed its code, and how they tested it.
- They found it easy and enjoyable, and expected anyone who already works with AI day to day to feel the same.
Onsite: Expertise (design)
- A system design round tied to the team's work. First: design a pipeline that automatically extracts and distills reusable agent skills for enterprise users.
- Then: what are the common parts of an agent's memory? The practice version is Design Memory for an AI Assistant.
Onsite: behavioral
- With the hiring manager. No questions were named.
After the onsite
- The offer depended on a reference check with two references.
- The candidate passed and then declined the offer.
Patterns across the reports
These patterns come from the two software engineer reports (01 and 02). Report 03 is a different role, so it stays out of the comparison.
-
The AI wrote the code, and the candidate owned the decisions. In 01 the round leaned toward design and the AI wrote all of the basic code. In 02 the AI produced the code too, and the interviewer said afterward that the grade came from how the candidate prompted it and weighed trade-offs.
-
An easy-feeling task didn't predict the result. Neither engineer found the task hard. The candidate in 01 felt the rate limiter went well and was rejected. The candidate in 02 called the task simple, yet ranked the round the hardest of their five. They weren't told what was being graded until the end, and the AI took minutes to answer.
-
The AI round sat next to a behavioral round. Both onsites had one. In 01 it came with a project deep dive; in 02 it came with a system design round, and the behavioral questions themselves were mostly about AI.
Keep practicing
- Sliding-Window Rate Limiter: the rate limiter from the AI coding rounds in reports 01 and 03.
- Key-Value Store with Transactions: the phone screen coding question in report 01.
- Snowflake system design from these reports: fault-tolerant cloud queue and scheduled job execution (report 02), memory for an AI assistant (report 03).
- Snowflake system design questions: every Snowflake design question on FastPrep. Sign-in required.
- Snowflake interview guide: Snowflake's interview process and question list.
- Snowflake hiring insights: hiring data for Snowflake.
- Experience feed: 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.
- Google: Google AI coding interview: an online assessment with HackerRank's built-in assistant, and a live round on a multi-file project where using AI was optional.
- 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.
- 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.