How can I prove I can work asynchronously?

What parts of your office work already involved decisions, handoffs, or updates that colleagues could act on without a meeting? Don’t invent a “remote project.” Instead, turn a real task into evidence: show how you documented status, clarified ownership, recorded decisions, and made progress visible for someone who wasn’t present.

The common failure is treating async as a communication style rather than a reliability test. In interviews, describe the problem, what information you shared, how you set expectations, and how you prevented work from stalling when someone was unavailable.

Create a small public work sample that shows your process, not just the finished result. For example, take a familiar business problem and publish a short brief with goals, assumptions, decision log, task board, and a weekly written update. Aim for a two-week project with artifacts someone could review independently.

There are two cases. If your office role already required independent follow-through, use real examples: a handoff document, written recommendation, or project update, anonymized if necessary. In interviews, explain what information you provided so others could act without waiting for you.

If most work depended on meetings, build evidence now through volunteer, open-source, or portfolio work. The useful framing isn’t “I’ve worked remotely”; it’s “I reduce ambiguity and leave a usable record.”

Which type of role are you targeting: individual contributor or project coordination?