I worked with teams located in Israel, Ukraine, Poland, UK and Easter, Central and West US while based on Mountain Time.

Long story short, really weird times. Even though most of the communications were async, I still started really early and then called it at midday because I didn´t have more battery on me. I followed up on things by mobile chat in the afternoon but I was already checked out mentally by 2pm. Sometimes when I felt rested enough I gave it a little more in the nights and coordinated with early birds from Europe before I hit the bed.

This went on for over 2 years easily. I gotta say I completely burned out and it took me a long time to recover.

For the ones asking why?. The business outsourced some services overseas which became part of the critical path.

I work in a global company with people in Asia, Australia, North America and across Europe. My team are all in NA and I'm in Australia. I just get up early to maximise cross over, two morning meetings for me a week. Works pretty well but I do get up/stay up occasionally for 2am meetings. Apart from all hands there's no pressure to do so. Hardest part is arranging a meeting between a European, American and myself - someone is going to be out of normal hours. Fully remote rather than "remote but this timezone" is great.

Most people don't like working 9-5. My sweet spot is 4 AM. Half the people I work with prefer nights - it's cooler, better time to smoke, etc. Maybe it's just SE Asia where people get lazy during the day. Or maybe we just have a culture of hanging out at night. 9-5 takes priority but teams tend to follow the devs.

The main issue is always the regular meetings, the standups. Most people prefer to wake up at 10. Some at 11 lol. So you can move standups around "lunch" safely enough. Some people hate standups at the end of the day (i.e. me) because it tends to overlap with the inconsistent end of day school schedules and traffic jams.

But do consider if you actually need standups. Everything should be on Jira. Whenever you commit a file, it can be on Jira too. Scrum was invented before all these tools, back when people had individual offices. Continuous Flow is a valid option and agile.

Other key meetings are what to do (grooming), what have we done (demo), and what can we do better (retro). You don't actually need to follow any sprint format. A clean format is meetings on Monday and Friday, but with new teams and startups, you might want one every 2 days.

If you can do async, do so. Lots of people prefer text too. Text is slower, mainly an issue for managers who need to talk to lots of people. But it lets people think more clearly and supply links as necessary.

You need to work with people who value async communications and uninterrupted work time (or cultivate this culture). I recently moved to EU and it's very very difficult for me to adapt to people insisting on having a call or a meeting for everything. It's such a waste of time and the knowledge is completely lost unless you make notes... in text. Before that I worked in SEA, with teams from across the time zones but in a very "Asian" context. Perhaps since not everybody spoke perfect English, the teams actually preferred typing.

For a while I worked on a 1pm-9pm schedule which gave me a decent overlap with the "let's have a quick call" folks. Having the whole morning to myself was nice.

I have worked with testers 9 hours off my schedule.

That worked out very nicely. We developed during the day, sent out a mail with test instructions, went home, and had a mail message with test results in the morning. So, it felt like you never had to wait for test results.

9 hours also isn’t too large a difference for the occasional phone meeting (one side would take the call from home, either before coming to work, or after getting home, and would take compensation time typically on the same day).

It does require people in both teams who can write clearly, though.

One's schedule inevitably turns into whatever they let it. If you're one that's naturally going to want to join every call or be around for the most active chat periods then no amount of caffeine or motivation is going to make the schedule you decide to keep sane. I'd heavily recommend staying away from caffeine to try to solve tiredness, at best it temporarily masks any symptoms while the problem remains at the end of the day.

Motivation itself isn't that much different than other remote jobs. Make sure it's something you're interested in working on, try to make a few close work buddies, and go enjoy life when the time you said you were going to clock out comes.

I think the key thing here is, it's highly unlikely you need meetings every single day with staff overseas and if you do there is usually a crossover hour. You don't need to both be in constant contact to do good work. You can easily work in different time zones without having a significantly different schedule.

Live in Hawaii, work operates on Central Time.

Wake up 4:45am, start work 5am (9am or 10am central). Make a bagel or something easy. Get drinks as needed. Get a snack before standup at 1pm central if needed. Get off at 1pm (5pm or 6pm central). Make lunch at that time. Eat dinner about 5-6pm. Head to bed at 7:30pm to 8pm.

I don't take a lunch. And if I do, I'll just work later or start earlier the next day.

I have to get on meetings at 4am sometimes when we do a deployment or have meetings with people who are more important than me. I've had to be on a 3am equivalent meeting once in the past 4 years. Small price to pay for the privilege of living in Hawaii.

