Live data from Hacker News

Stripe’s fifth engineering hub is Remote

stripe.com

31–40 of 277 posts

Re: Stripe’s fifth engineering hub is Remote

#31

..Remote (North America Only)..

They clearly state in the article that this is because they aren't currently set up as well to accommodate remote people across disparate time zones, but are looking to resolve that.

South America, Mexico, and other North American countries exist in the same timezones as the US and Canada. Is it something to do with hiring regulations being too much of a pain to deal with in countries where Stripe doesn't feel like the best talent is?

Additionally, why not just offer remote positions that require you to work US hours? I manage just fine as someone self-employed and remote working with people in the UK. This wouldn't need to be a permanent solution, but I don't see why exclusion is necessary here.

Re: Stripe’s fifth engineering hub is Remote

#32
post #8

Earlier quoted context omitted.

If you want to test out workers outside of USA but not have to solve the timezone related issues I recommend Colombia. There is at least one interested person there.

As someone who's worked remote with "timezone issues" before they're not for the company to solve. If you live in Europe but work for a US company that requires you to work US times, it's simple, you work US times. This is how I've worked before and it's worked out perfectly. In fact, I'm a bit of a night owl so I much preferred it.

I work at a company where everyone is expected to be in the office. But we have early birds and night owls employed by the same company to work together. We don't have a formalized solution as night owls do as you described and get on up if they have work due in the morning. Or the early birds will stay up late to help the night owls finish.

But a lot of companies take on "Core hours" and essentially solve the timezone problem even with a physical office. With core hours management is deciding that they don't want to solve the "timezone issues".

I wonder how well the opposite end of the spectrum would work. Our async communication tools are pretty good these days. You could keep someone solving the problem all day long with just 3 or 4 hires but instead people choose to work on the problem in scheduled bursts of 6 hours with their entire team.

Re: Stripe’s fifth engineering hub is Remote

#33
post #3

Great to see that a well-known company such as Stripe is embracing remote work because they've seen that remote workers are effective, not just as a mechanism to leverage locales with lower wages. Hopefully other companies follow suit.

I’m not sure this says anything about the wages being equal. The remote wages are anecdotally lower. Judging by the offers I’ve seen coming out of SF compared to some of their other hubs, it’s significantly lower. Not just in salary, but in equity as well.

Re: Stripe’s fifth engineering hub is Remote

#34
post #26

Earlier quoted context omitted.

Why would you expect remote to be less efficient? Working in an open office is incredibly distracting—of course there’s productivity gains from going remote.

I am full time remote for past 6mo. Never been less productive in my career. I'm looking to switch back to onsite as soon as I can. Edit: I'm not saying remote is bad - just that in my experience I'm definitely less productive.

Are you by chance just noticing all of the empty space that was previously filled with non-productive time in an office?

I've worked remotely for about 5 years now. Without the water cooler talk, chit chat, and misc distractions, I can easily fit a 8+ hour day into less than 6 hours when I work from home.

Re: Stripe’s fifth engineering hub is Remote

#35
post #8

Earlier quoted context omitted.

If you want to test out workers outside of USA but not have to solve the timezone related issues I recommend Colombia. There is at least one interested person there.

As someone who's worked remote with "timezone issues" before they're not for the company to solve. If you live in Europe but work for a US company that requires you to work US times, it's simple, you work US times. This is how I've worked before and it's worked out perfectly. In fact, I'm a bit of a night owl so I much preferred it.

I disagree — those issues are totally for the company to solve. Or at least, the company should be prepared to meet employees halfway. If a North American company is going to insist that I work North American hours whilst living in Europe, I'm just not going to work there. And I'm sure I'm not the only one who feels that way.

I live in Europe and work for a very remote-friendly, NY-based company, and I work pretty normal European hours. I have 2-3 hours of overlap with the various members of my team, and that's all I need. (In fact, I'm more productive in the morning here because it's easier for me to focus when our group chat is mostly quiet.)

Of course, it's not as simple as saying that you can work from anywhere for anybody at any time, but I don't think it's fair to say that timezone issues are not for the company to solve.

Re: Stripe’s fifth engineering hub is Remote

#37

