PORTFOLIO

Selected work

Two projects told as problems solved a level up, where the real fix lived above where the symptom showed up, rather than as a list of features shipped.

01 / PROJECT

Storefront Graph, the API behind volvocars.com

GraphQL Federation Search Vector Embeddings Platform Architecture

I joined after the endpoint was already federated. The work that mattered was what you can build on one API once stock cars and configurable cars finally live in the same index.

VIEW CASE STUDY →
The shape of Storefront Graph Hundreds of frontend clients call through a client registry into Storefront Graph, one federated GraphQL API. The graph fans out to nine subgraphs owned by six backend teams, each deploying on its own schedule: configuration, assortment, enrichment, price, availability, inventory, cart, visualisation, and the shared search index. The index holds stock cars and configurable cars together and is kept current by events rather than direct calls. Some subgraphs depend on two data sources owned outside the area, and a cache serves stored values when those go down. HUNDREDS OF FRONTEND CLIENTS Client registry Every caller known. Unknown clients turned away at the door. Storefront Graph One federated GraphQL API configuration assortment enrichment price availability inventory cart visualisation shared search index Nine subgraphs, six backend teams, each deploying on its own schedule The shared search index holds stock cars and configurable cars together, kept current by events Two data sources owned outside the area We could not fix them when they broke. A cache serves stored values, so an outage degrades part of a page instead of all of it.
02 / PROJECT

volvocars.com, the commerce platform

TypeScript React Next.js GraphQL Kubernetes AWS

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 →
The Customise your EX30 step of the car configurator on volvocars.com, showing the version chooser.

Want to talk through a problem?

I'm always happy to compare notes on hard frontend, architecture, and product problems.

START A CONVERSATION