Skip to main content

Careers

Open positions.

Pipeline-stage roles for the build-out. If you have built regulatory submissions for clinical software, shipped EMR integrations at production scale, or led clinical AI safety work, the descriptions below are written for you.1

The team is small and technical. The hiring bar reflects that, engineering depth and regulatory experience over title or institution. See the positions →

Figure 1.1

Four capability areas

Editorial four-quadrant capability map titled FOUR CAPABILITY AREAS, regulatory, clinical integration, AI safety research, customer engineering, with role-dot nodes in each quadrant, hairline annotations underneath, and a muted-teal arc orbiting one quadrant indicating active hiring.
Each open role lives in one of these four areas. The hiring document explains how each position takes specific architectural ownership.

By the numbers

Hiring context.

  • 3 (Open positions) — Pipeline roles posted — Each role has a written job description and a clear technical scope. We do not hire in advance of having real architectural ownership to assign.

  • Post-award (Engagement) — Pipeline timing — Pipeline-stage roles activate as the build-out scales. We welcome conversations now; engagement starts as each role is brought online.2

  • 1 (Substrate) — One codebase across the company — Every role contributes to one shared codebase. No track-specific silos, no AI-only versus compliance-only divide. Engineering depth across the full pipeline.

Capability areas

Four areas where the platform needs depth.

The open roles cluster into four areas that the platform must grow to support the next stage of the build-out. Each is a distinct architectural discipline, and each has named ownership in the hiring plan.

  1. Regulatory — Regulatory submission ownership for the AI-supervision protocol and the clinical-decision-support runtime. SaMD classification, predicate analysis, and 510(k) pathway work.

  2. Clinical integration — Production-grade FHIR R4 integration depth across enterprise EMRs. LIS, CIS, and CRM boundary work. Site-specific deployment that survives the long tail of EHR data quality.

  3. AI safety research — Supervision protocol research, hard-to-vary explanation construction, and adversarial evaluation against published clinical evidence.

  4. Customer engineering — Onboarding cadence, in-flight site engineering, and the SLA loop. The discipline that turns a deployed engine into a customer outcome.

How to apply

Email a CV and a paragraph on why this role.

Send to anton@regain.ai with the role title in the subject. We read every email. The paragraph matters more than the CV; specifics matter more than credentials.

Figure 3.1, 233 rules, the substrate every role contributes to

Editorial marginalia hiring-pipeline timeline titled POST-AWARD BUILD-OUT, four sequential nodes pipeline-stage / engagement / role-filled / scaled, with a muted-teal arc marking the build-out clock. Hairline navy linework on cream paper.

Figure 4.1

Ownership surfaces, what each role takes

Editorial architectural surface map titled OWNERSHIP SURFACES, four labeled cluster bubbles (regulatory, clinical integration, AI safety research, customer engineering) above a horizontal BUILD-OUT timeline, with a muted-teal hairline arc orbiting the AI Safety cluster indicating active hiring.
Each open role takes ownership of one specific architectural surface. The hiring document for each position names the surface and the success criteria.

Read more

Adjacent sections.

Footnotes

  1. All listed roles are pipeline-stage. We do not hire to fill seats; we hire to take ownership of specific architectural surfaces.
  2. Engagement timing follows the build-out cadence. Conversations are welcome at any stage.