Boris Cherny's Blog

Learning to work (very) remotely | Boris Cherny’s Blog

Learning to work (very) remotely

December 10, 2023

For the last year and a half, I have been working at Instagram in Japan. It’s a bit of an unusual setup: I live and work remotely from Nara, Japan, in a timezone that few other Meta engineers work in (most of Instagram and Meta are spread across the US and Europe).

I am fortunate to have the opportunity to have a setup like this. How I ended up here is a long story, which I will save for another post. For this post, I’d like to talk about what I have learned about effectively contributing to an engineering organization when you are isolated from your coworkers physically, temporally, and organizationally.

Learning to work again

Before moving to Japan, I served as the tech lead for Facebook Groups. That meant organizing meetings, building slide decks and spreadsheets, writing scoping documents, responding quickly to chat messages and emails to keep teams unblocked… You know what I wasn’t doing a lot of? Coding.

After moving to Japan, with so little timezone overlap (9am my time is 4pm in San Francisco, 7pm in New York) I suddenly found myself with nearly the whole day free. My coworkers went offline a couple hours after my day started, until London woke up for the last hour of my working day. That meant nearly zero meetings and few synchronous chats.

Due to the incompatible timezones, I started attending group meetings less and less. At the same time, my coworkers naturally took me out of the critical paths of important projects. If anything was time-sensitive, I was no longer a good person to take care of it. I wouldn’t be included in chats and email threads anymore. My directors wouldn’t ask me to put together quick planning docs after exec reviews, nor would I be included in those reviews in the first place. This stung, at first – I was used to being included in meetings, and learning about new information before others did. These are the things that made me feel important! I didn’t want to give them up. But I had no choice.

At first I struggled to figure out how to spend my new-found free time, and how to feel good about my contributions to Instagram. I experimented with a few ideas: hacking on new product ideas with the other engineers in Japan, mentoring engineers in our Singapore office (larger than the one in Tokyo), fixing tech debt that others left behind.

It turned out that most of this work wasn’t easy to do. It was hard to effectively work on product while disconnected from the bulk of our US-based product organization; and it was hard to be a good mentor while having little context on what was going on in the Singapore office.

However, I did find that writing code again was rewarding. In my first two weeks in Japan, I landed more code than I had in the previous year in Menlo Park. I’m an engineer, and this made me happy – I missed coding! While hacking on a few product ideas (Instagram Maps and QR Codes) and fixing tech debt around our Python codebase, I kept a running list of opportunities I found along the way: abstractions that were repeatedly slowing down engineers and causing reliability issues, small improvements we could make to the type safety of our libraries, new infrastructure that we could build and ways we could make existing infrastructure better.

Leaning in

I started to shift the kinds of things I worked on, to focus more on simplifying our codebase, improving our infrastructure, and making our engineers more productive. I had done infra and DevX work in the past (some of it open source), but it had always been limited to 20% time projects. It was never my main gig. I considered myself a product engineer, but found myself sliding deeper into the world of infrastructure and DevX.

This shift was not something I did intentionally. Because my day no longer filled up with meetings and obligations that other people put on my plate, coding and fixing the issues I found while coding gradually took up more and more of my time, until six months into being in Japan I realized that it had become my main work. I felt happy about the work I was doing, and satisfied to write code again. I started to gain a reputation as an engineer that knows the codebase and has good technical opinions, despite having been at Instagram a relatively short time, due to how much code I was churning out and the pain points I was fixing for other engineers. (By this point, I was in the top 1% of engineers at Instagram by code output.)

Reflecting back on this a year later, I realize I was doing the work that other engineers should have been doing, but often couldn’t due to the realities of being in an organization that demands more of your time and attention as you grow more senior. Famously, at Meta even senior engineers are expected to code (we don’t have many architect types), but their level of code output is often not the same as more junior engineers. I had essentially...