Timezone & Async Phrases: Working Across Time Zones
5 exercises on async handoffs, timezone-aware scheduling, and OOO messages. Choose the most natural and professional option.
0 / 5 completed
1 / 5
You've finished a task but your colleague in Singapore is offline. You want to let them know the work is ready without expecting an immediate reply. What do you write?
"I'll leave this in your queue for when you're online": This phrase explicitly frames the handoff as async — it goes into a queue (a natural metaphor in engineering), and it signals that no synchronous response is needed. Real examples: "PR is ready — I'll leave this in your queue for when you're online"; "No rush, I'll leave it in your queue for when you come back online." Option B is too apologetic and a bit passive — "I'll wait" puts you in a holding pattern. Option C ("no rush") is conversational but vague about what "it" is; "your queue" is cleaner. Option D asks for acknowledgement — "let me know" — which still creates a small expectation of reply. Option A is the most intentional, async-native phrase.
2 / 5
You're proposing a meeting time to a colleague in New York (you're in Berlin, UTC+2). You want to be helpful about time conversion. What do you say?
"In your timezone that would be...": Doing the conversion for the other person is a mark of thoughtfulness and async maturity. It removes friction and shows you've already thought about the inconvenience. Real examples: "I'm thinking 4 PM CET — in your timezone that would be 10 AM EST, does that work?"; "In your timezone that would be around 2 PM — let me know if that's feasible." Option A is helpful but the phrasing "your time or ours" can feel slightly transactional. Option C is passive-aggressive and shifts labour unnecessarily. Option D (UTC) is technically correct but impractical — most people don't have UTC mapped in their heads. Option B is the warmest and most professional form.
3 / 5
Two engineering teams in different continents have very few overlapping hours. You want to find a suitable meeting slot. What do you propose?
"Let's find an overlap that works for both teams": "Overlap" is the standard term in distributed-team vocabulary — it refers to the window when two timezone-separated groups are both online. The phrase is collaborative, action-oriented, and neutral. Real examples: "Let's find an overlap that works for both teams — I see a 2-hour window around 3 PM UTC"; "We're trying to find an overlap that works for both teams without anyone staying up late." Option A is vague and just restates the problem. Option C is blunt and can feel unfair — it singles out one team to sacrifice. Option D is valid practice but doesn't directly address finding the slot. Option B names the goal precisely and moves things forward.
4 / 5
A question comes up in a team thread that doesn't need an immediate answer. You want to handle it asynchronously without scheduling a call. What do you write?
"I'll async this — no need to wait on me": Using "async" as a verb is now idiomatic in distributed engineering teams — it signals a deliberate choice to handle something outside real-time. The phrase also releases the other party from waiting, which is a key async courtesy. Real examples: "Good question — I'll async this in Notion, no need to wait"; "I'll async this — expect a write-up in the doc by EOD." Option A is too casual and doesn't assign any ownership. Option C sounds dismissive of meetings without offering a clear alternative process. Option D is reasonable but wordy and slightly passive ("get to it later"). Option B is crisp, uses the right async-native vocabulary, and sets a clear expectation.
5 / 5
You're writing an out-of-office (OOO) auto-reply for a week-long leave. Which message is the most professional and informative?
Clear OOO messages: A good OOO message includes three elements: exact dates, an escalation path for urgencies, and a commitment to follow up. This sets clear expectations, respects the recipient's time, and prevents messages from falling through cracks. Real examples: "I'm OOO 21–28 June. Urgent: contact mark@company.com. Non-urgent: I'll respond 29 June."; "Out of office until 28 June — for time-sensitive requests contact the team lead at [email]." Option A is friendly but vague — "this week" is ambiguous, and there's no escalation path. Option C is formal but unhelpful — it offers no contact alternative or return date. Option D is too casual ("Ping me on Slack") for external or cross-company communication. Option B is complete, professional, and actionable.