Live data from Hacker News

We Don’t Simply Get Remote Jobs, We Join Remote Teams

remotebase.io

61–70 of 184 posts

Re: We Don’t Simply Get Remote Jobs, We Join Remote Teams

#61

> In remote team, we get to experience the culture at its most naked form. There is no catered lunch or a hip office with table tennis table. Everything artificial is stripped away. I totally disagree with this. The most naked form of communication is (and IMHO always will be) face to face. I can't tell how many countless times many emails were exchanged before simply speaking face to face solved the problem. Working…

Seriously, videoconfering (hangouts, webex, zoom.us, appear.in, etc...) solves this. As a matter of fact I can get a face to face meeting faster with remote worker than on-site workers.

Totally disagreed. In person is still 100x better than VTC. It's certainly a matter of opinion but you can't categorically say it's been solved

Re: We Don’t Simply Get Remote Jobs, We Join Remote Teams

#62
I've thought a lot about this. I am posting this in an attempt to give an example of what's worked for 1 company, not as a "guide" or "best practices". I post this in an attempt to give people ideas on what may work for them.

I operate an engineering team as a seed stage startup across 2 coasts of the US, multiple parts of APAC, and europe.

We are around 13 full time with a few part timers. We started as 2 people. Our first hire was co located with us. Our next one was remote.

From there we've made our hires only through referrals or our open source channel.

We did YC W16 this year as ~6 people and most of us remote. We've more than doubled the team after having raised nearly 3 million.

A few notes on what's worked for us:

Remote first office, no one (even if there is an office in your area) is required to come in (at all). We use https://gitter.im/ to interact with our open source community, partner companies, and team members.

Half of our hiring happens on gitter as well.

Some of us choose to for a separation of work and home.

We don't have job postings either. We do this on purpose. We tell engineers the same thing: Show up in our open source channel. This offends some people, but has worked for us. I won't claim this scales long term, but there have been fairly large companies (~800+) that have scaled this way just fine.

We've found productivity to be quite high overall. A lot less noise and very efficient communication.

Part of it is self management. The hires we make tend to have that part down pretty well. I've learned to spot bottlenecks. Part of that is just by keeping an eye on a lot of channels. Proactive reaching out if there are problems helps a lot. Periodic check ins are a must.

We do a weekly google hangout across 5 time zones that amounts to being a standup.

For scoping engineering work, we tend to have longer projects people are working on, usually a minimum of a week. This leads to less context switching.

Happy to answer questions or expand on anything that sounds interesting.

Re: We Don’t Simply Get Remote Jobs, We Join Remote Teams

#63

I've thought a lot about this. I am posting this in an attempt to give an example of what's worked for 1 company, not as a "guide" or "best practices". I post this in an attempt to give people ideas on what may work for them. I operate an engineering team as a seed stage startup across 2 coasts of the US, multiple parts of APAC, and europe. We are around 13 full time with a few part timers. We started as 2 people. Ou…

> Half of our hiring happens on gitter as well.

Can you please elaborate on that?

Re: We Don’t Simply Get Remote Jobs, We Join Remote Teams

#64

I've thought a lot about this. I am posting this in an attempt to give an example of what's worked for 1 company, not as a "guide" or "best practices". I post this in an attempt to give people ideas on what may work for them. I operate an engineering team as a seed stage startup across 2 coasts of the US, multiple parts of APAC, and europe. We are around 13 full time with a few part timers. We started as 2 people. Ou…

> Half of our hiring happens on gitter as well. Can you please elaborate on that?

It happens impromptu. I see a pull request or an interesting project someone built with us. If they stick around and seem interested in the project, I reach out via direct message and see what their goals are. I half heartedly ask them if they'd like to do this full time. If they seem interested, we setup a minor call and we talk about current projects they're working on, and what we're working on at the company.

We compare notes and see if interests line up. From there it's negotiations.

I've already seen their code and interacted with them for a few weeks by this point, so the interviews are painless and obvious.

One thing I make sure to do is be very clear/direct that we're a business. Here's how we make money, here's who our customers tend to be.

