Staff Software Engineer - Card Payments at PPRO
Sao Paulo
—
Jun 29, 2026
Sao Paulo
Jul 21, 2026
What this job asks for AI summary
A senior individual-contributor engineering role on a card payments team, focused on building and owning backend systems for Latin American and European markets — including authentication flows, reconciliation, and billing infrastructure. The position involves setting company-wide technical standards, leading architectural decisions across teams, and mentoring other engineers, all while remaining hands-on with code. It suits an experienced backend engineer comfortable with distributed, cloud-native systems at scale.
Staff level · São Paulo, Brazil · 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
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $135,980 (middle half $105,210–$171,980).
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)
This role is based in Brazil (BRL-denominated benefits such as meal vouchers at BRL 54/day and a BRL 3,000 L&D budget confirm a Brazilian location, most likely São Paulo given PPRO's office presence there). US benchmarks do not apply.
The posting explicitly titles this a 'Staff Software Engineer', and the described scope — setting company-wide technical standards, leading cross-team/cross-domain initiatives, and shaping architectural strategy — genuinely supports the Staff band.
Java is listed in the requirements section as the primary language with the parenthetical '(or other general-purpose programming languages)', indicating the hard gate is on backend engineering depth rather than Java specifically; alternatives reflect other general-purpose languages commonly accepted in this context.
AWS is listed in requirements as 'preferably AWS (or comparable experience with Azure/GCP)', making cloud-native experience a hard gate with AWS as the preferred option.
Kotlin, Spring Boot/Micronaut, Kubernetes, Docker, and Kinesis appear under the 'Some of the technologies you'll get to work with' stack narrative section — not in the requirements block — and are therefore preferred rather than hard gates.
No total years of experience are stated in the posting.
The role is hybrid (3 days/week on-site), not fully remote.
This role's work location reads as outside the US — the candidate pool, comp, and contention benchmarks here are US-only (BLS employment, Adzuna/USAJOBS demand, and certified H-1B wages), so treat them as a rough US reference, not a local market.
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.