
DataRobot Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 16 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at DataRobot.
Software Engineer
Avoid this place if you care about your time. While individual interviews were fine and the engineers knew their stuff, the overall process was disorganized. It was supposed to take 1-1.5 weeks, but got rescheduled a few times, messing up my deadlines. I had to chase them, and I had to reject another offer due to their expired deadline. I told the recruiter I had other offers and a deadline, and they said they'd decide the next day. That didn't happen, and I suspect they would have forgotten about me if I hadn't followed up multiple times. The whole thing took a month. After 5 rounds (including the initial HR chat), I barely learned about the team (random interviewers) and got a generic rejection. Also, like others said, it seems best to show minimal personality to pass. The process felt scripted, and there was no point connecting with interviewers since the final team was different. I guess sharing personal experience with the Hiring Manager backfired. Wish I knew that, so just stick to the scripted behavioral talk.
- Can you solve a variation of the FizzBuzz problem?
- Tell me about general system design concepts, focusing on the theoretical aspects.
Software Engineer
The interview process was smooth and professional with a clear description of the steps involved. The HRs were friendly and exhibited good job ethics. The team seemed friendly and collaborative. I would recommend this company to anyone seeking a dynamic, fast-paced environment.
- Were there any coding exercises from HackerRank?
Software Engineer
The interview process was really drawn out and they seemed uncertain about the role they were hiring for, as the position kept shifting throughout my interviews. I went through 7 different interviews, covering HR, technical skills, team fit, and company culture. The HR interviews were positive, hinting at an offer. Technical interviews involved coding challenges or technical discussions with the team. The cultural interviews felt strange, especially since I was told they aren't typically conducted for engineers, making me suspect the decision might have been based on a perceived lack of cultural fit rather than just seeking a reason to reject me. They mentioned looking for candidates with over 10 years of experience and those who are already 90-100% proficient in their tech stack. I was also told that without a referral, I wouldn't have been considered. From what I've gathered from others and during the interviews, they really emphasize Kaggle competitions and other external work that consumes your entire life, revolving 100% around the company, the tech field, and coding. It seems like there's very little work-life balance. They couldn't provide details on employee advancement and development within the company, or how often people get promoted or receive salary increases. When I followed up via email for information about why I didn't receive an offer, I got no response. I asked for feedback from the team and suggestions for improvement, but heard nothing back.
- Can you sort K lists containing N items?
- If you were given a log file with timestamps, user IDs, and resource IDs, how would you approach sorting the data for specific use cases, such as extracting user IDs and timestamps, and then sorting user IDs by timestamp?
- What are your interests outside of work?
DataRobot Software Engineer Interview Questions
Quoted word for word from DataRobot interview reports.
“What is the approach to sorting a two-dimensional array?”
Read reports →“Implement the logic for a vending machine.”
Read reports →“Can you sort K lists containing N items?”
Read reports →“How to find words within a given paragraph?”
Read reports →“Could you explain how random forest functions?”
Read report →“What are the pros and cons of using R?”
Read report →“What do you understand by unit tests?”
Read report →“Can you solve a variation of the FizzBuzz problem?”
Read report →“Can you explain a basic search algorithm?”
Read report →Formats, difficulty and experience
Across all 16 DataRobot interview reports.