WORK · SELECTED IMPACT

Production systems, platform leverage, and technical direction.

A focused hiring profile should answer what changed, why it mattered, and what kind of Staff/Principal scope it demonstrates. These case studies are based on the current resume.

CarGurus · Principal Software Engineer

Production ML at CarGurus

Problem: A backend engineering team needed to turn machine-learning work into a production application, not a data-science experiment.

Decision: Led the first non-data-science engineering team at CarGurus to ship a production ML application with a full MLOps pipeline.

Outcome: The application was highlighted to investors during an earnings call and gave backend teams a repeatable path for delivering ML-backed product systems.

Staff signal: cross-functional architecture, production ownership, rollout risk, and technical direction across team boundaries.

First Republic Bank · Senior Software Engineer, Principal scope

Delivery platform at First Republic

Problem: Release work was slow enough to create operational drag across many engineering teams.

Decision: Established a scalable continuous delivery pipeline and trained 50+ engineers, architects, and directors on the practices behind it.

Outcome: Deployments moved from days to minutes and the pipeline was adopted across hundreds of engineers.

Staff signal: platform leverage, developer experience, organizational adoption, and practical engineering standards.

Cimpress / Vistaprint · Lead Software Engineer

Commerce-platform rebuild at Cimpress

Problem: Tax lookup data was queried multiple times per page load and growing multiplicatively with each acquisition, threatening EU sales.

Decision: Built cross-team consensus for a replacement and designed cached, horizontally scalable microservices around a C# business-rules engine.

Outcome: The replacement sustained thousands of queries per second, A/B testing found legacy-system bugs, and ownership passed to a junior team that ran it without incident.

Staff signal: identifying a hidden scaling cliff, winning buy-in, and reducing long-term senior-engineering burden.

Apocoplay · Founder and CTO

Apocoplay infrastructure economics

Problem: Large-scale multiplayer games needed better server economics and faster modernization paths.

Decision: Led a 20-person team and designed server-side routing and rule-processing infrastructure for real-time multiplayer games.

Outcome: The engine reduced server and development costs by 90% per game and saved hundreds of thousands of dollars per title annually.

Staff signal: architecture under business constraints, technical leadership, and founder-level ownership of product economics.

Current public work sample

Black Skies is the current public systems case study. It shows the same habits these case studies describe: explicit tradeoffs, bounded consistency, falsifiable claims, and measurement discipline.