Business problems solved through front-end work.

Modernized enterprise Angular across the full span, incrementally — the way the framework’s own upgrade path intends. Teams kept shipping, and the next upgrade got less mysterious.

I’ve done Angular upgrades for many teams — in consulting, finance, healthcare, and energy. That repeat work made upgrades a practical part of the architecture.

Angular upgrades sound mechanical until you have lived through enough of them. Quite often, the perception is that it's just a simple software upgrade like upgrading your phone to the latest operating system. The command-line part is rarely the hard part. The hard part is discovering how much history has been preserved inside package versions, test assumptions, build tooling, third party dependencies, and components that nobody has wanted to disturb for a while.

Led the front end hands-on — a team of 7 as tech lead, and direction for dozens of developers. Code-quality expectations became normal delivery habits.

I’ve led enterprise Angular at TCS, Fidelity, World Fuel Services, AST, American Well, UST Global, and Apple. It shaped a leadership style grounded in hands-on code, mentoring, and architecture direction.

Enterprise Angular work has a particular texture. The UI is never just the UI. It is connected to service contracts, release timing, QA cycles, accessibility expectations, analytics needs, and the habits a team has built around reviewing front-end work.

Turned repeated UI decisions into reusable standards. That made Angular approachable for back-end-leaning full-stack developers.

Several roles centered on one thing: turning repeated UI choices into reusable standards. That meant style guides, component rules, Storybook surfaces, review habits, and real design-system work.

The Eastdil Secured role stands out because it made the design-system problem explicit. I architected, evangelized, built, and documented a style guide based on Material and Kendo. The goal was front-end work that felt less improvised. More than that, it helped full-stack and back-end developers who were new to Angular.

Shipped public, revenue-sensitive campaign surfaces at consumer scale. The deadlines were launch-day, every time.

I did commerce and campaign work for Guthy-Renker brands, Razorfish, Square One Solutions, and Age of Learning. It built a practical sense for public UI under deadline pressure.

Commerce work taught me a different kind of front-end pressure. The pages were public, the deadlines were tied to campaigns, and small implementation details could matter because the interface was directly connected to conversion, tracking, and launch timing.

The hands-on web foundation — CMS, full-stack, and browser-baseline work — that everything Angular later stood on.

I worked at Jobsync, Gorilla Nation/Evolve Media, Capital Group, and Fidelity National Financial. Those content-heavy jobs built the base for my later Angular work.

Before modern front-end tooling made everything feel named and packaged, a lot of UI work lived in the practical middle. That meant CMS templates, jQuery behavior, responsive CSS, and back-end integration. It also meant browser baselines and production systems that had to be handled with patience.

The fan archive that started my career — an award-winning site that drew a former Depeche Mode member into an official collaboration, later rebuilt in Angular on its own front-end architecture.

A long-running fan archive evolved from hand-built media pages into a structured Angular experience. It has resilient routing, responsive layouts, metadata, and content models that can keep growing.

DEPECHEMODE.TV is where my web career began to feel personal. The early site drew the attention of Alan Wilder, a former member of Depeche Mode. He brought me into an official online collaboration around the band’s Singles 86>98 release — a fan archive turning into something the artists themselves used. What makes it matter to me professionally is that this award-winning site has been rebuilt through nearly every era of the web — hand-authored HTML, streaming media, Flash, and, since 2014, a front-end-only responsive Angular site I’ve kept modernizing. It’s a labor of love that doubles as the place I dogfood my own architecture: content modeling, resilient routing, metadata, and accessibility. It’s the long-term care of a web project that still matters to people trying to find one specific thing in a lot of history.