Who you are
- You have 8+ years of product design experience , ideally on complex, workflow-heavy B2B SaaS products. You've shipped real features to real users and can talk about the business impact of your work.
- You've owned a design system or comparable infrastructure that other people built on top of. You've designed the contribution model, not just the components. You can talk about the tradeoffs you made.
- You’re comfortable spending time in the field. You enjoy observing operational workflows firsthand and are willing to travel to customer sites regularly to understand the reality of how the product is used.
- You have mature product instincts. When you see a crowded interface, your instinct is to question whether the workflow is right. You design workflow changes, not just UI improvements. The bar is whether your principle survives into the shipped product.
- You're opinionated, evidence-backed, and direct. You form a point of view quickly, back it up with what you've observed in the field, and hold the line when you disagree with engineers, founders, or customers, all while building strong relationships.
- You're customer-obsessed in practice , with an instinct for business outcomes. You can name the metrics your design moves were built to change and defend the bridge between the design and the metric.
- You're AI-fluent. You've worked on a product surface where AI was doing real work, and you have an informed point of view on how AI should and shouldn't show its reasoning in a UI.
- You're a multiplier from day one. You enjoy critique, mentoring, and infrastructure work because of what they make possible for others.
You might not be the right fit if
- You're looking to be the head of design at a Series A; this is a senior IC seat with ownership, not a management role.
- You've only worked on consumer products
- You need detailed specs or PRDs to start designing
- Your portfolio is concept-heavy and ship-light, or you can't point to a system someone else built on
Experience in healthcare, logistics, financial operations, or similarly complex operational domains is a strong plus — the operating-model pattern in our product (expert-in-the-loop workflow automation, cost-aware recommendations, audit-trail integrity) translates directly. The domain is deep but learnable.
Why now
You'd be joining a small design team at the moment it scales from co-ownership to a real function. You'll be the third designer to join the team — the staff IC who sets the bar and the pace for delivery. You’ll multiply the output of the entire design team, leading by example, and owning critical design initiatives.
The patterns you set today – in the design system, in how we collaborate with engineering, in the quality bar we hold, in how AI shows its work to clinical staff under time pressure — will shape the product for years. You'd be working alongside founders who care about design quality and give the team real autonomy, and an engineering team that ships fast and wants to get better at building well-designed software.