Want to know if this job is worth applying to?
San Francisco, California, United States
Hybrid
Hospitals run on three things: their people, their beds, and their supplies… and all are still managed with spreadsheets, phone calls, and gut instinct. Vitalize is building the system that runs it all intelligently, starting with labor—the biggest cost (nearly 60% of a hospital’s P&L) and the hardest operational problem.
We’re building the labor and capacity operating system for health systems—forecasting demand, matching the right staff to it automatically, and coordinating patients across the hospital.
The impact is real: we save hospitals millions in unnecessary labor spend, give clinical leaders back 10–20 hours every week, and are often the reason staff and leaders stay. This isn’t a nice-to-have—our customers pay 5–15x more than legacy incumbents because Vitalize is mission-critical software their hospitals rely on every single minute.
We’ve raised over $32M from top investors, and even our own customers.
We hire and grow everyone against the same four values. Each one comes from a real Vitalize story—interview with us to hear them!
🚗 Push the Car. Step in regardless of role. We help wherever we're needed, own problems end to end, and don't stay in our lane. People can count on us.
🏥 Premier 1K. We show up for our customers, always. Nearly everyone visits a customer site in their first month, and customer feedback informs everything we do.
🗣️ Run Towards the Ugly. Name the ugliest truth first, then propose the fix. Candor over comfort—we call out what's broken, and never get complacent. This shapes our craft.
💡 Think Bigger Fridays. See the gap, fill it—no permission required. Every decision is an experiment: we run it, let the results decide, and drive real impact from day one.
Foundations owns everything involved in getting Vitalize into a hospital's hands as fast as possible, configured correctly for how that hospital actually works.
Every hospital shows up with its own HRIS system, its own scheduling quirks, its own union contracts, and its own workflows. Foundations turns that variation into product across three areas:
Data & Intelligence—the integrations that pull hospital data in, and the data foundation our machine learning and AI models depend on
Delivery & Configuration—the tooling that lets our Deployments team stand up a hospital fast, and configurable workflows for customers whose reality doesn't fit the defaults
Rules & Compliance—union rules and workplace regulations, enforced consistently across the entire product as a core feature, configurable to each customer
The Foundations Team's north star is customer time-to-live. Every signed contract runs through Foundations before it becomes a hospital that's actually using Vitalize.
We're past proving this works and into making it scalable and repeatable. Today, too much of what it takes to launch a hospital is bespoke—engineering pulled in for a one-off integration, Deployments doing by hand what software should do, compliance logic written for one customer that should have been written for all of them.
You'll own turning that into a first-class product. Not by building custom code faster, but by building the layer that makes custom code unnecessary. Success in your first year is unlocking major ARR for the business by decreasing time-to-live without having to manually scale up the operations teams.
This role is based in San Francisco, CA, with a hybrid work culture of three days in the office and two days working from home.
Own the company-wide integrations roadmap and get deep enough in the technical design to make real calls with Engineering
Treat our Deployments team as a core customer. Find where they're doing manual work that software should do and automate it with high-quality output. Customer time-to-live is a key metric that requires balancing manual work on the Deployments team with tooling and automations
Turn dense union contracts and workplace regulations into precise, testable product requirements that hold up across every customer
Sit with customers during implementation—onsite, in their systems, with their IT and ops teams—and bring back what you learn as product, not as tickets. Expect to travel to customer sites for a few days every month or two
Partner with GTM and Deployments to see what's coming before it lands and shape the roadmap around it. Avoid the one-off and favor building the thing that makes the next ten one-offs unnecessary
Define what "configurable" means here in practice—config surfaces, mapping tools, workflow primitives—so variation gets handled by setup, not by a PR
You've built internal tooling with internal teams (Deployments, Customer Success, Customer Support) as your customer and you can point to how their throughput changed because of it
You've PM'd an engineering team at a high-growth startup through messy third-party enterprise integrations and you understand the integration itself
You've talked to customers during implementation, in their environment, when things were going wrong
You've prioritized a roadmap against live go-to-market pressure, and you've held the line when the loudest deal wasn't the right build
You've done this at a startup, where the system you were building didn't exist yet
You've owned a vendor relationship directly, working alongside a Customer Success or Deployments team, or working in healthcare, workforce management, or with UKG
Medical, dental, and vision insurance
401(k) with company match
Flexible PTO
Unlimited travel budget to visit customer sites
Twice-yearly company off-sites
Free meals in the office
$5,000 relocation bonus for eligible employees
Desk setup reimbursement
Commuter benefits
Monthly gym/wellness stipend
An awesome office in Jackson Square, steps from the water
