Applied AI Engineer; Forward Deployed) NYC or SF

Concurrence (formerly Amigo) is building the platform healthcare organizations use to build their own clinical AI agents. Our mission is to make excellent care accessible to every patient, not rationed by the limits of clinician time.

Underneath our platform is the Health World Model, which unifies a health system’s data into a living, event-level record of every patient’s care. On top of it, agents handle work across the patient journey, from intake and scheduling to medication management and clinical decision support.

Our agents have supported more than 10 million patient encounters and are on track to grow tenfold this year. We run natively on Databricks, integrate with every major EHR, and are backed by Madrona, General Catalyst, and Optum Ventures. We’re about 35 people, working in person in New York and San Francisco.

Applied AI is where Concurrence meets the real world. Our core engineering team builds the platform. We take it into health systems and build what each customer actually needs on top of it, as durable software that runs in production.

As a Senior Applied AI Engineer, you own an entire customer use case, not a ticket or a slice of one. You take a deployment from brief to production. You make the architecture calls inside it, commit the timeline, and carry the outcome.

Success isn't your agent staying up. It's the customer's number moving: more intake handled, fewer denials, faster time to billing close.

Your work doesn't stop at one customer. We build custom first, on purpose. When the same shape shows up under two customers, you're the one who sees it, and the pattern you proved becomes part of the platform everyone builds on next.

Applied AI runs ahead of the platform, not behind it. Our field work is the R&D that decides what Concurrence becomes.

• Own a whole use case, end to end. You run the build from the deployment brief to production and beyond. You set its internal design, commit the timelines, and ship at a bar that doesn't need anyone checking behind you.
• Build agent systems that hold up in clinical settings. That means hierarchies of agents and skills rather than one monolith, and evals that measure distributions, not vibes. Nothing reaches a patient until it clears our safety floor and eval gate.
• Take on the integration reality. EHRs, legacy systems, and customer data come in every shape. You find the path from what the customer has to what the platform needs.
• Make it compound. You turn field-proven patterns into first-class platform capabilities. You also push proven work down from agent reasoning into deterministic data lookups, the move where twenty tool calls become one. That's how we grow without turning into a services shop.
• Push back early. When a spec was never vetted, an integration isn't supported, or scope quietly changed mid-build, you raise it before the build pays for it.
• Raise the people around you. Mentor the engineers on your use case and help set how the team builds. Write documentation good enough that a coding agent or a new hire could pick up your work.

• Have shipped and owned complex production systems end to end, with real users depending on them.
• Have real experience building with LLMs and agents in production, or the engineering depth to get there fast.
• Treat non-deterministic systems with rigor. You know three runs of an agent is a feeling, not evidence.
• Hold the near term and the long term at once: what a decision costs now, and what it makes easier or harder for the team later.
• Are comfortable in the room with customers and clinicians. You'd rather understand the workflow than wait for a perfect spec.
• Care about craft. Your systems fail loudly to you before they fail…