Async-first engineering: 6+ years remote with US and EU clients
I’ve worked remotely for over six years, directly with US and EU B2B clients. Not “remote-friendly” — remote-first, where the company’s default mode of operation assumes nobody shares a room. That experience reshaped how I think communication, documentation, and ownership actually work.
Here’s what held up.
Writing is the interface
In an async team, writing quality isn’t a soft skill — it’s load-bearing infrastructure. Decisions, proposals, incident summaries, specs: if it isn’t written, it doesn’t exist. Three habits that matter most:
- Decision docs over decision meetings. A one-page doc with context, options considered, and the call — commented on across timezones — beats a synchronous meeting almost every time, and leaves an artifact new hires can read.
- Updates that don’t require interrogation. “Working on X, blocked on Y, expect it done Z” — sent before anyone has to ask. The update nobody has to request is worth three they do.
- Meeting notes are the meeting. If a decision was reached in a call and not written down, from the company’s perspective it didn’t happen.
Timezone overlap is a budget — spend it deliberately
Working with both US and EU clients means overlap windows are scarce. The discipline: reserve synchronous time for what genuinely needs it — relationship-building, contentious decisions, discovery conversations — and push everything else to writing. A calendar full of “sync to align” is usually a documentation gap wearing a meeting costume.
The discovery calls, though, I always keep synchronous. Sitting in a live conversation with a non-technical customer — hearing the hesitations, the “well, actually what we do is…” — surfaces requirements no form would capture. Some things are worth the timezone math.
Ownership without supervision
Remote-first only works when people own outcomes, not tasks. My operating mode — owning the loop from customer conversation through production traces — is exactly what async work demands: you can’t wait for a hallway answer, so you develop the judgment to make the call and document why.
The flip side: high-ownership engineers still need escalation paths that work across timezones. “I’ll raise it tomorrow” is how a one-day problem becomes a one-week problem. Async teams need explicit norms for what interrupts whom, and how.
The honest tradeoffs
Async-first isn’t free. Trust builds slower over text than over coffee. Tone is easier to misread. Junior people miss the ambient learning of a shared room — which is why I put real effort into mentoring and code review as teaching, not gatekeeping.
But done deliberately, the trade is good: deeper focus, better decisions (writing forces clarity that speaking lets you skip), and a team that keeps shipping while any given timezone sleeps.
Remote isn’t the future of work — it’s just work, done where writing and ownership replace proximity. I wouldn’t trade it back.