How do you write a resume for remote work?

What's different about a remote resume

A remote resume is almost identical to a traditional one, with four specific additions that signal to a hiring manager that you can work remotely without supervision. Remote-first companies screen hard for these signals because the cost of a bad remote hire is higher than a bad in-office one — async work exposes poor communicators faster and isolates struggling performers.

The additions are: an explicit time zone, named async tools, prior remote experience called out in role headers, and evidence of written communication in the bullets themselves.

The four signals that matter

1. Time zone in the header

Put your time zone directly under your location in the contact block.

Jane Doe
Halifax, NS · Atlantic Time (UTC-4)
jane@example.com · linkedin.com/in/janedoe

This does two things: it tells the recruiter whether you overlap with their team (a five-minute filter), and it signals that you understand async work begins with stating when you're online.

2. Remote experience called out explicitly

In the role header, state whether the role was remote, hybrid, or onsite. Don't hide it in a bullet.

Senior Product Manager — Acme Inc. (Remote, North America)
Jan 2022 – Present

If you have never worked remote before, you cannot fake this. Focus instead on demonstrating the skills remote teams need — written communication, self-direction, async collaboration — through the bullets.

3. Named async tools

Somewhere on the resume — usually the skills section or embedded in bullets — name the tools you use to work async. Generic "collaboration tools" is invisible to a recruiter scanning for signal. "Slack, Notion, Linear, Loom" tells them you have worked in a modern async stack.

Other legitimate tools to name if you actually use them: Figma (design sync), GitHub (code review async), Jira (ticket tracking), Asana, ClickUp, Miro, Zoom, Google Meet. List the tools you have used at depth. Don't pad.

4. Written communication in the bullets

Remote hiring managers read the resume itself as a writing sample. Bullets that are clear, concise, and quantified tell them you can write a clean PR description or a status update. Bullets that are vague or jargon-heavy suggest the opposite.

Strong: "Wrote and maintained the API deprecation playbook used by 40+ engineers across three time zones."

Weak: "Facilitated cross-functional synergy in a distributed environment."

The summary line for remote roles

Put the word "remote" in your one-line summary if it is true.

Senior product manager with 7 years across B2B SaaS, operating remote-first across the Atlantic/Eastern overlap since 2020.

That single line answers the first three questions in the recruiter's head: what do you do, how senior are you, can you work remote.

What to leave out

• Home office photos or "setup shots." Not appropriate on a resume.
• Self-described "remote ninja" language. Recruiters laugh at it.
• Irrelevant time zones. If you've only ever worked in one time zone, don't list three.

A note on time zone overlap

Most remote-first North American companies require four hours of daily overlap with the team's core hours. Before you apply, check the posting: "Open to any time zone with 4-hour overlap with US Pacific" means something different from "open to any time zone."

If you're in a time zone that requires early mornings or late nights for overlap, state your willingness in the summary or the cover letter — not by pretending you're in a different time zone.

The one thing remote hiring managers filter on first

They scan the resume for one-sentence answers to three questions:

1. Can this person write?
2. Have they worked remote before, and where?
3. Do they overlap with our team?

Every resume should answer all three in the first third of the page. Everything else is the resume you'd write anyway.