Re: We Don’t Simply Get Remote Jobs, We Join Remote Teams

#65

It is somehow ironic that not so long ago we could send ships on a 4 month trip around the word, could manage the construction of amazing buildings or sent armies to fight wars on the end of the word without being able to communicate with the people doing their job/duty. Nowdays we can barely let change the font size of a button on a webpage without having a stand up meeting or a conference call.

Not really. A lot of people died doing things that way. A lot.

Wow, Ethan! Great moves, keep it up, proud of you!

Re: We Don’t Simply Get Remote Jobs, We Join Remote Teams

#66

Earlier quoted context omitted.

> Half of our hiring happens on gitter as well. Can you please elaborate on that?

It happens impromptu. I see a pull request or an interesting project someone built with us. If they stick around and seem interested in the project, I reach out via direct message and see what their goals are. I half heartedly ask them if they'd like to do this full time. If they seem interested, we setup a minor call and we talk about current projects they're working on, and what we're working on at the company. We…

How does your interview process look like for such candidate?

Re: We Don’t Simply Get Remote Jobs, We Join Remote Teams

#67

Earlier quoted context omitted.

It happens impromptu. I see a pull request or an interesting project someone built with us. If they stick around and seem interested in the project, I reach out via direct message and see what their goals are. I half heartedly ask them if they'd like to do this full time. If they seem interested, we setup a minor call and we talk about current projects they're working on, and what we're working on at the company. We…

How does your interview process look like for such candidate?

Usually it's a just a quick phone conversation to talk about interest. The technical interview actually happens the second you enter my open source channel and contribute code or show off something cool you built.

This demonstrates a few things to me:

1. You know our codebase

2. You can build things we need

3. I've already collaborated with you

4. You're proactive and interested in solving problems we would have for you.

5. You're able to collaborate with others remotely.

Re: We Don’t Simply Get Remote Jobs, We Join Remote Teams

#68
post #25

> In remote team, we get to experience the culture at its most naked form. There is no catered lunch or a hip office with table tennis table. Everything artificial is stripped away. I totally disagree with this. The most naked form of communication is (and IMHO always will be) face to face. I can't tell how many countless times many emails were exchanged before simply speaking face to face solved the problem. Working…

> I can't tell how many countless times many emails were exchanged before simply speaking face to face solved the problem. I can't tell you how many times being able to look something up to respond in a more concrete way has solved countless meetings.

> I can't tell you how many times being able to look something up to respond in a more concrete way has solved countless meetings. reply

But when the questions and comments are not well expressed keeping the loop in text (email or Slack) makes the things worse. Obviously if you can just fire a voice conference everything can be sorted out but in my, just personal, experience remote workers are working more asynchronously and you don't expect to talk immediately without scheduling it earlier, much earlier than on-site where it is spontaneous.

Re: We Don’t Simply Get Remote Jobs, We Join Remote Teams

#69
When practically doing it, remote work has its pluses and its cons. At the same time, for the organization, it still multiplies the pool of candidates by at least 50. So, you could certainly get better talent. I live across the globe in a country that is much cheaper than back home while my effective tax rate is zero. I work from coffee shops and from my flat. I don't see why I would ever go back to sitting in an office ...

Re: We Don’t Simply Get Remote Jobs, We Join Remote Teams

#70

I've thought a lot about this. I am posting this in an attempt to give an example of what's worked for 1 company, not as a "guide" or "best practices". I post this in an attempt to give people ideas on what may work for them. I operate an engineering team as a seed stage startup across 2 coasts of the US, multiple parts of APAC, and europe. We are around 13 full time with a few part timers. We started as 2 people. Ou…

>>> We do a weekly google hangout across 5 time zones that amounts to being a standup.

>>> For scoping engineering work, we tend to have longer projects people are working on, usually a minimum of a week. This leads to less context switching.

This sounds like a pretty nice granularity -- glad to hear that it seems to be working out.

Most of the trouble I have with standups is the "daily" part...

Are there any downsides you've found to this kind of rhythm?

Post reply on HN