Remote Work Timezones

This cluster centers on the challenges of time zone differences in remote and distributed teams, including difficulties with scheduling meetings, synchronous communication, and productivity across large gaps like 12+ hours.

📉 Falling 0.3x Career & Jobs
2,525
Comments
20
Years Active
5
Top Authors
#5562
Topic ID

Activity Over Time

2007
2
2008
12
2009
9
2010
28
2011
47
2012
37
2013
80
2014
90
2015
86
2016
124
2017
112
2018
123
2019
151
2020
381
2021
315
2022
341
2023
261
2024
158
2025
160
2026
8

Keywords

NY US OK EOD IST SF IMO GMT HK PST timezone timezones team hours time zones remote teams time zone coast company

Sample Comments

loeg Mar 19, 2017 View on HN

Timezones still matter. It is a big pain to work with teams in a timezone 12 hours away.

narfz Nov 5, 2013 View on HN

my guess it's about timezones and visa. having 3 hours between a coworker and you is not that of a big deal but having 9hours time difference can be quite cumbersome.

Balero Aug 25, 2022 View on HN

As someone in Western Europe working for a US company, the Timezone thing is the biggest issue for me. My company is actually really good with it, but I still often finish work at 7-8pm local time, sometimes with little notice. Everything else can be worked around, or smoothed out, but this is the biggest intractable pain.

bshimmin Apr 28, 2017 View on HN

The biggest timezone gap we have is 3.5 hours, and they find it supremely convenient because they do other work in their morning. My company is based in the UK and we can only really work with people who can work in a moderately convenient timezone, at least on this sort of basis. If I hired a developer in San Francisco, I'd work with them in a different way, obviously.Nobody is being abused, don't worry!

bluefirebrand Mar 13, 2022 View on HN

This seems like a timezone problem at that point. Even remote teams can't function too well together if some of them are sleeping while others are working.

TrickyRick Jul 4, 2022 View on HN

You've never worked in an org with more than one time zone, have you?

Ididntdothis May 31, 2020 View on HN

I am sure there are legal reasons but if I had to set up a remote company I would probably try to restrict the timezones. My current company has dev teams in South America and India. They are all good people but dealing with India [13 hours) is a big pain because somebody has to make calls during his personal time instead of work time. It’s a real burden. And in my view you absolutely have to make direct calls from time to time. You can’t resolve all issues with asynchronous communication.

mikec3k Apr 22, 2013 View on HN

This might be a good alternative for someplace like my company where team members are in different time zones. When I'm getting to work around 9 in SF, it's already evening for the team members in Bulgaria.

datavirtue Jan 5, 2025 View on HN

False. I need you on my timezone or really close to it. I have been dealing with software development teams that are 12 hours off and they have settled into a pattern of ill-communication because it is simply too difficult to sync up properly. They dig in on analysis for stories on their time and have to ask questions of us. The following day they get an answer and have to reply again for more clarification. All this after having groomed with the business and having standups together early morni

JMTQp8lwXL May 23, 2020 View on HN

Businesses hire you with the understanding you'll be working in a specific timezone-- being remote is irrelevant. If you go half way across the world and your team is 12 hours ahead of you, standups (and other synchronous tasks) become impossible. If you need something from that teammate, you send a message, and wait 24 hours for a response. It obliterates collaboration and slows the business down.