← Back to Directory

Databricks

Large Enterprises

Most of these Databricks write-ups come from Software Engineers (142), then Machine Learning Engineers (9) and Backend Engineers (2). The most reported rounds are the technical phone screen (92), the system design round (48), the behavioral / leadership round (5) and the onsite coding round (4).

154 interview notes · updated Jun 2026

Databricks·Software Engineer·Technical Phone Screen

Jun 2026
Databricks coding interview with a grid pathfinding problem. Pretty standard BFS territory but the setup with the custom cell types threw me off for a second.
  • Given a 2D grid where cells are marked as start, destination, open road, or obstacle, find the shortest path from start to destination moving only in four directions. Return -1 if no path exists.

“Classic BFS setup.”

View Post

Databricks·Software Engineer·Technical Phone Screen

Jun 2026
Databricks technical phone screen with a networking/systems flavor. The main problem was a firewall rule evaluator, which sounds manageable until you hit the CIDR block query variant and have to reason about partial overlaps returning 'mixed'. Left feeling like I handled the single-IP case fine but fumbled explaining the block partitioning logic cleanly.
  • Given an ordered list of firewall rules in CIDR notation, each labeled allow or deny (first match wins), write a function that takes a single IP address and returns whether it's allowed or blocked under a default policy if nothing matches.
  • Extend the firewall evaluator so the query can be a CIDR block instead of a single IP. The function should return 'allow' if every IP in the block would be allowed, 'deny' if every IP would be denied, and 'mixed' if there's any split. How do you handle partial overlaps between the query block and the rule list?

“The single-IP case is pretty approachable once you convert each CIDR to a (network_int, mask) pair upfront.”

View Post

Databricks·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Databricks system design round, one big question on distributed key-value stores that went pretty deep. Felt like they wanted to see how far you could push the design before things got hand-wavy.
  • Design a distributed key-value store that supports get, put, and delete on string keys with byte-string values, optional TTL, optional compare-and-swap, horizontal scalability, high availability, configurable consistency, and low tail latency.

“This one sprawled.”

View Post

Databricks·Software Engineer·Technical Phone Screen

Jun 2026
Databricks coding round with a simulation problem that felt more involved than I expected. The follow-up caught me a bit flat-footed but I got through it.
  • Given a falling Tetris-like block, an array representing the environment (column heights and obstacles), and a horizontal offset, compute how many steps the block falls before it gets stuck.
  • Follow-up: after the block lands, print or return the updated environment state.

“I spent the first few minutes just trying to understand what 'stuck' meant given irregular obstacles, not just a flat floor.”

View Post

Databricks·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Databricks for a software engineering role. The prompt was a full-scale card payment network, Visa-style, and they wanted the whole thing: actors, flows, fraud, consistency, the works. Brutal scope for a single session.
  • Design a global card payment system similar to Visa, covering all major actors (cardholder, merchant, acquiring bank, card network, issuing bank), the full authorization/clearing/settlement flow, idempotency, fraud detection, double-spend prevention, multi-region availability, latency constraints for authorization, high throughput, reconciliation, and chargebacks.

“This is the kind of question where you spend the first five minutes just trying to figure out what NOT to cover.”

View Post

Databricks·Software Engineer·Technical Phone Screen

Jun 2026
Databricks coding round, one question but it had a follow-up that tripped me up more than the original. The base problem was familiar but they pushed further than I expected.
  • Given two strings s1 and s2, find all starting indices in s2 where the substring of length |s1| is an anagram (permutation) of s1.

“I'd seen the yes/no version of this before so I felt fine at first.”

View Post

Databricks·Software Engineer·Technical Phone Screen

Jun 2026
Round 2 at Databricks was a grid-based coding problem with a few layers to it. Nothing too exotic on the surface, but the follow-up added enough complexity that I had to switch from coding to just describing the approach.
  • Given a 2D grid with a start, destination, obstacles, and cells labeled with transportation modes (walk, bike, car, train), each mode having its own cost and time arrays, find the fastest single-mode path from start to destination. Break ties by cheapest cost. Movement is horizontal/vertical only.
  • Extend the previous grid problem to allow switching transportation modes mid-path, with a penalty for each switch. Then further restrict the total number of allowed switches.

“My first instinct was to run four separate BFS passes, one per mode, then compare results.”

View Post

Databricks·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Databricks ML engineer interview with a from-scratch coding problem on linear regression. Pretty technical, lots of follow-ups, and they had a buggy snippet ready to trip you up.
  • Implement linear regression with gradient descent from scratch, no ML libraries. Should predict y from a feature matrix X, compute MSE loss, and support a configurable learning rate with early stopping.
  • What happens to training when the learning rate is too large versus too small?
  • How would you normalize features before running gradient descent, and why does it matter?
  • Here is a buggy gradient descent implementation. Find and fix the bugs.

“The MSE normalization thing is where people slip up and I almost did too.”

View Post

Databricks·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Databricks SWE interview that focused on a system design question with a real-time metrics twist. Not a pure LeetCode session, more of a design-and-discuss format where they pushed on trade-offs pretty hard.
  • Design a key-value store that also exposes a method returning the average number of operations per unit time over a rolling 5-minute window. Walk through your data structures, how old entries get cleaned up, and how you'd handle thread safety.

“I started with the obvious deque-of-timestamps approach and they immediately asked what happens under high write throughput.”

View Post

Databricks·Software Engineer·Hiring Manager Screen

Jun 2026
Behavioral hiring manager round for a Solution Architect role at Databricks. Pretty much a structured resume walkthrough with a heavy focus on pre-sales experience, so if you're coming from a pure technical background without customer-facing work, prepare to scramble.
  • Walk me through your resume, specifically highlighting any hands-on pre-sales or customer-facing technical work you've done.
  • Tell me about a specific deal or account where you led a technical discovery call or scoping conversation. What was your approach?
  • How do you tailor a technical demo for different audiences, say a technical champion versus an executive sponsor?
  • Describe a time you handled a technical objection during a POC or demo. How did you respond in the moment?
  • Give me an example of a time you collaborated closely with an account executive or sales team on a complex deal. What was your role and how did you handle disagreements?
  • Tell me about a project or account where you took full ownership of the technical outcome. What did that look like and what would you do differently?

“This is the anchor question and it eats up a big chunk of the hour.”

View Post

Databricks interview FAQ

What rounds are in the Databricks interview?

Candidates most often report a technical phone screen (92 write-ups), a system design round (48), a behavioral / leadership round (5) and an onsite coding round (4).

What does the Databricks technical phone screen cover?

Across 92 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (119 questions), Technical Trade-offs (108) and System Design (73).

What is asked in the Databricks system design round?

Across 48 system design write-ups, the most tagged question topics are System Design (105 questions), Technical Trade-offs (84) and API & Integrations (29).