3 ms·
To me, there is one extremely insightful comment on the original post. The commenter asked what the timezone of the remote positions were and if that had an eff
by wallflower 9y ago
To me, there is one extremely insightful comment on the original post. The commenter asked what the timezone of the remote positions were and if that had an effect on the applications and hiring team.
As I'm sure anyone who has had to get up at weird, uncomfortable hours in the past to work with remote teams in India can attest, there is definitely a big difference between someone working remote in your country (3-4 hours difference, if not Russia) and someone working remote on the other side of the world (8-12 hours difference).
Greece is GMT+2 or GMT+3, depending on the time of the year. SF is GMT-8 or GMT-7, depending.
I know in a perfect world that remote workers would take jobs from a queue and work asynchronously and then submit their work to another queue. But the world doesn't work that way. People are still people, teams are still teams, we are not (all) coding robots yet.
- kostarelo 9y agoAbsolutely. FYI, I was targeting specifically timezones that I could be comfortable working with. There are a few outliers in the spreadsheet but were mostly close to my timezone so we would work the same hours. Unfortunately, I forgot to reply to the commenter.
- wallflower 9y agoThanks for the reply with the information about timezones. Best of luck with finding your remote job! Perhaps one will come out of the attention your blog post has joined. Since people at your current employer may well know about this, perhaps put a small text 'ad' at the top of your blog advertising that you are always interested in the appropriate remote opportunities in Node.js?