Skip to content

Instantly share code, notes, and snippets.

@ldgillen
Created March 1, 2017 22:03
Show Gist options
  • Save ldgillen/bd91194a1a7aa803f4b6f165a0ac0bd1 to your computer and use it in GitHub Desktop.
Save ldgillen/bd91194a1a7aa803f4b6f165a0ac0bd1 to your computer and use it in GitHub Desktop.
Comments on remote hires from #204

LDG: Something to keep in mind as we think about our next hires - I think we should require all new hires start working in DC, and then transition into remote work or Lisbon office, if that's what they prefer. I think this way it helps people assimilate into our culture and best practices.

Matt: I don't think requiring new hires to be in DC is necessary, and is going to be undesirable for anyone established elsewhere and looking for a remote gig. However, any remote hire of course needs additional consideration as to if it's the right fit since it's not for everyone.

Ali: I agree a little bit both with @ldgillen and @matthewhanson here. I think being in DC for the first week or so would be nice just so that we can learn about the remote worker and they can learn about us. But otherwise, having remote workers seems like it's part of our culture in some ways. So even suggesting that someone moves there seems wrong.

Matt: Starting off the job with a week trip, or even a 2 week trip is perfectly reasonable and should be expected, but I don't think we should expect someone to be able to move here for a short term stint (unless they are willing and able then that's great).

Derek: Agreeing that it'd be great to have more people co-located with us in either Lisbon or DC. That said, we shouldn't write off people who have shown that they can work reliably from somewhere else where they're rooted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment