Databricks · Primly Community

Databricks engineering manager interview loop, detailed debrief from the hiring side

careerveteran · 4 replies

I went through the Databricks EM loop last quarter, targeting a senior engineering manager role on one of their data platform teams. Figured I'd write up what actually happened since most posts I found were outdated or only covered IC.

The loop was 6 rounds total. Here's the breakdown:

Recruiter screen (30 min): Standard intro. They're genuinely trying to figure out team fit, not just checking boxes. Come with a clear thesis on why Databricks specifically, not just "AI/data is growing."

Hiring manager call (45 min): This was a real conversation. My HM asked about how I build trust with ICs who were skeptical of a new manager, how I've handled technical disagreements between senior engineers, and one question I didn't expect: "Tell me about a time you had to slow a team down that was moving fast."

Coding round (60 min, LeetCode-style): Yes, EMs code at Databricks. Medium difficulty. Graph traversal problem. They're not trying to trick you but they do want to see you can still write code. If you've been full-time management for 2+ years you should spend a few weeks dusting off.

System design (60 min): Distributed system at scale. I got something in the data pipeline space, which made sense for the role. They focus on trade-offs more than diagrams. I interrupted my own design twice to call out assumptions I was making, and the interviewer visibly appreciated that.

Behavioral x2 (45 min each): Classic STAR format. Lots of "tell me about a time you had to make a decision without enough data" and "how do you handle a consistently underperforming engineer." They care deeply about how you give feedback and how you've built inclusive teams.

Leveling: I came in targeting L7 (senior EM). The committee calibrated me to L6 (EM). The recruiter was upfront about it. No offer yet but the process itself was solid, no surprises after the recruiter set expectations.

Timeline from first contact to final debrief was 5 weeks. Two weeks of radio silence in the middle while they coordinated interviewers. Totally normal, don't read into it.

4 replies

director_dee

The coding round for EMs always sparks debate on the manager forums but I agree with their approach. You can't credibly evaluate IC engineers without being able to read code. The LeetCode-medium bar is reasonable, it's not about grinding hard problems, it's about whether you've stayed technically grounded.

firsttime_mgr

This is the part that terrifies me about making the EM jump. I've been in management 14 months and I can feel the coding muscles atrophying. Did they give any grace for syntax errors or is it really expected to be production-clean?

recruiter_rita

The "slow a team down" question is one of my favorites to watch candidates answer. Almost everyone reflexively talks about acceleration. The ones who have actually done it know it's usually the harder and more important leadership skill.

remote_swe_42

Did they discuss remote vs. hybrid? And was this SF-based or one of the other offices?