FanDuel Devops Engineer Interview Questions
& Process

So I was on a call for this job, and the interviewer just hung up on me within the first 5 minutes. I tried calling back, but they didn't pick up. They emailed later saying their phone was acting up, but I know I left a voicemail. It was pretty disrespectful.

First, I had to answer three pre-interview questions: What do you enjoy about DevOps?, Tell me about a project or piece of work you are most proud of (with lots of detail on tools, techs, outcome, challenges, and how you overcame them), and What are you looking for in a new role?. Then, there was a 1 hour phone interview with someone from the DevOps team, who asked general questions about my experience and expertise. It was very friendly and relaxed. After that, I had a ~4 hour in person interview at their office. Everyone was super friendly and really seemed to love working there. The three hours were divided like this: 1) A general technical chat with the DevOps manager and a team member. 2) Technical questions and a technical debugging test. 3) A soft skills chat, asking things like what you would do in x situation, or asking me to talk about a time I argued with a colleague. Again, it was all very friendly and relaxed. The technical test was the part I had an issue with. It involved debugging a test nginx server with a python application while someone watched my every move. I assumed the test would be on something I had experience with since I got the interview, but it wasn't. So they shouldn't expect someone to ace a test on something they know you don't have experience with. It also felt more like a python-specific SysAdmin test than a DevOps one, so it wasn't really suitable. Since this seemed to be the reason I didn't get an offer, I'd recommend expecting to be tested only on what they actually use and hope it aligns with your skills. They also seemed unhappy that my first instinct for debugging an unfamiliar application was to Google it and look at StackOverflow. I'm not sure what else they were expecting! Also, be prepared to only be offered a Mac laptop, so PC users might struggle with the unfamiliar interface. I did a lot of research on the company's history and products, but none of it came up during the interview, so don't bother and just focus on the technical/coding parts mentioned in the job description. I didn't get any specific feedback, so if you're unsuccessful, you'll probably be left wondering why.

The office and culture here are definitely 'Dev' culture. It's relaxed, techy, and has good break-out areas. I had a one-hour telephone interview, followed by three one-hour interviews all on the same day. Then, I was called back for another interview. The first of the three interviews was technical, the second was about team fit, and the last was a technical overview. Make sure you know as much as you should for the role. HR was pleasant and open to discussing salary and your interview experience to gauge your interest, situation, and possibly body language to see if you're the right fit.