The interview process was really smooth. I cleared all six rounds in total. I had a wonderful experience with Shintaro, the staff recruiter at Databricks. He ensured that all the round results were given to the candidates as soon as possible. After clearing all the rounds, the internal process for offering the offer letter was completed promptly. Unlike other firms that add a lot of delays in interviews and offer letters, Databricks has a very enthusiastic HR team! I didn't join Databricks, I received another offer that better suited my personal and professional goals.

I applied through LinkedIn and I completed two rounds. The first round was Managerial, and the second was a Coding round. The second round was conducted by Akshay Bagrecha. He asked me to write a trigger and told me that it must be a working code. I wrote the code, and I am 110% sure my code was correct—but there could have been a syntax error because I haven’t had the chance to work on the Task object before. My feedback came like this: "Coding-related aspects like exception handling and code comments could have been stronger. Readability could have been stronger. However, the interviewer felt it was a positive sign that I was able to effectively communicate my thought process at all times." Honestly, in a 1-hour interview, when you barely get 45 minutes to write live code, they expect comments as well as exception handling. I had no issue writing those too, but during the interview, I was explaining the code line by line to the interviewer—and that is also mentioned in the feedback. So what was the need for comments then? Sometimes companies hire people who may know the technical side but do not understand how to take interviews. Worst experience. I asked HR to reevaluate my interview or reschedule it, but they told me that I have to serve a 12-month cooling period.