Full Stack Engineer

Onovara is a clinical-grade longevity and healthspan membership platform, incorporated in Abu Dhabi (ADGM). Members follow a personalized, clinician-anchored annual programme - comprehensive testing, a structured plan, and continuous support from Carla, our AI adherence and lifestyle companion - with progress measured through sustained adherence and a longitudinal biomarker record that members own.

Our positioning is deliberate: process truth over outcome promise . We anchor to behavioural transparency and sustained adherence rather than outcome claims, we build to EU clinical standard from day one, and every member-facing scientific claim is drawn from a ratified Claims Register and reviewed for accuracy before publication - without exception.

We are pre-launch, moving toward first market entry, and this role completes the clinical and scientific core.

The role

We’re an early-stage, clinician-led digital health company, building to EU regulatory and data-protection standards. You’d be one of our first engineers, working directly with the founding team.

You’ll own the product surface end to end - the mobile app users work in and the console clinicians work in - from data model through interface.

The engagement begins with a defined MVP build and is structured to convert into a permanent senior role.

What makes this hard

• Correctness is a structural property, not a UI behaviour. In health software, “the interface doesn’t show it” is not the same as “it cannot be reached.” Rules about who may see what have to live somewhere a careless query, a future feature, or a compromised client cannot get around.
• The system has to be able to evidence its own behaviour. Months later, someone outside the company may need to establish what was accessed, by whom, and when it was approved. Software that can only assert it behaved correctly is worth very little in this domain.
• Clinical authority has to be legible in the data. Where clinicians sign off on what the software produces, that approval is a state the record carries - and what was proposed stays distinguishable from what was approved, permanently.
• One product, several very different markets. Different languages including Arabic and RTL, different regulatory regimes, different payment realities. Configuration, never a fork.

If that sounds like the interesting part rather than the annoying part, we should talk.

• Senior-level autonomy - you work from a written spec and deliver working, tested software without day-to-day management.
• A track record of owning something end to end, shipped and used by people who depended on it working.
• Real depth in the data layer - you design the schema before the screen, and you know how to make a rule the application layer can’t accidentally break.
• Judgment about correctness under time pressure - you know which shortcuts are recoverable and which ones you can never undo.
• Strong TypeScript, and mobile shipped to real users. We build in React Native; if you’ve shipped cross-platform mobile in something else and know why the hard parts were hard, tell us.

Strong plus

• Experience in a regulated or safety-critical domain - health, fintech, legal, aviation. Anywhere “it usually works” wasn’t good enough.
• Healthcare data or interoperability: FHIR, HL7, lab ingestion, wearable APIs.
• Internationalisation and RTL done for real, not as an afterthought.
• Design sensibility - you care how it looks and can hold a bar without a designer in the room.

We care more about what you’ve built and how you think than which frameworks are on your CV. Good engineers pick up tools quickly; judgment takes longer.