Senior Backend Engineer, Payments
Polymarket · New York, NY
—
Jul 23, 2026
New York, NY
Jul 25, 2026
What this job asks for AI summary
A senior backend engineering role focused on building and scaling the payments infrastructure behind deposits, withdrawals, and money movement on a prediction market platform. Day-to-day work involves migrating legacy systems to distributed services in Go/gRPC, integrating with payment processors and banking rails, and delivering regulated financial features such as KYC, fraud checks, and reconciliation. The role also carries mentorship and on-call ownership responsibilities for production money-movement systems.
Senior level · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 14,800 people nationally plausibly meet what this posting asks for (software developers). range 8,900–22,200
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
No work location or metro is specified in the posting; the role appears to be remote-friendly based on the absence of any office requirement, but this is not explicitly stated.
No total years of experience is explicitly stated; the posting uses 'senior-level' as a qualifier without attaching a year count.
Compensation is described only as 'competitive salary & equity' with no figures given.
DynamoDB and MySQL are listed together as the data store stack (both used, not interchangeable alternatives), but the posting presents them as a paired option ('DynamoDB/MySQL'); they are captured as separate skills with each listed as an alternative of the other to reflect the 'or' ambiguity in the slash notation.
Stripe is named as an example payment processor ('processors like Stripe'); it is listed as a required skill because it appears under the primary requirements block with firm language, though 'like' implies other processors would also be acceptable.
AWS and GCP appear only under a '(Plus)' section and are marked as preferred accordingly.
Docker/containers also appear only in the '(Plus)' section and are marked as preferred.
Experience in crypto, prediction markets, or regulated fintech environments is listed as a '(Plus)' and is a domain/context qualifier rather than a named technology, so it is omitted from the skills list per extraction rules.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.