Skip to content

100 Job Strategies · 7 of 100

Timezone Arbitrage

Your distance is only a problem until you describe it as coverage.

2 viewsLow effortPays off in 3-6 weeksRemote candidatesInternational applicantsSupport and operationsEngineers
Share

In short

Applying to companies six to ten hours offset from you looks like a disadvantage and is usually treated as one. Reframed deliberately — their overnight coverage, their morning handoff, an extra working day in the week — the same distance becomes a service the local candidate cannot offer. The tactic is not hiding the gap; it is naming the gap before they do and attaching a benefit to it.

The situation

A hiring manager in San Francisco opens two applications for the same remote role.

One is from Oakland. One is from Bangalore, twelve and a half hours ahead.

The manager's instinct on the second is immediate and unexamined: that's going to be painful for meetings. It goes in the maybe pile and quietly dies there.

Nothing about that candidate's ability entered the decision. A single fact about geography did — and it was never discussed, only assumed.

Why this works

Distance is not actually a cost to a company. Unmanaged distance is. The manager is not rejecting your timezone; they are rejecting the mental picture of a person who is asleep whenever anyone needs them.

That picture is yours to replace, and almost no candidate bothers. Most either avoid mentioning location or apologise for it, which confirms the concern rather than addressing it.

The reframe works because offset time has genuine operational value that companies routinely pay for. Support coverage outside local business hours is a real budget line. So is having someone pick up an incident at 3am local, or hand off work at the end of one day that lands finished at the start of the next. Teams that get this right describe it as "following the sun" and treat it as an advantage.

There is also a straightforward commercial angle when your cost of living is lower. This is a delicate thing to lead with, and you should not undersell yourself — but for many companies, a capable person in a different market at a sustainable rate is an attractive proposition, and the offset is part of why it works rather than a flaw to be discounted for.

The candidate who says "I overlap with your morning for four hours, I cover your night, and your Monday deliverable is ready before your Monday starts" has converted a liability into a line item.

How to run it

  1. 1

    Calculate your genuine overlap honestly

    Work out how many hours of your normal working day intersect their normal working day. Three to five hours is workable and worth stating plainly. Zero overlap is a much harder sell — be realistic about which you have.

  2. 2

    Name the timezone in the first two lines

    Do not bury it and do not hope they miss it. Raising it first means you frame it; leaving it to them means their assumption frames it.

  3. 3

    Convert the offset into a named service

    Overnight incident cover. End-of-day handoff. A finished deliverable waiting at the start of their morning. Support hours their local team cannot staff. Pick the one that matches their actual business.

  4. 4

    Commit to specific overlap hours

    "Flexible" reads as vague. "I work 2pm to 10pm my time, which is 9am to 5pm yours, permanently" reads as a person who has already solved the problem.

  5. 5

    Target companies with a real need for cover

    Anything with uptime obligations, customer support, live operations or global customers has genuine overnight demand. A local-market business with no out-of-hours need has nothing to buy.

  6. 6

    Pre-empt the async question

    Say how you work when nobody is online: written updates, documented decisions, clear handoffs. The unspoken fear is not distance, it is having to chase you.

What to say

Copy, then make it yours
Hi Chen, I'm applying for the Platform Engineer role. I'm based in Lisbon, which is five hours ahead of your team — I want to put that up front rather than have it come up later. In practice that means I overlap with your entire morning, and I'd work a shifted day (1pm–9pm my time) so the overlap is consistent rather than occasional. It also means your infrastructure has someone awake and on call during the hours your current team is asleep, which I understand is a gap when something breaks at 4am your time. I work in a written-first way by default — decisions documented, handoffs explicit — so the non-overlap hours produce progress rather than questions waiting for you. Happy to talk through how I'd structure the week. — Ana

When it does not work

  • Pretending an impossible overlap is fine. Twelve hours of offset with a team that runs synchronous stand-ups is a genuine mismatch. Overpromising here produces a bad first month, not a good hire.
  • Offering coverage nobody needs. Overnight availability is worthless to a company whose customers are all local and whose systems are not customer-facing. Match the offer to their actual operations.
  • Volunteering to be permanently nocturnal. Committing to hours you cannot sustain is a route to burning out in four months. Offer a shifted day you can actually keep.
  • Leading with being cheaper. Cost can be part of the appeal but should never be your opening argument — it anchors the conversation on price and invites them to discount you further.
  • Ignoring the legal and payroll question. Many companies cannot employ across borders without an entity or an employer-of-record arrangement. Ask early whether they hire internationally, contractor or otherwise.
The takeaway

Nobody rejects a timezone. They reject the picture of someone unreachable — so replace the picture before they finish drawing it.

Questions

How much overlap do I need for this to be credible?

Three to five hours of genuine overlap with the team's working day is comfortably workable and worth stating plainly. Two hours is possible for roles that are genuinely asynchronous but requires you to be explicit about how decisions get made without you. Zero overlap is a hard sell for anything collaborative, and pretending otherwise produces a difficult first month rather than a successful hire. Be honest about which situation you are actually in, because the mismatch surfaces immediately once you start.

Should I mention my location in the application or wait until later?

Mention it in the first few lines. The instinct to bury it is understandable but counterproductive: the manager will find out regardless, and discovering it themselves lets their unexamined assumption do the framing. Raising it first means you control the interpretation, and a candidate who has clearly already thought through the logistics reads as someone who solves problems rather than someone who creates them.

Which companies actually value offset coverage?

Any business with uptime obligations, live customer support, global customers or continuous operations has real demand for hours its local team cannot staff. Infrastructure, SaaS platforms, e-commerce, logistics, trading operations and anything with an on-call rotation are strong targets. A company whose customers are entirely local and whose systems are internal has no overnight need, so the coverage framing has nothing to attach to — target differently rather than forcing the argument.

Can a company legally hire me if I am in another country?

It depends on their setup and it is worth asking early. Some companies have local entities, many use employer-of-record services that handle cross-border employment, and many others engage international staff as contractors. A significant number simply cannot hire outside specific countries for tax or compliance reasons, and no amount of positioning changes that. Asking directly whether they hire internationally, and in what form, saves weeks of effort on processes that could never have concluded.

Find verified jobs from 100,000+ companies
Share

More from 100 Job Strategies

See all 25 in this series