Datadog: • 2-3 days hybrid, team-by-team is flexible. Not everyone even spends the entire day in-office. • has 3-4 rounds of interviews. there's a 1 hour 'leetcode style' test with 2 'relatively easy' (per the recruiter) questions. Later if you are looking at roles with more coding expectations, there are 2 more coding specific interviews. There's then an onsite with the hiring manager, followed by another onsite which is a 'team matching stage' where you'll meet directly with several teams and just interact and then sort of make a selection of which team best fit you. • For non code focus role mostly in the infra org they will cut the 2 extra code rounds, and will substitute in a systems interview

seems reasonable

If Toby is still there we might be able to get some additional insight as well. Happy to make a connection if you want Zach (or anyone else, but most of you would know him already)

either him or sarang

Datadog coding stage: • they recommend spending up to 2 weeks (no more) prepping for the code interview stage, using this leetcode filter on mostly easy with some mediums • practice using CoderPad, which is what the interview is held on • verbalize a solution before starting to code, and explain choices as you write • if you realize there was a more optimal solution other than what you were doing, verbalize that for points in your favor • must finish both questions to pass this stage. first question is a warmup, leave plenty of time for the second • the interviewer will help provide feedback to kind of steer you, so pay attention to their feedback • they recommend you attend a weekly demo of datadog if you haven't used it much

2 weeks!

Definitely first time talking to a recruiter where they actually recommend pushing out the first stage 😄

I expect Klaviyo to be similar

Klaviyo?

Everyone

this is super helpful. thanks zach!

i am also talking to datadog. the loop for infra roles looks like this: • HM screen - 45 mins. if you pass... • 5 rounds, 1 x hr ◦ People management ◦ Delivery management ◦ Technical overview ◦ System Design ◦ Coding interview - tailored more to systems as opposed to feature development in terms of context