Candidates applying for Senior Applications Developer roles take an average of 60 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at DraftKings overall takes an average of 22 days.
Common stages of the interview process at DraftKings as a Senior Applications Developer according to 2 Glassdoor interviews include:
Skills test: 33%
Presentation: 33%
Phone interview: 33%
Here are the most commonly searched roles for interview reports -
Received a very informal email to take a coding exam on HackerRank. The “exam” was a fairly simple scenario with several confusingly worded requirements that tested ability to process a text file of varying inputs and CRUD, sort, and print out the results. Easy enough. Completed the exam without any issues. All tests passed. Feeling good about the results except that was over 21 days ago and I’ve received ZERO communication back from them. I can only assume my solution wasn’t accepted but the lack of response is a bit unprofessional.
Interview questions [1]
Question 1
Simple CRUD, print over a collection. Test entirely unrelated to job listing requirements.
Thank you for taking the time to write a review. We regret the lack of follow up after the HackerRank test. Our talent acquisition team prides itself on responding to every candidate in our interview process. We'll review our records and make sure anyone taking a HackerRank test receives correspondence from us.
Jason
I applied online. The process took 2 months. I interviewed at DraftKings in Dec 2017
Interview
The company is basically a pretty girl at a bar who will say 'no' to you when she finds out that you used to live in a trailer. She'll never know or care what she's missed -- another guy will make sure of it.
The test they administer has nothing to do with competency and everything to do with compliance and conformity. I know because I'm very competent, but I failed the test because, as I said, it measures whether you hate being tested. I cannot stand being tested, largely because, especially for live-action tests, no adjustments are made at all for someone who doesn't like it when people watch him code. And when those people are looking to eliminate you from the process.
That is literally the test: Whether you can code normally when someone is watching you from the controls of the mechanical bull, trying to throw you off. What they will say the test is, is a simple object-oriented class and methods. A customer has multiple "line ups" and each lineup has a total score and a player list of player ids. When a player scores, you will have to adjust the total score of that player in each lineup. Similarly, return in another method the top customers by total score. That is, return the top 20 customers by the max scores in their lineups.
They also really insufficiently failed to make me WANT to take the test. If you're in the job market, you know that EVERY company wants you to take its test, and NO company wants to acknowledge that your time is being heavily taxed, anywhere from one half-hour to four hours at a time. When I asked for a salary range for the position, I was only told it was "competitive." They did not make it easy for me to look forward to being tested, because they completely failed to understand why anyone would not like to be tested.
They looked at my resume, but not at my github. I have been coding for over 20 years. I am obviously sore because I really wanted the job and I truly thought that I would be a good fit. I'm a punter, too, so I would have been paid for doing what I love to do.
Interview questions [1]
Question 1
The process takes almost two months. The email said, "If you have any questions, don't hesitate to ask" and the next email (a month later) said "Sorry, I didn't see your reply, here are the answers to your questions."
The questions were what is the salary range, and do I get intellisense. The answers were "Competitive" and "no."