Four parts interview: Technical coding test in C# language. see questions below. Team dynamics, (behavioral) System Design: including OOAD exercise. Technical deep dive: impacts driven, opportunity and show case one project you worked on previously. Followed by a recruiter's debrief of a 2 minute call, which I was expecting to give me a decision, rather the recruiter just said we will let you know. They use HackerRank for everything. To be honest it's the worst tool and very unuseful for design interviews, rather than focusing on your approach, you bump into learning how to use the HackerRank drawing tool as its awful.
Draft Kings: Data structure and algorithms: refactoring and scalability and run time of code. Complete in Java or C#. Interviewer was nice, gentle, and helping out with hints with good communication skills. Hacker Rank: Customer Discounts Validation. Given objects of ICollection
Senior Software Engineering Manager- Team Dynamic interview: Introduced himself, and the company, teams he is managing, asked about my background, leadership capabilities, mentorship, problem handling in teams, teams learning capabilities. He also asked situation based questions like, What If scenarios? When did you went above and beyond, how did you handle if a team member is constantly lagging progress, how did you handle requests for immediate bug fixing in live products? Etc
Lead Software Engineer- Object Oriented Design interview: Designing a Restaurant order management system: given the waiters are Robots not humans. Interviewer presented with different scenarios, asked questions on my approach, and inquired about how to extend the design to add more capabilities like introducing a cleaning robots. What functions could be made common among waiters etc.
Software Engineering Manager- Technical Deep Dive Interview: Had a call: interviewer introduced himself. Then I started on a project of my own choosing to walk him through on the architecture and OOD design of the software. External tools used in the system, alternatives that could be used. Some of the challenges and bottlenecks of the system. Problems faced and how did you fix those. As my project was on a public cloud provider for most parts, I also had some custom code written with heavy usage of events handling by the cloud component, rather than hand built scalability, security, DR, or resilience etc. The interviewer didn't look satisfied, and was probably looking for me to build everything by a coding language.
14:30-14:45- Erin Kinback - Talent Acquisition Lead- Recruiter Debrief A two minute call with recruiter, she just asked about how was the process overall and if I had any questions. She informed me that it will take a week or so to accumulate the feedback from everyone. She will keep me posted.
The following metrics were computed from 1 interview experience for the DraftKings Lead Software Engineer role in Dublin, Ireland.
DraftKings's interview process for their Lead Software Engineer roles in Dublin, Ireland is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for DraftKings's Lead Software Engineer interview process in Dublin, Ireland.