Founding Backend Engineer

About Neutropy

When a GP refers you to a specialist, the referral goes out and you are told someone will be in touch. So you wait. Days, weeks, sometimes months. Not because anyone is careless, but because reading every referral, calling every patient, and scheduling them in is slow, manual, endless work.

Neutropy fixes that. Our AI handles the entire workflow, from referral to scheduled appointment, cutting scheduling from days to minutes. We are live in Irish private healthcare today and scaling across the market.

The role

We are hiring our founding backend engineer: the first on the team, building directly alongside the technical co-founder. You will own the backend and the integrations that connect Neutropy to hospital systems, and keep them reliable as we scale from one hospital to many.

This is a high-ownership, 0-to-1 role. You will design the systems, build the integrations, and make the platform fast and dependable under real patient volume. The co-founder owns the AI and voice side, so your focus is the engine underneath: data, services, integrations and scale.

What you will do

• Own the backend end to end: services, data models and APIs the whole product runs on.
• Build and maintain the integrations that connect Neutropy to hospital systems.
• Make the platform reliable at volume as we go from one hospital to many.
• Shape architecture decisions. You will have real say.
• Ship end to end, and prove it works before you call it done.

What we are looking for

• 3+ years in backend development, strong in TypeScript, comfortable in Python.
• A track record of building and maintaining production systems and third-party integrations.
• Clean, pragmatic engineering and a bias for proving things work.
• Clear communication: you can explain a technical decision to a clinician and a co-founder in the same breath.
• Comfort owning a lot and working through ambiguity.

Strong pluses: healthcare data or any regulated-data environment (GDPR, Article 9); startup or early-stage experience.

Why this role

• Founding. You are first on engineering, building alongside the technical co-founder, with the ownership and equity that implies.
• Live and real. We are already in hospitals. Your code affects real patients from week one.
• Real craft. A clean, modern stack, serious test coverage, and a high bar for shipping things that work.