3 ms·
> So if you work for AWS for example out of an office in California, they might force you to relocate to Seattle. Throwaway because who knows what they are mon
by throwaway63492 3y ago
> So if you work for AWS for example out of an office in California, they might force you to relocate to Seattle.
Throwaway because who knows what they are monitoring.
We had an all-hands this week and the VP was pretty clear that they will force people to relocate at some point, saying that it made no sense for some people to be in New York if the rest of their team was in Seattle because it negatively impacted collaboration and "working on hard technical problems".
So I don't know what their timeline is, but at this point they are not really pretending that this will be between you and your manager/director. They will absolutely push this as a top-down policy.
- bugglebeetle 3y ago> negatively impacted collaboration and "working on hard technical problems". Meanwhile, most of their business runs on Linux…
- hdjjhhvvhga 3y agoI wonder why this argument is not publicized more.
- flashgordon 3y agoDamn I dont know what to say to this. Should I pissed off on all this backtracking and BS arguments for RTO? Or should I "pleasantly" surprised that instead of playing the "talk to your manager/hr" ping pong game leadership (remember Robert California episode in the Office with Andy stuck in between RC and his Wife for an office job??) is actually owning up to their BS policies?
- AwaAwa 3y agoSounds very much like a method to reduce head count without saying so.
- jwestbury 3y agoPretty crazy, because AWS has had fully-remote employees for a decade plus. I worked closely with a team who had two remote employees, one in NYC and one in CA, despite the rest of the team being in-office in Seattle. And you know what? They got along fine. The guy in NYC got promoted to L6 while I was there, so I can only assume they were happy with his work.