A remote-first employer is reading your CV with one question in mind, and it is not the one you prepared for. They already assume you can do the job. What they cannot tell from a standard CV is whether you produce results when nobody is watching, and that gap is where most remote applications quietly die.
Office CVs rest on an unspoken assumption: someone will be nearby to notice your effort and vouch for your reliability. Strip that away and the document has to carry the proof by itself.
Start with the location line, and do not delete it
The most common instinct when applying for a fully remote role is to delete your address. It feels logical - if location does not matter, why mention it? It matters more than you think, just not the way it used to.
A remote employer needs two things from your location: the country you are legally resident in, and the time zone you work from. The first determines whether they can hire you at all, through an entity, an employer of record, or a contractor agreement. The second determines whether you overlap with the team enough to be useful. A recruiter who cannot answer either question at a glance will move to the next CV rather than guess.
So do not write your street address, and do not leave the line blank:
Lyon, France (CET) - open to fully remote
That single line answers the legal question, the overlap question and the intent question in nine words. A specific work authorisation is worth flagging too: "EU work authorisation, no sponsorship required" saves a recruiter an email.
Tag the work mode inside every role line
Plenty of candidates have three solid years of remote experience buried in their CV and never say so. They assume the reader will infer it from the company name, or from a line about "collaborating with international colleagues". Nobody infers anything during a six-second scan.
Put the work mode in the role line itself, where it cannot be missed:
- Marketing Manager, Acme - fully remote, distributed team of 12
- Backend Engineer, Northwind - hybrid, 2 days on site, team split across London and Warsaw
- Support Lead, Cortex - remote-first company, managed 6 agents across 4 time zones
The pattern is work mode, then scale, then distribution. Scale and distribution matter because remote coordination gets harder as the team grows and spreads. A person who ran a distributed team of 12 has solved problems that a solo remote contractor has not, and the reverse is also true - deep self-direction is its own credential.
If your remote experience was informal, say that plainly rather than inflating it. "Remote 3 days/week for 18 months" is credible. "Extensive remote experience" is not.
Evidence the five competencies remote managers actually screen for
This is the heart of the document. Remote hiring managers are checking for a specific set of behaviours, and each one has to be shown with an outcome rather than claimed with an adjective.
Asynchronous written communication
The single highest-signal competency, because in a distributed team writing replaces most of the conversations that used to happen at a desk. Do not write "excellent communication skills". Show the artefact and its effect.
Weak: Strong written and verbal communication skills.
Strong: Replaced the weekly status call with a written update template adopted by 4 teams; cut recurring meetings from 5 to 2 hours per week.
Self-management without supervision
Show that you owned a scope and delivered it on a timeline you set. Anything involving a deadline you managed yourself, a backlog you prioritised, or a project you ran without a manager sitting in the same building counts.
Example: Ran the Q3 pricing migration solo across 6 weeks with weekly written checkpoints, no missed deliverables.
Documentation habits
Documentation is how remote teams scale knowledge without meetings. If you built a runbook, a wiki, an internal FAQ or a decision log, that belongs in the CV with a number attached - how many people used it, or how much onboarding time it saved.
Working across time zones
Name the actual spread. "Coordinated with engineering in Bangalore (IST) and sales in Austin (CST) on a 3-hour daily overlap" tells a reader far more than "international experience". It also proves you treat overlap as a resource to be designed.
Onboarding and mentoring people you have never met
This is the competency almost nobody puts on a CV, and it is the one that separates a competent remote worker from someone a manager wants to hire. Bringing a new hire up to speed when you have never shared a room with them is genuinely hard. If you have done it, say so, with the number: "Onboarded 5 remote hires across 3 countries; average time-to-first-shipped-PR of 9 days."
Before and after: one bullet, rewritten
Most CVs already contain the raw material. The problem is that it is written for an office reader.
Before: Managed the content calendar and worked with colleagues in other offices.
>
After: Owned the content calendar for a fully distributed team of 8 across CET and EST; ran the whole cycle async in Notion with a 24-hour review SLA, shipping 42 pieces in a year with zero live planning meetings.
The after version says the same thing about your job, and something completely different about you. It names the work mode, the time zone spread, the tool, the async process, the service level, and the output. A remote hiring manager reads that and stops worrying.
The tooling line, and why half of them are wasted
A row of tool names - Slack, Notion, Jira, Linear, Figma, Miro, Zoom - signals that you have lived inside a distributed workflow. It is worth including, because these tools carry conventions: threads instead of channels, docs instead of decks, tickets instead of verbal handoffs.
But a bare list is close to worthless on its own, because everyone lists the same seven tools. The value comes from pairing at least two of them with usage inside your experience bullets. "Built the team's Notion knowledge base" and "Migrated 3 workstreams from email threads to Linear" prove fluency. A logo wall proves nothing. Keep the skills section as a scannable line, then let the bullets do the proving.
The ATS keyword angle
Recruiters filter their applicant pools on literal keywords, and "remote", "distributed", "hybrid" and "time zone" are among the terms they search. If none of those words appear in your CV text, you can be a perfect remote candidate and never surface. Use the local-language equivalents when applying in another market - "teletravail" for France, "teletrabajo" for Spain and Latin America - because a French recruiter searches in French. Put the words in naturally, inside role lines and bullets, not in a keyword block at the bottom.
Three mistakes that sink remote applications
- The CV reads as purely office-bound. Every bullet implies a room: "attended daily stand-ups", "presented to the leadership team", "supported walk-in requests". None of it is wrong, but a reader with 200 applications has no reason to believe you have worked any other way.
- No evidence of written communication. If your CV never mentions a document, a template, a spec, a runbook, or a written process you created, the strongest remote signal available to you is missing.
- No signal about availability. Say what your overlap looks like. A line such as "Available 09:00-18:00 CET, regular overlap with US East Coast until 12:00 EST" removes the biggest unknown in the recruiter's head. If you have done sustained work outside your own hours, that is worth stating too.
What to do this week
Go through your CV once with a single filter: for every bullet, ask whether it would still make sense if you had never been in the same building as your team. The bullets that fail are the ones to rewrite - add the work mode, the time zone spread, the tool, and the number. If you are starting from your LinkedIn profile, a tool like Postulit will get the structure onto the page so you can spend your effort on the rewriting, which is the part that wins the interview.
One concrete change to make first: add the location line with your time zone. It takes thirty seconds and it answers the question every remote recruiter asks before anything else.