I build interfaces
people use.people use.

I designed and ran A/B tests across landing pages, product listing pages, and product detail pages for Pizza Hut, Premier Inn, Mulberry, and Omaze — driving gains in conversion rate, revenue per visitor, and click-through rate while reducing bounce rate.

The tests that won did not get rolled back. Those variants became the live interface, and the client kept and maintained them, so the work outlasted the experiment that justified it.

Two things made the program better rather than just bigger. I built an in-house statistical analysis tool that replaced a manual Google Sheets workflow, automating p-value and statistical-significance calculations so the team could evaluate results faster and more reliably. And I introduced a React-based testing workflow that brought component-based development into experimentation — complex test variations became faster to build and easier to maintain.

Winning variants became the brands’ permanent UI.

Rental staff used to describe vehicle damage in free text, which is slow to write and hard to dispute later. I owned the replacement: an on-screen car diagram where staff tap the exact spot, attach photos, and hand back a structured record.

The hard part was where it runs. Inspections happen in parking lots and underground garages with weak or no signal, so I built the tool offline-first — photos and in-progress reports persist on-device and survive page reloads and connections dropped mid-inspection.

Photo-backed evidence for every rental, captured in minutes.

Topflight's website was mine from the first commit. I was the only frontend developer on it, building and shipping the entire site in HTML, CSS, and TypeScript.

Owning the whole front end is also what the experimentation program ran on top of — every A/B test I designed and shipped was a change to code I had written myself, which is why complex variations were possible at all.

One developer, the entire front end, in production.

A new product line alongside the core rental marketplace: a monthly car lease. I was the only frontend developer on it and built every screen it needed.

That meant both sides of the marketplace — listing and pricing flows for the rental companies offering subscriptions, and creation, editing, and review of customer subscriptions for internal staff.

Every screen shipped, from company pricing flows to staff review.

Getting access to expressPay’s payment APIs meant going through a manual onboarding process and contacting support. I built the developer dashboard that replaced it with self-serve access.

I also developed the documentation site for the payment APIs, giving developers a single reference for integrating payments, and built a retail platform enabling retailers to sell expressPay’s services.

Replaced a manual onboarding process; less need to contact support.

Listing a vehicle meant typing out its description and full specification list by hand — the kind of repetitive entry that keeps inventory from getting listed at all.

I integrated AI-assisted listing creation: wiring up the LLM API and designing the prompt flow so the output is structured, accurate to the vehicle, and useful as a starting point rather than something staff have to rewrite.

Manual data entry replaced with generated, reviewable content.

The company serves an international customer base, but the product shipped in one language. I rolled internationalization across both surfaces — the customer-facing website and the internal admin dashboard.

Six languages went live: English, German, French, Italian, Dutch, and Chinese.

English, German, French, Italian, Dutch, and Chinese.