AI Operations Associate

Key Responsibilities

• Own the automation roadmap and deliver measurable operational leverage against it.
• Shadow clinical and back-office teams to understand workflows and find the highest-ROI automation opportunities, then build repeatable processes for capturing, shipping, and monitoring automations in production.
• Lead data integrations across major EHRs owning the error handling, and reliability of those pipelines.
• Match the automation stack to the workflow. Use APIs and portal integrations where possible, and browser/desktop automation and screen-level robots for last-mile flows.
• Stand up and maintain internal AI tooling (LLMs, agent frameworks, knowledge assistants) and train teammates to become power users.
• Scope and execute with automation vendors, holding them to delivery, quality, and reliability standards.
• Partner with Engineering on integration patterns, data contracts, and what belongs in product vs. ops.
• Enforce documentation, monitoring, and change-management practices for reliable production systems and data-driven decisions.
• Act as a conduit between operators, clinicians, and internal teams, informing product and roadmap with workflow-level insight.

Requirements

• 1–3 years of experience in management consulting, software engineering, product management, or a similar analytical/technical role, ideally with exposure to high-growth or ambiguous environments.
• Strong problem-solving instincts with a bias toward action: comfortable scoping an ambiguous problem, breaking it down, and shipping a working solution end-to-end.
• Genuine fluency with modern AI tooling (LLMs, agent frameworks, prompt engineering) and a clear sense of where AI works well versus where it breaks down.
• Hands-on technical aptitude: comfortable with APIs, light scripting (Python, JavaScript, or similar), and picking up new tools quickly. You don't need to be a senior engineer, but you should be able to read code, write automations, and debug your own work.
• Exposure to healthcare, operations, or regulated industries is a plus, but not required. We care more about how quickly you can learn the domain than what you've already seen.
• Strong written and verbal communication; able to translate between technical and non-technical stakeholders and write clearly for leadership.
• Comfort working cross-functionally with Engineering, Product, and Operations, and an ownership mindset about outcomes rather than scope.
• Bachelor's degree.