I was originally reached out to by a recruiter.
I went through the whole process, and the feedback was they'd like to "hire me" but not as a Senior role. What that meant was the recruiter would spend the next couple of days "looking for a role for me." (shocker, it didn't exist).
I was then reached out to, saying they didn't have a role for me. Oddly enough, literally two days later, DK posted a role for an iOS dev.
I reached out to the recruiter, and they let me know this was exactly what they were referring to. Not sure why I had to reach out to them, though, if they were looking for a role for me.
Anyways, long story short, they made me wait an additional two weeks to be told they went a different route.
Throughout the waiting process, the recruiter would never reach out unless I did, or tell me they would a certain day with no follow-up, which felt odd because they originally reached out.
Honestly, the original process wasn't horrible, but they really need to work on this process and not lead people on. A recruiter should NEVER tell a candidate they'd like to bring them on when they have zero say.
Typically, interviews that people have mentioned involve two stages.
The first stage is a technical interview for an hour. The second stage is an all-day, 3-hour interview. Some of these interviews are cultural, followed by technical discussions.
The following metrics were computed from 1 interview experience for the DraftKings Senior iOS Developer role in United States.
DraftKings's interview process for their Senior iOS Developer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for DraftKings's Senior iOS Developer interview process in United States.