Software Engineer
marcus.chen@email.com · (415) 882-5541 · San Francisco, CA · github.com/marcuschen · linkedin.com/in/marcuschen
March 8, 2026
Stripe Engineering Team · San Francisco, CA
Dear Hiring Manager,
Most engineers treat payment infrastructure as plumbing — something to route around, abstract away, and forget. I've spent four years doing the opposite: going deeper into the stack, obsessing over the edge cases, and building the systems that hold when everything else fails. That's why Stripe is the only place I want to do this next chapter of work.
At Crestline Technologies, I owned the rebuild of a core API gateway processing 120M requests per day. The old system was bleeding latency at p99 — 1.8 seconds on a path that had no business taking that long. I rearchitected the routing layer, eliminated three redundant serialization hops, and deployed a new caching strategy across our Kubernetes clusters. P99 dropped to 380ms. Infrastructure costs fell by $210K annually. The team shipped faster because the foundation finally held its weight.
What draws me to Stripe specifically is the scale at which correctness matters. A rounding error at Stripe isn't a display bug — it's real money, real trust, real consequences. I've read the engineering blog closely, from the work on idempotency keys to the approach on resumable uploads, and I recognize the thinking of engineers who care about the same problems I lose sleep over. That culture of rigor is exactly the environment where I do my best work.
I'd love to talk about the Software Engineer role and where the team is pushing hardest right now. I'm ready to go deep on whatever the hardest problem on your roadmap is.
Best regards,
Marcus Chen