Cold-called by a recruiter who turned out to be the recruiting manager. Ordinarily, I would not engage, but he had a couple of smart things to say, and I've seen DraftKings everywhere lately. I became extremely interested after learning about the company and hearing about the engineering team/projects. The recruiter then asked a few surprisingly deep technical questions and asked if I would do a technical phone interview with one of their engineers.
The phone interview was a relatively simple coding exercise. The recruiter called an hour after, gave me feedback, and asked if I would like to interview at their office. He explained what to expect, and I interviewed a week later.
Three interviews:
I felt good about the coding exercise but knew I bombed the design interview. The recruiter came in at the end and gave me feedback that they weren't moving forward, with good reasons (did I mention that I bombed the design interview?). I was disappointed but appreciated the candid feedback. The entire process was really well organized. Everyone was responsive. It's clear that they hire a lot of really smart people and care about their product. I'll study up and try again next year.
Tell me about a design decision that you would not make again and why.
The following metrics were computed from 15 interview experiences for the DraftKings Senior Software Engineer role in Boston, Massachusetts.
DraftKings's interview process for their Senior Software Engineer roles in Boston, Massachusetts is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for DraftKings's Senior Software Engineer interview process in Boston, Massachusetts.