Staff Software Engineer, Payments Intelligence

Stripe · Seattle, New York, San Francisco · 8511 PayIntel - Eng · listed August 4, 2026

The shape of it

Seniority
Staff
Experience asked
5–10 years
Where
Not stated
Requirements listed
5
Length
496 words

In the posting’s own words

Payment Intelligence is comprised of multiple product teams building AI-first solutions to some of our customers’ biggest challenges, including fraud/abuse ( Radar ), payment optimizations ( AuthBoost ), Disputes, Authentication, and merchant analytics. We’re a mix of machine engineering engineers and full-stack software engineers impacting ~every Stripe transaction, creating revenue opportunities for Stripe and our customers, and helping protect the broader ecosystem.

What it asks for · 5

  • 10+ years of software engineering experience, including 5+ years of experience in a strategic technical leadership role
  • Experience leading engineering team(s) working on Distributed systems, API design, and user facing products
  • Proven track record of delivering pragmatic solutions that accelerate business growth
  • Ability to drive projects at a high-level while also being hands on and contributing directly to technical solutions as necessary
  • Effective communication skills and a proven ability to work cross-team, cross-org, and cross-functionally.

Also a plus

  • Experience with payments systems and/or fraud detection
  • Familiarity with ML systems in production: model serving, training pipelines, observability, and evaluation
  • Prior experience with 0-1 product builds: you've started with a blank page and ended with a production system, and you have clear opinions about what makes that process go well or poorly
  • Experience across a range of software languages and frameworks; our stack includes Java, Ruby, Python, TypeScript, Kafka, Flyte, Airflow, and Mongo.
  • Experience navigating ambiguity in a fast-moving organization - you can make confident technical decisions with incomplete information and update gracefully when new constraints emerge

What the job covers

  • Define technical strategy for multiple experiences across the Payment Intelligence portfolio, with a focus on quality and performance
  • Champion a quality-first engineering culture - establish standards, tooling, and processes that make it easy to ship high-quality code at scale
  • Partner with some of Stripe’s largest merchants to co-build the future of payment-centric intelligence
  • Partner cross-functionally with product, design, and ML colleagues to ship the very best software possible
  • Work across the stack - contributing to infrastructure and foundational systems, but also FE, API, and ML-adjacent work.

Tools and skills named

Cloud & infra
  • Distributed systems2×
  • Kafka
  • Observability
Languages
  • Java
  • Python
  • Ruby
  • TypeScript
Models & research
  • Machine learning4×
Data
  • Airflow

Words the posting leans on

  • experience9×
  • product6×
  • systems6×
  • engineering4×
  • software4×
  • technical4×
  • engineers3×
  • merchants3×
  • payment intelligence3×
  • solutions3×
  • stack3×
  • api2×
  • build2×
  • building2×
  • contributing2×
  • cross-functionally2×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Stripe

every open role at Stripe

How this page was made

An automated read of a public job posting, fetched August 24, 2026 and last changed by Stripe on August 18, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.