I had an initial recruiter screen lined up but had to move it due to schedule conflicts. I emailed my recruiter days in advance and never heard back.
Weeks pass. I decide that I'd try to connect by messaging a couple of DraftKings recruiters that had reached out in the past (one being the tech recruitment manager), but never hear back from either.
A couple of weeks pass. I hear from a random DraftKings talent sourcer on LinkedIn. I explain what had happened and don't even hear a slight apology (huge red flag looking back).
After this call, she sends me a canned HackerRank where the only JavaScript code is Node (which I honestly have no clue how a stdout works in). The problem is a standard “build a RESTful endpoint” problem but with an algorithmic twist for a final part.
Needless to say, the front end position I had applied to certainly had absolutely nothing to do with this. I got a canned rejection letter afterward. Honestly, looking back at this after the offers I received from other large Boston companies (higher offers than DraftKings would have provided too!), I will never be considering this company again and will tell my friends from prior roles.
Report the organizational hierarchy of an org chart that you build out.
The following metrics were computed from 36 interview experiences for the DraftKings Senior Software Engineer role in United States.
DraftKings's interview process for their Senior Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for DraftKings's Senior Software Engineer interview process in United States.