Databricks interview notes, page 7 of 22

“Wasn't sure if they wanted a system design answer or a product walkthrough.” The rest of the author's notes on Software Engineer interview at Databricks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with a plain dict and got the basic operations working pretty fast.” The rest of the author's notes on Software Engineer interview at Databricks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The scope was massive and I tried to cover everything which was a mistake.” The rest of the author's notes on Software Engineer interview at Databricks, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one took me a while to even parse correctly.” The rest of the author's notes on Software Engineer interview at Databricks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Started with a queue, which felt natural, but they pushed back pretty fast on memory.” The rest of the author's notes on Software Engineer interview at Databricks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I hadn't touched CIDR notation since a networking class years ago so there was a solid 30 seconds of internal panic.” The rest of the author's notes on Software Engineer interview at Databricks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was a HashSet with a synchronized copy on iterator() call, which works fine but I fumbled explaining why the lack of ordering requirements actually matters here.” The rest of the author's notes on Software Engineer interview at Databricks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Ran through my background and it felt fine, but I rambled a bit at the end trying to connect everything to Databricks specifically.” The rest of the author's notes on Software Engineer interview at Databricks, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to scan the whole row and column after every move, which is obviously too slow.” The rest of the author's notes on Software Engineer interview at Databricks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one sprawled in every direction and I struggled to pick a thread.” The rest of the author's notes on Software Engineer interview at Databricks, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.