A good, relaxed place to work with bad on-call
A good, relaxed place to work with bad on-call
- Nice, relaxed people.
- Slightly above average compensation.
- 35 hours a week, other than on-call.
- Very high WFH flexibility.
- Fun products to work on sometimes.
- A few really talented engineers that stay for the product.
- Low pay for high performers.
- Work is not super challenging.
- Some managers don’t seem to put in effort toward the growth of those under them.
- ONCALL: The oncall is pretty unreasonable here. There is not enough focus on reducing unnecessary pages in basically all teams. Oncall should really be paid given this.
Make on-call paid, so those who are stuck on it don’t see it as much of a negative.
Was this helpful?
DraftKings Interview Experiences
Software Engineer
Bad. I have to say that HR is really inefficient. I got the feedback for the onsite interview after a month, after I emailed them three times! It's really unfair that others' questions were about restaurant design, but mine was a new one!!! The emplo
Software Engineer
I was called for a technical phone interview in which I was asked to write code for a question comparing a few user's total scores and then give each user a competitive rank. The interviewer asked me to talk through the code as I wrote it. Part of t
Software Engineer
There was one question to solve for 90 minutes on the HackerRank coding question. I passed all test cases but received a rejection email a week or two after.
Software Engineer
United StatesDecember 19, 2019Bad. I have to say that HR is really inefficient. I got the feedback for the onsite interview after a month, after I emailed them three times! It's really unfair that others' questions were about restaurant design, but mine was a new one!!! The emplo
Software Engineer
United StatesSeptember 1, 2015I was called for a technical phone interview in which I was asked to write code for a question comparing a few user's total scores and then give each user a competitive rank. The interviewer asked me to talk through the code as I wrote it. Part of t
Software Engineer
United StatesDecember 29, 2022There was one question to solve for 90 minutes on the HackerRank coding question. I passed all test cases but received a rejection email a week or two after.
