Datadog Software Engineer Phone Screen Questions
5+ questions from real Datadog Software Engineer Phone Screen rounds, reported by candidates who interviewed there.
What does the Datadog Phone Screen round test?
The Datadog phone screen typically lasts 45-60 minutes and evaluates core Software Engineer fundamentals. Candidates should expect 1-2 algorithmic problems, basic system design discussion at senior levels, and questions about relevant experience. The goal is to confirm technical competence before bringing candidates onsite.
Top Topics in This Round
Datadog Software Engineer Phone Screen Questions
Two classic problems The following content requires a score higher than 188. You can already view it. 1. Given a `bucket_size` and a `bucket_width`, and a set of input numbers, return the number of nu
## Problem "Mado" means window in Japanese. Given an `m x n` integer matrix and a window size `k`, compute the sum of every valid `k x k` submatrix. Return all sums in a result matrix of size `(m-k+1) x (n-k+1)`. Optimize beyond the naive O(m * n * k^2) approach. ```python def mado_sum(matrix: list[list[int]], k: int) -> list[list[int]]: ... ``` ``` Input: matrix = [ [1, 2, 3], [4, 5, 6], [7, 8, 9] ] k = 2 Output: [ [12, 16], # top-left 2x2: 1+2+4+5=12; top-right: 2+3+5+6=16 [24, 28] # bot-left: 4+5+7+8=24; bot-right: 5+6+8+9=28 ] ``` ## Follow-ups 1. Describe the 2D prefix sum technique. What is its time and space complexity? 2. How does your approach handle matrices where `k > min(m, n)`? 3. What if instead of sum you need the maximum value in each window? How does your approach change? 4. Extend to a 3D tensor with window size `k x k x k`. How does the prefix sum generalize?
## Problem Simulate a change (otsuri) dispenser that returns optimal coin combinations for a given amount. ## Tags greedy, dynamic_programming
Datadog SWE Phone - Total File Size
## Problem Calculate the total size of files in a directory tree, recursively summing nested folder sizes. ## Tags recursion, binary_tree, hash_table
Datadog SWE Phone - Word Pattern
## Problem Determine if a string follows the same pattern as a given word pattern using a bijective character-to-word mapping. ## Likely LeetCode equivalent LC 290 - word-pattern ## Tags hash_table, strings
What to Expect in the Datadog Phone Screen Round
The Datadog Software Engineer Phone Screen round has a specific calibration purpose distinct from other rounds in the loop. Across 5+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Phone Screen round at Datadog show recurring patterns in difficulty and topic distribution. The Phone Screen round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Phone Screen Round Timing and Format
The Phone Screen round at Datadog typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Datadog Software Engineer Phone Screen commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 5 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access