Full-Stack Engineer, Product & Patient Experience - HealthTech

Full-Stack Engineer, Product & Patient Experience

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 product-minded full-stack engineer to own the patient-facing experience. This role sits at the intersection of engineering, product and design. You will own outcomes, not just tickets: you decide what a flow should feel like, build it end-to-end and watch real patients use it within weeks.

A confusing payment step or an unclear status message is not a cosmetic problem in healthcare; it is the difference between a patient continuing treatment and dropping out. We want someone who notices those details and then ships.

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 the patient side as your home turf.

• Build product, end-to-end: take a patient problem from discussion and Figma through React and React Native to the Hono API and PostgreSQL, ship it, and watch real patients use it within weeks.
• Think in systems and abstractions: see the platform behind the feature request and build the right component or primitive once, so it works in the web app and both native apps.
• Own patient-portal flows: onboarding, subscriptions, notifications, profiles and the portal itself, including the states nobody drew (loading, empty, error, recovery).
• Improve Velora Tools where the clinician experience meets the patient experience: status, follow-ups, communication.
• Make product and prioritisation calls with product and design, not just execute on specs handed to you.
• Build the backend and data changes your features need, including Stripe, Firebase and BankID integrations.
• Use PostHog and patient feedback to find out what actually works, and iterate.

You may be a good fit if you

• Have 3+ years of experience building production software, ideally full-stack in TypeScript.
• Have strong product taste: you notice spacing, hierarchy, wording and interaction states, and you can explain why a change improves the experience.
• Can operate as a team of one when needed, taking a feature from idea to shipped, while keeping the team informed.
• Own outcomes, not just code. You care whether the thing you built actually solved the patient's problem.
• Hold yourself to a high bar without needing external pressure.
• Are comfortable making decisions with incomplete information.
• Use AI tools daily in your development workflow, understand where they add value and where they can mislead, and actively keep up with a field where tools, models and best practices evolve from week to week.

Strong candidates will have

• Shipped consumer-facing products where the quality of the experience visibly affected the numbers.
• Deep comfort with React and TypeScript, and working knowledge of a Node/Bun backend, PostgreSQL and an ORM.
• Experience with React Native, design systems or accessibility work.
• Experience with payments, identity or another domain where mistakes actually matter.
• 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.