CartPanda Senior Backend Engineer

Fluveo

Abo

ut t he Ro le We're b u i lding a gl obal paymen ts plat t form — API-first, modeled af er S tripe — and hiring o ur first engineer. The fo u nder b u i lt t he en t ire prod u c t wi t h AI t l oo ing (Clau de Code, Cursor). The plat form is l ive: f ull merchan t API, dashboards, paymen t orchestrat ion, doc umen tat ion, CI/CD. Now we need a senior engineer t o own prod u t c ion rel l iabi t i y, code qual t i y, and infrastru c ture decisions as real merchan ts onboard and real money moves. This is no t a "wri t e CRUD endpoin ts" ro le. AI generat es t he majori t y of t he code. Yo ur job is t o review i t, cat t ch he edge cases t hat cause do u ble-charges or race t condi ions, ensure zero-down t ime migrat ions, and be t he person who k nows exac tly what t o do when paymen ts break at 2 AM. Yo u'll inheri t a mature codebase and a discipl ined engineering process — no t a blan k slat e — and ext end bo t h as t t he eam grows.

What Yo

u'll Do Review and harden AI-generat ed backend code dai ly — mandat ory check gat es, no empt y cat ch bl ocks, no parseFl oat on mone tary valu es (every t hing is in t eger cen ts) t ype- ** O stru wn prod u t c ion moni t oring, alert ing, and inciden c tured l ogging (zero l og), on-call t response** — Sen try, Manage database performance — qu ery opt imizat ion, migrat ion safe t y, t connec ion poo l ing on Neon serverless (d ual-driver: HTTP reads, WebSocke t transac t ions) ** O perat e and upgrade Hyperswi t ch** — o orchestrat or ru nning on Docker/Rai lway; yo and even tually own i ts Ku berne t es migrat ion ur open-so u'll manage urce paymen t t he service l ifecycle Make infrastru c ture decisions — scal ing strat egy, service bo depl oymen t pipel ine improvemen ts u ndaries, Fluveo 1 A Ensure paymen t fl ow correc t ness — idempo transi t ions, se ttlemen l t reconci iat ion, ledger in t ency, stat e machine t egri t y ** O wn secre ts and environmen Rai lway, Vercel, and AWS t managemen t** — Doppler sync across Keep engineering doc umen ru nboo ks, API con trac ts l ive in tat ion c urren t — archi t ec ture decisions, utl O ine and must stay in sync wi t t h he code

Tech S

tack | Layer | Techno l ogy | |---|---| | API Server | TypeScript, Hono.js v4.6+, Zod val idat ion, @hono/zod- openapi | | O RM / Database | Drizzle O RM, Post greSQL 16 (Neon serverless — d ual-driver: HTTP reads, WebSocke t transac t ions) | | API Gat eway | Go 1.22+, Upstash Redis rat e l imi t ing, zero l ogging | l og stru c tured | Paymen t O rchestrat ion | Hyperswi t ch (Rust, Docker) wi t h S tripe connec t or | | Workfl ow Engine | Temporal Cl o re try l ogic | u d — webhoo k del ivery, paymen t sagas, | Fron t ends | Next.js 15, Tai lwind v4, Clerk aut h, shadcn/u i | | Infrastru c ture | SST Ion, Vercel, Rai lway, ** AWS ECS Fargat e**, Gi tHu t c ions CI/CD | b | Edge / Async | Cl o u dflare Workers, Cl o u dflare R2, Cl o u dflare Q u u e es | | Secre ts | Doppler (synced t o Vercel, Rai lway, AWS Secre ts Manager) | | Moni t oring | Sen try (Node.js + Go) | | Cache | Redis (Upstash) | | Monorepo | pnpm workspaces, gi t worktrees |

Fluveo 2

Requ

ired 5+ years backend engineering TypeScript — advanced: yo u can read Hono.js ro and Zod val idat ors wi t ho ut ramp-up t ime ut es, Drizzle schemas, Post greSQL — deep: qu ery tu ning, transac t ion iso down t ime migrat ions, connec t ion poo l ing lat ion levels, zero- Prod u inciden t c ion operat ions — yo u've been on-call, triaged mult i-service ts, b u i lt moni t oring and alert ing from scrat ch Docker — comfortable managing and deb u gging con tainerized services CI/CD — Gi tHu b A when a depl oy breaks t c ions or equ ivalen t; yo u u nderstand what happens Monorepo experience — pnpm workspaces or equ t o work clean ly across package bo u ndaries ivalen t; yo u k now how Comfortable reviewing AI-generat ed code — no t l j ust "using Copi o au t di ing code t hat AI wro t e from spec t o prod u t c ion: cat t ching ype gaps, missing error pat hs, incorrec t assumpt ions abo ut ext ernal APIs t," b ut

S

trong Bon us Go — o t he bar ur API gat eway is Go; yo u don't need t o be expert b ut readable is Paymen ts / fin t ech domain — PSP in l ledger design, reconci iat ion t egrat ions, idempo t ency patt erns, Temporal or any workfl ow engine — Temporal Cl o u d is core t o o ur async fl ows Ku berne t es — Hyperswi t ch migrat ion t o ECS/K8s is on t he roadmap Cl o u dflare Workers — we're expanding edge usage Hyperswi t ch or any open-so urce paymen t orchestrat or experience

No

t Requ ired Degree or cert ificat ions Fluveo 3 FAANG pedigree Having used t his exac t stack before — a strong engineer ramps fast

What Makes This Ro

le Differen t Yo c ulture inciden u're engineer #1, no t engineer #50.* There's no exist ing engineering t o inheri t — yo u u b i ld i t. That means yo u ur j dgmen t on code qual t i y, t response, and syst em design becomes t he default. The AI workfl ow is real, no t a talk ing poin t.* Clau de Code ru ns wi t h mandat ory checkpoin ts: t ype-check gat es before every commi t, PR GRESS.md fi O les track ing every agen t's work, mult i-agen t sessions across gi t worktrees. Yo u'll be t he h uman in t hat l oop — reviewing diffs t hat span six fi les wri tt en in parallel by su bagen ts, cat t ching he edge cases t he model didn't see. The work is consequ t en ial.* Paymen idempo t ency key means a merchan t means down t ime. Yo u'll wri t t e he ru acco u n table when t hings break — because yo most of i t. ts are u nforgiving. A b u g in an ge ts charged twice. A bo t ched migrat ion nboo ks, own t he alerts, and be u're also t he one who preven t ed No process overhead.* No sprin commi tt ee. Yo u see a problem, yo equal measure. u t ceremonies, no t icke ts, no design-by- fix i t. That's l iberat ing and demanding in Equ t t i y hat means some t hing.* First engineering hire at an early-stage paymen ts company. Genero us all ocat ion, standard vest ing, priced at t he gro u nd fl oor.

What We're No

t We won't pre t t end his is easy. Yo u're joining a two-person t eam (fo u nder + yo u ) wi t h real merchan ts and real money on t he plat form. There's no senior engineer above yo u t o escalat t e o. If yo u need ext ensive men t orship, a large t eam t o distrib ut e risk across, or a mature engineering org t o learn from, t his isn't t he righ t t fi ye t. Fluveo 4 If yo u wan t maximum ownership, minimum b ureau t hat ships — t his is i t. cracy, and t o b u i ld some t hing

Plus

Equ l t i y is avai lable t o of incen t ives t o grown Projec t is backed wi t u h f nds and fo u nder expert ise A Fluveo 5