Databricks · Primly Community

Databricks product designer / UX interview and portfolio review: what to emphasize, what to skip

brand_ben · 3 replies

I'm a product/brand designer with 8 years of experience and I went through the Databricks design interview last spring for a senior IC product designer role. Posting this because design interview content for B2B data companies is weirdly sparse.

The short version: they take design seriously but the audience is technical and you need to respect that in how you present your work.

Recruiter and HM screen: Two calls before any portfolio review. They spend a lot of time here understanding your background with complex information architecture and data visualization. If you've worked on dashboards, developer tools, or enterprise products, lead with that. Consumer apps are fine but translate them to the B2B context explicitly.

Portfolio review (90 min): This was with two PMs and a senior engineer in addition to two designers. Not unusual for Databricks. The engineer asked the best questions. He pushed hard on how I knew a design decision was the right one, whether I tested alternatives, how I handled conflicting feedback from different stakeholders.

Two big things I noticed: They want to see that you collaborated deeply with engineering, not just handed off specs. Show your edge cases documentation, your design-engineering sync notes, something that shows you understand implementation constraints. Case studies should be problem-first. Don't start with "here's the beautiful UI." Start with "here's the mess we were given and here's how we defined what success looked like."

Design exercise (take-home): 48 hours to redesign a specific flow in their notebook product. Clear scope. I treated it like a real project: user problem framing, 3 concepts at wireframe fidelity, one pushed to higher fidelity with interaction notes. They're looking for judgment and clarity of thinking.

Behavioral: Very similar to SWE behavioral. Collaboration, ambiguity, getting alignment without authority. Have 4-5 real stories ready.

One honest note: Databricks is still maturing on the design side. There's a lot of opportunity but also a fair amount of "design comes in at the end of a sprint" energy that you'll need to be comfortable pushing back on.

3 replies

alex_design

The "problem-first" point should be tattooed on every designer's portfolio. Every case study that opens with a polished UI screenshot and then tries to backfill the problem loses me in the first 30 seconds. The best ones open with a gnarly constraint and make you feel the mess.

ux_uma

Having a senior engineer in the portfolio review is a good sign in my experience. It means design isn't siloed. Did you feel like the designer interviewers and the engineer interviewer were calibrating against the same rubric or were they looking for different things?

intl_isla

Was the role remote-friendly or did they expect Seattle or SF presence? I've been hesitant to apply to Databricks design roles because most of them say "preferred SF" in the JD.