'pends on the timezone. It is easy in finance to live in NY and work London or vice versa. Working London from SF though looks to be a lot harder. To work Singapore or Hong Kong from NY would be a stressful lifestyle.

I work about 5-6 hours outside of my company's primary time zone, but they tend to try and keep any meetings I need to attend to after 6am or so in my time zone. I don't have much trouble being motivated to work, I am only part time for now anyways, but I do get out and do a daily walk before I do anything heavy for the day, so I'll do some meetings, planning, and admin in the mornings then walk then I have energy to sling code for 4-6 hours.

Some days I just don't work, and I learned to give myself the day (rarely two) but get back to work with a strong day the following day to regain my momentum. I find momentum is key in working remotely, you have to maintain a steady pace and not go too hard or too easy or else you're going to burn out or develop bad habits.

I tend to work whatever days are necessary, weekend or whatever. My life is very flexible, so sometimes I'll have a mid-week weekend and work the weekend instead.

tl;dr: momentum is key, try and work at least a few hours a day and ensure you maintain a steady pace over time without doing death-marches or being lazy.

The last time I worked on a team with members in different time zones (very different -- half the team was in the US, half in India), the only thing it realistically affected was meetings. Since we were essentially 12 hours apart, there was no way to schedule meetings so that they were convenient for everybody. What we did was to alternate who had to have the meeting at the weirdo time. Spread the pain and all that.

My last employer was truly global, I was interacting with people from Japan to the west coast of Canada, with the bulk of people in EU timezones.

Worked great for me, I'm a little bit to the east of CET. My mornings, my most productive hours, were typically unmolested. Then chill out into meetings in the afternoon.

My boss was in Toronto, had to work a bit late to do calls with him, but usually had a long lunch or big dog walk on those days.

His day was typically meetings in the morning, work in the afternoon. The opposite of mine.

I pitied the Australians. They seemed to be attending calls at brutally antisocial hours.

For many years I worked for US based company from European timezone. 9-10 hours difference. It's been okay. I started work around 2-3pm and left around 10pm. It was pretty tough because I couldn't sleep for 3-4 hours after my work day ends that meant 1-2am.

On the bright side I could sleep as much as I wanted in the morning and do chores in first half of the day.

What helped me with motivation is Daily Standup with my team where you have to report about your L24 progress and what you're going to be N24. This added enough stress to increase my motivation to do stuff. I couldn't show up with nothing or lie my way out of it. Also US comp was pretty big motivator. Geo arbitrage etc.

I've done this as a short term contract (freelance). One was 12 timezones different. We found about an hour a day to overlap and tried to be efficient with that time. Most of our communication was async (and naturally would have been for the type of work, even if I was local) so we didn't always need the full time.

It disrupted my sleep cycle, which was tougher than I expected. I'm always up late, but working late is different. The project was exciting, so motivation wasn't an issue.

I'd do it again, for the right project. But I personally wouldn't want to do anything more synchronous than an hour a day.

I started working at wordpress.com (Automattic) in 2006. Everyone was remote.

I was in the UK, a colleague was in Eire and everyone else the US. The colleague was (still is) a coder, I did user support. Communication was IRC. The effect for me was that I'd do my full day then stay online as the US folks started theirs. 15+hr days became the norm (I moved into tackling spam as well as user help) and on more than one occasion I'd just work through the night. ENTIRELY up to me, zero pressure, not even implied. I just like to stay on top of things.

Motivation? I was hired to do a job, so I did it.

At the time I imbibed a lot of caffeine but that was as much as addiction as anything else. Kicked that habit before I left.

It took some years but teams were eventually set by timezone +/- a few hours which was good.

Never work with teams to the west because they will always schedule meetings for what they think is mid-morning and it's lunchtime where you are.

3 years working with people in a very different timezone. It can be a curse or a blessing and it all depends on the project / people.

Schedule wise, I do some regular evening hours (2 / week) to catchup - that can be a real problem sleep wise. If you finish your calls late in the evening, especially the ones where you are the one doing the talking and presenting things, it's very hard to go to sleep straight after that. You need to add at least 1h of winding down time.

As for motivation, from my experience, when I'm working on something I really like, I'm 10x more efficient that I would be in the office. When you start in the morning, you know that for a long period there will be nobody to interrupt you and you get a LOT more done.

The opposite is similar though - when I'm not motivated by a project, it's insanely hard to motivate myself. But maybe it's a sign that the project shouldn't be done in the first place.