About

I'm a senior full-stack engineer based in Pittsburgh. I've spent the last several years as technical lead for Penn State's primary web platform — a multi-tenant Next.js architecture serving tens of millions of visits a year — where I've worked across the full stack: design systems, CMS architecture, backend APIs, platform infrastructure, and the internal tooling that holds it all together.

I didn't start in software. I studied mechanical engineering, and I think that background changed how I approach problems in ways that are hard to fully articulate. Engineering as a discipline is about finding determinism in complex systems — using known laws and repeatable patterns to make behavior predictable. I brought that instinct into software, and it's shaped how I think about component architecture, token systems, data pipelines, and platform design. The problems are different but the underlying question is the same: how do you build something that behaves the way you expect it to, consistently, at scale, under conditions you didn't fully anticipate?

That question is what I find most interesting about this work. Not any particular technology, but the systems thinking underneath it — how the layers relate to each other, where the contracts are, what breaks when they're violated.

Outside of work I live with my wife and our cat, and I'm slowly renovating a 1958 house in Pittsburgh, mostly by watching YouTube until something makes sense. I do my own woodworking, take it seriously as a pizza critic, and write when I have something worth saying.

Technical lead across platform, design system, CMS architecture, analytics, and backend infrastructure.

psu.edu — psu.edu/news — med.psu.edu — ctsi.psu.edu

Open source color system tool for design and engineering workflows.

webshades.dev

Designed and optimized mud terrain tires for global market release.

Collaborated on storage performance modeling under simulation.

Public-facing web applications, Mintopoly, Small Batch Standard.