Candidates describe Databricks Software Engineer processes that typically include a recruiter screen and live coding with follow-ups, and in some cases a virtual onsite with system design and behavioral discussion. Here is what they report and how to prepare.
$202K
Avg. Base Comp
$402K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates who interviewed for Databricks Software Engineer roles describe a coding-first process that starts with a short recruiter conversation, moves to live technical screens, and in at least one case adds a virtual onsite with system design and behavioral discussion. The shape varies by report, so ask your recruiter to lay out the sequence and the exact coding stack for your team. One candidate expected a backend, database-heavy loop but found the technical round was frontend coding locked to TypeScript, and withdrew.
On the coding side, the reports lean on classic data structures and algorithms. One candidate got a one-hour CoderPad session built around House Robber and then its circular follow-up. Another had an hour to solve a breadth-first search problem while narrating, with attention to complexity, testing, and code style, and no AI or Google allowed. A third saw implementation-heavy problems such as Tic Tac Toe and said a single failing test case mattered, so finishing clean, working code counts as much as outlining an approach.
System design shows up as its own conversation, and one candidate called it the hardest part of the onsite. Practice thinking out loud and explaining tradeoffs rather than racing to an answer. The same candidate also had a round of SQL and Python questions that felt straightforward by comparison.
The behavioral and manager conversations focus on past projects, why Databricks, and how you handled a disagreement. Prepare specific project stories that include the technical decisions you made and why.
Synthesized from 59 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Databricks process.
The recruiter screen was short, about 20 minutes, and it was mostly a fit conversation rather than technical questions, so I'd treat it as a chance to explain clearly why you want this role and what your background brings. The hiring manager screen was the part I'd spend the most prep time on. It ran about an hour and was full of behavioral questions, so expect a long stretch of walking through past experiences rather than a quick check-in. The rest of the loop as I understood it included a Design & Architecture interview, a live coding round, and a Build and Demo, but I never got to the Build and Demo, and I received a no-offer decision. I don't have firsthand detail on the design or coding rounds beyond their names, so I can't speak to how hard they were. What I'd take away is that the behavioral conversation carries real weight early in the process, and it helps to be ready to go deep on a handful of stories for a full hour.
Prep tip from this candidate
Prepare several detailed behavioral stories you can extend for a full hour, since the hiring manager screen was mostly behavioral and ran long. Also rehearse a concise answer on your motivation and fit for the roughly 20-minute recruiter screen.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Databricks
Write a query to show the number of users, transactions, and total order amount per month in 2020
| Question | |
|---|---|
| Merge Sorted Lists | |
| Total Spent on Products | |
| String Mapping | |
| Hurdles In Data Projects | |
| Centralized Event Ingestion | |
| Cumulative Sales By Product | |
| Target Indices | |
| Priority Queue Using Linked List | |
| Spam Classifier | |
| Transformer Encoder Layer | |
| Employee Benefits Outreach | |
| Shortest Path Algorithms | |
| Text Editor With OOP | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Weighted Average With Missing Dates | |
| Delivery Online | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| String Shift | |
| Top 3 Users | |
| Raining in Seattle | |
| First Touch Attribution | |
| Job Recommendation | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Daily Retention Summary | |
| Find the Index with Equal Left and Right Sum |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe a recruiter call covering background, current work, and why Databricks. One candidate's call lasted about 15 minutes, included salary expectations, and gave an overview of the teams, the product, and the rest of the process. That candidate reported no online assessment before the technical rounds.
Reported screens are hands-on. One candidate had a one-hour CoderPad session with about five minutes of introductions before House Robber and its circular follow-up. Another had a DSA screen that felt like a LeetCode medium. Expect to explain complexity and adapt your solution as the interviewer pushes.
One candidate describes a virtual onsite covering algorithms, systems design, behavioral, and coding. The algorithms round felt medium-to-hard and system design was the toughest part. A live coding round gave one hour for a breadth-first search graph problem, judged on complexity, testing, and code style without AI or Google.
One candidate's final round was a behavioral and resume discussion with a senior person or manager, covering past projects and why Databricks. Another was asked how they handled a disagreement. Prepare specific project stories with the technical decisions you made.
