Time Zone Management: Working US Hours from India Without Burning Out

It's 10:47 PM and I'm sitting on a call where my product manager in San Francisco is walking through the sprint priorities for next week. My wife is watching something on Netflix in the bedroom. My daughter went to sleep two hours ago. There's a half-eaten dinner plate on my desk that I never finished because the 9:30 PM call ran over. This is my Monday through Friday. Sometimes Saturday too, if there's an incident.

I've been working US hours from India these days for about three years. IST is 9.5 or 12.5 hours ahead of US time zones depending on whether you're working with East Coast or West Coast teams (and whether daylight saving is active — which shifts things by an hour twice a year, and yes, that matters more than you'd think). For most Indian remote workers with US clients, the core working hours look something like 6:30 PM to 2:30 AM IST if you're syncing with Pacific Time, or 7:30 PM to 3:30 AM for Mountain, or 8:30 PM to 4:30 AM for Eastern.

Those are the raw numbers. What they don't capture is what living on this schedule actually feels like. So let me be honest about that before we get into the tips and tricks.

What the First Month Feels Like

When I started, I thought it would be easy. I'm a night owl anyway. I figured I'd sleep until noon, start work in the evening, and have my mornings free. On paper, it made sense. In practice, the first month was a mess.

The problem isn't staying up late. Most of us can do that. The problem is that the rest of India operates on normal hours. Your bank closes at 4 PM. The electrician comes at 10 AM. Your parents call at 8 AM because that's when they have tea. The vegetable guy is gone by 11 AM. Doctor's appointments are from 10 to 1. Your kid's school starts at 7:30 AM. None of the world accommodates the fact that 7:30 AM is the middle of your night.

So what happens is you end up sleeping in broken chunks. You work until 2:30 AM. You wind down until 3 or 3:30. Fall asleep by 4. Get woken up at 8 because someone's at the door, or your phone rings, or sunlight comes through the curtains. You get 4 hours. Maybe you nap in the afternoon for 2 hours. That's 6 hours total but split across two sessions with a gap in between. It's not the same as 6 continuous hours, and your body knows it.

By the end of the first month I had a permanent headache, I was irritable with my family, and I was drinking four cups of coffee after 6 PM just to stay sharp for calls. I gained 3 kilos because I was eating dinner at midnight and snacking through the night. My social life was effectively zero — by the time Saturday rolled around, I was so sleep-deprived that I spent most of it unconscious.

I'm telling you this not to scare you off but because nobody talks about it when they're selling the "earn in dollars, live in India" dream. The money is real and it's good. But the cost is also real, and you should know what you're signing up for.

The Schedule That Actually Works (For Me)

After a lot of trial and error, I settled on a schedule that's sustainable. Not perfect — sustainable. There's a difference. Here it is:

7:00 AM — Wake up. Not optional. I set an alarm and I get up at 7 regardless of when I went to sleep. This was the single most important change I made. Having a fixed wake time anchors your circadian rhythm. I used to sleep until noon and it made everything worse.

7:00-8:30 AM — Morning routine. Exercise (30 minutes, usually a walk or home workout), breakfast, shower. This window is also when I handle anything that needs to happen during "normal" hours — bank visits, calls to utility companies, school drop-off.

9:00 AM-12:30 PM — Deep work block (async). This is the golden window. My US team is asleep. Nobody is pinging me on Slack. No meetings. I use this time for the work that requires concentration — writing code, drafting documents, reviewing PRs, thinking through architecture decisions. This is when I'm most productive, and it's the time that most Indian remote workers waste by sleeping through it.

12:30-1:30 PM — Lunch. A proper lunch with family. Not at my desk.

1:30-4:00 PM — Nap + personal time. This is the other critical piece. I nap from about 2 to 3:30 PM. Sometimes 4 PM if I was up late the night before. This isn't laziness, it's strategy. The nap gives me a second wind for the evening work session. Without it, I'm useless by 11 PM.

4:00-6:30 PM — Light work, admin, emails. US East Coast is starting to come online around 4:30-5 PM IST (that's 7-7:30 AM ET). I catch up on any async messages that came in, respond to emails, do code reviews, handle low-focus tasks. Sometimes there's a standup with the East Coast folks around 6 or 6:30 PM IST.

6:30-7:30 PM — Dinner with family. Non-negotiable. I eat dinner with my wife and daughter at a normal time. Even if there's a meeting at 7 PM, I block my calendar. This is the hill I will die on.

7:30 PM-12:30 AM — Core US overlap hours. This is meeting time, pair programming, real-time collaboration, Slack responsiveness. Depending on the day, this is either packed with calls or relatively quiet. I aim to log off by 12:30 AM. Sometimes 1 AM if something is on fire. Rarely later.

12:30-1:30 AM — Wind down. No screens. I read, listen to a podcast, or just sit. The temptation to scroll my phone is intense but the screen light destroys my ability to fall asleep.

1:30 AM — Sleep.

Total sleep: roughly 5.5 hours at night + 1.5 hours nap = 7 hours. Not ideal — 8 would be better — but it's enough to function without accumulating sleep debt week over week. The key is the biphasic pattern: the afternoon nap isn't optional in this schedule. Skip it and by Thursday you're running on fumes.

What Most People Get Wrong

I've talked to a lot of Indian remote workers about their schedules, and there are patterns in what doesn't work.

"I'll just shift my entire sleep schedule." The plan: sleep from 3 AM to 11 AM, work from 6 PM to 2 AM. Sounds logical. The problem: you're sleeping through the entire morning, which means you miss every single thing that happens in the real world before noon. You can't exercise outdoors (it's too hot by 11 AM in most Indian cities), you can't run errands, you can't see friends, and if you have kids, you basically miss them Monday through Friday. People who try this usually last 3-6 months before the isolation gets to them.

"I don't need a nap, I'll just power through." Sure. For a week. Maybe two. Then the 10 PM meeting becomes torture and your brain starts producing mush instead of code. The human body isn't designed for a single 5-hour sleep episode. If you're going to sleep less at night (which US hours from India forces you to do), you need to compensate during the day. Some people do this with a short 20-minute power nap, but I find 60-90 minutes works better for a sustained schedule.

"Coffee will fix it." Coffee after 4 PM will help you stay alert for the evening, but it will also delay your 1:30 AM bedtime to 3 AM. My rule: no caffeine after 3 PM. I switched to green tea for the late afternoon, and after 7 PM, just water. Yes, I'm a little less sharp at 11 PM than I would be with a cup of coffee, but I fall asleep faster and sleep deeper. The net effect is positive.

"Weekends, I'll sleep normally." The idea of catching up on sleep over the weekend by sleeping from 11 PM to 9 AM is appealing. And you can do it occasionally. But if you dramatically shift your sleep schedule on weekends, you get social jet lag — your body essentially experiences the equivalent of flying across several time zones twice a week. Monday evening you're groggy and out of sync, and it takes until Wednesday to readjust. I keep my weekend wake time within 1 hour of my weekday wake time. I might sleep until 8 AM instead of 7 AM on Saturday. But 7 to 11 AM is too much of a jump.

The Health Stuff Nobody Warns You About

Let me be honest about what working these hours has done to my health, because I think people need to hear this with clear eyes.

Weight gain. Eating dinner late (or eating twice — once at 7 PM with family, then snacking again at 11 PM while working) is common. Your metabolism is slower at night. Late-night eating is strongly correlated with weight gain in basically every study I've read. I put on 7 kilos in my first year of US hours. It took active effort — structured meal times, no snacking during work hours, intermittent fasting on some days — to bring it back down. I'm still 3 kilos heavier than when I started.

Vitamin D deficiency. If you're sleeping through peak sun hours (10 AM - 2 PM), you're not getting sun exposure. My vitamin D levels dropped to 14 ng/mL after a year — the normal range starts at 30. I now take a 60,000 IU supplement weekly (prescribed by my doctor) and make a point to get 20-30 minutes of morning sun before 9 AM. Get your levels checked.

Digestive issues. Eating at odd hours messes with your digestive system. I developed acid reflux that I'd never had before. Eating a heavy meal at midnight and then going to bed two hours later is a recipe for GERD. The fix for me: lighter meals during work hours (fruits, nuts, yogurt rather than full meals), and finishing my last food intake by 11 PM.

Mental health. This is the big one and the one people don't talk about enough. Working when everyone else is asleep is isolating. Your evenings — the time most people socialize, attend events, visit family — are consumed by work. Weekday dinners with friends essentially stop. Evening weddings and functions conflict with your work schedule. Festival celebrations happen while you're on a call. This takes a real psychological toll over time, and it's not something you can hack with a productivity tip.

I went through a period of about four months where I was no-kidding depressed. Not just tired. Depressed. I didn't connect it to the schedule at first — I thought work was stressful, the weather was bad, whatever. But when I took a week off and lived on normal hours, the difference was dramatic. The schedule was a major contributor. I started therapy (online, conveniently scheduled at 11 AM when nobody at work is awake), and it helped. I'm not saying this to be dramatic. I'm saying it because if you're six months into US hours and you feel like something is wrong, it might not be you — it might be the schedule.

Tips That Actually Help

Here are the things that have made a genuine difference for me. Not aspirational Instagram advice. Real stuff that works.

Blackout curtains. If you're sleeping past sunrise (which you are on this schedule), you need total darkness. I spent Rs 4,000 on blackout curtains for my bedroom and they're the best investment I've made for sleep quality. The difference between waking up at 7 AM because your alarm went off and waking up at 5 AM because sunlight hit your face is two hours of sleep you can't get back.

A dedicated workspace with a door. If you're working until midnight and your family is asleep, you need a room where your keyboard sounds and your voice on calls don't disturb them. And they need a space where their 7 AM noise doesn't wake you when you're trying to sleep until 7. A door. That's the key feature. Not a standing desk, not a Herman Miller chair. A door.

Blue light management. I use Night Shift on my laptop starting at 10 PM and wear blue-light-blocking glasses after 11 PM. Does it make a huge difference? Honestly, maybe 10-15 minutes faster sleep onset. But when you're sleeping on tight margins, those 15 minutes matter. Also, the glasses are a physical cue to my brain that sleep is approaching, which I think matters as much as the actual light filtering.

Pre-made meals. Cooking at midnight isn't going to happen consistently. I batch-cook on Sunday — dal, rice, some sabzi — and portion it out for the week. Weeknight "dinner" at 11 PM is reheating something in the microwave for 3 minutes. This eliminated the late-night Swiggy orders that were terrible for both my wallet and my waistline.

Morning exercise, non-negotiable. This was hard to start because after 5.5 hours of sleep, the last thing you want to do is move. But morning exercise does three things: it wakes you up better than coffee, it ensures you get outside and get sun, and it creates a buffer between your daytime life and your nighttime work life. Thirty minutes is enough. Walk, jog, yoga, whatever. Just move before the day takes over.

Communicate your schedule to everyone. Your family, your friends, your parents, your neighbors. "I work from 7:30 PM to 12:30 AM. Please don't call me during those hours unless it's an emergency." "I sleep from 1:30 AM to 7 AM and again from 2 PM to 3:30 PM. Please don't ring the doorbell during those times." People forget if you don't remind them. My mom still calls me during work sometimes because she forgets. But mostly, once people know, they adjust.

Protect your weekends like your life depends on it. Because kind of, it does. If you let work bleed into Saturday and Sunday, you lose the only time you have for a normal human life. I am extremely firm about weekends. I don't check Slack. I don't respond to emails. My status says "off" and I mean it. Some managers test this boundary. Hold it.

Tips That Sound Good But Don't Actually Work

"Just negotiate flexible hours." Everyone says this. In theory, your US company should be flexible about when you work. In practice, meetings are scheduled during US business hours because that's when the team is available. You can try to move your standup from 10:30 PM to 8 PM, but if the rest of the team is in a meeting at 8 PM your time, it doesn't work. You adapt to the majority time zone, not the other way around. Some companies are sincerely async-first and give you real flexibility. Most are "remote-friendly" which means "you can work from home but you still need to be online when we're online."

"Use polyphasic sleep." I see this advice in remote work forums and it drives me crazy. Polyphasic sleep — sleeping in multiple short bursts throughout the day — is an interesting experiment for people with total control over their schedule. It doesn't work when you have a 4-hour block of meetings from 8 PM to midnight that you can't interrupt with a nap. Stop recommending this to people with real jobs.

"Move to a closer time zone." "Why don't you just move to Dubai? It's only 1.5 hours behind IST." Great, now I'm 1.5 hours less misaligned with my US team but I've also moved to a different country, away from my family, into a much higher cost of living, and I need a work visa. This isn't a practical tip for 99% of Indian remote workers.

"Alternate between morning and evening schedules weekly." Some people suggest working morning hours one week and evening hours the next. I tried this. It's the worst of all worlds. Your body never adjusts to either schedule. You're perpetually jet-lagged. Pick one schedule and stick with it.

The Family Conversation

If you have a spouse, kids, or live with parents, working US hours from India isn't a solo decision. It affects everyone in the house.

Your spouse effectively becomes a single parent during weekday evenings. Dinner, homework, bedtime routines — they're handling it alone because you're on a call. If both of you work, you need to figure out who covers the evening shift with kids. In my case, my wife handles bedtime (7:30-8:30 PM) and I handle the morning (7-8:30 AM). This works because she's a morning person and I'm available in the mornings. If she also worked late hours, we'd be in trouble.

Your parents, if they live with you or nearby, will have opinions about you "sleeping during the day" or "working at night like it's some call center job." The generational understanding of remote work is still catching up. I've had this conversation multiple times with my father-in-law, who truly doesn't understand why I can't just tell my company to let me work from 10 AM to 6 PM. Patience helps. Showing them the salary helps more.

Your social circle will thin out. This isn't inevitable but it's common. When you're unavailable every weekday evening and spending weekends recovering, you attend fewer gatherings, accept fewer invitations, and slowly drift from people who operate on normal schedules. I've lost touch with friends I used to see weekly. The ones I've kept are the ones who adjusted to meeting me for breakfast or a weekend afternoon instead of dinner.

When You're Working with Multiple US Time Zones

Some of you are working with teams split across Eastern and Pacific time. My team has people in New York (ET) and San Francisco (PT). That's a 3-hour spread on their side, which translates to a wider window I need to cover.

The overlap window that works for all of us: 9:30 PM to 12:30 AM IST (12 PM to 3 PM ET / 9 AM to 12 PM PT). That 3-hour window is when we schedule all meetings. Everything outside that is async. This works because the team agreed to concentrate meetings rather than spread them throughout the day. Not every team will agree to this, but it's worth pushing for.

If your team won't concentrate meetings, you end up in the worst-case scenario: meetings scattered from 7 PM to 2 AM IST, with gaps between them that are too short to do deep work but too long to just wait through. I've been in that situation and it's miserable. You're effectively "on call" for seven hours even though you have maybe three hours of actual meetings. The rest is dead time.

The fix: push for documented async communication. Loom videos instead of live presentations. Written proposals instead of brainstorming meetings. Recorded standups instead of live ones. Every meeting you eliminate is an hour you reclaim for either work or sleep.

How to Know When It's Too Much

This is the part I wish someone had told me earlier. There are signs that the US hours schedule is doing more harm than good, and you should take them seriously.

If you're getting less than 6 total hours of sleep (including naps) more than twice a week consistently, that's not sustainable. Sleep deprivation compounds. It doesn't reset on weekends.

If your relationship with your spouse or family has noticeably deteriorated since you started this schedule, and it's exactly about your availability and not other factors, that's a signal.

If you're using alcohol to fall asleep. I know several remote workers who started having "a drink or two" after logging off at midnight because it helped them fall asleep faster. That path leads somewhere bad.

If your work quality has dropped. If you're making more mistakes, missing details, forgetting things that were discussed on calls, you're not just tired — you're impaired. Sleep-deprived work isn't just slower, it's worse. Your manager might not say anything, but the quality difference shows up in code reviews, in client feedback, in things you used to catch but now don't.

If you dread Sunday evenings because Monday is coming. Every job has some of this, but if the dread is exactly about the schedule rather than the work itself, your body is telling you something.

What to do about it: First, talk to your manager about adjusting overlap hours. Even one hour less of required overlap can make a meaningful difference. Second, consider whether a role with a UK or European client would give you similar income with a more manageable time zone (3.5-5.5 hours ahead of IST instead of 9.5-12.5). Third, if you've been doing this for more than two years and you're still struggling — not just inconvenienced but really struggling — it might not be the right setup for you, and that's okay. Not everyone's body adapts to inverted schedules. Some people do it for five years and feel fine. Some people do it for one year and hit a wall. Both responses are normal.

The money from US-hours remote work is seriously life-changing for most Indian workers. But money is a means, not an end. If the schedule is costing you your health, your relationships, or your sanity, recalculate the equation. There are remote roles with European companies that pay well and don't require you to be awake at 1 AM. There are US companies with truly async cultures where overlap hours are minimal. There are ways to earn in dollars without living nocturnally. The US-hours night shift is one path, not the only path. Take it with eyes open, protect what matters, and know when to change course.