Hacker News Reader

Comment by patio11 | Hacker News Reader

I work at Stripe, including on this post. As we mentioned, our remote hiring is in scaled production mode in the U.S. and Canada, and in early stages elsewhere. We anticipate this will change, and are working towards changing it, as quickly as various constraints allow.

View on HN

There are 212 job openings listed on Stripe's careers page as either located in the United States or remote. Of those, 17 are remote (~8%) & the rest are not. So even excluding non-US listings, it's a small percentage -- Seattle has ~30%, SF has ~50%, NYC has ~11%.

Even though a single job listing can/does represent multiple job openings, that's true for all the listings as well. So all other things being equal, I would expect Stripe to have way more remote listings if it's been as successful as this post implies. Which leads me to believe the reality is much more nuanced and that the blog post is a bit heavy with PR fluff (no shame!).

Also, big fan.

Its worth noting that this article is about the Stripe remote _engineering_ hub. Stripe intentionally scaled its engineering presence remote first. There are remote Stripes in other parts of the company but this post was about the concerted effort to hire engineers remotely. Further as patio11 mentions downthread that the math on this is hard to diagnose from the outside. I don’t have any specific information about this but I wouldn’t be surprised if the single job title “Infrastructure Engineer - Remote” will be hired into more than all engineering roles in NYC.

The numbers from the blogpost “ Over the last year, we’ve tripled the number of permanently remote engineers, up to 22% of our engineering population.“ is a fairly straightforward way to read the posting about this.

Disclaimer, I am a “Infrastructure Engineer - Remote” at Stripe.

I'm pretty confident that we made only true claims, particularly the ones with numbers. If your model doesn't agree with our SQL, I think the maximally polite observation I can make is that one of us is probably wrong.

Or both.

> As we mentioned, our remote hiring is in scaled production mode in the U.S. and Canada, and in early stages elsewhere.

What if I'm based elsewhere, but would be happy to work North American timezones?

Time zones are not the sole constraint we have, and many of those constraints are not ones that we can simply waive by mutual agreement. For example, some activities we engage in are restricted to regulated entities in some countries, and those restrictions are things we have to thoroughly understand, sometimes negotiate, and plan for prior to onboarding employees in a particular jurisdiction.

That's the easy bit, hard is pay wages in another country and ensuring your obey all local laws and regulations. You basically have to set up an entity in the countries you wish to hire from and then become familiar in the law there which is quite a hurdle.

I would suggest amending the article, as it seems to imply positions are currently available outside the US and Canada, when this is not the case. This section in particular:

>We have increased the places we can hire remotely from. Today, Stripes are based in over 50 cities worldwide. We now have the capability to hire remote employees in Australia, Brazil, Canada, France, Germany, India, Indonesia, Ireland, Japan, Mexico, Netherlands, Singapore, Sweden, UK, and the U.S.

Reply on news.ycombinator.com