Writing a CV for remote-first companies

A remote hiring manager is not only asking whether you can do the job. They are asking whether they can manage someone they may never meet in person. Your CV has to answer both questions, usually in under thirty seconds.

Lead with outcomes, not responsibilities

"Responsible for the marketing site" describes a job description. "Rebuilt the marketing site in six weeks, cutting page load from 4.1s to 1.2s and lifting trial signups 18%" describes a person.

For each role, write two or three lines in this shape: what you owned, what you changed, what the measurable result was. If you do not have numbers, use scope — team size, budget, number of markets, volume handled.

Make the remote part visible

If you have worked remotely before, say so explicitly and describe how. "Worked across three timezones as the only European engineer on a US team" tells a hiring manager more than a list of tools.

If you have not worked remotely formally, look for the adjacent evidence: open-source collaboration, freelance client work, distributed volunteer projects, writing that was reviewed by others. Remote work is largely about written coordination, and that leaves traces.

Write like someone who communicates in writing

The CV itself is a sample. Keep sentences short. Use consistent tense. Cut every adjective that is not doing work. A recruiter reading forty applications will notice the one that reads cleanly, even if they could not tell you why.

Practical rules that help:

• One page per decade of experience, and never more than two
• No paragraph longer than three lines
• No skill bars, no rating dots, no headshot
• Tools listed only if you would be comfortable being tested on them

Structure that survives an automated first pass

Most remote applications go through an applicant tracking system before a person sees them. That system is looking for the words in the job description. Mirror the vocabulary of the role where it is honest: if they say "design system", do not write "component library" and hope.

Use a single-column layout, standard headings, and a file name that identifies you. Avoid tables, text boxes and anything that turns your experience into an image.

The section most people skip

Add three or four lines at the top — not a summary of your career, but a statement of what you are for. Something like: "Frontend engineer focused on design systems and accessibility. Built the component library used by eleven product teams." That is enough to anchor everything below it.

Before you send it

Read the posting again and underline every requirement. Then check that your CV answers each one, in order of importance to them. If a requirement is missing, do not bury it — either address it in a cover note or accept that this application is a long shot and spend your time elsewhere.

A CV is not a record of everything you have done. It is an argument that you should be interviewed.