Backend Engineer

Maxana

20h•Remote

About The Position

Our client processes serious subscription volume, and every renewal, plan change, and upgrade has to resolve into the right charge, the right credit, and the right event — every time — or a customer's order doesn't ship. You'll work in the backend of that system: subscription and renewal logic, credit ledgers, payment events, and webhook reliability. The core stack is TypeScript (Google Cloud Functions) alongside Go services — you'll live mostly in TypeScript, and we'll teach you the Go you need. If you've built billing, checkout, or transaction systems in Node/TypeScript and sweat correctness, this role was written for you.

Requirements

3+ years of backend TypeScript/Node in production — services, APIs, and async workflows, not just scripts.
Payments or billing experience strongly preferred — subscriptions, webhooks, PSP integrations (Stripe, PayPal, Adyen, or similar), or other financial-correctness domains (ledgers, lending, e-commerce checkout).
Postgres fluency — schema design and queries you'd defend in review.
Willingness to learn Go — some of the platform lives in Go services; you don't need it on day one, but you need to want it.
Testing-minded by instinct — you write the test alongside the code.
AI-native workflow — you use AI-assisted engineering tools as part of your craft. Expected, not optional.
Strong written and spoken English and availability on US business hours

Nice To Haves

Comfort touching the React surfaces your APIs feed is a plus; deep frontend work isn't the job.

Responsibilities

Build the money logic — subscription lifecycle, renewals, credits, and plan-change machinery that decides what a customer owes and what happens next.
Guard the signal — every transaction emits a payment event that gates fulfillment; you'll treat event correctness and webhook reliability as the core of the job.
Integrate the stack — work with payment processors and orchestration APIs, handling auth/capture, refunds, retries, and edge cases cleanly.
Test like it's load-bearing — automated coverage written alongside the code; partial credits and multi-cycle renewals have too many edge cases for manual QA.
Close the loop when needed — comfort touching the React surfaces your APIs feed is a plus; deep frontend work isn't the job.