Agree. I have a job and you can either be remote or onsite. I am well on the way to c-suite roles partially because I choose to be on-site, and of course the necessary hard work. We don't typically make someone COO or Director of Engineering if they're remote for many reasons.
Another reason to eschew remote is impact. Much easier to have impact and do real, meaningful work from onsite where one can convince people of things and drove companies in certain directions. Imagine Steve Jobs as a remote employee. Maybe this is cynical, but remote is great if all you want from life is to be well paid and code. For many, there's much more.
It depends. You describe working for a "remote allowed" company.
My advice for any engineers that want to do the remote work thing and still have career advancement is find a "remote only" company.
Everything you said is true for larger orgs who have physical presences. For small shops that have developed remote-only cultures most of those negatives are moot.
If I were ever looking for work again I would only entertain offers from remote-only companies unless I was getting desperate.
Another reason to eschew remote is impact. Much easier to have impact and do real, meaningful work from onsite where one can convince people of things and drove companies in certain directions. Imagine Steve Jobs as a remote employee. Maybe this is cynical, but remote is great if all you want from life is to be well paid and code. For many, there's much more.