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 121–122 of 122 results

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