Job Opportunities API

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 We think the companies that win the next five years are the ones that put a capable AI agent behind every function in the business, faster and more reliably than anyone else. Operations, supply chain, customer experience, marketing, finance, compliance. Work that used to take a team now takes an agent and a person who knows how to direct it. This is not a research role and it is not a conventional engineering role. AI engineering is the functional label. The real job is taking a problem from any corner of the company and turning it into a production agent that quietly does the work, week after week, without breaking. The best version of this person has strong judgment about how to build. They do not reach for the heavyweight tool every time. When an agent is a short build, they use what is already there, Claude's managed agents or something off the shelf, and they ship it the same week. When the problem is genuinely complex, they reach for LangChain, LangGraph, Pydantic AI, and instrument it properly in LangSmith. They know the difference, and they never over-build. Somewhere right now there is an engineer who has built agents that real teams depend on. Not demos. Systems that take action, recover from failure, and earn trust. They are not on the market. But they are past the point where their current work still teaches them something, and they are ready to build the next thing. This is the role that person will take. WHAT YOU'LL OWN The agents. You will build production agents across every function at Healf. You will be hands-on in the code, shipping, not directing from a distance. The work is broad by design: operations and supply chain one month, customer experience or marketing the next. The build approach. You will own how we build agents. Off-the-shelf and managed agents where the job is small and speed matters. Frameworks like LangChain, LangGraph and Pydantic AI where the problem demands it, with evaluation and observability through tools like LangSmith built in from the start. Choosing well, every time, is the job. So is knowing when not to build at all. Reusable building blocks. You will drive velocity by building reusable building blocks. Every agent should leave behind components the next one can use, so the team gets faster with each build instead of starting from scratch each time. The unhappy path. Anyone can demo an agent that works. You build for the times it doesn't. You design for failure, retries, edge cases and clean handoffs to a person when the agent should not decide alone. You ship, watch how it behaves with real users, and tighten it. An agent is finished when it can be trusted on its worst day, not its best. Build versus buy. Frameworks, managed agents, models, infra. You will own these calls with authority and the context to make them well, and you will not default to building when buying is faster and just as good. The engineering principles. Not a style guide. The actual principles for how we build agents that can be trusted. The core one is evaluation: you decide what a good answer looks like before you ship, build a way to measure it, and keep measuring so quality never quietly slips when a model or a prompt changes. On top of that