A remote-first CV is not a standard CV with "remote" added to the job title. Hiring managers reading hundreds of applications in asynchronous-first teams scan for different signals than office hiring managers do.
Spell out how you have operated without an office. Phrases like "managed projects across three time zones via written updates" or "delivered weekly written status reports to distributed team" are more convincing than a location field saying "remote." Concrete evidence of async output matters more than declarations of preference.
Remote jobs reward people who finish things without being asked. Highlight projects you owned end-to-end, decisions you made without daily manager input, and deliverables you defined independently. These patterns reassure hiring teams that you will not need constant shepherding.
For many remote roles, your application email and CV prose are an implicit writing test. Clear, tight sentences signal low communication overhead. Vague, padded descriptions signal high overhead. Edit your CV copy as carefully as any client deliverable.
State your actual working time zone and your availability window plainly. "UTC+7, 8am–5pm with two overlap hours with UK time" is far more useful than "flexible." Teams building schedules around distributed members need real information, not reassurances.
Remote hiring often moves fast with fewer calls. A portfolio link, GitHub profile, or writing samples URL converts passive curiosity into active evaluation without requiring a call to schedule. Make it easy to see your work without emailing you first.
If the company's engineers are mainly in Europe and you are currently in Asia, address this in a cover note: how you plan to handle the overlap, whether you have done this before, and what it looked like in practice. Hiring teams appreciate applicants who name the coordination challenge rather than pretending geography does not exist.