The interview process is split into a couple of steps.

First, there is a call with the Recruiter, discussing motivation, previous experience, expectations, etc. This is also a good opportunity to learn more about the company from someone inside.

After this step, there is a Technical Interview. In my case, it was a call with two engineers, talking about previous experience related to the position I applied to, with a couple of related questions as well. Then, we ran through a GitHub ticket, checking whether I could understand the problems and code, and whether I was able to talk about it with the engineers.

The next step was split into three calls:

• Behavioral: Questions related to project management, SDLC, and more soft-skills oriented topics.
• Design: CI and delivery pipeline analysis, looking for bottlenecks and improvement ideas.
• Manager: A call with the engineering director, discussing the challenges the person in this position will face, possible approaches, etc.

On every step, there was always time to ask questions. Everyone was very eager and willing to answer as best they could.

Due to the fact that there are a couple of calls in the process, scheduling everything can sometimes be challenging, especially if you are based in Europe, when some of those calls require people from Datadog HQ to participate.

Q: Describe the typical SDLC?

Q: How would you look for bottlenecks in the release process?

Q: What was the biggest challenge in your career and what did you learn from that?