Datadog Interview Experiences

8 results

• 

  Reviewing an AI-Assisted Batching PRDatadog · Software Engineer · Senior+ · Onsite · Aug 2026

  In the code review round, I was given a pull request for an issue where a Python application was crashing under heavy load. The pull request changed the existing synchronous processor, which handled one request at a time, into a batched processor that handled 40 requests at a time. The repository still included the synchronous processor as a reference. However, if creation of the batched processo…

• 

  Datadog Account Executive interview: clear recruiter guidance with an uneven panelDatadog · Account Executive · Jul 2026

  The recruiter reached out and was helpful and transparent throughout. Before I spoke with a hiring team, I received a PDF explaining each stage and what I needed to prepare. That made the process predictable, and I did not feel as though I was guessing what would happen next. After the recruiter call, the process followed a standard pattern: an early phone or screening stage and then video interv…

• 

  Datadog Account Executive interview: sales process and a mock cold callDatadog · Account Executive · Jul 2026

  The process felt organized from the beginning. I started with a recruiter conversation and then met hiring leaders. In those calls, it seemed they were comparing my experience with what they needed in an Account Executive: my approach to sales, how I described my impact and how well that experience would translate to their environment. The hiring-manager questions were more pointed. I explained m…

• 

  Datadog Software Engineer HackerRank and final technical interviewDatadog · Software Engineer · Online Assessment · Jul 2026

  Rejected

  The process felt smooth and standard. It began with a HackerRank-style online test containing two LeetCode-like questions. Next came a roughly half-hour recruiter call focused on fit and the usual recruiter topics. The final technical stage lasted about an hour. It included more medium-hard LeetCode-style questions and a separate behavioral and HR block within the overall stage. The recruiter and…

• 

  Datadog Solutions Engineer interview: presentation cancelled after the role was filledDatadog · Solutions Engineer · Online Assessment · Jul 2026

  Rejected

  I reached the presentation stage after initial screens and a HackerRank assessment. It was due to be in person, and I put considerable effort into preparing something I felt confident presenting. Late the day before, a message said the role had already been filled and I didn't need to come in. The timing felt awful after all the preparation I'd done that week. Later, HR said they appreciated my p…

• 

  Datadog Software Engineer Interview Experience: manager roleplay after recruiter screenDatadog · Software Engineer · Jun 2026

  Rejected

  I applied through the job portal and a recruiter contacted me for a brief video call about my background, salary expectations, and basic fit. The next stage was more detailed: I met with two managers who dug into my experience. Near the end of that discussion, they switched to a practical roleplay scenario to test my hands on skills. It was direct and focused on what I could do rather than only w…

• 

  Datadog Solutions Engineer Interview Experience: Deep technical final stageDatadog · Solutions Engineer · HR Screen · Jun 2026

  Rejected

  I went through a standard multi-round Solutions Engineer process. It opened with an English-language HR conversation about who I was, whether I knew Datadog, and my salary expectations. Next came an online HackerRank test with prompts on SQL, Linux, containers, APIs, and installing and setting up a Datadog agent. I then met the hiring manager for behavioral questions with some technical content b…

• 

  Matching Queries Against a Log StreamDatadog · Software Engineer · Technical Screen · Jun 2026

  The first-round problem was query and log stream matching. I was given a stream containing two message types: Q: xxx was a query. Each query needed a unique ID, and I had to output an acknowledgment. L: xxx was a log. For each log, I had to output the IDs of all queries that it completely matched. The example input was: The expected output was: My approach was to use a HashMap