Palantir · Primly Community

Palantir product designer / UX interview and portfolio review: a full account

alex_design · 5 replies

I went through the Palantir product designer loop over about six weeks earlier this year. Long process. Here is everything I wish I had known going in.

Background: I'm a staff-level designer with a mix of enterprise SaaS and consulting. I was interviewing for a senior product designer role on a Foundry product team.

The process: Recruiter screen. Design challenge take-home (more on this below). Portfolio review with two designers. Onsite with four people: another designer, a PM, an engineer, and a cross-functional design critique.

The take-home design challenge: They gave me a hypothetical problem: something like "design a way for a user to understand how data was transformed as it moved through a pipeline, without technical knowledge of the underlying system." Two-week window. They wanted a clear problem framing, evidence of user research thinking (even if hypothetical), and medium-fidelity wireframes with reasoning.

Do not over-design the visuals. I saw advice to make it pixel-perfect and I disagree. They responded to the thinking more than the polish. The one critique I got was that I'd jumped to a solution before fully documenting competing approaches.

The portfolio review: Bring 2-3 projects where you can talk about the full arc: business problem, constraints, research methods, design decisions, iteration, outcome. They really pressed on constraints, especially what you cut and why. One question I got: "where in this project did you make a design decision that another designer might have made differently, and why did you choose your direction?"

The design critique round: They showed me an existing interface and asked for feedback. Be honest. Don't compliment your way around real issues. They know the interface has problems.

What Palantir design actually does: Mostly enterprise data visualization and complex workflow design. If your background is consumer apps with small surface areas and you've never thought about information density, data provenance, or power-user workflows, that's a gap.

Comp: 240-270k total for senior designer, NYC or Palo Alto. Q2 2026.

5 replies

brand_ben

"Be honest" in the design critique is real advice that a lot of people ignore. In an agency context I learned early that flattering a client's existing work doesn't help anyone. At companies that have strong design culture, sugarcoating is a red flag, not a safe play.

ux_uma

The take-home prompt you described is exactly the kind of enterprise-specific problem where consumer design experience doesn't fully transfer. How do you surface data lineage to a non-technical user? That's a real, hard problem in the data platform space. Did you do any competitor analysis or did you lean more into principles/heuristics for the framing?

alex_design

Combination. I looked at how dbt and Airflow try to handle lineage visualization (for context), then built the user framing from scratch based on what a non-technical data consumer actually needs to answer. Mixing real-world precedent with original framing seemed to land well.

pm_priya

The question about "a decision another designer might have made differently" is smart. It's testing for design judgment AND self-awareness. The candidates who struggle are the ones who say "I don't know, I think my approach was just correct."

content_cole

240-270k for senior designer is on the high end for the market but tracks with enterprise-focused companies that have a smaller designer-to-eng ratio and expect designers to go deep rather than wide. Context matters for that number.