How to write an ATS-friendly CV that still reads like a person wrote it
What applicant tracking systems actually parse, the formatting choices that silently break them, and how to fix a CV without stripping the personality out of it.
Distributed teams rarely break down over technical ability. They break down over the shrinking window in which two people can talk.
Every collaborative task has a component that is cheaper synchronously. Unblocking a confused colleague takes four minutes on a call and two days over messages. When the shared window is too small, those exchanges queue, and a one-day task becomes a one-week task.
The threshold most distributed teams converge on is around four hours of daily overlap for collaborative roles, and closer to two for independent ones. Below that, teams either restructure the work to be genuinely asynchronous or quietly push someone to shift their day.
That pushing is the real risk. A job advertised as remote-anywhere with a team clustered in one region often means the outlier hire moves their working day by four hours. It is survivable for months and corrosive over years.
Convert both working days to UTC and take the intersection. A person working 09:00–17:00 in Lagos is 08:00–16:00 UTC. A team working 09:00–17:00 in New York is 13:00–21:00 UTC. The intersection is 13:00–16:00 — three hours.
Now subtract lunch, subtract the hour at each end that is realistically consumed by starting and finishing, and ask whether what remains fits the meetings the role actually requires. Three hours on paper is often ninety usable minutes.
Ask where the rest of the team actually sits, not where the company is registered. Ask which meetings are mandatory and what time they run in UTC. Ask whether the last three hires outside the core region are still with the company.
Ask what happens in an incident at 03:00 your time. A good answer describes a rota. A bad answer describes goodwill.
Publish the overlap window in the posting, in UTC, before the salary. It filters harder than any requirement you could write and it filters on the thing that actually predicts success.
Then hold yourself to it. If the window is 12:00–16:00 UTC, do not schedule the decision-making meeting at 17:30 because it suits the founders. The window you publish is a promise, and the first time you break it your distributed hires learn where they really sit.
Four hours is the common standard for collaborative roles. Teams that have genuinely invested in written communication run comfortably on two. Anything advertised as zero overlap should come with visible evidence of async practice — recorded decisions, written proposals, no standing meetings.
A one or two hour shift is normal and sustainable. A four hour shift means permanent misalignment with everyone you live near, and it is the most common reason people leave otherwise good remote jobs within two years.
The CV builder runs the nine parser checks described here automatically, and rewrites weak lines with you. Free, no card.
What applicant tracking systems actually parse, the formatting choices that silently break them, and how to fix a CV without stripping the personality out of it.
The three ways to pay someone in a country where you have no company, what each costs, and the misclassification risk that catches small teams out.
Location-based pay bands, how to find the real range, and the arguments that actually move an offer for a distributed role.