Time off and async strategies for remote developers during the 2026 World Cup

The 2026 World Cup runs roughly five weeks across mid-June to mid-July. Remote developers face a decision: full PTO during the matches that matter, partial async working, or a mix. ## Option 1: full PTO during key matches Two to three days off for your country's group-stage matches, then one to two weeks during the knockout rounds. Total budget: 8 to 12 PTO days for a fan attending the latter rounds in person. ## Option 2: async working around the schedule Shift your working hours to bracket match times. East-coast US matches play 12:00 to 21:00 local. Working 06:00 to 11:00 plus 22:00 to 02:00 gives you the matches in between. Sustainable for a week, hard beyond that. ## Option 3: mixed approach Take PTO for your team's big matches and the final. Work async around the rest. Best for fans who want continuity at work but the freedom for high-impact matches. ## How to request the time off The way you ask matters. Submit the request more than 4 weeks ahead. Frame it as "I plan to be off X to Y, and I will hand off A and B before leaving." Concrete handover plans get approved faster than vague requests. ## Managing the team during your absence Pre-record short Looms covering ongoing context. Designate one person as the named point of contact for each open project. Block your calendar in the team's shared calendar; do not just disappear. ## Returning Plan a soft re-entry day. No major deploys on day one back. Reserve the first morning for catching up on async messages and reviewing what shipped while you were out. ## What does not work Trying to work full hours while attending matches. Saying nothing in advance and disappearing for a week. Taking PTO without coordinating handoffs.