Principal Product Designer, Vertical Solutions

About the role. You will own the experience for one of our verticals, and a capability that runs across all of them. You work alongside the PM who owns the roadmap and in front of customers yourself, so you know why a workflow exists commercially, not just how it should feel. Start with the vertical. An agent does most of the work, then hands a decision to a person who is accountable for the outcome: reviewing a claim against policy, releasing an order that is short on allocation, approving an invoice exception. You design what that person's screen is for, inside the real context they work in, and then you build it. Now the part that spans. The rules that govern this work live in the heads of people who have done the job for fifteen years. You own the experience for how our agents learn from those people, and how that learning stays legible to whoever has to answer for it. There is no generic version of what a fifteen-year veteran knows, so you can’t design this in the abstract. Your vertical is where it becomes real, and what you build there must hold up everywhere else. You will work with the designers who own the other verticals from the start. You will report to the Senior Director of Design for Vertical Solutions.

Responsibilities

Own your vertical end to end: the queue a reviewer starts in, the administration experiences that get a customer configured and live, and the dashboards a process owner uses to find bottlenecks.; Own how our agents learn from the people who work alongside them, and how that stays inspectable by whoever is accountable for the outcome.; Own the generalization path; decide what belongs in the shared capability and what is local to your vertical; be accountable to all the verticals.; Set direction across both with PM, engineering, and platform partners.; Build working software and the tooling that makes the team faster; open PRs into the product repo through standard review.; Drive business outcomes; design is measured against the same product metrics the team carries; establish the baseline for your surface and be precise about what design influences.

Requirements

An excellent design and experience thinker. Knows how to work with customers on what they need, not just what they ask for. This is non-negotiable.; Around 10 or more years owning meaningful product areas, with a consumer-grade bar you bring into a high-stakes domain.; A strong instinct for what the experience needs. You dig into unfamiliar domains, spot the gaps early, and push quality higher rather than waiting to be told.; You want the business context, and you go get it from PMs and customers firsthand rather than waiting for a brief.; You build. Claude Code is your primary tool. You don’t need to be a software engineer, but you should be comfortable with a modern frontend stack and able to move quickly from idea to working prototype. Not fluent in Claude Code yet? You can learn it here if you are genuinely excited to work this way.; You can hold your position. You can write the code, decide what should be built, and make the case for it in a room of designers, PMs, and engineers.; You work well horizontally, designing something that serves several teams while keeping it coherent.; Familiarity with GitHub, Figma, and Claude.ai, and comfort with ambiguity.

Nice to have

Experience designing for AI or agentic products, especially anything involving human oversight, trust, memory, or governance.; Experience in a regulated or operationally complex industry: healthcare, life sciences, financial services, supply chain, or manufacturing.; Experience with knowledge systems, or any product where accumulated knowledge had to stay trustworthy over time.; Experience building internal tools or AI-assisted workflows that other people came to depend on.

Benefits

Flexibility in when and where work gets done; Hybrid work with regular office time and flexible cadence.