Working Across US and India Time Zones: A Practical Guide for Remote Teams

The US-India time corridor is one of the most common remote team setups in tech and one of the hardest to manage. India Standard Time (IST, UTC+5:30) is 9.5 hours ahead of US Eastern and 13.5 hours ahead of US Pacific. There is no "good" meeting time for both sides. Here's how teams that do this daily actually make it work.

The Numbers: US to India Time Difference

The first number is during summer (EDT/IST), the second during winter (EST/IST). India does not observe daylight saving time, so the gap changes by 1 hour when the US switches clocks.

Key insight: US East Coast teams have about 1.5 hours of overlap with India if both sides stretch slightly. US West Coast teams have effectively zero overlap during normal business hours.

The Actual Overlap Windows

There are two practical meeting windows for US East Coast and India:

Morning IST / Late Evening ET (the standard slot)

* During EDT; add 1 hour during EST

Late IST / Morning ET (the afternoon slot)

* During EDT; add 1 hour during EST

The fairness issue: if you always use the morning IST slot, the US team is always giving up their evening. If you always use the late IST slot, India is always giving up their evening. Rotate between the two if the meeting is recurring.

Patterns by Team Type

Engineering teams

The most common pattern for US-India engineering teams:

• One daily standup at 8:30 AM IST / 10:00 PM ET. Keep it under 15 minutes. The US side records it for anyone who can't attend.
• Code reviews happen asynchronously. India submits PRs at end of their day (6-7 PM IST); US reviews them in the morning (9-10 AM ET). This creates a natural handoff cycle where code moves forward across the day.
• Design discussions and sprint planning go in the late IST / morning ET window (8 PM IST / 9:30 AM ET) since these need more back-and-forth. Alternate with the morning IST slot to share the burden.

Sales and client-facing teams

If your India team supports US clients:

• India team shifts hours to overlap with US business. A common pattern is a 2 PM – 11 PM IST shift, which covers 3:30 AM – 12:30 PM ET. This is standard in Indian BPO and tech services companies.
• For occasional cross-team syncs, use the 8:30 AM IST / 10 PM ET slot and keep it weekly, not daily.

Support teams (follow-the-sun)

The US-India gap is actually an advantage for support coverage:

• India covers 6 AM – 3 PM IST (7:30 PM – 4:30 AM ET) — overnight US coverage.
• US covers 9 AM – 6 PM ET (6:30 PM – 3:30 AM IST) — overnight India coverage.
• Handoff meetings at shift boundaries: 8:30 AM IST / 10 PM ET and 9 AM ET / 7:30 PM IST.

DST Impact

India does not observe DST. The US does. This means:

• When the US springs forward (March), the gap shrinks by 1 hour. Your 8:30 AM IST standup moves from 10 PM EST to 10 PM EDT — same clock time, but it's actually 1 hour earlier in real terms.
• When the US falls back (November), the gap grows by 1 hour. The same meeting now happens at 11 PM EST, which is meaningfully later.
• Adjust your meeting times in November when the US falls back. The gap getting wider is the painful direction.

Making Async Work

With only 1-2 hours of realistic overlap, the US-India corridor is fundamentally async. Teams that fight this burn out. Teams that embrace it build systems:

• Written daily handoffs. At the end of each side's day, post a 3-bullet summary: what you finished, what's blocked, what the other side should pick up. Slack channel or Notion page — doesn't matter, as long as it's consistent.
• Loom over meetings. A 5-minute video walkthrough of a design mockup, architecture decision, or bug investigation can replace a 30-minute meeting. The recipient watches it at the start of their day.
• Shared Kanban boards with explicit handoff states. Instead of "In Progress," use "In Progress (India)" and "In Progress (US)" so both sides know who owns what at any point.
• Decision logs. When decisions happen in a meeting that only one timezone attends, write down the decision, the reasoning, and who was involved. This prevents "we discussed this last night" becoming a source of frustration.

Cultural Context

A few practical notes from teams who've worked this corridor for years:

• Indian public holidays are different. Diwali, Holi, Republic Day, and Independence Day (August 15) are major holidays that US teams often don't have on their radar. Share holiday calendars at the start of each quarter.
• The half-hour offset matters. IST is UTC+5:30, not +5. That :30 makes every conversion slightly awkward and is the most common source of "I thought the meeting was at..." mistakes.
• Bangalore/Hyderabad/Pune tech culture often runs late. It's common for Indian engineering teams to work 10 AM – 7 PM or later, which actually helps the overlap. Don't assume a hard 9-to-5 IST schedule.