El proceso tomó 1 semana. Acudí a una entrevista en Databricks (San Francisco, CA) en mar 2019
Entrevista
I was contacted by Databricks, had an initial phone call with a recruiter, and then did a technical phone screen. I did not pass the phone screen. It was not a good experience (see details in the interview question section).
My suggestion to Databricks is that you choose interviewers with good English skills for phone screens and train them how to talk into the phone and present the material to the interviewee. Otherwise you'll keep losing competent candidates like you did with me. FWIW, it was such a bad experience that I wouldn't recommend Databricks to anyone. This interview was a waste of my time.
Preguntas de entrevista [1]
Pregunta 1
You have a list of servers numbered with nonnegative integers, like this: [0, 1, 5, 4, 2]
You have n + 1 servers numbered 0, 1, 2, 3...n
If they fail, we have to bring up a new server
Each new server has to be numbered with the lowest possilbe number
Write a function that returns the smallest nonnegative missing integer from input array, and if none are missing, return the next number in the sequence.
So it would return 3 for the above input.
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.
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.
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.
