Solutions Architect, Inbound AI Deployments

About the company

Hippocratic AI develops clinically safe generative AI agents that perform non-diagnostic, patient-facing tasks for healthcare organizations.

About this role

THE OPPORTUNITY Health systems and health plans are deploying inbound AI at scale. Hyro, Orbita, Nuance, Notable - everyone's building in this space. But there's no standard. No one's defined what good looks like in healthcare inbound. Hippocratic AI is positioned to own that. We have the technology, the customers, and the trust. What we need is someone to define the playbook - the methodology that becomes the industry standard for inbound AI in healthcare. You're going to build that system. You'll work with our best customers, synthesize what works, and create the frameworks that scale us from individual successes to a repeatable, differentiated offering. The methodology you build becomes how Hippocratic AI wins in inbound for the next five years. This is a Solutions Architect, Inbound AI Deployments role. You're not executing deployments; you're defining how everyone else executes them. You're writing the playbook that our deployment strategists and engineers will follow for the next 50 customer engagements. You're designing the repeatable system that scales us from one-off successes to a replicable, differentiated offering. This role reports directly to the CPO. You'll split your time between health system partnerships (understanding what works in the real world), product engineering collaboration (ensuring what you design is buildable), and internal enablement (teaching your frameworks to the deployment team). WHAT SUCCESS LOOKS LIKE IN YEAR ONE - Inbound AI Methodology Defined: You've synthesized best practices from 5+ health system deployments into a clear, documented methodology for inbound AI in healthcare. This becomes the Hippocratic AI standard—how we approach every inbound deployment from discovery forward. - Repeatable Configuration Framework: You've designed the configuration architecture (decision tree patterns, IVR logic flows, provider directory mapping, escalation rules) that deployment strategists and FDEs will use repeatedly. It's documented, tested, and proven across 3+ customer deployments. - Deployment Playbook: You've codified the end-to-end deployment model: discovery, configuration, testing, go-live, iteration. This becomes the playbook that deployment teams execute on every inbound engagement. - Customer Learnings Synthesized: You've worked hands-on with 5-7 health systems and health plans on their inbound AI deployments. You've labeled decision trees, configured IVR logic, and validated configurations against real patient call patterns. You understand what works, what doesn't, and why. - Product Requirements Translated: You've translated patient access workflows into crisp product requirements and configuration standards. You've submitted 3-5 feature requests to the Front Door product team—each one addressing a scaling constraint you discovered in the field. - Engineering Partnership Established: You've built credibility with the Front Door product and engineering teams. They see you as the voice of inbound deployment reality. Product roadmap priorities reflect your input. - Enablement & Documentation: You've created the frameworks, decision trees, configuration templates, and documentation that deployment strategists and FDEs will use to execute inbound deployments without you. Training is documented. Patterns are replicable. - Competitive Differentiation: You've identified what makes Hippocratic AI's inbound approach different/better than Hyro, Orbita, Nuance, Notable, Fabric. You've articulated this in customer conversations and product strategy. - Scaling Signal: Your methodology and frameworks have been used by 3-4 other deployment team members. They're not coming back to you with "how do I...?" questions; they're following your playbook and executing successfully. YOUR CORE RESPONSIBILITIES - Inbound AI Methodology & Framework Design: Define the core methodology for inbound AI configuration, decision tree architecture, IVR logic, and provider directory setup. This becomes the standard the entire organization follows. Design repeatable patterns for call center workflows, patient access scenarios, and escalation logic that apply across different health systems and health plans. Document your methodology in clear, usable frameworks that deployment teams can execute without continuous guidance from you. Continuously refine the methodology based on learnings from new deployments and customer feedback. - Customer Implementation & Requirements Translation: Partner directly with 5-7 health system and health plan customers on inbound AI deployments. Spend significant time in configuration sessions, validation work, and go-live support. Translate patient access, call center, and inbound workflows into crisp product requirements and configuration standards that scale beyond individual deployments. Identify where your methodology breaks or needs refinement. Feed learnings back into the framework. Validate that configurations perform correctly against real patient call patterns and business metrics. - Product & Engineering Partnership: Work closely with the Front Door product and engineering teams to ensure the methodology you define is technically sound and buildable at scale. Identify product gaps, configuration constraints, and feature requests based on deployment learnings. Prioritize ruthlessly—what unlocks the most scaling? Influence product roadmap priorities based on deployment reality (not just customer requests). Collaborate on product design for inbound features; ensure they're built with deployment scalability in mind. - Deployment Team Enablement: Codify your methodology into frameworks, playbooks, decision tree templates, and training materials that deployment strategists and FDEs will rely on. Train deployment team members on your methodology, frameworks, and best practices. Create documentation that answers "how do I configure X?" so deployment teams can execute independently. Build a knowledge base and community of