I've worked remotely for years now (still less than 10). It's OK. It took a while to get used to. I am not a full-time SWE, so it's better when I am coding o

I've worked remotely for years now (still less than 10). It's OK. It took a while to get used to. I am not a full-time SWE, so it's better when I am coding on things. The quiet and lack of distraction is important. Even then, I turn on some music and put on headphones. What was very useful to me when I was working in an office was the hallway conversations, and making all the random connections. You would find opportunities to learn and get involved with things, and expand your sphere of influence. There's pros and cons. I'm not sure leadership understands the utility of quiet and isolation for coders. As well, there's the concern about "How do we know they're working" - which is a very old school way of thinking. That old school way of thinking also goes like, "We pay you to be here 8 hours a day, so you better be here and not screwing around". But that's not really what you're being paid for in a SWE position. If you aren't meeting your KPI's (hitting deadlines, pushing good code, spreading knowledge, etc.) you'll get fired. Because you're getting paid to perform well, not just sit there working - you're paid to work well. So - if you hire people who can hit every KPI and work 20 hours a week, who cares? You're not paying someone hourly anyways. You're paying a salaried worker.