Senior Product Designer

The problem

Hospitals still run their most important operations — staffing, labor planning, and capacity — on paper, spreadsheets, and guesswork. It’s a system that wastes thousands of hours and millions of dollars every year.

Vitalize replaces this with intelligent, automated staffing operations. Our platform brings real-time decision support to clinical leaders, eliminating manual work, reducing unnecessary labor spend, and unlocking patient capacity for hospitals.

We’re building the core operating system for hospital workforce operations — competing directly with legacy HR/ERP platforms. And we’re winning. We’re already live across 20+ hospitals, near 8-figures in revenue, and have raised funding from top investors. We’ve 3x’ed revenue in the last 3 months, and are scaling fast.

The role

You'll be the second product designer at Vitalize, joining our founding designer to scale how we design, build, and ship product.

1. You'll own complex product surfaces.
The core of this role is designing data-dense interfaces that hospital staff rely on every day, like shift schedules, staffing dashboards, configuration tools, recommendation systems. You'll simplify these workflows and flatten the learning curves.
2. You'll build the design system alongside the founding designer.
We're at the beginning of this journey. We have a component library in Figma, a Tailwind codebase, and a growing gap between them. You'll help close that gap: building reusable components, establishing color and spacing standards, creating patterns that let engineers build correctly without waiting for design.
3. You'll work directly with customers.
Design at Vitalize starts with real workflows, not requirements docs. You'll visit hospitals, observe how nurses and staffing offices actually work, and use that context to shape what we build.
4. You'll partner closely with engineering.
Our Senior engineers ship fast. Your job is to collaborate through the build, make tradeoffs together, and care about what actually ships to production. At Vitalize, quality is everyone's responsibility.

Who you are

- You have
4+ 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, not just the design rationale.
- You have
strong product instincts
. You rethink problems from first principles rather than layering fixes on top of existing patterns. When you see a crowded interface, your instinct is to question whether the information architecture is right.
- You're
opinionated and direct
. You form a point of view quickly, back it up with evidence, and aren't afraid to push back when you think the product is heading in the wrong direction.
- You have
design systems experience
. You've built or contributed to component libraries, token systems, or pattern documentation. You understand how design infrastructure scales and why it matters for engineering velocity.
- You're
customer-obsessed in practice.
You've done field research: you've gone to where users work, seen the problems they face, and used that context to shape what you build.

You might not be the right fit if:

• You've only worked on consumer products
• You need detailed specs or PRDs to start designing
• You're looking for a remote role
• Your portfolio doesn't include shipped work that contributed to business outcomes

Experience in healthcare, logistics, or similarly complex operational domains is a plus, but not required. The domain is deep but learnable.

Why now

We're at the stage where every design decision compounds. The patterns we set today, in the design system, in how we collaborate with engineering, in the quality bar we hold, will shape the product for years. You'd be joining at the moment where the team is small enough that you can influence everything, and the company is growing fast enough that your work will scale to thousands of users across dozens of hospitals.

You'd be working alongside a founding designer who built the product from scratch and knows the domain deeply, a CTO who cares about design quality and gives the team real autonomy, and an engineering team that ships fast and wants to get better at building well-designed software.