The hiring process at Databricks takes an average of 60 days when considering 2 user submitted interviews across all job titles. Candidates applying for Big Data Architect had the quickest hiring process (on average 60 days), whereas Big Data Architect roles had the slowest hiring process (on average 60 days).
The process had five structured rounds, each focusing on different skill sets:
Hiring Manager Round A conversational chat about my current role, project scope, and responsibilities. We discussed my experience with system design, coding best practices, and how I approach problem-solving in team settings.
Technical Assignment (Algorithms + Data Structures) A take-home exercise with LeetCode-style problems and a small feature implementation task. The goal was to write clean, efficient code while handling edge cases.
Technical Deep-Dive (Live Interview) A detailed discussion on my past projects, API design, CI/CD workflows, Git branching strategies, and debugging approaches.
System Design Round – I was asked to design a simplified real-time messaging platform, explaining architecture choices, scalability considerations, and trade-offs.
Behavioral / Culture Fit Round – Focused on collaboration, communication with cross-functional teams, and handling ambiguity under pressure.
I had been practicing on Hack2Hire before the interview their mock coding sessions and system design drills really helped me organize my answers and stay calm when faced with follow-up questions.
Interview questions [1]
Question 1
How would you design a notification service that supports both real-time and batch delivery?
I applied in-person. I interviewed at Databricks (Singapur)
Interview
HR Screen > Manager Interview.. The first 15 minutes felt normal. Standard questions about my background, why I was interested in the role, and my experience with product roadmaps. Then things took a sharp turn.
Instead of asking about my leadership philosophy or how I'd approach their specific challenges, the interviewer began drilling down into the proprietary methodologies my current company uses... I felt I was taken for advantage as the interviewer tend to search for information as we're competitors. Not something I would expect from a brand like Databricks, very disappointing.
Interview questions [1]
Question 1
How would you replace xxx at xxx company with Databricks?
I applied online. I interviewed at Databricks in Jul 2025
Interview
Sent in my CV through the open roles portal for a SWE (Backend) role. Sourcer reached out to schedule a 30 min recruiter call describing the role and giving me the opportunity to discuss my background (ML PhD, somewhat unrelated to the role), after which we scheduled a 1h technical screen (algorithms/data structures). Got notified same day that feedback was very positive and that they'd like to proceed to an onsite loop.
Onsite loop was scheduled about a week out, 2 1h interviews per day on Monday and Tuesday. Monday was behavioral with Directer of Engineering + algorithms/data structures, Tuesday coding + systems programming. Got notified on Wednesday that feedback was good again and that they'd like to proceed with reference checks.
Submitted references and synced with them about the process by Monday of the next week, and the calls were happened on Wednesday and Thursday. Due to how the hiring committee works, it took until Tuesday of the next week before I got the confirmation they would be extending an offer, after which it took a few more days to get a concrete offer, which I negotiated for about another week before signing.
The CoderPad platform was used for writing code and Google Meet for the call. Recruiters have access to a fairly complete list of recommended resources for the interviews, so make sure to ask if they don't send it over automatically.
Interview questions [4]
Question 1
Technical screen + algorithms round of onsite were reasonably traditional.
Without giving any specifics (signed NDA), expect questions to be more "applied" than traditional LeetCode, i.e. "we're trying to solve this concrete problem under the following constraints, how would you go about that?" In my case, these questions involved a lot of follow-ups, to the point where I don't think you can "finish" the question in the allotted time; they just keep making things more complicated until you get stuck or time runs out. In many cases, interviewers expect you to go beyond the best purely algorithmic solution and instead discuss tradeoffs like in my case, giving up resolution/granularity for improved speed. The question during the onsite was significantly more involved than the one during the technical screen.
Behavioral interview was also fairly standard.
This was a 1h chat with the hiring Director of Engineering about my background, asking typical behavioral questions. After each answer, the interviewer would either ask follow-ups or recap my answer in a few sentences before moving on to a different behavioral question.
The coding round of the onsite loop is similar to an algorithms question, but the focus is not necessarily on providing a solution with optimal runtime but more so on making sure you can clearly think through a solution, write understandable code.
The systems programming round involved a question combining elements of computer science fundamentals, multithreading, and a big systems design component.