The process was set up through Andreessen Horowitz.
The first phone interview was introductory. The interviewer asked a lot of questions about what I knew of Databricks, what projects I had done, what my favorite programming language was, and what I expected from an internship at Databricks.
The second interview was a phone call and technical screening. I didn't do well on that, but I asked for feedback from the interviewer. He was very kind and thorough in his advice, and he asked me to reapply next year.
Instructions: You are given a k-by-k grid of letters, plus a dictionary of valid words. Your goal is to find all words you can trace out in the grid. Tracing can move up, down, left, or right. For any given word, you can use each grid coordinate at most once.
Example: Grid: EA BD
Dictionary: {BAD, BE, BEAD, BED, DAD}
Output: BE, BEAD
Not in the output: BAD (diagonal move) DAD (uses bottom-right coordinate twice).
Note that in a real scenario, the grid size would be approximately 15x15, and the dictionary size would be approximately 10,000.
The following metrics were computed from 1 interview experience for the Databricks Software Engineer (Internship) role in San Luis Obispo, California.
Databricks's interview process for their Software Engineer (Internship) roles in San Luis Obispo, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Databricks's Software Engineer (Internship) interview process in San Luis Obispo, California.