Datadog · OA → Phone screen → Onsite
In process2019–2026 Datadog SWE Intern OA / Interviews: 23 Experiences
Two reports put a 15-minute project discussion inside a 75-minute technical round.
Coverage: SWE internships and co-ops · OA, phone screens, technical finals and a take-home · January 2019–October 2026, plus one undated report for the May–August 2025 cohort · New York where specified.
What came up
Nine of these 23 experiences describe coding questions, while four mention a resume, previous project or past-work discussion. Graph topics range from BFS and DFS to a shortest-path task.
| Topic | Reports |
|---|---|
| Coding questions, including reports without named topics | 9 of 23 |
| Resume, previous projects or past work | 4 of 23 |
| Graph traversal or shortest paths | 3 of 23 |
| Hash maps or log aggregation | 2 of 23 |
| SQL | 2 of 23 |
| Arrays | 1 of 23 |
| Tries | 1 of 23 |
| Website-monitor project | 1 of 23 |
A candidate can appear in several rows. One 2022 OA account also mentions multiple-choice questions.
Questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| HTTP Log Queries | 1 report | May 26, 2019 (report date and FastPrep history); January 2019 (interview) |
| Minimum Latency Server Path | 1 report | May 26, 2019 (report date and FastPrep history); January 2019 (interview) |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| Why Datadog? | 1 report | August 2025 phone screen |
Project Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Console Website Monitor | 1 report | May 26, 2019 (report date and FastPrep history); January 2019 (interview process) |
The three linked tasks come from the same 2019 candidate. Eight of the nine coding accounts stop at topics, difficulty levels or results, without giving an identifiable prompt. Neither 2022 SQL account gives the actual query.
23 candidate timelines, loops, and screens
01: A quick OA and behavioral response, then a final-round wait
Interview period: September–October 2026 · Role: Summer 2027 SWE intern applicant
The candidate was still asking about the OA on September 29. By October 8, they reported hearing back a day after their OA and a day after the behavioral round. The recruiter had also confirmed advancement verbally near the end of the call.
On October 16, they said the final had been two days earlier. The interviewer had suggested that next steps would arrive within two weeks.
02: A technical interview about a week before October 20
Interview period: Approximately mid-October 2026 · Role: SWE intern applicant
In an October 20 reply, this candidate confirmed taking the technical interview about a week earlier and was still asking about results.
03: Verbal advancement followed by an email
Interview period: October 2026 · Role: SWE intern applicant in a summer-2027 discussion
The recruiter said during the call that the candidate would advance. A confirmation email arrived a few hours later.
In a separate October 16 update, the same candidate said their final had been a few days earlier and they were still waiting.
04: About two weeks from OA to the behavioral invitation
Report date: October 9, 2026 · Role: SWE intern applicant in a summer-2027 discussion
This candidate reported roughly two weeks between the OA and advancement to the behavioral stage.
05: A 60-minute HackerRank OA for the winter term
Interview period: August–September 2026 · Role: Winter SWE intern applicant
The candidate received a 60-minute HackerRank assessment on August 31 and confirmed that the application was for the winter term. On September 10, they described their own OA as easy.
06: A rejection email one week after the final
Report date: October 17, 2025 · Role: Winter 2026 SWE intern applicant
The candidate said a rejection email arrived one week after the final interview.
07: One full OA test set and one partial set
Interview period: September 2025 · Role: 2026 SWE intern applicant · Result: Rejected after OA
This returning applicant received an email advancing them to the OA. In a September 15 post, they reported passing all 15 tests on one question and 10 of 15 on the other. The remaining hidden cases failed.
A September 19 update confirmed rejection after the OA. The candidate did not describe either task or their algorithm.
08: No advancement to team matching
Interview period: September 2025 · Role: Winter 2026 SWE intern applicant · Result: Rejected before team matching
On September 15, the candidate said they had not advanced to team matching. In a September 17 reply, they gave seven days as their response time.
The post does not establish which event started that seven-day wait.
09: Winter 2026, with overlapping descriptions of a 75-minute final
Interview period: August–September 2025 · Internship term: January–April 2026 · Location: New York City · Result: Offers reported
Two anonymous reports may describe the same application cycle, so this is one conservative entry. Their differences remain visible below.
The report with exact dates
- Applied August 18.
- Took a 60-minute OA on August 19, described as two LeetCode medium questions.
- Had a 30-minute behavioral phone interview on August 25, including an overview of a previous project.
- Completed a 75-minute final on September 2: a project overview, two technical questions and a bonus.
- Received an offer September 8.
The other winter report
The August OA was also 60 minutes, but the author called its questions easy. The 30-minute phone round covered the resume and Why Datadog?
The September final lasted 75 minutes. It included a 15-minute project discussion, an array question, a DFS/BFS question and a bonus involving tries. The author reported a September offer and a US$7,500 housing stipend.
The two submissions also differ on hourly pay and work arrangement. Neither gives an identifiable coding prompt.
10: Two OA mediums, a recruiter call and an offer
Interview period: August–September 2023 · Role: Summer 2024 SWE intern · Location: New York · Result: Offer
The candidate had previously been contacted by a recruiter on LinkedIn, then applied on opening day.
HackerRank OA
There were two medium questions in a 60-minute assessment. The candidate said they passed every test in under 30 minutes.
Recruiter and technical rounds
An August 31 HR call ended with verbal confirmation that they would advance. A later update described the full sequence as OA, recruiter phone call and a 75-minute technical interview. The candidate felt the technical questions were manageable with LeetCode-medium knowledge, but did not give the prompts.
On September 14, they reported being invited to a results call. A September 21 update confirmed an offer, and the candidate described the response time as about a week. The posts measure timing from different events, so they do not establish one exact final-interview date.
11: An easy and a medium on the OA, then an offer
Interview period: August–September 2023 · Role: SWE intern · Result: Offer
This candidate applied without a referral. On August 26, they said their OA contained an easy and a medium LeetCode question, with the phone screen still ahead.
By September 18, they reported an offer. They described the final questions as LeetCode mediums and recommended solving at least two. That recommendation does not establish how many questions were in their own final.
12: A referred applicant described the final they were expecting
Report period: September 2023 · Role: Summer 2024 SWE intern applicant
The candidate applied with a referral and described an OA followed by a recruiter phone call.
They said the upcoming final would be 75 minutes, with an in-depth discussion of a personal project and two LeetCode-style questions. This was the format they were expecting; the post does not describe a completed final or an outcome.
13: A results call three days after the final
Interview period: October 2022 · Role: Fall 2023 SWE intern · Result: Offer accepted
The candidate heard back three days after the final to arrange a call in the following days. They later confirmed that the call led to an offer and accepted the fall-2023 internship.
14: A SQL question alongside coding and multiple choice
Interview period: September 2022 · Role: 2023 SWE intern applicant · Platform: HackerRank
The candidate completed the OA but did not solve its SQL question because they did not know SQL. In a September 22 clarification, they described the other content as LeetCode medium coding and multiple-choice questions.
The SQL schema, requested result and coding prompts were not given.
15: Another candidate left the SQL question unsubmitted
Report date: September 27, 2022 · Role: SWE intern applicant in the same 2023-internship discussion
A different candidate said they had just taken the OA, were surprised by the SQL question and left it unsubmitted.
They did not describe its objective or their other questions. This establishes a second SQL sighting. Both query objectives remain unknown.
16: Roughly two months before recruiter contact
Interview period: January 2022 · Role: SWE intern applicant · Result: Rejected
In a January 26 update, this candidate reported rejection. They also said roughly two months had passed between submitting their resume and hearing from a recruiter.
17: Recruiter contact the day after submitting a resume
Interview period: January 2022 · Role: SWE intern applicant · Result: Rejected
This candidate said the recruiter contacted them one day after resume submission. They reached the final, initially posted while waiting, and later edited the update to report rejection.
18: Two final-round coding questions, with help on the second
Interview period: The week before January 19, 2022 · Role: SWE intern applicant · Result: Rejected
The candidate completed two coding questions within the interview time. They solved the first independently and needed interviewer help on the second.
A later update reported rejection.
19: An accelerated process and an offer a week later
Interview period: August–October 2021 · Role: Summer 2022 SWE intern · Result: Offer
The candidate applied in late August, interviewed in early October and received an offer about a week later. They said an Amazon return offer had accelerated the timeline.
20: A current intern broke one interview into three parts
Report date: October 5, 2020 · Role: Current SWE intern
The author described one round with approximately:
- Ten minutes on the resume and past experience.
- Fifty minutes for two easy/medium LeetCode-style questions.
- Ten minutes for the candidate's questions.
That adds up to about 70 minutes. The interview date and coding prompts were not given.
21: A September application and a later rejection update
Interview period: September 2020 · Role: SWE intern applicant · Result: Rejected
The candidate applied at the beginning of September and had an interview coming up by September 10. A September 29 update said the interview had not been bad, but they had been rejected.
22: HTTP logs, a server graph and a website-monitor take-home
Interview date: January 2019 · Report date: May 26, 2019 · Role: SWE intern, MS CS student · Location: New York · Result: Offer not accepted
Technical phone screen: 45 minutes on CoderPad
The candidate said this screen had no behavioral questions. It contained two coding tasks.
- HTTP Log Queries. Each request record contained an IP address, HTTP verb, status, response time, size and request time. Example requests included listing HTTP requests from the last two months or selecting status-200 requests. The interviewer repeatedly changed the query requirements and asked the candidate to discuss tradeoffs before implementing an approach. In a later reply, the candidate discussed binary search for a three-month time range and said they implemented hash-map aggregation by status and IP.
- Minimum Latency Server Path. Servers were labeled by IP address, and links had known transmission times. Given a start and end server, the candidate had to find the minimum-time route and show its path. A later reply names Dijkstra as the approach.
Take-home: Console Website Monitor
Build a console program that keeps monitoring website availability and performance. Users choose the sites and each site's check interval. The author clarified that output should show availability, maximum and average response time, and response-code counts for each site at a given reporting frequency. That output frequency is separate from the per-site check intervals.
The candidate used Go with a fixed number of goroutines and mentioned Scala/Akka as another option. They favored concurrency over a single-threaded implementation; the report does not say Go was required. They did not deploy the program and submitted it through the company’s own submission box.
CTO or technical-director conversation
The last conversation covered past experience. The candidate described the recruiter as responsive and the technical interviewer as knowledgeable. They received an offer but could not accept it because of visa issues.
23: Undated report with a project deep dive, hash maps and BFS
Interview date: Unreported · Internship term: May–August 2025 · Role: SWE intern · Location: New York City · Result: Offer
The sequence was OA, phone screen and a 75-minute technical interview.
The technical round included a 15-minute project deep dive and two LeetCode variations: one easy hash-map question and one easy-to-medium recursion/BFS question. The report does not give either task's objective.
The internship term identifies the cohort; it does not establish the interview date.
Patterns across the reports
-
Project discussion used part of the technical slot. The winter-2026 description in report 09 and the summer-2025-cohort account in report 23 each put about 15 minutes of project discussion inside a 75-minute technical round. The 2023 applicant in report 12 was told to expect a project discussion too, but did not report completing that final.
-
OA response times differed even within the 2026 discussions. Report 01 describes hearing back a day after the OA. Report 04 gives roughly two weeks from OA to behavioral advancement. These are two individual timelines, rather than one shared turnaround time.
-
A results-call invitation became an offer in two older accounts. Reports 10 and 13, from 2023 and 2022, both describe a call invitation followed by an offer confirmation. The 2026 applicants who were still waiting did not establish what their own next contact would mean.
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.