Katkat

Company

Databricks interview questions

122 practice questions in the style of Databricks's interviews, covering Software Engineering Fundamentals, Behavioral & Leadership, Coding & Algorithms, System Design, ML System Design, Statistics & Math, Machine Learning, Data Manipulation (SQL/Python).

Questions122

2 easy84 medium36 hard

Your progress0/122

Databricks interview questions by the numbers

Last updated

Katkat has 122 Databricks interview questions. The largest topics are Coding & Algorithms (42%), System Design (28%) and Software Engineering Fundamentals (11%). By difficulty: 2% easy, 69% medium and 30% hard. The most common round is Onsite (57%). Frequent concepts include System Design, Distributed Systems, Concurrency and Data Structures.

Difficulty

  • Easy2% · 2
  • Medium69% · 84
  • Hard30% · 36

Interview rounds

  • Onsite57% · 69
  • Technical Screen36% · 44
  • HR Screen7% · 8
  • Online Assessment1% · 1

Roles

  • Software Engineer83% · 101
  • Machine Learning Engineer7% · 9
  • Data Scientist5% · 6
  • Backend Engineer2% · 3
  • Frontend Engineer2% · 2

Frequent concepts

  • System Design18% · 22
  • Distributed Systems11% · 13
  • Concurrency9% · 11
  • Data Structures9% · 11
  • Algorithms6% · 7
  • Scalability6% · 7

Showing 31–60 of 122 results

  • Tests your ability to architect a real-time collaborative frontend application, focusing on client-side state synchronization, deterministic list ordering, idempotent mutation protocols, and graceful network reconnection.

    DatabricksFrontend EngineerSystem DesignOnsite
  • Tests designing an in-memory index that tracks direct and referral revenue across customers and efficiently supports threshold-bounded minimum revenue queries using balanced search trees.

    DatabricksSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question tests the ability to design a scalable, fault-tolerant distributed file system by addressing challenges in metadata management, data chunking, and cluster availability.

    DatabricksBackend EngineerSystem DesignTechnical Screen
  • Design a distributed file system from a one-line prompt, driving the scoping of workload, semantics, scale and durability yourself. Tests separating metadata from data, block replication and placement, read and write paths, failure recovery, and scaling the namespace for a staff-level backend role.

    DatabricksBackend EngineerSystem DesignOnsite
  • Design a high-throughput, thread-safe embedded log writer that safely batches and persists records from thousands of concurrent producer threads into an append-only file.

    DatabricksSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design a distributed file system namespace capable of handling millions of files and directories with strong consistency and high availability.

    DatabricksSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design a distributed key-value store architecture that incorporates observability, specifically tracking per-key or per-prefix Queries Per Second (QPS) metrics in real-time.

    DatabricksSoftware EngineerSystem DesignTechnical Screen
  • Design a concurrent, in-memory key-value store that tracks read-access frequency using a sliding-window hit counter per key while keeping memory footprint bounded.

    DatabricksSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Design a single, thread-shared component that lets up to 4,000 worker threads inside one process append small telemetry records to one local file, durably and without a disk sync per call. Tests group-commit concurrency design, a crash-safe on-disk record format, and backpressure reasoning.

    DatabricksSoftware EngineerSystem DesignOnsite
  • Tests your ability to architect a scalable, real-time messaging platform like Slack, focusing on connection handling, fan-out delivery, channel message ordering, and presence management.

    DatabricksSoftware EngineerSystem DesignOnsite
  • Tests the ability to design a high-throughput, thread-safe buffering system that decouples client write operations from high-latency storage I/O using concurrent synchronization, backpressure, and background worker threads.

    DatabricksSoftware EngineerSystem DesignOnsite
  • Design a Visa-style card payment system, choosing between the card network and a merchant-side scope. Tests real-time authorization routing to issuers, idempotent handling of retries and reversals, clearing and settlement with an auditable ledger, fraud checks, and multi-region availability.

    DatabricksSoftware EngineerSystem DesignOnsite
  • This problem tests your ability to design a high-throughput, fault-tolerant transaction processing system that guarantees data integrity across distributed services.

    DatabricksSoftware EngineerSystem DesignTechnical Screen
  • Design and implement a concurrent write-ahead log (WAL) engine featuring group commit, monotonic sequence assignment, torn-tail crash recovery, and explicit durability promises.

    DatabricksSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question tests your ability to design a distributed, fault-tolerant transaction processing system for a digital storefront, focusing on data consistency and concurrency control.

    DatabricksSoftware EngineerSystem DesignOnsite
  • This question evaluates a software engineer's ability to design a clean, type-safe API for a generic key-value store, covering data modeling, interface design, and extensibility. It tests practical software design skills including generics, error handling, concurrency, and the ability to evolve an in-memory prototype into a persistent implementation without breaking callers.

    DatabricksSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates understanding of durable storage and crash-consistency, including on-disk data layout, filesystem durability semantics, concurrency control, and performance trade-offs for single-node embeddable key–value engines.

    DatabricksSoftware EngineerSystem DesignOnsite
  • This problem tests your ability to design a thread-safe, high-throughput logging system that balances memory efficiency with I/O performance under concurrent load.

    DatabricksSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question evaluates understanding of time-series data structures and streaming counters, testing algorithm design, space/time complexity analysis, correctness across edge cases, and handling of large-scale event tracking.

    DatabricksSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates a candidate's skills in single-node cache design, including in-memory key/value storage, eviction policy management (e.g., LRU), durability considerations, concurrency control, and techniques for reducing contention such as sharding or striping.

    DatabricksSoftware EngineerSystem DesignTechnical Screen
  • Design an equity Order Management System (OMS) that manages order lifecycles, ensures idempotent broker interactions, and guarantees state reconciliation under distributed failures.

    DatabricksSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates skills in concurrent programming, synchronization primitives, and designing thread-safe bounded data structures that support blocking operations with timeouts, fairness, and backpressure.

    DatabricksSoftware EngineerSystem DesignHR Screen
  • This question evaluates understanding of IP addressing and CIDR notation, bit-level conversion between prefixes and integer ranges, and the design of scalable data structures and algorithms for prefix/range queries, rule priority handling, and rule-set operations (allow/deny semantics).

    DatabricksSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Design an end-to-end e-commerce platform for selling books, balancing read-heavy catalog exploration with strictly consistent inventory reservation and fault-tolerant checkout workflows.

    DatabricksSoftware EngineerSystem DesignOnsite
  • This problem tests your ability to design a distributed e-commerce platform by focusing on consistency models for inventory, scalable search architecture, and robust order processing.

    DatabricksSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's understanding of efficient algorithm design and minimal state management for a Tic-Tac-Toe engine on an n x n board, including constraints such as O(1) time per move and O(n) space.

    DatabricksSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to design an efficient class to manage game state, focusing on constant-time win condition checking using auxiliary data structures.

    DatabricksSoftware EngineerCoding & AlgorithmsOnsite
  • System design question about an online bookstore whose order service inserts orders into a database and then publishes messages to Amazon SQS. Probes what should happen when the insert succeeds but the publish fails, how to keep the database and queue consistent across crashes, and how consumers avoid duplicate processing under at-least-once delivery.

    DatabricksSoftware EngineerSystem DesignTechnical Screen
  • This question tests the ability to design two distinct systems: a reliable transactional e-commerce inventory service and a low-latency real-time chat application, focusing on appropriate database choices and communication protocols.

    DatabricksSoftware EngineerSystem DesignOnsite
  • This interview question evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer for Design concurrent range-aware file caching client states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    DatabricksSoftware EngineerSystem DesignHR Screen

