Interviews by company · Snowflake

Snowflake bans AI in coding interviews, but one candidate was allowed it in the phone screen, then graded on how they gathered the requirements and proved the code.

Snowflake's rule is plain. Its careers blog post of January 20, 2026, still up and unchanged in November, says all candidates do coding interviews "without the use of any coding or AI assistants", rules out AI in assessments and take-homes too, and holds one coding interview in person. Two candidate reports from late September 2026 describe exceptions, one each. A software engineer technical phone screen, sixty minutes in CoderPad, Python, with AI allowed, where the recruiter framed the evaluation as how you gather requirements, test and debug. And an in-person round in an AI Engineer onsite, called AI Augmented coding in that report, where you bring your own laptop and assistant and the assistant may write the code. Both got the same task: a rate limiter with client tiers whose limits change at runtime. Here is the rule, what the two reported rounds were, what the follow-ups asked, and where the reported candidate lost points.

Snowflake's rule: no AI in coding interviews

Snowflake's careers blog published an AI cheat sheet for candidates on January 20, 2026. It says Snowflake currently requires all candidates to do coding interviews without any coding or AI assistants. AI is also off limits in written assessments, take-homes and technical exercises, and one of the coding interviews is held in person. The post was still up, and unchanged, in November 2026. Snowflake has not said whether any team or role is exempt.

So plan for a loop without an assistant. The two rounds below are exceptions, one candidate report each, and neither report says why AI was allowed: a team's choice, an interviewer's, or a pilot. If your recruiter says a round allows AI, these two reports are the closest description we have of what it may look like.

What the two reported exceptions look like

In the phone-screen report, the round is a shared CoderPad, an hour, Python, with AI allowed; the report does not say whose assistant it was or what it could do. The prompt is spoken, and short: build a rate limiting service with tiers, let the limits change at runtime, enforce the right limit per client, reject over it. The interviewer then adds the fallback rule out loud: a client nobody configured, or a broken configuration, falls back to a global default policy, and both default-deny and default-approve are fine as long as you pick one. You are expected to ask what is missing before you write.

In the one report of an AI Engineer onsite, the round was in person. You bring a laptop with whatever assistant you like already set up. The reported prompt was the classic design and implement a rate limiter; the assistant may write the code, and the candidate explains the algorithm they chose, what else they considered and why not, and then how they prompted, what they reviewed and what they tested.

What the follow-ups are really about

The phone-screen follow-ups came in a fixed order. Why this algorithm, and the pros and cons of each alternative. Add tests that prove it runs. The real clock is too fast for a bucket to refill between two calls, so how do you test refill: the answer they wanted was to inject a clock or, less elegantly, to sleep. Then the step up: everything is in memory on one instance, how does this become a distributed cluster. The candidate ran out of time before that one.

Our read: the task is small on purpose, and the round is a requirements and verification exercise with a rate limiter as the prop. Two details the reported candidate got wrong are the ones a careful reading of their own design would have caught: raising a tier's limit changes the ceiling, not the tokens a bucket already holds; and refill is time elapsed times the rate, not times the capacity. Both are the kind of thing an assistant will happily get wrong in confident code.

What is confirmed, and what is not

  • Confirmed by Snowflake: no coding or AI assistants in any coding interview; no AI in assessments or take-homes; one coding interview in person (careers blog, January 2026).
  • Reported once each, against that rule: AI allowed in a software engineer phone screen (CoderPad, Python, 60 minutes); an in-person AI Augmented coding round in an AI Engineer onsite.
  • In both reports: the rate limiter as the task.
  • Reported once: the runtime-update requirement and the default policy; the clock-injection follow-up; the recruiter's framing of the evaluation; the exact order of the follow-ups; the two question types of the onsite round; the distributed-systems follow-up as the one that ran out of time.
  • Not known: why AI was allowed in either round, and whether the rule has team or role exceptions Snowflake has not published; which assistant the phone screen provides, if any, beyond what the candidate brings; whether the same task is used for other roles; how the phone screen weighs against the onsite.

How we would prepare

  • Prepare to write it yourself. By Snowflake's rule your coding interviews have no assistant, and one is in person. Ask your recruiter which rounds, if any, allow AI before you plan around one.
  • Ask the fallback question yourself. What happens to a client with no tier, or a tier that was deleted? The interviewer added it out loud; saying it first is the requirements-gathering they grade.
  • Know what a runtime update does to live state. Decide, and say, whether a raised limit adds tokens now or only raises the ceiling, and whether a cut clamps. The reported candidate lost this one.
  • Inject the clock before you are asked. A limiter that takes a time source is testable without sleeping; the follow-up is asking whether you built it that way.
  • Have the distributed answer ready in two sentences. A shared store with an atomic check-and-decrement, and what you lose when the store is down. It was the follow-up nobody reached.
  • If an assistant is allowed, read its refill arithmetic. Elapsed time times the rate, clamped at capacity. It is one line, and it is where the generated code goes wrong.

Nyrion's Snowflake section starts with Tiered Rate Limiter, built from these reports: client tiers with buckets, limits that change at runtime with the settle-then-apply rule spelled out, a default policy for unconfigured clients, and a fake clock in the tests so refill is checked the way the follow-up asks. A third stage adds a shared downstream capacity that must never be exceeded, from a related exercise. The tiers, the runtime updates, the default policy and the clock question are what candidates describe; the exact API, the numbers and the shared-capacity stage are ours.

How this round compares with other companies' versions, and what every version grades: the AI coding interview guide.

Frequently asked, briefly answered

Which Snowflake rounds allow AI?

None, by Snowflake's published rule: its careers blog post of January 20, 2026 says all candidates do coding interviews without any coding or AI assistants, and rules out AI in assessments and take-homes too. Two candidate reports, one each, describe exceptions in late September 2026. A software engineer technical phone screen: sixty minutes in CoderPad, Python, AI allowed, with the recruiter framing the evaluation as how you gather requirements, test and debug. And an in-person round in an AI Engineer onsite, called AI Augmented coding in that report: bring your own laptop with any assistant preinstalled.

What was the task?

A rate limiting service in both candidate reports. The phone-screen prompt, in the candidate's words: different clients have different tiers such as free, pro and enterprise; the limits for each tier can be updated at runtime without restarting; a request carries a client identifier and the service enforces the tier's limit; over the limit, reject. Spoken addition: a client with no tier, or a broken configuration, falls back to a global default policy.

What did the follow-ups ask?

In order, from the phone-screen report: why this algorithm and the pros and cons of the alternatives; tests that prove it runs; how you test the refill when the real clock is too fast between calls (inject a clock, or sleep); and how a single in-memory instance evolves into a distributed cluster. The onsite report adds: how you prompted, reviewed and tested what the assistant wrote.

Where did the reported candidate lose points?

Two lessons the candidate wrote down afterwards: raising a tier's limit does not add tokens to existing buckets, capacity is only the ceiling; and refill is elapsed time times the refill rate, not times the capacity. They finished the implementation and the tests and ran out of time before the distributed-systems follow-up. Rejected.

Does the assistant write the code?

Under Snowflake's published rule there is no assistant in any coding interview. In the reported AI Engineer onsite round it may: the candidate still has to explain the algorithm chosen, the alternatives and the trade-offs, then walk through how they prompted, reviewed and tested. The phone-screen report says only that AI was allowed, not whose assistant it was or whether it could write into the code.

Practice problems tagged for Snowflake

Browse the catalog and open the Snowflake section. No login required to look; sign in when you want to solve one.