About the role

Senior Backend Engineer enhancing health data platform at Molecular You. Owning platform quality, driving technology adoption, and ensuring security compliance.

Responsibilities

Own platform quality and consistency — you notice when two services handle errors differently and fix it, not file a ticket
Thoughtful introduction of new technology — you're skeptical until it earns its place, then you drive adoption through
Security and compliance balance — you've made design decisions where delivery and security were in tension, and you navigated them with judgment, not just caution
Production improvements from diagnosis through to resolution — you close the loop
New health report products developed alongside our scientific PM — from clinical question to shipped feature

Production experience with Ruby on Rails and Elixir/Phoenix — shipped and operated, not just familiar
Distributed systems in practice: async messaging (RabbitMQ or similar), failure modes, idempotency, dead-letter queues
Infrastructure ownership: Terraform and AWS at a level where you can drive a change, not just read one
At least one example of reducing platform entropy — a migration, deprecation, or refactor that made a system class simpler, not just larger
Experience owning a security or compliance decision end-to-end (HIPAA/PIPEDA context is a plus; the judgment is the requirement)
Clear, direct communication — you can explain a technical trade-off to a scientific PM without either oversimplifying or retreating into jargon

Ownership of platform quality and engineering standards across a production health platform
A role where your architectural decisions are load-bearing, and you'll know it