Company
Role
KLAR is a Northern European private equity firm (~€2bn AUM) investing in business services and industrial technology across the Nordics, DACH, Benelux, and the UK. We own and operate 10+ portfolio companies with over 10,000 employees combined.
Each runs on its own combination of ERPs, CRMs, field-service tools, and accounting systems, and each has workflows where the right piece of software would meaningfully impact how the business operates and how it performs financially. This role exists to find those workflows and build for them – backend, integrations, and AI where it earns its place.
This is a key technical hire into KLAR’s Catalyst Team (KCT), KLAR’s value-creation team working hands-on inside portfolio companies on 4-8 week implementation sprints. As such, you will play a key role in defining the technical foundation: the stack, architecture, and engineering patterns that future deployments will build on.
You will work hands-on inside portfolio companies with existing infrastructure, such as ERPs, CRMs, field service tools, and accounting systems, and build production software on top of them. The work spans backend development, systems integration, AI/LLM deployment, workflow automation, and cloud infrastructure.
You will work in focused 4-8 week sprints, shipping real software into production at the end of each engagement. This is a hands-on role with regular on-site work alongside teams across Northern Europe.
Day to day, this means:
You have 5+ years of experience building and shipping production software, and a track record of delivering AI-powered features or products in real-world environments. Above all, you’ve owned production software end-to-end: built it, shipped it, and operated it long enough to know what production actually demands.
You’ve worked at the intersection of AI capabilities and business needs, and you’re comfortable being the only technical person in a room of non-technical operators. You can navigate imperfect systems and undocumented APIs, push back when the requirement is wrong, and ship pragmatically when it is right. You know how to turn messy problems into software that actually gets used. You find lifting performance in a real operating business as interesting as the technology that does it.
Python is the primary language, but strong engineering judgement and a pragmatic approach to problem-solving matter more than stack preferences. You’re comfortable across cloud environments like AWS or Azure, and you adapt your architecture and tooling to fit the situation.
Technical requirements
Nice to have: