Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Databricks

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Databricks | Offerte di lavoro di Databricks | Stipendi di Databricks | Benefit di Databricks
      Colloqui di DatabricksColloqui per Senior Software Engineer presso DatabricksColloquio di Databricks


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Le migliori aziende per "stipendio e benefit" vicino a te

      avatar
      DONE by NONE
      3.8★Stipendio e benefit
      avatar
      Digital Natives
      4.4★Stipendio e benefit

      Colloquio per Senior Software Engineer

      15 lug 2021
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa

      Altre recensioni di colloqui per Senior Software Engineer presso Databricks

      Colloquio per Senior Software Engineer

      16 apr 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza positiva
      Colloquio difficile
      Colloquio nella media

      Candidatura

      La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Databricks

      Colloquio

      Interview process consists of technical screening, manager interview, virtual on-site, then take home coding assignment. Recruiter was very helpful and responsive at first, but the further the process got, the less responsive they were. I had a lot of fun during the interviews. I love a good challenge and none of the questions seemed terribly difficult. I was really looking forward to the work there, but what happened afterwards left a bad taste in my mouth. Finally, after submitting the take home assignment, I was ghosted by the recruiter for two weeks. No acknowledging me despite several attempts to make contact. I finally got rejected without any feedback other than implying I was under-qualified for the role. This was after the recruiter saying I did well in prior steps. Why waste a candidate's time with all these interviews and work if the candidate was unqualified? If it wasn't a qualifications issue, why lie about it? Ghosting someone is also pretty rude. Is there not any way to at least acknowledge that the process is still ongoing when contacted? I'm pretty disappointed and won't be recommending Databricks to anyone.

      Domande di colloquio [1]

      Domanda 1

      Can't discuss due to NDA. Recruiter provides information about the kinds of questions you'll be asked before each interview phase.
      Rispondi alla domanda
      2

      Candidatura

      Ho sostenuto un colloquio presso Databricks

      Colloquio

      The Databricks interview is notoriously tough and they absolutely live up to that reputation. The process moved quickly but the technical bar is incredibly high. They do not care how fast you can solve a generic LeetCode puzzle. They want to see if you understand memory management, distributed state, and thread safety. The virtual onsite had a mix of deep system architecture and a heavy live coding session where you actually have to compile, run, and debug your code.

      Colloquio per Senior Software Engineer

      20 feb 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso Databricks

      Colloquio

      Screening round was a system design question. Did not make it through. I do think for such an involved question, the interviewer spent a bit too long explaining the question at the beginning and didn't leave enough time for me to implement the solution. But that was probably not the reason for not passing.

      Domande di colloquio [1]

      Domanda 1

      Standard system design question. Practice with Hello Interview or similar site.
      Rispondi alla domanda
      1

      Colloquio per Senior Software Engineer

      23 gen 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 3 mesi. Ho sostenuto un colloquio presso Databricks

      Colloquio

      Interview consisted of 5 rounds: 2 system design (single box and distributed), 1 coding and 2 behavioral and personal deep dive. Overall the experience was pretty good. The interviewers were nice, seemed to pay all attention, and all of them were really smart and fun to talk to.

      Domande di colloquio [1]

      Domanda 1

      Coding was not a typical leetcode style, instead it was a generic problem, which could be tacked on with follow ups like better structuring, modularity etc. Single box design focussed on concurrency, reliability and crash recovery. The discussion on past projects was extremely detailed and technical. The system design question seemed too focussed on the domain rather than one of the standard distributed design questions.
      Rispondi alla domanda