Pretty fun interview process if you like to write code and do clever design. It started with a remote coding exercise, not homework style; an engineer is with you online. The questions were very fairly simple loop manipulation and basic data structures. Next came a half-day interview in their office that involved more coding, an OO design challenge, and some softer "get to know you" interviews.

I got a real sense of the environment. They care about your foundation in computer science at a practical level and ability to work independently on projects (design). The interviewers were all very nice but a little bit direct, which some could take as abrupt.

I was rejected the next day. They told me that they had a feedback session and I did well on code and the personal stuff but fumbled (no pun intended) the OO interview to the point where it is a "no." I mostly agree; the feedback is fair, but I wish they had more tolerance for a learning curve on that because I don't get a chance to do much OO in my current job. It's hard to get rejected, but it was a good experience. I would have accepted an offer without hesitation.

Interestingly enough, they helped me get another job. I had an interview with a different company later that week that I would not have passed if DraftKings had not asked me the OO question and got me thinking about OO design.

A logic-oriented coding challenge to evaluate player lineups.