Software engineer
I design and build reliable payment, ledger, and payout systems—where idempotency, observability, and correctness matter.
Selected work
A cross-company view of billing, ledgers, payouts, and event-driven platforms—patterns you can discuss in depth in any senior system design interview.
Recurring subscriptions, monthly invoicing, and payment collection with retries—without double-charging customers.
Highlight: Async invoice generation for spiky load, idempotency keys against retry storms, batching and indexing for DB pressure.
Append-only, double-entry ledger for charges, refunds, and payouts—with reconciliation to external processors.
Highlight: Duplicate events from at-least-once delivery, reconciliation jobs, and correctness via immutable entries.
Host payouts across processors and banks with lifecycle tracking, retries, and bank reconciliation.
Highlight: Idempotent payouts, unreliable bank APIs, late webhooks, and stuck-state tooling operators could trust.
Fare calculation and charging after trip completion—from trip-end events to receipts.
Highlight: Idempotent billing per trip, pricing caches, promotions/taxes, and commute-hour traffic.
Kafka-based bus so billing, notifications, and analytics could consume trip events without synchronous coupling.
Highlight: Ordering, duplicates, consumer lag, DLQs, reprocessing, and schema evolution at scale.
Experience
Payments, ledgers, payouts, and event-driven platforms—shipping under real reliability and scale constraints.
Airbnb
Apr 2023 – Present
Lyft
Jun 2018 – Apr 2023
Skills
Backend-first, with production experience across payments, ledgers, and high-throughput event pipelines.
About
I gravitate toward high-stakes domains: payments, ledgers, and global money movement. The interesting problems are almost always the same—idempotency, retries, reconciliation, and operational clarity when things go wrong.
I partner closely with product and finance to keep designs explainable, auditable, and safe to evolve. I care about observable systems, tight feedback loops in production, and interfaces that make edge cases first-class.
B.S. in Computer Science
University of Virginia
Based in Northern Virginia. Open to strategic IC roles and staff+ platform work.
Contact
Whether you're hiring, collaborating on a platform, or comparing notes on billing architecture—reach out.