Time-zone overlap strategies for Sri Lankan remote workers
The overlap problem no one warns you about
You land the remote job. The salary is in USD or GBP, the commute is your corridor, and Zoom is your office. Then reality arrives: your London manager starts at 9 a.m. BST (2:30 p.m. Sri Lanka Standard Time), your US client's standup is at 10 a.m. ET (8:30 p.m. SLST), and your Sydney team wraps up just as you're having lunch.
Sri Lanka sits at UTC+5:30 — the same zone as India but without a massive tech hub to normalise it globally. That means you're often working with foreign colleagues whose clocks barely align with yours. Getting this wrong means late nights, half-days of silence, and the creeping feeling that you're always one step behind.
Know your overlap window — exactly
Before you negotiate anything, map the actual overlap for your specific role:
- UK (GMT/BST): 3.5–4.5 hours. Their 9 a.m.–1 p.m. is your 2:30–6:30 p.m. SLST in winter. This is the most workable pairing for Sri Lankans.
- USA East Coast (ET): 1–2 hours in the late afternoon. Their 9–10 a.m. ET is 7:30–8:30 p.m. SLST. Sustainable only if you front-load your day and accept one evening call.
- USA West Coast (PT): Near-zero synchronous overlap. Their morning starts at 10:30 p.m. SLST. This arrangement either goes fully async or burns you out within three months.
- Australia (AEST): 1.5–2.5 hours, but in your early morning. Their 8–9 a.m. AEST is your 2:30–3:30 a.m. SLST in winter. Friendly only for early risers.
- Singapore/Malaysia (SGT): 2 hours of afternoon overlap. The most natural regional pairing.
Write this down before your first week begins. Share it with your manager and get explicit about when you are reachable and when you are not.
Front-loading: the strategy that saves you
For any US or Australian pairing, front-loading your day is your most powerful tool. Complete your deep, independent work — code, writing, analysis, design — in the morning before the rest of your team wakes up. When they come online, you are ready to review, answer questions, and push decisions through quickly before their day fills up.
A structure that works for many engineers at companies like Virtusa and IFS working with US clients:
- 7:00–12:00 SLST — deep async work, no interruptions
- 12:00–14:00 SLST — lunch, triage overnight messages
- 14:00–17:00 SLST — live calls, code reviews, quick syncs
- 17:00 SLST — close out, write handover, log off
The discipline pays off fast. You are never blocked waiting for an answer because you have already queued up questions to resolve in the live window.
The async handover is your superpower
The best remote workers aren't the ones who respond fastest; they're the ones who write handovers that mean nobody needs to ask.
At the end of every working day, drop a short handover note in your task tracker — Jira, Linear, Notion, whatever the team uses. Three sentences: what you completed, what is blocked, and what you need from them tomorrow. Written at 5 p.m. Colombo time, it lands in your London manager's inbox overnight and they read it at 8 a.m. BST before you even wake up.
This single habit builds more cross-timezone trust than any number of late-night calls.
Negotiate the call window early, not later
When you join a remote team, the first conversation most people avoid is the one about call times. Have it in week one. A simple framing:
"My productive overlap with your timezone is 2:30–6:30 p.m. my time. I'm happy to take one standing call per week outside that window if it's truly critical, but I'd like to protect my mornings for deep work. Does that work for the team?"
Most reasonable managers will agree. The ones who don't are giving you important information about the culture early — which is far better than discovering it at month six.
Tools that reduce the friction
- World Time Buddy — keep four clocks pinned: Colombo, your team's main hub, and the US coasts if relevant to your role.
- Loom — record short video walkthroughs instead of scheduling calls. A three-minute Loom at 5 p.m. your time is often more useful than a calendar invite 12 hours later.
- Slack's scheduled send — write your message now, deliver it when their working day begins.
- Google Calendar's "working hours" feature — set it honestly. When colleagues see your availability accurately, they stop scheduling 7 a.m. calls.
The boundary conversation you will eventually need
Six months in, something will creep. A manager who "just needs five minutes" at 10 p.m. your time. A team chat that runs hot at 11 p.m. SLST. A client who treats your async availability as synchronous.
When this happens, name it once, calmly and directly: "I've noticed we've had several calls after 8 p.m. my time lately. That's not sustainable for me. Can we look at shifting them into our regular overlap window?"
You are not asking for a favour. You are protecting the working arrangement that makes your output possible. Sri Lankan remote workers who set this boundary consistently earn more respect from experienced remote managers — not less.
The overlap window is fixed; the strategy around it is yours to build. Build it deliberately in week one, protect it in month six, and the time-zone gap becomes a structural advantage rather than a daily grind.