Software Engineer - Backend
Cardless · San Francisco, CA
$165,000–$260,000from the description
Jul 7, 2026
San Francisco, CA
Jul 21, 2026
What this job asks for AI summary
A backend engineering role focused on designing and scaling the server-side systems behind a co-branded credit card platform, covering areas such as applications, accounts, transactions, fraud, and rewards. The work spans the full project lifecycle — from architecture and implementation to deployment and maintenance — with cross-functional collaboration across product, design, and compliance. Best suited to engineers with deep backend experience in distributed systems, APIs, and databases.
Senior level · 5+ years · San Francisco-Oakland-Berkeley, CA · 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 11,000 people in the San Francisco-Oakland-Berkeley, CA area plausibly meet what this posting asks for (software developers). range 8,300–14,300
Applicant volume Heavy — This req sits in a large pool with little in its requirements to thin it, and auto-apply tools fire at everything in the occupation. Applying early and leading with the rare skills below is what gets read.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $190,744 (middle half $167,095–$224,501). This posting is about at that midpoint.
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 (5)
The title 'Backend Engineer' carries no explicit seniority level, so advertised seniority is Unspecified; however, the requirements gate on 5+ years of industry experience and deep domain expertise, supporting a Senior classification.
The backend language requirement names Java and Python as examples ('e.g. Java, Python'), indicating these are interchangeable options for the same requirement — captured as one skill with alternatives.
Financial systems / reconciliation workflows / data integrity is listed under 'Nice to have' but names no specific technology or tool, so it was omitted from the skills list per extraction rules.
ML pipelines and feature stores appear under 'Nice to have'; 'feature stores' is a concept rather than a named tool, so only 'ML pipelines' is captured as a preferred skill.
This role is 5 days a week in-office in San Francisco — not remote.
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.