The process started with a take-home coding challenge, which was actually an absolute blast compared to others I've had in the past.
The in-person interviews were fairly detailed, asking about my experience, having me do a pair programming exercise (which was tough), and some architecture diagramming.
Ultimately, it came down to not having an overwhelmingly large amount of non-Kubernetes experience. They do have pretty high standards there; I've become friendly with some of the SREs and seen what's expected of them.
I won't lie when I say I was devastated when I found out I didn't get an offer, as I thought things had gone wonderfully. It very much felt as though 8/10 things were a perfect fit. I've since gotten over it and been able to reflect positively on what was an intense but awesome interviewing process.
What are some reasons you wouldn't want to use Kubernetes?
The following metrics were computed from 2 interview experiences for the Datadog Senior Site Reliability Engineer role in New York, New York.
Datadog's interview process for their Senior Site Reliability Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Datadog's Senior Site Reliability Engineer interview process in New York, New York.