3 ms·
[Stripe cofounder] Thanks! We're always paranoid that we're too slow, for whatever it's worth. We're still iterating on the supporting models and frameworks.
by pc 7y ago
[Stripe cofounder]
Thanks! We're always paranoid that we're too slow, for whatever it's worth.
We're still iterating on the supporting models and frameworks. We think a lot about pace layering -- how do we have teams that think on multi-year horizons (infrastructure, security, etc.) alongside teams that are rapidly iterating at much earlier stages of development. I think a lot goes wrong when organizations insist on too much consistency in their operating approach.
We've now identified a few semi-formal mechanisms that have helped substantially. (For example: larger companies tend to want to aggressively standardize roles. This makes sense when operating at scale but less so in the early days. So, we've made it easy to hire for ill-defined roles in nascent product areas -- we figure we can codify those roles later as needed and that doing so sooner is a premature optimization.) We'd certainly consider writing a blog post once we feel that they might be generalizable.
(If anyone reading this is interested in helping us figure things out, please do apply. We're particularly interested in hiring engineers who are interested in these questions.)
- swampthinker 7y agoHey Patrick, could you elaborate more on hiring in nascent product areas? What does making it easier actually entail compared to hiring in more established areas of Stripe?
- brettcvz 7y agoMakes sense! For the eventual blog post, I'd be particularly interested in hearing how you decide which small bets to make (e.g. did Corporate Cards start from an employee saying "I want to go work on this"? An internal new-products strategy team? An executive?), and what structures you have in place for deciding when to invest more heavily in a bet. We are trying to figure out how to do this at Clever, and I know others like Segment (https://segment.com/blog/finding-product-market-fit-again/ https://segment.com/blog/finding-product-market-fit-again/) are thinking about this as well, so hopefully we can start putting together some advice on how to create an "engine" for layering new products onto an established platform.
- bogdanu 7y agoDo you know what's annoying to me? Seeing how awesome products you have but can't use them because I live in Romania. Come on... :D I know there's Atlas, but for a bootstrapper I can't afford it (especially when I don't know anything about legal stuff).
- no_wizard 7y agoAny tips on landing a callback from your hiring team then? :) I have years of experience with “big data” but I’ve always thought payments would be a good, similar vertical that would be far more interesting
- tempsy 7y agoPro-tip: trying to get through the "front door" is usually a waste of time. Try to find a recruiter on LinkedIn (sometimes their profile is actually linked to a job listing) and contact them directly through a message.
- mjhea0 7y agoI really wish you'd focus time and energy on documentation and examples for the current products. I wrote this blog post after a very frustrating experience with Stripe Connect: https://testdriven.io/blog/setting-up-stripe-connect-with-django/ https://testdriven.io/blog/setting-up-stripe-connect-with-dj...
- mjhea0 7y agoMoving from the legacy checkout to elements was complex since you do not mention in the docs that validation checks no longer get checked on the client and instead have to happen on the sever.
- joncrane 7y ago>If anyone reading this is interested in helping us figure things out, please do apply. Do you have a link? Thanks.
- iscrewyou 7y agohttps://stripe.com/jobs/search https://stripe.com/jobs/search