Meta threatens to fire workers for return-to-office infractions in leaked memo
sfgate.com
sfgate.com
Tracking the people who write the code to track people seems very Meta.
If anyone gets fired as a result of this, or suffers performance penalties for not attending team events in fear if this, that would be a slam dunk constructive dismissal case no? This seems so absurd that any employment professional would draft and approve this.
a) It's just one of many ways that employees can negotiate more favourable contract terms. They can also negotiate more annual leave, fewer hours, smaller notice periods etc... and with proper management it shouldn't cause issues.
b) People who work regularly in the office have perks like their own permanent desk and PC.
c) The cause of this unfavourable situation is the 3 day / week policy put in place by senior management in the first place. Imagine cutting the carpark in half to save costs, and then removing the bike racks as well so that the car drivers don't feel as hard done by. It comes across as spiteful.
As for the "added work of managing", I'm not sure I follow. I previously managed a couple of people, one of whom came in 2-3x per week and the other was almost completely remote but came in occasionally. Once things are set up so that meetings or calls can be done remotely or in-person on the fly, this isn't much of an obstacle. Perhaps it becomes more of an obstacle with larger teams, but that isn't something I hear from other managers in my company. It is tricky to run meetings with half the people in the room and half remote - but this isn't solved by forcing remote workers to stay remote (if anything it makes it worse).
And this is probably why Meta is instituting this policy.
They are changing the default back to what it was (working in office which they can easily defend was the expectation when most employees outside of remote workers were hired), so instead of an employee being able to negotiate a benefit in return for coming to the office, the employee needs to give up benefits in a negotiation to work remotely.
A company I worked for with two Bay Area locations wanted to use badge data to show that certain employees were not based in SF. They were using badge data to support this, and then they could reduce their sf tax base.
For remote in general I’m sure this also applies, even more at the state level. Say you’re in Nevada but coming to the office 4 times a week in California. California will come after its tax share, without any question. It’s likely there a headache to figure out for both you and your company.
(Sarcasm, of course.)
seems like he just says whatever is best for the stock price at any given time.
https://www.theguardian.com/technology/2022/nov/15/major-inv...
Seems like some people understood it as "everyone should be able to be fully remote in 2023". As far as I can see; he still has 6 more years ahead of him to allow some of his employees to be fully remote (and half that won't be able to).
[1] https://www.cnbc.com/2020/05/21/zuckerberg-50percent-of-face...
I'm currently interviewing with Meta. If I get the job, I'll have a long commute on a train with limited runs each day.
Being able to use train time for work could be the difference between a sane and untenable lifestyle.
There are also plenty of other companies that offer fully remote arrangements, many of whom haven't sunk untold millions of dollars into commercial real estate and need to be able to justify their investment.
Please don't presume that you have enough information to rebuke me.
Haven't made that mistake in awhile...
> It’s not complicated.
You didn't know what tradeoffs I have to consider, so I doubt you can know if the decision is complicated or not.
In actuality, my decision involves guessing at the likelihood of various outcomes, and how they relate to competing ideological goals.
> Telling yourself so is only making excuses for the company.
You guessed (wrongly) about my thought process. Furthermore, I don't see why you had any confidence to make that guess, let alone chastising me based on that guess.
That said, while I absolutely appreciate the need to provide for your family, if you can get a job offer from Meta, you could get a job offer at countless other companies that aren't directly contributing to the downfall of civilization.
Oops, sorry :)
> if you can get a job offer from Meta, you could get a job offer at countless other companies that aren't directly contributing to the downfall of civilization.
I've been unemployed for 5 months now, and looking hard.
You may be trivially correct, if I end up not getting an offer from Meta. ;)
Now, as you might expect, I don't seek the downfall of civilization. But I can't think of a single employer whose work is entirely safe from that accusation, so it's a question of tradeoffs and guesses regardless.
I wonder how that breaks down. People working 5 and others working 0? Or most working 2-3. My firm's average is about 1.5, and we have a new mandatory, but not enforced, 3 day a week rule.
I checked and it's 4.3 miles by car, probably more like 3 or 3.5 miles as the crow flies, making this flight a violation of Federal law.
Also, it's definitely possible to get an airspace waiver to fly within 5 miles of an airport, so that's another possibility of doing it legally. Those airspace authorizations for low level flights aren't particularly difficult though get, as I understand it (I'm a pilot, but not a drone pilot, though I know a few)
Strongly suggests a drone - No other metadata on the image/getty images however.
Why do you think they'd be prohibited by federal law?
This means that around 25% of workers are still fully remote. Companies (and us) have to realize that remote is not suitable for everyone and for all positions. I’m one of the lucky few working fully remote in my company, but I think that a good “healthy” distribution for software related companies would be: 20-30% on site, 20-30% remote and the rest 40-60% hybrid.
Everything that needs to be done is possible on laptops nowadays, and the big server machine that used to hum in the dedicated "server room/closet" is now "in the cloud" instead). I can contact a fellow team member faster now than walking over to their desk, and I can also see immediately whether they are busy or otherwise not available.