Open positions
2
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.
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
By the numbers
Hiring context.
Engagement
Post-
Pipeline timing
Pipeline-stage roles activate as the build-out scales. We welcome conversations now; engagement starts as each role is brought online.2
Substrate
1
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.
-
01
Regulatory
Regulatory submission ownership for the AI-supervision protocol and the clinical-decision-support runtime. SaMD classification, predicate analysis, and 510(k) pathway work.
-
02
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.
-
03
AI safety research
Supervision protocol research, hard-to-vary explanation construction, and adversarial evaluation against published clinical evidence.
-
04
Customer engineering
Onboarding cadence, in-flight site engineering, and the SLA loop. The discipline that turns a deployed engine into a customer outcome.
Positions
Roles open for the current and pipeline-stage build-out.
PIPELINE
FDA Regulatory Consultant
SaMD / AI-ML Medical Devices
Define the dual-track FDA strategy for autonomous clinical AI: De Novo + BDD (TA1) and MDDT qualification (TA2). Pipeline-stage role; engagement begins as the build-out scales.
PIPELINE
Clinical Integration Lead
EHR/Workflow — Pipeline-Stage Role
Build the FHIR/HL7 bridge connecting our CVD Agent to Epic at US academic medical centers.
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
Figure 4.1
Ownership surfaces, what each role takes
Read more
Adjacent sections.
Team
The current roster, leadership, engineering, customer service, and QA. Five people, two entities, one substrate.
Meet the team →Epistemology
How we know what we know. The Popperian foundation behind every clinical AI claim and every supervision verdict.
Read the approach →About
An infrastructure company, not a SaaS dashboard. Self-funded, two-org structure, clinical systems deployed at medical centers in Central Asia.
Back to the About hub →Footnotes
- All listed roles are pipeline-stage. We do not hire to fill seats; we hire to take ownership of specific architectural surfaces.
- Engagement timing follows the build-out cadence. Conversations are welcome at any stage.