[https://app.ashbyhq.com/api/images/user-content/b5f7de27-4bd6-4d48-b6ed-ec89eb566843/7f6782d8-2749-472d-a68e-38abdcdf80a8/1750099265864.jpeg] HEALF IS EUROPE'S FASTEST-GROWING COMPANY. Number one on the FT1000, number one on the Sifted 100. From £1m to over £100m in under three years, with a small, talent-dense team and an electric culture with day one founder intensity. Now we're aiming for £1bn in the next three. We curate the world's best wellbeing brands across The Four Pillars™: EAT, MOVE, MIND, SLEEP. That's the first chapter. THE NEXT CHAPTER IS HARDER AND MORE INTERESTING. We are moving from one market to many, from e-commerce to a technology platform, and from curating wellbeing to defining it. We are a health company, so we think we should act like one. At its fullest expression, Healf redefines what wellbeing means for tens of millions of people. WHY THIS ROLE IS HEALF At Healf, we think engineering judgment is one of the most important forms of capital allocation in the company. Every architectural decision made in the next twelve months determines what is possible in the next five years. Every hire you make changes what the platform can become. That is why we do not see this as a conventional engineering leadership role. Engineering leadership is the functional label. Defining what a next-generation wellbeing intelligence platform looks like is the real job. We are not laying down tracks. We are deciding where the train goes. Somewhere right now there is a principal engineer at a Series B health-tech company who has spent three years making the right calls quietly. Who designed the system that works. Who has said no to things that looked fast but would have cost the company two years of rework. That person probably has never heard of Healf. They wouldn't click on a LinkedIn InMail. But if someone who understood what they actually cared about reached them with the right story at the right moment, they would listen. There is also a founding engineer at a well-known consumer tech company who is twelve months past the point where the work became maintenance. Who built the thing, watched it scale, and is now ready to build the next thing. They are not looking. But they are ready. These are the people we want. And this is the role those people will take. WHAT YOU’LL OWN - The architecture. You will design the full wellbeing intelligence stack from first principles. Backend, data, ML systems. Infrastructure capable of learning from live user interaction. The choices you make in the next six months will define what's possible in year three. You will own those choices. - The build vs buy decisions. Every platform team reaches these inflection points. You will own them with authority and with the context to make them well. - The engineering principles. Not a style guide. The actual principles that govern how your team thinks about quality, velocity, and long-term consequences. You will define what good looks like here. - The technical strategy. You will partner directly with the CTO. This is not advisory. You will have real authority over the direction of the intelligence layer and the product platform it powers. - The team. You will grow and mentor the engineers who build alongside you. Every person you bring in raises the floor. You will build the nucleus that scales wellbeing intelligence. - The product feedback loop. You will work cross-functionally with Product and Design to ship. You will build via continuous experimentation. You will be close to real users and real outcomes. WHAT YOU'LL DELIVER IN THE FIRST 12 MONTHS - A production-grade intelligence layer powering personalised decisioning for hundreds of thousands of customers - A scalable data architecture designed for international growth from the start - A high-talent engineering nucleus built around your judgment - Clear product differentiation driven by intelligence, not curation alone - A platform that others in health tech study and try to replicate WHY YOU’RE HEALF You have built something from zero. Not joined after product-market fit. Not inherited a working system. You architected something from the beginning and watched it scale to meaningful usage. You know what that feels like in both directions — the early ambiguity and the later scale. You have made platform-level decisions with long-term consequences. And you have lived with them long enough to know which ones you got right. You have built or integrated ML and data-driven systems in production. Not in notebooks. Not as experiments. Shipped, live, used. You have influenced technical direction beyond your immediate team. Not through authority. Through judgment that others trusted. You have operated in a high engineering bar environment where architectural thinking was respected and expected. You are not looking for the next job. You are looking for the thing worth building next. THE REALITY This is hard. It requires speed and precision. It requires building for scale without overbuilding. It requires making good decisions in conditions of genuine ambiguity, with real consequences, and without the luxury of consensus. You will sometimes be wrong. What matters is that your judgment compounds over time and your errors get smaller as the system gets bigger. If you want to spend the next two years building something foundational that others will be building on for a decade, this is that opportunity. SHOW US - A system you architected from zero. What were the first principles you started from? What did you get right early that saved you later? What did you get wrong, and how did it shape the next decision? - A build vs buy decision with real stakes. What did you choose, why, and what happened? - A moment where you saw how something would break six months before it did. What did you do with that knowledge? - An engineer you hired or developed who became better than you expected