Hiring across time zones without regretting it

Hiring internationally is usually framed as a cost decision. That framing is why it so often goes wrong: you optimise for rate, end up with a twelve-hour gap on a role that needed four hours of overlap, and conclude that remote hiring does not work.

The decision that matters is not where someone lives. It is how much of the work requires both of you awake at once.

Work out the overlap the job actually needs

Be honest about this before anything else, because every other decision follows from it.

Needs several hours of overlap. Live customer support on your business hours. Anything where someone is blocked waiting on you several times a day. Roles that are mostly meetings. Junior roles where someone is still learning and needs quick answers.

Needs a couple of hours. Most ongoing operational work. One daily touchpoint, questions answered within a few hours, the rest done independently.

Needs almost none. Well-specified project work with clear acceptance criteria. Editing, design production, bookkeeping, research, content. Work that arrives as a brief and comes back as a finished thing.

Most people overestimate. It is worth asking: *when was the last time I genuinely needed an immediate answer from this role?* If the honest answer is rarely, you have a much larger hiring pool than you thought.

But do not talk yourself into zero when it is four. A new hire in their first month needs far more access than the same person in month six, and a role that works asynchronously once established can fail badly during onboarding.

Say it in the posting, precisely

"Remote" means at least four different things, and the gap wastes an enormous amount of people's time — most of it theirs.

Write the rule as a sentence anybody can check themselves against:

Remote. Work from anywhere, but we need at least four hours overlapping 9am–5pm GMT.

Or, when it genuinely does not matter:

Remote, any time zone. We work asynchronously; there are no standing meetings.

Or, when there is a restriction, say it rather than hoping:

Remote within the EU or UK. We cannot currently employ outside those, for payroll reasons.

That last one feels unwelcoming to write. It is far kinder than the alternative, which is someone in Lagos spending an hour on an application, two hours on a task, and finding out at offer stage.

Decide the employment question before you post

This is the part that surprises people in month two, and it determines who you can actually hire.

Broadly there are three routes:

Contractor. Simplest to start. They invoice you, they handle their own tax. Works well for project work and part-time arrangements. The risk is misclassification — if you control their hours, their tools and their methods, many countries will treat them as an employee regardless of the contract, and the penalties land on you.

Employer of record. A third party employs the person in their country and bills you. Costs a monthly fee per person. Removes essentially all of the complexity and is the normal answer for a full-time hire in a country where you have no entity.

Your own entity. Only sensible when you are hiring several people in one country.

You do not need to resolve this perfectly before posting. You do need to know which one you are offering, because "we'll figure it out" turns into a withdrawn offer, and that is a genuinely bad thing to do to someone who has resigned.

Pay: pick a policy and say it out loud

There are two defensible positions and one indefensible one.

Pay for the role. Same band wherever someone lives. Simple, easy to explain, and you compete for the best people globally. More expensive.

Pay for the market. Adjust by local cost of living. Cheaper, standard practice, and it means two people doing identical work are paid differently — which they will eventually discover.

No policy. Each person negotiated individually with no principle behind it. This is what most small companies actually do, and it is the one that causes real damage when it comes out, because it looks like — and usually is — paying people what they would settle for.

Either of the first two is fine. Pick one, write it down in a paragraph, and be able to say it to the person it costs money.

The practical things people forget

Equipment. Someone in another country needs a laptop. Shipping it may incur customs charges larger than you expect. A budget for them to buy locally is usually simpler.

Getting paid. International transfers can take days and eat a meaningful percentage in fees and exchange spread. Agree who absorbs that before the first invoice, not after.

Public holidays. Their calendar, not yours. Write it down at the start so nobody is surprised.

Working hours drift. Two countries change clocks on different dates, so your carefully agreed four-hour overlap quietly becomes three for a fortnight twice a year.

Onboarding takes longer. Everything a new person would absorb by overhearing has to be written down or said deliberately. Budget double the time you would for a local hire, and write things down as you go — you will reuse all of it.

What makes it work

The teams that do this well are not the ones with the best tooling. They are the ones that write things down.

If a decision only exists in a meeting, the person who was asleep did not get it. If a process only exists in someone's head, the person six time zones away is blocked until that head is available. Documentation stops being bureaucracy and starts being the thing that lets anyone do their job.

That is the actual cost of hiring across time zones, and it is worth being clear-eyed about: you pay in writing things down. Most teams find they should have been doing it anyway.

When you are ready, post a role and state the overlap and the location rule in the post itself. And if you want the rest of the posting to do its job, we wrote about that.