In my experience, remote engineers are often some of the most productive engineers at an organization. When any engineer can demonstrate a strong track record

In my experience, remote engineers are often some of the most productive engineers at an organization. When any engineer can demonstrate a strong track record of shipping, any idea of "laziness" goes away pretty quickly. I think one of the reasons why "laziness" comes up is because remote engineers aren't physically in the office to be shoulder tapped for questions (though so many questions now go in Slack anyway). A somewhat opposite problem I've seen is that when people work remote, they kind of "forget to stop" and end up working way more than a standard workweek. A start to solving both of these issues when working remote is to establish a clear schedule of your working hours and your "availability for questions" hours. I.e., make it clear 1) when you're working and when you're not 2) when you're available for answering questions vs reserving your time for working in flow. Can use something like a Slack status to remind colleagues.