00. Work

Work

Twelve years at one company can look, from the outside, like nothing much happened. No job changes, no row of logos. From the inside, the company, the product, and my role kept changing shape. They changed slower than a new employer every couple of years would have made it look.

What follows is that stretch at FashionUnited, an independent platform for the international fashion industry, in over 30 countries and 9 languages. I tell it as a few eras, with what I shipped and what changed because of it. The dates are approximate. In practice each era blurred into the next.

Not everything fits an era. Along the way I also moved the whole company onto a single work-tracking system, turned tribal knowledge into a markdown handbook, and kept a fleet of devices secure and low-touch. That is the quiet work that makes the other work possible.

For a closer look at a specific project, the problem, the stack, and what came out of it, see the case studies.

Career chapter 1 of 4

2013-2014

IT Project Manager

What I shipped

  • Drove the responsive redesign of fashionunited.com. New desktop and mobile templates became the foundation of the modern news platform.
  • Learned the product and the industry from the inside, just as fashion's readership shifted to phones.
What changed

The core product was mobile-ready at the moment that started to matter.

Career chapter 2 of 4

2014-2019

IT Manager

What I shipped

  • Built the multi-market platform architecture. 30+ locale-specific domains are served from one codebase, with a custom routing layer and a shared component library.
  • Introduced the Elixir/Phoenix GraphQL API. Domain-separated Postgres databases sit behind one API that powers every market and integration.
  • Moved the infrastructure to Google Cloud. Multi-cluster Kubernetes across the EU and the US, all of it managed as code with Terraform.
What changed

Launching a new market became configuration instead of a rebuild. The platform stopped blocking international expansion, and there were no snowflake servers left to be afraid of.

Career chapter 3 of 4

2019-2024

IT Manager

What I shipped

  • Migrated the frontend to a Next.js progressive web app, shared across all markets.
  • Made releases boring. Continuous deployment on merge for the API and the frontend, with monitoring that catches issues before readers report them.
  • Built the data side. A BigQuery warehouse, privacy-friendly analytics without cookie-banner debt, and self-serve dashboards so leadership can answer its own questions.
What changed

Releases became routine. A small team ships daily without ceremony, and decisions started running on data instead of gut feel.

Career chapter 4 of 4

2024-present

AI-powered Engineering Manager

What I shipped

  • Led the migration off Next.js to React Router and Vite across all 30+ markets, market by market, with rollback plans. Builds got much faster, recurring infrastructure cost went down, and the stack is fully open source.
  • Wrote and carried out the editorial AI roadmap. Press-release processing, translation, scheduling, and cross-market syndication run as code-based, version-controlled pipelines with human approval gates.
  • Shipped an email agent for the news inbox. It classifies and routes 50 to 100 messages a day at roughly 90% accuracy, so the inbox no longer needs a human first pass.
  • Rolled AI tooling out to the whole company, engineers and non-engineers, with a maturity framework covering every role.
What changed

I now lead AI-powered engineering. Editorial time went back to original journalism, and the work is aimed at a more efficient and transparent fashion industry.

The eras above are the day job. The side projects are where I build for myself, end to end, on my own schedule.

See the side projects