A shared component system for driver email and landing pages
At Uber I worked as a Technical Marketing Engineer, sitting close to the marketing teams and focused on the driver side of the business. The problem was a familiar one: triggered emails to drivers had each been built slightly differently, so the experience drifted from one notification to the next and any design change that needed to scale became a manual, template-by-template chore. Because drivers rely on these communications to do their work, inconsistency wasn’t just cosmetic — it muddied a channel drivers depended on.
The role
Technical Marketing Engineer · Uber (~2014–2017). Built a shared component system spanning driver email and landing pages.
Componentized the driver email templates
I built a shared component library and rebuilt the triggered driver emails on top of it, so every message looked and felt like one coherent system. Design changes now flowed automatically from the library to every template, replacing the manual updates that used to bog down any product-wide change.
Extended the system to driver landing pages
Beyond email, I brought the same componentized approach to landing pages built for drivers — so the consistency and maintainability gains carried across more of the surfaces drivers actually touched.
Leaned into the marketing-engineering side
Partnering directly with marketing teams, I focused on the engineering craft behind their campaigns and triggered sends — making it faster to ship changes and easier to keep the driver experience on-brand and on-system.
Impact
A consistent, on-brand driver experience across triggered email and landing pages, with product-wide design changes no longer requiring manual, template-by-template updates — and faster turnaround on marketing-driven changes to driver-facing content.
This is a snapshot of older work (~2014–2017) — happy to go deeper on any part of it in conversation.