I am not going to repeat what one of the candidates said in March 2022 from Austin, TX. It was my exact same experience.
The technical screening was good.
The OO Design was poorly explained. I have a strong feeling this person had little to no real programming experience, since he was not following what I was explaining to him, but he kept on insisting on asking for meta trace, which was exactly what I was doing in terms of objects, methods, and the call chain.
The third round, technical deep drive. I explained and answered everything about the architecture I had at hand. They probably wanted me to have a built-in Google search; I'm not sure. I am guessing this was the round that wrecked me.
The final round with the hiring manager was a bit weird. The manager asked fewer questions and made me ask more, and explained a lot, which was indeed helpful. But it was weird that most of that hour was me interviewing him.
And in two working days, I got a rejection.
DraftKings' interview was one of those interviews where you have no clue what went wrong.
Robot Restaurant for OOD: the one complex system you had worked on for a deep dive and a behavior round.
The following metrics were computed from 36 interview experiences for the DraftKings Senior Software Engineer role in United States.
DraftKings's interview process for their Senior Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for DraftKings's Senior Software Engineer interview process in United States.