I went into the Databricks interview process specifically asking hard questions about work life balance because I burned out badly at my last job. Here's what I found out, some from the process itself and some from people I know who work there.
The honest version: Databricks is not a 9-to-5 company. If you're looking for a job where you clock out at 5pm and nobody notices, this probably isn't it. The pace is fast and there's a genuine ambition culture. That said, from what I heard it's not the brutal grind of some FAANG shops at peak crunch either.
A few things people told me directly: The team experience varies a lot by org. Core infra teams (Delta Lake, MLflow, compute) tend to run harder because the products are business-critical and have large enterprise customers. Growth and go-to-market adjacent teams apparently have more breathing room. On-call is real if you're on the platform side. One engineer I talked to said his team was on a 1-week-on rotation. That felt manageable but it's not zero. Several people mentioned that Databricks leaders actively say they want people to have a life, but the actual culture depends heavily on your direct manager. Top-down messaging and day-to-day reality don't always match.
What I asked in interviews: "What does a hectic week look like on your team?" (More useful than "what's WLB like") "How does the team handle on-call and incident response?" "What's the expectation around response time on Slack after hours?"
The answers varied by interviewer. One was very candid that his team had some rough patches during a major product launch. I appreciated the honesty.
For me personally, the comp is compelling enough that I'm willing to work hard. But I went in with eyes open about what that means, which felt better than being surprised after joining.