I build money infrastructure — lending, payments, products real companies acquire. Not because it’s a job. Because good enough is not enough.
I don't just write code. I develop a deep obsession with the domain until I understand it better than almost anyone in the room.
I started writing code at 17 — not because someone handed me a curriculum, but because broken systems bothered me more than broken grades. At MetaKeep, within my first year on the job, I shipped an acquisition-grade payment integration that became the technical backbone of due diligence for a NASDAQ-listed deal. At Revalon, I built the core lending engine from scratch — pricing risk, executing loans, running it live with zero bad debt
Before this, I worked alongside engineers who built WhatsApp Pay, Meta’s Diem, and Twitter’s social graph. That’s the bar I hold myself to: not whether something works, but whether it’s right
I don't ship features — I internalize the problem space. Lending platforms, payment systems, account security — I go deep until I understand the threat model, the incentive structure, the edge cases that kill companies. Then I build.
From zero to a payment onboarding flow used in a NASDAQ acquisition. From zero to a lending platform with disciplined automated execution and integrated risk controls. Most engineers prototype. I ship.
I see the whole board — core platform, application layer, DevOps, security architecture. When I build lending infrastructure I think about recovery workflows, custody boundaries, reconciliation, and auditable decision trails simultaneously.
Remote · Platform Engineering · Financial Infrastructure
Rezolve AI · NASDAQ: RZLV · Remote
Next-Generation Distributed Ledger Infrastructure
“Being in a room with people who've shipped systems at civilisational scale doesn't just teach you — it permanently recalibrates what you think is possible.”
Meet Jain · On working with world-class engineersWorked alongside builders of