Sr. Software Engineer, Backend
Prosper · San Francisco, CA
$173,000–$205,000
Jun 29, 2026
San Francisco, CA
Jul 21, 2026
What this job asks for AI summary
A senior backend engineering role focused on the end-to-end loan application journey, from initial rate check through funding. The work centers on building and maintaining Java and Kotlin microservices on Spring Boot, migrating away from legacy systems toward event-driven architectures on GCP, and integrating with REST and GraphQL APIs. Suits an experienced backend engineer comfortable with distributed systems, cloud infrastructure, and working within a regulated financial environment.
Senior level · 6+ years · Remote · Bachelor's required · Full-time
Pay in the description: $173,000–$205,000
“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 9,500 people nationally plausibly meet what this posting asks for (software developers). range 4,000–14,200
Applicant volume Light — Few people clear these requirements, so an application that does clear them gets looked at. Worth applying to even if you miss a nice-to-have.
Rare in this occupation — lead with these, and say what you built with them.
What the occupation pays Median $135,980 (middle half $105,210–$171,980). 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 (6)
The degree requirement is a gate but with two paths: BS in EE/CS with 8+ years, or MS in EE/CS with 6+ years. The minimum total experience is set to 6 (the lower bound under the MS path); the BS path requires 8+ years. The degree requirement is set to Bachelors as the minimum formal degree that satisfies the gate.
GCP Pub/Sub is listed under the required 'Skills that will help you thrive' section as an event-driven pattern example ('such as GCP Pub/Sub'). The 'such as' qualifier means the specific tool is interchangeable, but the event-driven capability itself is a hard gate; no widely-accepted single named alternative was provided, so GCP Pub/Sub is retained as the primary named tool.
Firestore, Spanner, Cloud Functions, and CI/CD appear under the same 'Skills' section but are framed with 'Familiarity with' — a softer qualifier that signals preferred rather than hard-gated proficiency.
AI coding assistants (Cursor, Copilot) are listed under 'Skills that will help you thrive' but framed as 'Active use of' and 'commitment to exploring' — aspirational language rather than a hard gate; treated as preferred.
The role is open to fully remote candidates as well as those in San Francisco or Phoenix offices. The San Francisco CBSA is used as the primary metro given Prosper's headquarters location.
This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.
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.