animo (v. Latin): to breathe life into, to give spirit or motion to

An EMR is a static system of record. We’re building the AI operating system that transforms it into an autonomous system of action.

Every medical practice in America sits on top of a patient panel full of signals: uncontrolled A1Cs, missed lab work, open care gaps, incomplete follow-ups, and billable work nobody has the staff to chase. The EMR contains the answer to what should happen next. Today, that answer dies inside a chart. Patients fall through the cracks and miss out on care while practices leave millions of dollars trapped in their EMR.

Animo is building the AI operating system that closes the loop. We connect any major EMR, HIE, and payor through a clinical rules engine and a suite of autonomous agents that turn dormant patient data into completed visits, closed gaps, and incremental revenue. We call it the EMR Brain. It already powers two product lines, with more on the way.

We're about to hit $1.5M in annualized revenue in less than six months of going live. We're on track to raise our Series A in the next three months.

We're hiring our founding engineer. Based in NYC. In-person preferred, open to hybrid.

What this is not

It's not a chatbot wrapper. It's not a research role. It's not dashboard software. The work is backend, data-heavy, and customer-close. LLMs make the product architecturally possible, transforming messy, unstructured clinical context into reliable autonomous action. Done right, it unlocks care for thousands of patients who'd otherwise fall through the cracks.

What you'd actually build

You'd work directly with me and Lazar (CTO, my co-founder) on the systems that make the platform real:

• LLM-powered clinical systems. Voice agents, care plan generation, autonomous charting, clinical summarization, and other agentic workflows in a compliance-heavy environment.
• Data extraction. Pulling structured data out of EMRs, clearinghouses, and unstructured clinical documents via APIs, EDI, browser automation, and LLMs. The data is messy and the standards are fiction.
• Continuous care loop systems. Long-running clinical workflows that connect patients, providers, and payers across EMRs and back.
• Compliance + billing infrastructure. APCM, CCM, CMS, and FFS billing pipelines that hold up to audit. Boring on the surface, load-bearing in reality. This is how our customers actually get paid.
• Data pipelines. Ingestion, normalization, and enrichment of clinical and billing data at scale.
• Backend services + infrastructure. Production services, async task queues, CI/CD, cloud deployment.
• Product. Sitting with clinicians and operators, watching them work, turning what's broken into shipped software. If you don't want to be in the room with the user, this isn't the job.

Who you are

We care more about range, ownership, and velocity than credentials.

• You take end-to-end ownership: data model → service → deploy → post-mortem without hand-holding.