Not a typical engineer.
Graphic-design roots, systems thinker, twenty years hands-on. I treat user problems as the interesting part and writing the code as the means to solve them — and I tend to look upstream of where the symptom showed up.
Graphic artist → developer → staff engineer.
I started out as a graphic artist in advertising, and that's permanently shaped how I work. I treat user problems as the interesting part, and writing the code as the means to solve them. Requirements are not interesting — problems are.
Given a problem, I tend to look upstream. The best fix often lives a level or two above where the symptom showed up, and sometimes in a different place entirely. My most impactful work has come from investigating hard problems and prototyping solutions in small teams before committing to a full build.
For the last several years I've been a Staff Engineer and Engineering Manager at Volvo Cars, staying hands-on while shaping the architecture of consumer-facing platforms in React, TypeScript, and GraphQL at global scale. A couple of things I'm proud of: cutting platform latency from 3 seconds to under 500ms, and re-architecting the vehicle configurator so roughly half of all customer interactions became effectively instant. Neither came from incremental tuning — both meant rethinking the problem a level up.
I also cover product and UX for my team, which I genuinely enjoy. I'm a product-minded engineer, not someone looking to leave the code behind — I just do my best work in roles where what to build is as much my question as how to build it.
Selected Work
VIEW ALL PROJECTS →- TypeScript React Next.js GraphQL
volvocars.com — Commerce Platform
The car configurator had a 3-second latency problem. The fix wasn't where the problem appeared — it was a level up, in the data model and the API layer.
VIEW CASE STUDY →