About
Full-stack engineer in New York. I take ownership of systems end to end, and write up the trade-offs so the next engineer doesn't have to reverse-engineer the decision.
30–35s → 3–5s cold
Analytics API latency
Q2 2026
Tech Excellence Award
99.99%
Pipeline uptime
Case study
21s → ~10s → <2s → ~250ms
A data delivery API was running warehouse DML on the hot path — 20–30 second queries under load. A streaming write API over gRPC cut responses to about 10 seconds. Moving the read path to PostgreSQL + EF Core brought them under 2 seconds, and about 250ms at p99 on the migrated routes. Three architectural decisions, not query tuning.
I'm a full-stack engineer who has always been wired to understand how things work — take them apart, learn the mechanics, put them back together better. That instinct turned into programming in 2015 and grew into a career building tools that solve real problems at scale.
I'm strongest on the backend — schema design, migrations, gRPC, message pipelines — but I routinely own the full path when it matters: Next.js frontends, Auth0, multi-pod caching, microfrontend shells. The pattern is the same: find the bottleneck, pick the right tool, ship with tests and measurable latency.
At Visa I worked on payment and eligibility systems at production scale (20M+ monthly requests on the eligibility path) — modernizing .NET and Spring Boot services, rebuilding 200+ stored procedures into APIs (95th-percentile latency down 40%), migrating Click to Pay to Next.js and React (40% faster page loads and 30% fewer API errors for 10M+ global users per month), and building the first real-time benefit-redemption pipeline between the Visa Card Eligibility Service (VCES) and the Visa Digital Benefits Platform (VDBP) at 99.99% uptime.
After Visa I spent a self-directed stretch shipping mobile apps, a CRDT collaborative editor, and RAG prototypes — the kind of end-to-end work that keeps API design honest.
At Mobility Global I started on an internal data delivery platform — taking core API latency from ~21 seconds to ~10 with a streaming write API, then to under 2 seconds on PostgreSQL (about 250ms at p99 on the migrated routes), while modernizing the frontend and migrating dozens of routes off the warehouse. Then a financial analytics API from 30–35 seconds a query to 3–5 seconds cold and about a second warm in production. That expanded into the micro-frontend platform several teams now ship into, now live as Mobility Global Sales Solutions: Module Federation, Fastify BFFs, shared contracts, Auth0 identity and OpenFGA authorization. Three applications run on it with 10+ more in the pipeline, serving 100+ internal users, dealer groups and Dealer Relationship Managers. I co-established its architecture with our Architecture team and set up the Claude Code workflow around it. It's where most of my time goes today.
The public pages for that work: Mobility Global Sales Solutions, Retail Pricing: Benchmark (the product behind the Q3 2026 Innovation Excellence Award), and the FeeSync registration page, one of the apps hosted on the platform.
This site is the latest iteration of that habit: the fourth generation of my personal site, on Next.js 16 with an MDX essay pipeline, static generation, and the same supply-chain discipline I document in npm audit triage. How the earlier generations differed is written up in four generations of my personal site; all of them are still online as archives.
BigQuery Storage Write API over gRPC, then PostgreSQL + EF Core for OLTP — two architectural moves that took an interactive API from 21-second tails to ~250ms p99 on the migrated routes.
From last-write-wins string sync to Yjs binary updates, append-only Postgres persistence, and object-storage snapshots — how a production-style collaborative editor handles concurrency, reconnects, and durability.
Expo Router, Firebase split-brain messaging, Zod as schema source of truth, why I skipped an API gateway, and what a frozen social-mobile codebase taught me about shipping IRL-first software.
22 technical essays across enterprise platform work, mobile archives, and side projects — with decision tables and measured outcomes. Browse all writing →
October 2025 — Present/New York, NY
Mobility Global (formerly S&P Global Mobility)
February 2025 — October 2025/Remote
Self-Directed
September 2022 — February 2025/Miami, FL
Visa, Inc.
June 2022 — August 2022/Boston, MA
Wayfair, Inc.
September 2020 — July 2021/New York, NY (Remote)
Digital memorial platform (remote)
Faster queries, lower latency, leaner builds. A 21s API path that lands at ~250ms changes what a product can do — that's the work I optimize for.
When a system moves money or market data for millions of users, correctness and uptime aren't optional. I design for failure modes, not just the happy path.
Every engineering decision should move a number — p95 latency, error rate, coverage. I orient around outcomes, not activity.
Readable code and clear writing are the same discipline. The next engineer — often future me — should understand the why without an archaeology dig.
September 2017 — June 2022
Williams College
Sep 2018 · Pass
Harvard Business School Online
A 150-hour Harvard Business School program on business fundamentals: Business Analytics, Economics for Managers, and Financial Accounting, taught through HBS's case-based method.
Next
Get in touch
Happy to go into more detail on any of this. I read every message.