3 ms·
This question depends heavily on whether the whole company is remote or not. If it's not a "remote first" company, then you need to be prepared to be left out
by rubicon33 7y ago
This question depends heavily on whether the whole company is remote or not.
If it's not a "remote first" company, then you need to be prepared to be left out of a lot of conversations. Your opportunity to grow beyond engineering is extremely limited. You'll likely never be promoted past engineer. IMO this is the biggest issue you have to face as a remote engineer, the rest is in the noise.
If it IS a "remote first" company, then all the other issues presented are worth focussing on.
- johnstorey 7y agoThis is the key issue. If a company is built to be remote -- over documentation; excessive communication; no two people are local to each other; a culture around the online communication tools (to replicate the watercooler); and most importantly 3 - 4 overlap of all teams so you know when meetings can be scheduled. Have that, and you can work extremely well. If you are "distributed" in the sense there is a HQ full of managers, and a bunch of other offices because that's where people could be found with the right skill set, no set overlap hours, and HQ still has the practices on of non-distributed culture (conversations about important topics happen face to face for instance). Well, then, you have to accept you will be out of the loop and work very hard to be remembered and involved.