More replies.
Less time writing.

Payments infrastructure at Stripe

Five years building at Stripe's scale means Alex has navigated the exact architectural challenges this role requires — high-throughput transaction processing, distributed consistency, and fault-tolerant system design. This isn't transferable experience, it's directly applicable experience.

Monolith-to-microservices transition

The job description specifically calls out needing someone who has 'decomposed large systems' — Alex's work migrating Stripe's payments monolith maps directly to what this team is about to attempt. Most candidates understand the theory. Alex has the scar tissue.

Series B timing

Moving from a public company to a Series B is a deliberate career signal — engineers who make this move typically want ownership, greenfield problems, and equity upside. The role offers all three, which makes the pitch genuine rather than manufactured.

Hey Alex, Your work migrating the payments monolith to microservices at Stripe caught my attention — specifically because the team I'm working with is about to hit that same inflection point. They're a Series B fintech building a distributed ledger layer for cross-border payments. The engineering problem is genuinely interesting: high-throughput, eventually consistent, global. They need someone who's already navigated that transition at scale, not someone who's read about it. Fully remote, greenfield from here, $160K–$220K + equity. Worth 15 minutes? Jamie Reeves Tech Talent Partner