Hacker News new | past | comments | ask | show | jobs | submit login

How does a payment service wind up with over a 1000 engineers?

I understand that "engineers" may not mean "developers", it could DevOps, site reliability and all the bits and pieces that make up a large service provider, but over a 1000?

Can someone please enlighten me?




It's a fair question, I think you need ~10 or so to do the work and 990 to bikeshed the horrors that come about when you have what should be a few 3mb HTTPS APIs at $50-100pcm split between 1000 resume-hungry engineers and a taste for cloud complexity.


probably has something to do with the products that go beyond accepting credit cards listed on https://docs.stripe.com/products, though I suspect operating just the credit card accepting part is harder than you imagine.


Surely in 2024 we can't be classifying Stripe as just "a payment service"


What else have they done that's worth giving a shit about?




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: