Lävi Clinical Suite

Careers

Work where the build refuses to lie.

We build regulated medical software the way it should be built — and we have arranged the tooling so that cutting corners is harder than doing it properly. If that sentence made you curious rather than tired, read on.

Clinical validation and regulatory development in progress · not CE-marked

01 — How we work

The discipline is the point

  • The build fails when the paperwork lies

    Traceability from requirements to tests is machine-checked. If a requirement cites a test that does not exist, or a controlled document drifts away from the shipped code, the build fails. We added those guards after our own audits caught traceability rows that did not hold. Once was enough.

  • Refusal is a feature

    The product's most distinctive behaviour is knowing when not to answer: when a longitudinal comparison fails its own prerequisites, the result is withheld and the refusal is reported. Engineering that honestly — fail-closed input handling, explicit abstention states, provenance on every run — is the day-to-day work here.

  • A documented lifecycle that is actually used

    IEC 62304 Class B lifecycle, ISO 14971 risk file, a controlled-document set — maintained beside the code and enforced by it, not an appendix written after the fact. A large automated test suite runs continuously across multiple runtime versions.

  • Small team, short distances

    The founder is a neuroradiologist who reads the studies this software is for. Clinical questions get answered across the table, not across a ticket queue.

02 — Practicalities

What you would want to know

Open roles. No formal open positions right now. Speculative applications are welcome — and read.

Where and how. Based in Tartu, Estonia. Working arrangements depend on the role.

Some of the plumbing, for orientation: Python, FastAPI, OHIF, Orthanc, PostgreSQL, DICOM and DICOMweb, Linux.

If your work touches medical imaging, clinical software or regulatory affairs, write to andreas@lavi-clinical.com — the founder answers his own email.

Status as of 2026-08-21