Databricks interview experiences

All 17 →
  • Downleveled from L6 to L5, Same Question Twice, RejectedDatabricks · Software Engineer · Senior+ · Onsite · Sep 2026
    Rejected

    I applied for L6 with 9 years of experience, and got a referral. The HR screen questions made me a little uncomfortable. Starting from the first company after I graduated all the way to my current one, they asked about every single one why I left and whether I got promoted. But the HR seemed nice, and scheduled a phone screen for a week later. Phone screen: the book seller question. Honestly I di…

  • Game Logic, Referral Credits, and Chat DesignDatabricks · Software Engineer · Onsite · Sep 2026

    The report describes two coding sessions and a chat-system design discussion in a Databricks onsite. One coding exercise involved a turn-based board game, including player switching, board output, and correctly ending wins or draws. Its follow-up introduced automated play. The other exercise tracked account credits associated with referrals, queried accounts meeting a threshold, and extended cred…

  • System Design Screen on the Bookstore Question, Passed After a WeekDatabricks · Software Engineer · Technical Screen · Aug 2026
    In progress

    The interviewer seemed like a very senior person, I felt his level was really high. I got the hugely popular Bookstore question. He asked a lot of questions about failure modes. For example: if the request inserts into the DB but then SQS fails, what should happen? How can we prevent that? I said I would use a transaction outbox. He said he had never heard of that pattern, we spent a while with m…

  • Cleared the Full Onsite, Then Rejected After a Messy Reference-Check SagaDatabricks · Software Engineer · Onsite · Jul 2026
    Rejected

    Phone screen: system design — design a music playlist. The recruiter told me it would be a full-stack SD round with front-end code and everything, so I spent a long time brushing up on React, but it turned out to just be a normal SD round with no front-end content at all. My answer was pretty average. The interviewer seemed nice but looked exhausted the whole time — not sure if he was just overwo…

  • Phone Screen Plus Five Onsite Rounds, Then an OfferDatabricks · Software Engineer · Senior+ · Onsite · Jul 2026
    Offer

    End of June: Phone Screen — Coding: KV Store + Hit Counter Implement a KV Store that also supports tracking averageGet and averagePut. The main focus was on how to maintain a sliding window, and the follow-up extended it to stats over the past 1 hour, 1 day, and 1 week. Early July: Onsite 1 — Coding: File Encryption Tree Optimization Given a file system tree made of DirectoryNode and FileNode, wh…

More companies