I'm a software engineer at Coinbase, transforming the future of finance through stablecoins.
Right now I'm building the platform that enables enterprises and businesses to issue their own custom stablecoins. I've shipped rewards products used by hundreds of thousands of people, and I care as much about how a system is designed as what it ships — architecting things that hold up as products and teams scale. Lately I've been deep in AI-assisted development.
Download resumeLead frontend engineer on the Stablecoin-as-a-Service platform that lets enterprise partners issue and manage their own stablecoins, live on the Coinbase Developer Platform. I built the onboarding flows, supply management, rewards, and an analytics dashboard on live on-chain data.
Frontend lead for Coinbase's first multi-asset rewards product (hold USDC, earn Bitcoin). It grew to ~$400M enrolled across 100K+ users, with $4M+ in BTC rewards paid out and counting. I also crossed into backend here, automating the BTC payout funding that used to be a manual biweekly treasury process.
Reward rates were drifting apart across surfaces, so I built a central resolver that every web surface across coinbase.com now uses, plus automated UI tests that keep catching anomalies long after launch.
Across all of it I own projects end to end — design docs through rollout and monitoring — co-led launch alignment across 4 partner teams, and wrote an onboarding guide the whole team now uses.
Fortinet's security appliances can capture live network traffic, but inspecting it used to mean exporting files to an external analyzer. I built a fully-featured capture UI directly into the product, closing that gap and improving user efficiency ~35%.
Engineered 6 reusable components and optimized rendering logic — load times dropped ~30% and the team's development time ~20%.
Along the way I resolved 40+ customer-reported issues, which lifted user satisfaction ~15% and taught me a lot about debugging other people's networks from a stack trace and a hunch.
Worked inside Carbon, IBM's open-source design system — the kind of environment where accessibility, theming, and API consistency are requirements, not nice-to-haves. I designed 6 reusable components that improved consistency across the application and cut component load speed ~20%.
Building at IBM's scale early in my career shaped how I think about components: design them for the next ten teams that will use them, not just the screen in front of you.
My first taste of end-to-end ownership: I solely built an internal web app that streamlined my team's workflow — Flask backend, SQL data layer, Jenkins for CI — lifting operational efficiency ~35% and team productivity ~50%.
Being the only engineer on it meant every decision was mine to make and mine to live with, which is where I first learned to write design docs before code.
My first industry role, at an early-stage AI fintech tackling employee financial stress. I delivered 20+ user stories across the React + TypeScript front end and its GraphQL API, at the pace only a startup demands.
Startup breadth over big-company depth: I touched everything from UI polish to API shape, and got my first look at shipping AI-driven product features — a thread that's run through my work ever since.
Never got the chance to publish it — but the build was the payoff: hands-on experience hooking real-world APIs into a mobile app and working out token-optimization strategies to keep LLM calls fast and cheap.
I use AI heavily in my workflow — agentic coding tools, LLM integrations, automating the boring parts — and I think it's changed how frontend work gets done. Off the clock: lifting and golf.