271
Meta updates RTO policy with stricter mandate, saying workers may lose their jobs if they don't show up 3 days a week
(www.businessinsider.com)
This is a most excellent place for technology news and articles.
This is the best summary I could come up with:
"As with other company policies, repeated violations may result in disciplinary action, up to and including a performance rating drop and, ultimately, termination if not addressed."
Meta first informed employees of its RTO efforts in June, saying that beginning after the Labor Day holiday, people who were hired to work in an office should return for at least part of the week.
In a March memo announcing a layoff of 10,000 employees, he wrote that a company analysis found that "engineers earlier in their career perform better on average when they work in-person with teammates at least three days a week."
Being fully remote means Meta will not maintain desk space for such workers, who should not come to an office "more than 4 days every 2 months," Goler's memo said,
From: Lori GolerDistributed work updatesTL;DR:• We shared in June that beginning September 5, people assigned to an office will need to spend at least 3 days per week in person to foster healthy relationships and strong collaboration.• Managers will hold their teams accountable to the In-Person Time Policy on a monthly basis.
To help teams build predictable collaboration practices, we're asking remote workers not to visit the office more than 4 days every 2 months- unless there's a clear business reason (team onsite, required in- person meetings) or to attend Meta-sponsored events like Company All Hands, Metamate Meetups, or Hackathons.• Managers will review this monthly, subject to local law and works council requirements, and remote workers who consistently exceed the threshold will be required to transfer to an office and meet the minimum 3 days/week in-person requirement.Remote applications:• We're moving to a monthly review cycle for remote work applications by org leaders so they can fully assess and understand the impact of these requests on their organizations and sites as they implement their org-specific location strategy.
The original article contains 1,469 words, the summary contains 307 words. Saved 79%. I'm a bot and I'm open source!