Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empleadores

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      Databricks

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Databricks | Empleos en Databricks | Sueldos en Databricks | Prestaciones en Databricks
      Entrevistas en DatabricksEntrevistas para el cargo de Senior Software Engineer en DatabricksEntrevista en Databricks


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

      • Ayuda
      • Pautas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de autorización de cookies

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para Senior Software Engineer

      27 nov 2020
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Me postulé a través de un reclutador. Acudí a una entrevista en Databricks

      Entrevista

      My interview experience was surprisingly terrible. Starting with a recruiter who wouldn't tell me which interview was which (apparently its policy not to disclose this; and the expectation is that there's no extra preparation required :facepalm: ) I was basically setup for failure with one of my coding interviewers asking me a very very specific LC hard level question with barely 30 minutes remaining in the interview. I was so turned off by this that the rest of the interviews became a joke to me. Despite the other interviews(HM, design, coding) being decent, I felt the Databricks interview process is artificially difficult(asking LC hard to senior candidates with 30 minutes remaining). I was really surprised that a company like Databricks had such a poor hiring process. Would not recommend interviewing here unless they make some serious changes.

      Preguntas de entrevista [1]

      Pregunta 1

      LC hard level question for coding; everything else is similar to what you find online
      1 respuesta
      8
      avatar
      Respuesta de Databricks
      5y
      Thank you for taking the time to share your feedback and for your investment in our interview process. It is important to us that our candidates feel set up for success for their interviews and have an exceptional candidate experience. We appreciate the time you dedicated to the process! We are always looking for ways to improve. If you are open to it, please contact me directly to share any more feedback you might have.

      Otras evaluaciones sobre las entrevistas para el cargo de Senior Software Engineer en Databricks

      Entrevista para Senior Software Engineer

      16 abr 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Databricks

      Entrevista

      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.

      Entrevista para Senior Software Engineer

      20 feb 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Me postulé a través de un reclutador. Acudí a una entrevista en Databricks

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Standard system design question. Practice with Hello Interview or similar site.
      Responder pregunta
      1

      Entrevista para Senior Software Engineer

      23 ene 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 3 meses. Acudí a una entrevista en Databricks

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 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.
      Responder pregunta