Staff Software Engineer (Pro Donate)
GoFundMe · San Francisco, CA
—
Jul 16, 2026
San Francisco, CA
Jul 21, 2026
What this job asks for AI summary
A senior individual-contributor engineering role focused on the checkout and donation experiences within a nonprofit fundraising platform. The position involves leading frontend architecture decisions, owning testing and observability strategies across payment-critical flows, setting team-wide engineering standards, and mentoring other engineers. It suits an experienced React/Next.js/TypeScript engineer with a background in technical leadership and a strong interest in code quality and production reliability.
Staff level · 8+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 3 times — it's one opening, so apply once.
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,300 people nationally plausibly meet what this posting asks for (software developers). range 4,200–21,500
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
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 (9)
No office location is specified in the posting; the role appears to be remote-eligible based on the hybrid work benefit mention and absence of any location requirement.
The JD requires '8+ years' of overall experience and '2+ years at Staff or Lead scope' — the 8-year figure is captured as the overall years minimum; the 2-year Staff/Lead scope requirement is a role-level qualifier noted here.
Frontend testing is listed as a hard requirement but names no specific framework (e.g. Jest, Cypress, Playwright); it is captured as a general skill rather than a named tool.
Frontend observability similarly names no specific tool (e.g. Datadog, New Relic); captured as a general skill.
GraphQL and REST appear only under the 'Preferred' section as backend/API familiarity; GraphQL is listed as primary with REST as an alternative since they are presented as interchangeable options in that context.
AI development tooling (agentic workflows, AI-assisted review/test generation) appears under 'Preferred' and is marked accordingly.
Containerization and cloud platforms appear under 'Preferred' as infrastructure/delivery tooling with no specific products named.
'Secure-by-default practices in payment-adjacent flows' is a required competency but names no specific technology or tool, so it is omitted from the skills list per extraction rules.
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.