2025–2026 Datadog AI Coding Interview (Code Review and Feature Development), Experienced SWE Onsite / Phone Screen: 5 Experiences
- Company
- Datadog
- Reports
- 5 interview reports
- Level
- Full-time
- Stages
- Onsite
Datadog's AI coding interview comes in two shapes in these reports: reviewing a large pull request with AI help, or building a small client with your own AI tool. The Snowflake query client shows up most, and candidates wrote more about setup trouble and follow-up questions than about the code.
Coverage: 4 experienced full-time SWE onsites, interviewed January–September 2026 and reported April–September 2026 · plus 1 full-time phone screen whose hiring level isn't stated, kept in a separate supplement (reported November 13, 2026; its header lists a July–September 2025 interview season) · AI-assisted code review and feature development rounds only · These accounts don't establish the internship environment
What came up
Three of the four experienced candidates built something with AI help, and one reviewed a Python change. Two of the builds were a Snowflake query client. None of the four names a Python application framework.
| Topic | Reports | Most recent report |
|---|---|---|
| Python PR review with AI help | 1 of 4 | July–September 2026 interview (reported Sep 4, 2026) |
| AI-assisted implementation | 3 of 4 | April–June 2026 interview (reported May 14, 2026) |
| Follow-up questions after the first version | 3 of 4 | April–June 2026 interview (reported May 14, 2026) |
| Snowflake query client | 2 of 4 | April–June 2026 interview (reported May 14, 2026) |
| Dependency or package setup problems | 2 of 4 | April–June 2026 interview (reported Apr 27, 2026) |
These counts cover the 4 experienced reports. A candidate can appear in more than one row.
Questions we found
AI Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Review a Batched Processor Pull Request | 1 report | July–September 2026 (interview period); Sep 4, 2026 (report date and FastPrep history) |
| Build a Snowflake Query Client | 2 reports | Reports: April–June 2026 (interview period), May 14, 2026 (report date); January–March 2026 (interview period), Apr 30, 2026 (report date). Additional FastPrep history: Jul 23, 2026; Jun 5, 2026. Supplement report: Nov 13, 2026 (report date; header lists July–September 2025) |
One experienced candidate described the AI round and their Java setup without naming the task. Additional FastPrep dates and the supplement report don't add to the counts above.
4 detailed candidate timelines from the AI rounds
01: A Python PR with a missing fallback
Interview period: July–September 2026 · Report date: September 4, 2026 · Role: Full-time SWE · Stage: Onsite
The candidate reviewed a large PR for a Python application that failed under heavy load. The change replaced one-at-a-time processing with batches of 40 requests. The original synchronous processor was still in the repository.
They found two concrete issues in the batched processor review:
- If the batch processor couldn't be created, the new code returned
Noneinstead of falling back to the existing synchronous processor. - The PR claimed capacity of 6,000 requests per second per instance, while the README described peak demand of 8,000 per instance.
The candidate stressed how big the PR and its documentation were. In their account, AI was expected to help find and rank the critical bugs, with the important suggestions checked against the code. Python is explicit; the framework and dependency list aren't disclosed.
02: A query client, with secrets and batching as follow-ups
Interview period: April–June 2026 · Report date: May 14, 2026 · Role: Full-time SWE · Stage: Onsite
The task was to build a Snowflake query client: connect to Snowflake, start a query and check its status. The candidate used Claude Code and described the first implementation as quick.
Follow-ups covered secret management and batching. The report doesn't give the programming language, a Python framework or the exact batching requirement.
03: Java in a self-configured environment
Interview period: April–June 2026 · Report date: April 27, 2026 · Role: Full-time SWE, moving from a current job · Applied: Referral · Stage: Onsite · Result: Rejected
This candidate could use their own AI tool, any one they liked, and shared their screen so the interviewer could watch how they worked with it. The problem itself wasn't hard: the AI wrote the code in one pass. Dependencies were what slowed them down, and they were stuck on environment setup for a while. They came away feeling that solving the problem wasn't the real test, but couldn't tell what the interviewer wanted to see.
In a May 7 clarification, the author said they used Java in their own, self-configured environment. The actual coding task wasn't disclosed, so this account shows one candidate's setup without identifying a Python framework.
The candidate later reported a rejection. System design had gone well; feedback on the AI round was "mixed" and mentioned follow-ups that weren't covered. They had finished ten minutes early and answered both follow-ups the interviewer asked, and felt any further ones should have been asked too.
04: Package compatibility consumed most of the round
Interview period: January–March 2026 · Report date: April 30, 2026 · Role: Full-time SWE · Stage: Onsite
Another candidate got a Snowflake client task and could use local AI tools. Package compatibility problems took more than 30 minutes. They connected successfully with about ten minutes left and had little time for follow-ups.
In an author reply, they listed client extensions the interviewer had suggested: pagination, multiple tenants, authentication, long-running queries, recovery, cancellation and throttling. These were possible directions, not features they finished. The author thought the task was about a query client rather than building a backend service.
Neither the original post nor that clarification names a Python framework.
Supplement: hiring level not reported
This full-time report doesn't say whether the candidate was experienced, new grad or something else, so it sits outside the counts above.
05: A Snowflake API client on a phone screen, finished too fast
Report date: November 13, 2026 · Interview season stated in the report header: July–September 2025 · Role: Full-time SWE, level not stated · Applied: Referral · Stage: Technical phone screen · Result: Rejected
- The round ran on a website that opens a virtual environment much like VS Code. Any AI tool was allowed, including a command-line coding agent.
- The task was to implement read and write operations against a Snowflake API and handle errors, close to Build a Snowflake Query Client.
- The candidate let the AI write it. It was done very quickly, and then they weren't sure what to do next while the interviewer kept asking follow-up questions.
Looking back, the candidate would rather have added features one at a time and kept control of the pace. As in reports 02 and 03, the first version came quickly, and follow-ups filled the rest of the round.
Python framework status
The full-time reports give useful task mechanics, but they don't establish FastAPI, Flask or Django as the interview framework. The supplement report doesn't name one either. The SWE intern framework also remains unconfirmed in the material available so far.
An intern discussion contains an unanswered question about FastAPI. It doesn't include a candidate's confirmation after finishing the round.
The FastAPI and pytest labels in the linked FastPrep practice workspaces describe the exercise setup we authored. They don't identify dependencies supplied by Datadog. The original repositories and their dependency manifests were unavailable.
Patterns across the reports
These cover the 4 experienced reports.
-
The Snowflake query client. Reports 02 and 04 both got a Snowflake client task. Report 02's follow-ups were secrets and batching; report 04's interviewer suggested pagination, multiple tenants, authentication, long-running queries, recovery, cancellation and throttling as directions.
-
Setup, not code, took the time. Reports 03 and 04 both lost time to dependencies or package compatibility, more than 30 minutes in report 04. Report 03 said the AI-written code itself came in one pass.
-
Follow-ups after the first version. Reports 02, 03 and 04 all describe follow-ups once a first version existed: secrets and batching in 02, two follow-ups in 03 whose coverage the feedback questioned, and suggested client extensions in 04, where little time was left.
Keep practicing
- Build a Snowflake Query Client: the client task from reports 02, 04 and 05.
- Review a Batched Processor Pull Request: the PR review from report 01.
- Datadog project-coding questions: AI project workspaces for Datadog (sign-in needed).
- 2019–2026 Datadog SWE Intern OA / Interviews: 23 Experiences: the intern cohort, covered separately.
- Datadog interview guide, Datadog hiring insights and the interview experience feed.
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.
- 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.