Four years in production fintech, from intern to owning whole tracks end to end. I like the unglamorous parts of money software: idempotency, reconciliation, state machines, provider abstractions, and the compliance layer that decides whether a transfer is allowed to exist at all.
Now building independently: backend systems for clients, and AI agents that do real work.
|
Money movement Cross-border corridors across MX, US, EU and CN. SPEI/CLABE rails, OTC matching engines, stablecoin on/off-ramps (Bitso, Rio, Walapay), multi-sig treasuries, and the reconciliation that keeps all of it honest. |
Identity & compliance KYC/KYB pipelines, UBO verification, identity enrichment, and transfer gating. The checks that run before a cent moves. |
Agents & automation A blog digest over 14 engineering blogs, an idea hunter across Reddit/HN/YC, an energy research agent, a content classifier. One Bun monorepo, GitHub Actions, Neon, Claude API. |
transfer: INITIATED ββΆ SCREENED ββΆ FUNDED ββΆ SETTLED ββΆ RECONCILED
idempotency lives in the database, not in the handler
providers sit behind an interface; none leak into the domain
state changes through transitions, never through updates
money if it doesn't reconcile, it didn't happen
BS in Computer Science, TecnolΓ³gico de Monterrey (2021β2025). Pivoting from backend toward AI engineering, and studying Postgres, Node internals and system design along the way.



