Background
About me
I'm a Senior Architect with over a decade of experience working on systems where the stakes are real. Insurance platforms, industrial IoT, large-scale enterprise integrations. The kind of environments where a poor architecture decision doesn't just slow you down, it costs you years.
A lot of my work sits at the messy centre of large organisations, where systems that were never meant to talk to each other have to, where data has to move reliably across registries, claims platforms and third-party vendors, and where the integration is the hard part. I've owned that work end to end: the design, the patterns, the stakeholders across every system that touches it, and the steering-committee conversations that keep it on course.
Alongside that, I've spent recent years in DevSecOps and quality engineering. I co-founded a DevSecOps function at a major Nordic insurer and built a Center of Excellence that set standards and ways of working across multiple engineering teams, including the security tooling platform used across the organisation.
Before all of that, I led a small engineering team at EPOS, where I designed and physically built an IoT test lab to simulate real-world hardware interactions. It didn't exist before. We built it from scratch, both technically and organisationally. That's a fairly good example of how I work. I don't wait for perfect conditions. I figure out what's needed and build it.
These days a good share of my hands-on time goes into AI. I'm building Lucra AI, an AI assistant for hiring teams, which keeps me in the code daily: agent design, prompt and context engineering, the product itself. It's also given me fairly grounded views about where AI earns its place in a system and where it's mostly noise, which tends to be more useful to a client than enthusiasm on its own.
My background sits at the intersection of technical depth and delivery. I've worked closely with both engineering teams and senior stakeholders, translating architecture decisions into language that works in a boardroom, and translating business constraints into approaches engineers can actually build. I understand both sides of that conversation and have spent a long time getting better at bridging them.
I work independently because it means the person you speak with is the person doing the work. No handoff after the proposal. No junior team in the background.
I take on both focused engagements and longer embedded roles, depending on what the situation actually calls for. What draws me to a piece of work is whether it has real impact. Problems that matter to the people working on them, and outcomes that hold up over time.
If any of that sounds like what you're looking for, I'm happy to have a conversation.