I applied through other source. I interviewed at Databricks
Interview
I was asked Leetcode hard questions in the phone screen. One of these was already listed on the Leetcode page for databricks. The second one wasn't. You will clear the interview if you've seen the questions before. It is still possible to solve the question if you haven't seen it, but you have to be quick.
I personally am not a fan of Leetcode questions, especially hard and that too for the phone screen. There's a reason it's called a "phone screen". I'm happy I didn't pass this round as I wouldn't want to work at a place that lays so much emphasis on Leetcode.
I was sent an automated response that my applications isn't being considered anymore. Thank you Databricks for confirming again that you're searching for code-bots and not engineers.
10
Other Software Engineer Interview Reviews for Databricks
Had an initial recruiter screen for a Software Engineer position. The call lasted around 15 minutes and covered the usual ground: my background and experience, motivation for applying, current role, and salary expectations. The recruiter also gave a clear overview of teams, the product, and the full interview process ahead.
1. Phone interview with HR.
2. Technical coding question using coder pad. Have to implement from scratch.
Interview process was very fast and recruiter was friendly
Question was little vague but it seems to be leaked a lot on the internet
Interview questions [1]
Question 1
Why Databricks?
Past experience.
Projects you have worked on
didn't make it past the first technical round. questions are decently challenging (ie: leetcode med/hard level difficulty), and can range from very mathy topics to bit manipulation, to dynamic programming. be prepared for all scenarios and all topics on leetcode.