Deployment Strategist

Required Qualifications

• Relentless operator. You run toward ambiguity, not away from it. You move fast, solve problems independently, and adapt without losing sight of outcomes. You ship, learn, iterate.
• World-class communicator. You can brief a CNO, align an IT director, and coach frontline nurses — sometimes in the same afternoon. You translate complexity into clarity and build trust at every level of a multi-stakeholder enterprise.
• Insatiably curious. You don’t accept surface-level answers. You dig until you understand how the hospital actually works — the politics, the workflows, the incentives, the hidden constraints. You uncover the real problem, not the loudest one.
• Structured but flexible. You build systems, not rigidity. You bring order to chaotic environments, create processes that scale, and know when to bend them to reality.
• Customer-obsessed to the core. You want to be on-site. You want to see the workflows. You remember details because you care. Your energy comes from being close to the problems and driving change with the people who feel it.
• Technically fluent (preferred, not required). You don’t need to code, but you should be comfortable navigating integrations, understanding the basics of feasibility, and communicating clearly with engineering about how real-world workflows translate into product.
• Relentless operator. You run toward ambiguity, not away from it. You move fast, solve problems independently, and adapt without losing sight of outcomes. You ship, learn, iterate.
• World-class communicator. You can brief a CNO, align an IT director, and coach frontline nurses — sometimes in the same afternoon. You translate complexity into clarity and build trust at every level of a multi-stakeholder enterprise.
• Insatiably curious. You don’t accept surface-level answers. You dig until you understand how the hospital actually works — the politics, the workflows, the incentives, the hidden constraints. You uncover the real problem, not the loudest one.
• Structured but flexible. You build systems, not rigidity. You bring order to chaotic environments, create processes that scale, and know when to bend them to reality.
• Customer-obsessed to the core. You want to be on-site. You want to see the workflows. You remember details because you care. Your energy comes from being close to the problems and driving change with the people who feel it.
• Technically fluent (preferred, not required). You don’t need to code, but you should be comfortable navigating integrations, understanding the basics of feasibility, and communicating clearly with engineering about how real-world workflows translate into product.