Great place to work, still tons of growth ahead
Great place to work, still tons of growth ahead
- Interesting technical problems.
- Co-workers are very smart and very collaborative. Consistent high quality, unlike high variance at FAANG.
- Engineering org is still small enough that you can have a lot of impact regardless of your level.
- Focus on building great products, cut through BS, company doesn't waste time on distractions.
- Well-positioned for lots of future growth.
Technical debt from organic growth over many years, but this is also an opportunity and the company is prioritizing fixing it.
Internal tools could be better, but this is also an opportunity (if you work on a team that works on internal tools) and the company is working on fixing it.
WLB is not ideal, but also not as bad as some people say. It seems to be more a function of the kind of people Databricks hires than something imposed by management.
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.
