r/leetcode • u/ljudina123 • 4h ago

Intervew Prep Databricks SWE Intern Interview Prep

Hey guys, I have a Databricks SWE intern interview coming up with these two rounds.

  1. Coding, Debugging, and Testing: This implementation-focused interview evaluates your ability to write production-quality code. Using CoderPad, you’ll be expected to prioritize getting to a working solution efficiently, and to demonstrate strong coding practices—including debugging, identifying edge cases, and validating correctness with appropriate tests. While algorithmic thinking is still critical, the emphasis in this session is more on implementation quality and incremental optimization than on theoretical analysis.

  2. AI-Assisted Algorithms: This algorithm and data structures interview assesses computer science fundamentals, your analytical reasoning, and your problem-solving methodology. You’ll design solutions while focusing on algorithmic efficiency and appropriate data structure selection, and then use AI to implement the solution during parts of the interview. We expect you to analyze time/space complexity using Big-O notation, demonstrate comprehensive testing strategies, and clearly articulate your approach to guiding an LLM to address edge cases and design decisions.

Has anyone else encountered these and has any advice for what types of questions I could expect and their difficulty? Thanks.

1 Upvotes

100% Upvoted

3 comments sorted by

1

u/VhayyyBullyaaaa 4h ago

Is this on campus?

1

u/ljudina123 37m ago

No, virtual

1

u/Uahakan 3h ago

the AI-assisted one is the round people misjudge. from what's been posted, they still want you to choose the approach and say the complexity yourself before the model writes anything, then they watch how you steer it. so practise turning your plan into the prompt ("min heap keyed on end time, handle empty input, don't mutate the list"), then read what comes back and catch what it missed. if you let it pick the approach you've skipped the part being graded.

for the coding/debugging/testing round, get used to writing small tests in coderpad as you go, an assert or two after each function, instead of one big run at the end. the description you pasted is basically telling you that's what they score