Build and debug full-stack payments infrastructure across Stripe's stack

This Stripe Software Engineer role (New York, Global Operations) designs and maintains APIs and services in Ruby, Scala, and Go, builds full-stack web applications with React/TypeScript on the frontend, engineers payments integrations with financial partners, and works with MongoDB, SQL, and Presto for data analysis — all requiring roughly 2 years of hands-on experience in each named area plus 1 year specifically in payment-processing reliability.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Backend API/service design in Ruby, Scala, or Go
Full-stack web app development with React/TypeScript
Performance and latency tuning of backend systems
Payments integration with external financial partner systems
Data work with MongoDB and SQL/Presto
Building and testing reliable payment-processing systems

Common question themes

Walk me through a backend service you built and later tuned for performance/latency

Describe a full-stack feature you shipped, from API design to the React frontend

Tell me about debugging a production issue that spanned multiple layers of the stack

How would you design a system to reliably store or process sensitive payment data

Describe an API you designed — what tradeoffs made it intuitive for its users

Tell me about a MongoDB schema or SQL/Presto query problem you solved for analysis

How candidates describe it

Real Software Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Stripe Software Engineer interviews

All Stripe interviews