How to Write a CV for Remote Jobs in 2026

Remote roles in 2026 attract 5–10× more applicants than equivalent in-office roles. Your CV has to do extra work to signal that you're not just looking for a remote job — you're someone who has *actually thrived remotely* and can do it again.

The four signals recruiters look for on a remote CV

1. **Proven remote tenure** — at least one role you held remotely for 12+ months
2. **Written communication** — evidence you produce clear, async-friendly documents
3. **Self-direction** — outcomes you owned end-to-end without daily oversight
4. **Time-zone overlap and reliability** — you understand and engineer for the team's working hours

Your CV should make these four signals impossible to miss.

Where to put remote signals

In your header

State your time zone explicitly. "London, UK (GMT+0)" — this is more useful to a US-based remote-first company than just "London, UK".

If you're open to overlapping hours, say so: "Available 13:00–22:00 GMT to overlap US Pacific".

In your summary

Mention remote experience explicitly in the 3-sentence summary:

"Senior backend engineer with 8 years building distributed systems, including 4 years fully remote at GitLab and Doist. Specialise in async-first written communication and high-trust low-meeting teams. Led the migration of a 40-service monolith with a 6-engineer team spread across 5 time zones."

In each role

For each role, tag whether it was remote, hybrid, or in-office:

``` Senior Backend Engineer · GitLab — Remote (global) Mar 2022 – Present ```

For hybrid, say the split: "Hybrid (2 days London office)".

In your achievement bullets

At least 2–3 bullets per remote role should demonstrate remote-specific competencies:

• "Owned end-to-end delivery of the payments platform with a 6-engineer team across 5 time zones; shipped 12 quarterly milestones on time using async RFCs and weekly written updates."
• "Authored the team's incident-response playbook used in 40+ on-call rotations across 3 regions."
• "Mentored 4 distributed engineers through promotion, conducted 90% of 1:1s async via Loom and written docs."

Tools to list (and how to)

Recruiters scan for the remote stack. Include the tools you genuinely used:

• Communication: Slack, Microsoft Teams, Discord, Twist
• Async video: Loom, Tella
• Docs: Notion, Confluence, Google Docs
• Project tracking: Linear, Jira, Asana, ClickUp
• Pair / mob programming: VS Code Live Share, Tuple
• Whiteboarding: Miro, FigJam, Excalidraw

The "remote-friendly" employer list

If you've worked at one of the well-known remote-first companies, lean into it. Recruiters know the cultures. Examples: GitLab, Automattic, Doist, Buffer, Zapier, Basecamp, 37signals, HashiCorp (pre-IBM), Loom (pre-Atlassian), Posthog, Vercel.

If you haven't, your CV needs to do the signalling those company names would have done.

Red flags to remove

• "Looking for the flexibility to work from home." Frame it as a strength you bring, not a personal preference.
• "Self-motivated" with nothing to back it up. Replace with an outcome you owned.
• Listing 12 collaboration tools you barely use. List 4 you used daily.
• Vague tenure ("worked remotely sometimes"). Be specific: "Fully remote since Mar 2020."

Cover letter does the rest

A short cover letter is more important for remote roles than for in-office. Use it to:

• Confirm your time zone and overlap hours
• Name the specific tools and async practices you've used
• Give one concrete example of remote impact
• Confirm your home setup if asked (broadband, dedicated workspace)

Templates well-suited for remote applications

A clean, single-column ATS-friendly template is the right baseline. The Slate Tech and Modern Blue templates work particularly well for remote tech roles — clean, scannable, and recruiter-friendly.