Pretty fun interview process if you like write code and doing clever design. Started with a remote coding exercise ... not homework style ... an engineer is with you online. The questions very fairly simple loop manipulation and basic data structures. Next came a half day interview in their office that involved a 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 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 a abrupt. I was reject the next day. They told me that they had a feedback session and I did well on code and the personal stuff but didn't fumbled (no pun intended) the OO interview to point where it is a NO. I mostly agree ... 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 reject but it was a good experience. I would have accepted an offer without hesitation. Interestingly enough, they help 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 the OO design.