Arbetsbeskrivning

Full-Stack Engineer, Platform & Integrations

Velora Health, AI-native HealthTech · Stockholm, hybrid · Full-time

Stack: React and React Native · Hono on Bun · Drizzle and PostgreSQL · Google Cloud Platform · Stripe, Firebase, BankID, PostHog

About Velora Health

Velora Health is a rapidly growing AI HealthTech startup on a mission to address the leading causes of preventable death. Our goal is bold yet simple: a longer and healthier life for more people, through the fusion of personalized care and a holistic approach to health.

We started by tackling one of the biggest global health issues: obesity, which affects nearly 1 billion people worldwide. Through our platform and digital health clinic at velora.se we have already helped thousands of patients lose weight and keep it off, which means they live longer and with fewer diseases such as type 2 diabetes and cardiovascular disease. In Sweden alone, 2 million people could live longer with Velora. We are now expanding beyond obesity into broader chronic care, giving people access to the latest and most effective research-based treatments.

We are AI-native and use AI across the whole company. Today we are a 20-person team across clinical care, engineering, growth and operations. In engineering you will have five or six colleagues you work closely with every day across engineering, product and design, plus the clinicians who use what you build. We run two products on one TypeScript codebase, Velora Tools for our clinicians and the patient portal (web app plus two native apps), and we ship to production every week.

About the role

Velora is looking for a full-stack engineer to own the systems that have to be right: payments and subscriptions, identity, third-party integrations and the internal platform (Velora Tools) our care team runs on. You will own outcomes, not just tasks: when a Stripe webhook arrives out of order or BankID behaves unexpectedly, you are the person who understands the whole path and decides where the fix belongs.

The interesting work here is rarely an isolated endpoint. It is understanding the entire flow, choosing where logic lives, handling failure properly and keeping the platform easy to change as we grow.

What you'll do

We build two products on one TypeScript codebase: Velora Tools, the system our clinicians run their day on, and the patient portal, a web app plus two native apps (iOS and Android). You will work across both, with Velora Tools and the shared platform as your home turf.

• Build product, end-to-end: take a clinician or patient problem from investigation through the React UI, the Hono API and PostgreSQL to production, and follow it there.
• Think in systems and abstractions: see the platform behind the feature request, decide where the logic belongs and build the right primitive once for Velora Tools, the web app and both native apps.
• Evolve Velora Tools so clinicians and operations can work accurately and fast, from schemas to screens.
• Build and harden integrations with BankID, Firebase and external services, designing for partial failure and inconsistent responses.
• Add the logging, monitoring and error handling that make production understandable, and investigate incidents when they happen.
• Improve CI/CD, local development and testing on Google Cloud so the team ships faster with more confidence.

You may be a good fit if you

• Have 3+ years of experience building and operating production backend or full-stack systems, ideally in TypeScript.
• Think in failure modes: idempotency, retries, ordering, timeouts and what the user sees when something breaks.
• Can operate as a team of one when needed, taking a problem from investigation to production, while bringing in the right people when a decision affects the wider product.
• Own outcomes, not just code. You care whether the payment was actually correct, not whether the ticket was closed.
• Prefer the smallest change that solves the problem and can tell when a new abstraction is warranted.
• Hold yourself to a high bar without needing external pressure.
• Use AI tools daily, stay up to date as models, tools and best practices evolve, and confidently question generated answers, verify assumptions and recognise when privacy, security or correctness require extra care.

Strong candidates will have

• Built or owned payment, subscription or identity systems in production.
• Proficiency across the stack (TypeScript, React, a Node/Bun backend, PostgreSQL) with depth on the backend.
• Experience running services on GCP or a comparable cloud, including CI/CD, secrets and observability.
• Experience in healthcare, fintech or another regulated environment.
• A track record of shipping independently, not just contributing to larger efforts.

Logistics

Location: Hybrid, with our office in Stockholm. We like to see each other in person about once a week, but it is not a requirement; work from where you work best.

Language: Fluent Swedish, spoken and written, is required. Our clinicians, patients and internal tools are Swedish, and you will be talking to all three. Our codebase and documentation are in English.

Compensation: Monthly salary set by experience and scope.

Start: As soon as we find the right person.

We encourage you to apply even if you do not match every line above. We would rather talk to a strong engineer with an unusual background than miss them because of a checklist.

How we are different

We are a healthcare company that behaves like a product company. Payments, identity and clinical workflows are all in one codebase, so a single engineer can own a problem from the patient's screen to the database and back. Mistakes matter here, which is why we ship small, review carefully and keep the bar high.

We use AI heavily in development: exploring the codebase, prototyping, writing tests, reviewing changes. You choose your own editor and tools and we pay for them. You are still responsible for what you ship, and in a healthcare context that means knowing when the tool is wrong.

You will work directly with our lead engineers, product lead and the founders. There are no layers between you and the people who decide what we build.

We are 20 people today and the engineering team will roughly double over the next year. The people who join now will be the ones who shape how we build, and several of them will lead teams, own domains or take on roles that do not exist yet. Your scope here is set by what you take on, not by your title.