Integration Reliability Engineer, Payments

Stripe · Canada · 8548 Payins - Eng · listed July 22, 2026

The shape of it

Seniority
Mid level
Experience asked
2–6 years
Where
Not stated
Requirements listed
7
Length
729 words

In the posting’s own words

Our team partners closely with various finance and infrastructure engineering teams to ensure timely delivery of accurate data between financial partners, internal stakeholders, and Stripe leaders. We report and trace all of Stripe’s money movement transactions, including payments in more than 30 currencies and dozens of countries. You’ll own building and scaling Stripe’s manual and programmatic financial reporting and reconciliation processes for intra-company and outgoing money movement transactions.

What it asks for · 7

  • 2-6 years of experience in a technical role (ex: Technical Operations, Software Engineer, etc.)
  • Have experience managing communications and workflows with technical and non-technical teams across internal and external stakeholders
  • Ability to write high quality code. We work mostly in Ruby and Java. However, languages can be learned: we care much more about your general coding skill than knowledge of a particular language or framework
  • Comfort using SQL to navigate Stripe's data and diagnose the scope and urgency of issues
  • Be able to build operational processing and tooling from scratch to prevent repeatable issues
  • Comfort with developer tools (e.g. git), and an ability to make well-scoped code changes in Stripe's codebase
  • Great technical problem-solving skills, with an ability to develop a working understanding of a technical system using a variety of methods. These include (but aren't limited to): reading/writing code, reading documentation or partner specifications, running debugging programs, reading logs, asking well-formed questions to domain experts, or digging into the raw data through various interfaces

Also a plus

  • Knowledge of and experience with payment technologies and ecosystems
  • Experience managing communications and workflows with external financial partners and vendors

What the job covers

  • Become a domain expert in an area of Stripe’s payments stack
  • Find automated solutions and implement tool updates to drive operational efficiencies
  • Engage with Stripe's financial partners to drive alignment on product usage, troubleshoot and solve technical problems or breakages
  • Organize and direct complex technical changes and projects between Stripe and our partners
  • Identify and automate inefficient or unnecessary manual processes through code changes, partner agreements, or making and coordinating more complex code changes across Stripe
  • Design future anomaly detection systems and tools to ensure that data flowing through our partner and internal systems is reliable and correct
  • Collaborate across the company, including engineering, accounting, financial partnerships and product, to trace and account for billions of dollars moving through the Stripe platform
  • Handle inquiries from internal Stripes and external partners' technical teams, often requiring detailed investigation and sometimes code changes

Tools and skills named

Languages
  • Java2×
  • Ruby2×
  • SQL
Ways of working
  • Git
  • Technical writing
Go to market
  • Partnerships

Words the posting leans on

  • partners12×
  • technical10×
  • financial8×
  • payments8×
  • experience5×
  • code changes4×
  • data4×
  • financial partners4×
  • internal4×
  • language4×
  • money4×
  • platform4×
  • product4×
  • requirements4×
  • build3×
  • ensure3×

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 25, 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.