Blog  ›  Remote work

How to prove you can work remotely when you never have

The chicken and egg problem, and the three things that break it.

Remote roles attract enormous application volume, so employers filter hard, and one of the easiest filters is prior remote experience. If you have none, you need to supply the evidence another way.

What they are actually worried about

Not whether you can work unsupervised. Whether you can communicate in writing, manage your own priorities, and raise a problem before it becomes a crisis. Those are the three failure modes of remote hires.

Three things that work

• A public body of written work. A blog, thorough documentation, detailed pull request descriptions, a well written portfolio. It proves the communication half directly.
• Any distributed work you have already done, even inside an office job. Coordinating with a supplier abroad, running a project across two sites, supporting a client in another country. Name it in those terms.
• A short contract or freelance engagement. One three month remote project removes the objection permanently.

Say it in the application

One sentence, concretely: I delivered a hotel project for a client in Nigeria while based in Lebanon, covering design through construction documentation, working across a two hour difference. That sentence does more than any claim about being self motivated.

What not to do

Do not describe yourself as a self starter who thrives independently. Every applicant writes it, it carries no information, and it uses a line you could have spent on evidence.