El proceso tomó 4 semanas. Acudí a una entrevista en Databricks
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 1
Can't discuss due to NDA. Recruiter provides information about the kinds of questions you'll be asked before each interview phase.
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.
