Solutions Architect, Inbound AI Deployments

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 practice around inbound deployments.

• Strategic Vision & Competitive Positioning: Define what makes Hippocratic AI's inbound approach differentiated vs. competitors (Hyro, Orbita, Nuance, Notable, Fabric). Articulate the strategic positioning of our inbound solutions to customers and internally. Identify white space and expansion opportunities in the inbound market (new use cases, new customer types).

What You Bring

Must-Have

• BA/BS degree required.

• Domain expertise in patient access, call center operations, or inbound workflows. You understand what makes a good call center configuration, what drives call routing decisions, how IVR impacts patient experience, why provider directories matter.

• 8+ years in inbound/patient access technology or healthcare operations. You've spent significant time in or around call centers, patient access workflows, IVR systems, or inbound healthcare technology. You understand the pain.

• Deep hands-on experience with inbound AI or contact center automation. You've personally configured IVR systems, designed decision trees, or deployed call center AI solutions. You've labeled data, tested configurations, validated performance. You know how to make it work in practice.

• Proven track record building repeatable systems. You don't just execute one-off projects. You've built frameworks, playbooks, or methodologies that let other people execute consistently after you. People use your work; they don't reinvent it.

• Full-lifecycle ownership mindset. You're comfortable owning the entire deployment lifecycle—from customer discovery through configuration, testing, go-live, and iteration. You don't hand off; you see it through.

• Product thinking with operational execution. You think strategically about what should be built and how to scale. You also know how to get into the weeds—configuring systems, testing edge cases, debugging issues.

• Communication and persuasion skills. You can explain complex inbound workflows to non-technical customers. You can articulate product requirements to engineers. You can align teams around a methodology.

Nice-to-Have

• Hands-on experience with inbound digital front door platforms (Hyro, Orbita, Nuance, Syllable, Notable, Fabric).

• Background in healthcare operations, health plans, health systems, or patient access.

• Experience building configuration tools or internal frameworks that enable others to execute consistently. Familiarity with healthcare data standards (FHIR, HL7) and EHR integration points relevant to inbound workflows.

• Prior experience at healthcare AI/SaaS companies or forward-deployed organizations.

• Track record of mentoring and enabling other operators to execute frameworks you've built.

Why Hippocratic AI

• You're joining the future of safe, clinical AI. Hippocratic AI is the only generative AI platform built from the ground up for safe, autonomous clinical conversations. Our 99.9%+ accuracy has been earned through rigorous clinical training and validation.

  The team is world-class. Founded by healthcare innovators, physicians, and AI pioneers from El Camino Health, Johns Hopkins, Washington University, Stanford, Google, Meta, Microsoft, and NVIDIA. You'll work alongside people who've spent careers transforming healthcare.

• You're backed by the best. Recent $126M Series C at $3.5B valuation, led by Avenir Growth, with support from CapitalG, General Catalyst, a16z, Kleiner Perkins, and leading healthcare systems. We have the resources and runway to execute our vision.

• You're defining a new category. Inbound AI in healthcare is nascent. There's no standard playbook. You're not optimizing someone else's system; you're creating the system that becomes the industry standard. That's rare.

• You partner with world-class teams. You'll work alongside experienced deployment strategists, forward-deployed engineers, product leaders who understand healthcare, and AI researchers pushing model boundaries. You'll learn as much as you teach.

• The platform actually works. You're not trying to make a mediocre AI system work in healthcare. Hippocratic AI has 99.9%+ accuracy and trust from leading health systems. You're building methodologies on top of something that already works.