Interesting problems, tight planning
Interesting problems, tight planning
- Solves some very unique problems.
- Everybody you meet is incredibly competent.
- Quarters are planned down to the days.
- There is not a lot of room to freely explore.
- Engineering diversity is not great.
Additional Ratings
Was this helpful?
Databricks Interview Questions
Databricks Interview Experiences
Software Engineer
Extremely unprofessional interviewer who worked on his own stuff the entire interview and deliberately didn't reveal the second part of the question. Attitude is bad and impatient. If you don't want to interview, just don't accept the interview. I'd
Software Engineer
The first part was the Technical Screen without OA. It was a standard graph problem, maybe like a Leetcode Medium. It was an hour total, and I had about 10 minutes at the end to ask my interviewers some questions.
Software Engineer
Data structure heavy questions (not the typical LeetCode) – you need to implement a class to perform certain operations. I was also asked some behavioral questions at the beginning, but I don't know whether this is standard.
Software Engineer
United StatesNovember 19, 2025Extremely unprofessional interviewer who worked on his own stuff the entire interview and deliberately didn't reveal the second part of the question. Attitude is bad and impatient. If you don't want to interview, just don't accept the interview. I'd
Software Engineer
Seattle, Washington, United StatesNovember 18, 2025The first part was the Technical Screen without OA. It was a standard graph problem, maybe like a Leetcode Medium. It was an hour total, and I had about 10 minutes at the end to ask my interviewers some questions.
Software Engineer
United StatesNovember 12, 2025Data structure heavy questions (not the typical LeetCode) – you need to implement a class to perform certain operations. I was also asked some behavioral questions at the beginning, but I don't know whether this is standard.
