DraftKings Software Engineer
DraftKings Software Engineer
Strong managers.
Great learning culture.
Well-established resources and processes.
Flexible work schedule/model.
Well-balanced on-call schedule.
Lots of engineer liberty.
Disconnect between executive management and development teams.
Fast-paced work.
Continuously listen to employees' concerns and respect all opinions, regardless of whether they are submitted anonymously or not.
Additional Ratings
Was this helpful?
DraftKings Interview Experiences
Software Engineer
Got reached out by a recruiter on LinkedIn. Initial online coding exercise for 90 minutes in Hackerank. Difficult: Medium-Hard. Got invited for an onsite interview. (In a week) Round 1 (1 hour): Algo/DS based. Round 2 (1 hour): OO design. Round 3 (
Software Engineer
Applied through campus recruiting. Heard back within a few days and a phone interview was scheduled the next week. First interview started with questions about personal background and experiences, and then quizzing on basic technical computer progra
Software Engineer
I applied through Glassdoor and was contacted by a recruiter within 24 hours. They asked some technical questions about Big O and object-oriented design, though they seemed more satisfied by naming buzzwords of the topics than doing a deep dive into
Software Engineer
Boston, Massachusetts, United StatesAugust 1, 2019Got reached out by a recruiter on LinkedIn. Initial online coding exercise for 90 minutes in Hackerank. Difficult: Medium-Hard. Got invited for an onsite interview. (In a week) Round 1 (1 hour): Algo/DS based. Round 2 (1 hour): OO design. Round 3 (
Software Engineer
Boston, Massachusetts, United StatesDecember 1, 2017Applied through campus recruiting. Heard back within a few days and a phone interview was scheduled the next week. First interview started with questions about personal background and experiences, and then quizzing on basic technical computer progra
Software Engineer
Boston, Massachusetts, United StatesMay 1, 2018I applied through Glassdoor and was contacted by a recruiter within 24 hours. They asked some technical questions about Big O and object-oriented design, though they seemed more satisfied by naming buzzwords of the topics than doing a deep dive into
