Nielsen

I spent five and a half years at Nielsen working on the Browser SDK — the JavaScript measurement library that powers audience crediting for some of the biggest media companies in the world. When your code runs on millions of devices and clients' revenue depends on the numbers it reports, "it works on my machine" is not a phrase you get to use.

Senior Software Engineer (2022–2024)

Modernizing a legacy SDK

The Browser SDK predated most of modern JavaScript. I led the refactor to ES6+ — modules, classes, modern async — without disrupting crediting for existing client integrations. That last clause is what made it hard: hundreds of clients had integrated against years of accumulated behavior, and a "cleaner" implementation that changed the numbers was a failed implementation. The payoff was real: better maintainability, better runtime performance across browsers, and a codebase new engineers could actually navigate.

Beyond the browser

Measurement was moving to the living room, so the SDK had to follow. I delivered viewability metrics and expanded SDK support to Smart TV and DOM-less environments including Tizen, WebOS, and React Native — environments where you can't assume a DOM, a window, or any of the browser APIs a "Browser SDK" was built on.

Owning the infrastructure

I managed our AWS infrastructure and GitLab CI/CD integration, provisioning resources with Terraform and streamlining the release pipeline — taking releases from a manual, error-prone process to something the team could run routinely.

Software Engineer (2019–2022)

I cut my teeth resolving critical SDK defects affecting crediting accuracy: reproducing client-reported measurement discrepancies in production browser environments, tracing them through the SDK, and validating fixes against expected analytics output. It was detective work — a client says their numbers look wrong, and you have to figure out whether it's their integration, our SDK, the browser, or the data pipeline downstream.

What I took away

Nielsen taught me to respect production. Backwards compatibility, cross-browser quirks, devices you've never heard of, and data that has to be right — it's the kind of engineering discipline you only build by carrying a pager for code that can't afford to be wrong.