Remote Work Across Time Zones: How I Stay Effective

I work from Bandung, Indonesia (GMT+7). My current employer is in Sweden. Past clients were in Singapore, the US, and across Southeast Asia. Making this work is not magic. It is a set of deliberate habits.

The Reality of GMT+7

From Indonesia, the overlap windows are real but specific:

• Europe: 2–4 hours of real-time overlap in the afternoon (my time) when Stockholm is in their morning
• US East Coast: Almost no natural overlap. Their business day ends around midnight my time
• APAC: Strong overlap; Singapore, Tokyo, and Sydney are within a few hours

So async communication is not a preference for me. It is a requirement. The teams that work well with me have made async their default. The ones that struggle expect me to be online whenever they are.

The Async-First Stack

Long-form writing over quick calls. When I need to explain a technical decision, an architecture tradeoff, or a bug investigation, I write it out. Not a paragraph, but a proper explanation with context, reasoning, and a recommendation. It takes longer to write and saves three rounds of back-and-forth meetings.

Video for two specific things only. Kicking off a project (establish trust and shared understanding) and resolving ambiguity that has already gone through one written round without resolution. Not for status updates, not for “quick questions” that could be a message.

Status updates are my responsibility, not my manager’s. I post end-of-day summaries in shared channels without being asked. What I worked on, what is blocked, what I will pick up tomorrow. This builds trust with remote managers faster than any number of meetings.

Time-boxed response expectations, clearly stated. When I send a message that needs a response, I say when I need it by. “No rush” means they can reply tomorrow. “Before EOD your time” is a specific ask. Remove ambiguity.

Protecting the Overlap Window

When I do have real-time overlap with my team, I protect it. Meetings go here. Code reviews that need discussion go here. Everything else is async.

For CheckProof (Sweden), my overlap is roughly 2–5 PM my time (8–11 AM Stockholm). That window is good for meetings. The rest of my day is deep work: no interruptions expected, none given.

Documentation as a Force Multiplier

Good documentation scales your availability beyond your timezone. When I document decisions, I reduce the number of questions that require my synchronous presence.

My minimum documentation bar for any nontrivial decision:

• What we decided
• What we considered and rejected, with reasons
• What to do if we need to revisit this

This costs 20 minutes to write. It saves hours of future meetings across timezones.

Calendar Hygiene

I block my deep work hours on the shared calendar. Not as “busy”, but as named blocks like “Deep work, no meetings.” That tells people when I am available without needing a conversation about it.

I also block my local evening (which is European morning) for potential urgent overlaps. I am not always available then, but the space exists if needed.

The Equipment Reality

Remote work across long distances requires reliable infrastructure. Non-negotiables:

• Primary internet with a backup (mobile hotspot at minimum)
• UPS for power, since Indonesia has occasional outages
• A quiet space for video calls when needed
• Headset with decent microphone quality

Blaming your environment for missed communications is not professional. Own your setup.

What I Tell Clients Upfront

Before starting any engagement, I establish:

1. My timezone and typical working hours
2. My expected response time for async messages (within 24 hours for non-urgent, same working day for urgent)
3. How to reach me if something is genuinely urgent (direct message vs. channel post)
4. My overlap windows for real-time collaboration

Setting these expectations early removes friction for everyone. Clients who need someone available in US time zones during their business hours are better served by someone in the Americas. I am upfront about this.

The Upside Nobody Talks About

Working across time zones has a real productivity benefit: nobody interrupts your deep work. When Stockholm wakes up, I have already had 6 hours of uninterrupted focus time. The code that gets written between 8 AM and 2 PM my time, before any overlap begins, is some of my best.

The myth of remote work is that timezone distance is only a cost. In practice, it is also a forced focus mechanism.