Im wondering what learnings has Stripe figured out that makes their remote workers as productive as their in-office employees. Do they use things like OKR, slack,etc ? What works and what doesn't - is there a cognitive disconnect between remote teams and people who work in office . Is there an expectation of minimum screen time expected from remote employees?

We use Slack, Zoom, Google Docs, Github, and a handful of other widely-adopted technologies. They're really good and we couldn't do this without them, but they're probably not the lynchpin to making this work at scale.

We're working constantly on improving the integration of peers throughout the company. Something Stripe Atlas does, for example, is schedule time for the team to low-key socialize without an explicit agenda, in part because by default some decisions get made in a hallway and some information travels at the speed of coffee, and we've learned we should go out of our way to be inclusive of employees who don't passively benefit from those factors.

I cannot conceive of a reason we'd track screen time for employees, remote or otherwise. I can model why a company which had an adversarial relationship with employees might want to do that (to discourage shirking). We do not have an adversarial relationship with our employees, and (hopefully) have more interesting utility functions than that.

I expect we'll continue publishing what we learn on this in Increment, our engineering blog, and other places. It seems unlikely to me that five years from now instituting this policy will be very contentious at well-run tech companies; that implies we, as an industry, have to get much better at this very quickly. We're always happy to share what we've learned.

Re: Stripe’s fifth engineering hub is Remote

#38
post #31

Earlier quoted context omitted.

They clearly state in the article that this is because they aren't currently set up as well to accommodate remote people across disparate time zones, but are looking to resolve that.

South America, Mexico, and other North American countries exist in the same timezones as the US and Canada. Is it something to do with hiring regulations being too much of a pain to deal with in countries where Stripe doesn't feel like the best talent is? Additionally, why not just offer remote positions that require you to work US hours? I manage just fine as someone self-employed and remote working with people in t…

Mexico is part of North America, remember NAFTA? (North American Free Trade Agreement)

It's as easy to hire Mexican remote employees as Canadians, see W8-BEN

Re: Stripe’s fifth engineering hub is Remote

#39
post #26

Im wondering what learnings has Stripe figured out that makes their remote workers as productive as their in-office employees. Do they use things like OKR, slack,etc ? What works and what doesn't - is there a cognitive disconnect between remote teams and people who work in office . Is there an expectation of minimum screen time expected from remote employees?

Why would you expect remote to be less efficient? Working in an open office is incredibly distracting—of course there’s productivity gains from going remote.

My experience is that some people genuinely are less productive without the social pressure net of their co-workers around them, or literally the boss on-hand as a sort of "productivity enforcer." It's varied wildly from job to job, office culture to culture, and at an individual level, but I take all those experiences with me and it tints my perceptions of productivity as well.

I remember when I was a recruiter it was a life of KPIs handed on down from on high. Management would pat you on the shoulder as they walked by if you were on a call, expressing approval of your activity. We'd crack jokes only somewhat ironically like "any time is a good time for a client call!" If you were still in the office at 7, you could expect a heartfelt appreciative email from management. If you hadn't been on the phone for an hour, a boss may shout across the room "bit quiet over there, someone check if komali_2's napping!"

Then on the days that all of management was at an off-site, things got a lot "looser." Less calls, less grandstanding, more hanging out in the kitchen, longer lunch etc. I don't know if productivity was actually lower ( it probably wasn't ) but it felt that way, because of the culture of our work place.

To that business, the idea of working from home would be laughable. Never mind that there were independent recruiters working out of their house and pulling in literally millions in revenue. How could you be as productive as an office of hardcore recruiters with their managers setting excellent KPIs and tracking goals and establishing milestones and shouting "a bit quiet over there!" occasionally?

Of course now that I'm an engineer I'm easily more productive on my own at home or at a cafe than I am in my office for a multitude of reasons. My purpose is to explore and explain why some people, particular management, believe remote to be less efficient.

Re: Stripe’s fifth engineering hub is Remote

#40
One thing I've found when working in a silo or remotely is the difficulty of getting accolades.

Pretty much all discretionary accolades like "team member of the month" is related to building rapport with the decision maker.

This factors into not just the employee of the month, but bonuses and layoffs.

I'm not even sure if abstracting this out into specific performance metrics is the solution, an individual will still want to give another certain individual praise at their discretion.

Just something to be conscious of.

Glad Stripe is having success in this area.

Post reply on HN