First was a coding invitation, then a recruiter phone screen.
After that, I was scheduled for a technical phone round.
The interviewer joined late at first, and due to network issues, we were delayed by a few more minutes.
After we started, the interviewer asked to design a couple of features of their application (DS, Algo) and then added a couple more functionalities.
I was able to get all questions.
In the end, I was implementing the last feature, and the interviewer rushed me, saying that I only had a few minutes left (basically my interview time just got shorter because the person arrived late, something that was not my fault).
I somehow managed to miss a part of the feature, but the interviewer didn't ask me to try to implement it, so I didn't stress out.
I was later rejected, saying that the last part which I couldn't implement was crucial and that is why they rejected me. BS.
They are completely binary in their decision-making, and the fact that they do not clarify things that matter to them the most is frustrating.
Design features of DraftKings contests.
The following metrics were computed from 73 interview experiences for the DraftKings Software Engineer role in United States.
DraftKings's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having good feelings for DraftKings's Software Engineer interview process in United States.