The Databricks interview process usually takes around two to eight weeks and starts with a recruiter screen. During this screen, I talk about my background, experiences, and why I’m interested in the company.
After that, there’s a technical phone screen where I solve algorithm or coding problems live, usually on CoderPad. If I do well, I move on to a virtual onsite that includes three to five rounds focused on coding, system design, and behavioral questions.
For software engineering roles, the interviews tend to dive deep into data structures, algorithms, and scalable system design. Data or ML roles include Spark, data pipeline, and machine learning case studies.
The interviews are tough but fair—they often increase in complexity to test my reasoning, problem-solving depth, and ability to communicate clearly.
Afterward, a hiring committee reviews all the feedback before deciding whether to extend an offer, and sometimes there’s a team-matching step. Overall, the process is thorough and emphasizes clarity, correctness, and thoughtful engineering decisions.
Implement NumPy functions using C in less than 40 minutes. Other ones were just LC hards.
The following metrics were computed from 127 interview experiences for the Databricks Software Engineer role.
Databricks's interview process for their Software Engineer roles is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Databricks's Software Engineer interview process.