A resume built for office jobs and a resume built for remote jobs should look different, because the thing you’re proving is different. A hiring manager scanning for a remote hire isn’t just asking “can this person do the work?” — they’re asking “can this person do the work without me checking in on them?”
Lead with outcomes, not hours
Remote work is judged on output, so your resume should be too. Instead of describing responsibilities, describe what changed because of you: the feature shipped, the process you cut from two weeks to two days, the support ticket backlog you cleared. Specific, measurable results tell a remote hiring manager exactly what they’re getting without needing to watch you work.
Name-drop the remote-relevant skills directly
If you’ve worked async, across time zones, or on a fully distributed team before, say so explicitly — don’t bury it. A line like “collaborated daily with engineers across four time zones using written design docs and recorded demos” tells a reader far more than “strong communication skills” ever will.
Keep your location line honest and simple
If a role says “Worldwide (Remote),” you generally don’t need to list your city at all — your time zone, if it matters for overlap, is enough. If a role has a region requirement like “Remote, EU,” make it easy for the reader to confirm you qualify instead of making them guess from a city name.