I see how this could be a problem. Luckily where I work, everyone is a remote. And I think this is something to watch out for, make sure remote working is embedded in company culture before accepting the role.
The lesson for me there was to assume that not everyone has the mission's interest at heart.
My problem was that for me getting on base was a 2 hour commute, and I had 90% of the gear I needed to do my work rihgt at home -- it got more done to work from home and only show up to deliver prototypes for testing, or use the "big boy" machine tools.
This is also why many startups insist on people not working remotely. Startups frequently need to make decisions on very low information, such that the only conceivable reason you'd have for following through on the decision is trust.
http://careers.stackoverflow.com http://www.remoteworking.io https://weworkremotely.com