Senior Technical Program Manager, Applied AI [NYC or SF]
- Compensation
- $175K–$230K / yr
- Location
- New York City
- Work setup
- Onsite
- Seniority
- Senior
- Employment
- Full time
- Experience
- Not specified
- Category
- Ai engineering
- Posted
Skills
Must have
- You've shipped software as an engineer before moving into program management, and you can still read code, follow a system design discussion, and reason about APIs, data pipelines, integrations, and L
- You've run delivery as a technical program manager, engineering manager, or delivery lead, including across multiple concurrent teams, customers, or deployments.
- You've built a team's execution system from scratch, not just operated one someone else designed.
- You're deeply fluent in Linear or a comparable tool, and you've used its API, integrations, or automations to make tracking cheaper for everyone.
- You've measured delivery and estimation in a way engineers trusted, and you know how to keep those metrics from being gamed.
- You earn engineers' respect rather than their tolerance. You're direct, you ask the uncomfortable question, and people still want you in the room.
- You have relentless follow-through. This is the job.
Nice to have
- Experience in healthcare or health IT, such as EHR integrations, hospital security reviews, clinical validation cycles, or HIPAA environments
- Experience in a forward deployed, solutions engineering, or professional services organization
- Familiarity with Databricks or other modern data platforms
Full description
About Concurrence
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.
About this role
Our Applied AI team is a group of forward deployed engineers (FDEs). They take Concurrence from signed contract to production at our customers, usually across several accounts at once. Each account has its own data, integrations, clinical workflows, and deadlines. This role reports to the Head of Applied AI.
Our FDEs are excellent builders. What we need now is someone who makes the whole operation legible. That means knowing at any moment what every FDE is working on, what's at risk, what's blocked and why, and whether we'll hit what we've committed to.
This is a hygiene role in the best sense. If work isn't tracked in Linear, we can't plan capacity, judge workloads, measure on-time delivery, or help people get better at estimating and meeting dates. You'll make Linear the trustworthy source of truth for applied work. You'll do it with the follow-through, judgment, and technical credibility that make engineers see it as useful rather than bureaucratic.
You've been an engineer, and that matters. When an FDE says they're "blocked on platform," you need to know whether that's true. Is it a real platform gap, or applied-side work that hasn't been done? You need to be able to push back credibly in either direction.
Above all, you have relentless follow-through. You don't let things drop, you don't wait to be asked, and you don't stop chasing until it's done.
What you'll own
- The cross-account delivery plan. You'll own the plan across every active deployment: dates, dependencies, FDE capacity, and risk. You're the person who sees conflicts coming two weeks before they hit.
- Linear as the source of truth. You'll design how Applied AI works in Linear and then hold the team to it. That includes the project structure per account, labels that separate applied blockers from platform blockers, an estimation scale, and a shared definition of done. The result: tickets are current, statuses are honest, and due dates are set and met.