Remote work is not simply “doing the same thing but from home.” For a distributed team to function at a senior level, the key is not location, but asynchronous methodology.
From my base in Madrid, I collaborate with teams in London, Berlin, and Amsterdam. Here’s how I do it so that distance becomes a competitive advantage, not an obstacle.
The Philosophy: Less Slack, More Documentation
The biggest enemy of a developer’s productivity is interruption. If my day is full of Slack notifications and 15-minute “quick” meetings, I can’t enter a state of deep work.
My approach is Async-first:
- Documentation by Default: If a decision isn’t written in Linear, Notion, or the code itself, it doesn’t exist.
- Batch Communication: I respond to messages at specific times of the day, not in real-time.
- Meetings as a Last Resort: Only if a comment thread becomes circular or for team bonding.
Tools of a Senior Asynchronous Workflow
For this system to work, I use tools that allow for total autonomy:
- Linear / Jira: For task management with exhaustive descriptions. Each ticket must have context, acceptance criteria, and possible edge cases defined.
- Loom: To explain complex features or do demos. A 2-minute video saves a 20-minute meeting.
- Claude Code + MCP: I use AI to generate technical documentation drafts and PR summaries, ensuring my colleagues have all the information they need without having to ask me.
PRs That Tell a Story
In an asynchronous environment, the Pull Request is the most important communication document. My PRs don’t just contain code; they contain:
- Why this change is being made (link to the task).
- How it was implemented (key technical decisions).
- How to test it (exact steps).
- Evidence (screenshots or Loom videos).
This allows a colleague in another time zone to review my code and provide feedback without needing us to sync up.
Availability and Overlap
Although I am async-first, I understand the importance of overlap. I work on CET/CEST time, which gives me:
- 100% overlap with Central Europe.
- 80% overlap with the UK.
- 4-5 hours of overlap with the US East Coast.
During these overlap hours, I am available for critical reviews or urgent blockers, but the core work remains asynchronous.
Advantages for the Company
When you hire a senior developer with an asynchronous mindset, you don’t just get code:
- Scalability: The team can grow without communication noise exploding.
- Resilience: If someone is missing or in another time zone, work doesn’t stop.
- Quality of Life: Fewer meetings mean happier and more productive developers.
Conclusion
Asynchronous remote work requires discipline and excellent written communication. It’s the difference between a team that survives remote work and one that thrives in it.
If you are looking for a Senior Full Stack who knows how to work autonomously and keeps your team aligned without constant meetings, let’s talk.
