● /HIRE · TWO TRACKS · ONE OPERATOR
I run the payments stack you don't want to outsource.
You are hiring a senior or staff payments engineer, or a head of platform. I have shipped what you are about to build. Read the receipts, then book a call.
receipts
six of the things I will tell you about on a call/01
Built and shipped an in-house payment facilitator on direct JPMC rails. Under twelve months. PCI DSS certified 2022. JPMC called it one of the fastest payfac implementations they had seen.
/02
$1B+/yr payments platform I lead today at Squire.
/03
Brought the platform into PCI DSS scope. Network tokens plus a PAN vault behind a strict API. Zero card data in app databases.
/04
Shipped Watchdog, the real-time stability and incident-detection platform. Catches misbehaving systems before customers see them; saved revenue and CS cost during incidents.
/05
Three production ledgers across two decades. Double-entry, audited, partition-tolerant. The boring stack, on purpose.
/06
Led engineering at BVNK from employee #3 to acquisition by Mastercard, March 2026.
"One of the fastest payfac implementations we have seen."
JPMC · on the Squire payfac launch · 2022
what I look for in a role
if any of these are no, neither of us should waste the call// yes
- Real payments scope. Money moves, ledgers, networks, fraud. Not "payments adjacent".
- Senior IC or executive title with engineering authority. I write code and I lead.
- Remote-first with at most one travel week per month. Lisbon based.
- Comp band published before the first call. I will tell you mine if you tell me yours.
- Public-safe technical stack. I read the source before signing.
// no
- "Founding engineer" at pre-revenue with no payments problem yet.
- Lead a team of 80 and never touch code. That is not the job I took.
- Hybrid mandates requiring relocation. Not now.
- Crypto-only mandates without a real settlement story.
You read the receipts. Now let's talk specifics.