Thats it. HR knows who is working on visa. Inform them of the situation, give them 3 months, away all their accesses and let them spend the 3 months to look for a new job. Meta makes a bazillion USD pr yeah. Even if they had to pay 1000 works on visa for 3 months it wont make a dent in their profits.
For the employee that just relocated, on the other hand, this makes all the difference in the world.
Corporate greed is disgusting when its put above Human decency like this.
This is a HUGE stress, and also puts you at a disadvantage against your prospect employers.
IMHO, there should be legislation for covering these cases. I.e. when you sponsor a Visa as an employer, it should be mandatory to pay the employee for a minimum of 12-24 months. If you want to lay them off, that's fine, but legally they would still be considered employed and paid in full until that grace period expires.
edit: To be very fair, though, there is an implicit warning in the paperwork and interview for every US work visa for exactly this kind of situation. It's not like they're playing some gotcha game. They don't come right out and say it, but, it's also not exactly hidden between the lines or in small print.
I am NOT 100% sure about this, but to the best of my knowledge, this is not the case in Canada. Work Permits are issues for the duration of the expected work and are usually at least one year long. If you lose your job, you can still remain in Canada until the expiry date of your work permit. You cannot simply start working elsewhere, but if you find a new job, your new employer can start the process of applying for a work permit for you while you are waiting in Canada. So this developer should be good to stay for another 11 to 12 months, if not even longer, while searching for a new job.
I wish there was a way to make this happen but I keep hearing software workers don't need unions because we already make so much money and the better ones have nothing to worry about.
I support "keeping them on the books" for purposes of visa and health insurance, for example, but there are legitimate security reasons to have people cut off quickly when they've been laid off or fired.
I suppose if you had really, really, really good meals provided, it would be reasonable to argue about whether that was a benefit or there for people in the office.
I think its b/c getting fired is bad ofc, but not bad like in the US. I mean we have universal basic income, free healthcare etc. So I just don't think people feel pressured in a way that drives them to exploit access even after a notice, or get mad at the company in the same way. I'm just speculating. Again, there are companies and positions in companies where its a no brainer that access is revoked for security reasons.
Most companies stop having "legitimate security reasons" when the alternative is to pay people for doing nothing. Turns out the fact that actual sabotage and theft of trade secrets is illegal (and often represents a breach of the employment contract, which can incur hefty fines) is a sufficient deterrent for most industries.
People on immigration visas were not given traditional severances. They were simply kept on the books for that period of time without having any access to any resources and/or being expected to do any work.
I’m not entirely sure what happened if they started a job before the period ended. Whether they got the rest of the money as severance or forfeited it but I doubt they really cared.
The solution is obvious: Stop clinging to this backward butts-in-seats culture that has people move to a new location even if the job they're going to do can easily be done from anywhere in the world.
Good/best practices are rarely followed, maybe 20% of practitioners actually follow them in any field.
So that means that on a daily basis, about 80% of people need to work in those "broken" environments.
Having people relocate to another country, because your organization isn't able to fix its own internal problems, means you're simply outsourcing your own costs to your employees.
And except for a select few, most people can't bend reality.
Reality being as it is, is no argument for not trying to be better or improve a situation:
Contrary to the Shaw quote above I’d say that simply resigning oneself to reality as it is and therefore precluding better approaches is the unreasonable choice.
There are all sorts of tools that allow for an asynchronous human connection, e.g., asynchronous video recordings.
Working mostly asynchronously also doesn’t mean you can’t have the occasional synchronous online meeting (including coffee) as well.
Is there any proof that's truly the case? Or isn't that yet another one of those commonly accepted, yet rarely questioned truisms when it comes to - an often dysfunctional - work culture?
Not the OP but the proof is my own experience in both in-office and remote settings. And everyone is going to go by their own life experiences. If enough people think that remote setting sucks and that junior engineers, along with many other roles, are more effective in person, then the burden of proof is on you to demonstrate that that's not the case.
Therefore, someone claiming it doesn't work, is effectively saying it doesn't work for their company, which in turn gives rise to questions as to why that's the case:
Is their company and its work truly that unique and special that it can only effectively be done synchronously and in person?
Or is it rather that the company in question itself has an underlying organizational problem?
Yes. My company is also in that category. We employ a lot of junior engineers too. >90% of them say they want some in-person interaction because it is hard to ramp up effectively on a complex codebase and a different culture.
> Therefore, someone claiming it doesn't work, is effectively saying it doesn't work for their company, which in turn gives rise to questions as to why that's the case
Because we are all humans and in absence of an in-person presence, we are not able to form trusting deep relationships.
> Is their company and its work truly that unique and special that it can only effectively be done synchronously and in person?
for example we are using gather.town. much better than Google Meet (full HD screen sharing, ad-hoc breakout sessions, blablabla, free under team size of 25, if I remember correctly)
I keep hearing such arguments but those typically aren't backed up by any data or reason as to why that's the case.
That said, poster child remote-first companies such as Basecamp, GitLab, or Zapier have their people gather a few times throughout the year, too, to allow them to get to know each other better. That's not a contradiction at all and something entirely different than mandating people move to specific location to work there the entire time.
I'd say burden of proof is on you to provide any data that remote work is equally good.
I have given remote-working a shot for three years - first ~1.5 were mandatory during COVID and last ~1.5 were during normal times. My company has gone all in on remote work and has tried to make it work. It just doesn't work and everyone is openly admitting its flaws. To name a few: a lack of trust, very shallow relationships, struggles for junior and new team members to ramp up, a lack of engagement etc.
Based on my personal experience and that of my social and professional circles, >80% people seem to prefer a hybrid model where they work 2-3 days in office and 2-3 days at home. Of course, in-office days have to be mandated for the entire team to be effective.
Much better than days of notice.
The solutions seem pretty simple to me, contractually required notice periods. My last job I had either a two or three month notice period, I can't quite remember. For those coming over on visas, you could have an initial notice period that's longer.
> I think maybe the best thing to do here is just to give good severance packages?
Missing in this for the case of visas is about how long you're allowed to stay in the country without a job. A notice period should mean you're still employed, so that adds to any grace period around a visa.
> You'd inevitably just end up protecting certain types of crappy situations (recently located) over other types of crappy situations (family member just died).
Maybe, yeah. But protecting some people rather than none is an improvement, particularly when some cases are extremely easy to identify and may make a much larger proportion of people affected significantly.
But that’s socialism! Soon after, we’ll be eating our own dogs, who wants that?
/s
> Maybe I'm missing something here.
Maybe look at how it's done in pretty much every other developed country in the world? Employees have notice periods and extra safety margins around visas.
(Of course not in USA)
More importantly, the average de-facto "standard" in many contracts is longer.
Additionally, many companies go beyond the contract requirements.
I think for a few months the company should subsidize renting a place, so new hires who move are not forced to liquidate everything back home. (Relocation packages are a thing after all.)
Large layoffs in large orgs are generally done at a team level rather than an individual level. So presumably this individual's entire team no longer exists.
So out of respect for them relocating do you then try to reposition them in the company somehow?
And what about all the people who didn't relocate but may have recently left stable job for an opportunity at Meta? Do they not matter or should they also be repositioned out of respect? And what about those who have personal reasons that make the layoff extra difficult? For example, those who might have just had a new born or who have family members in hospital? Do their personal situations not also matter?
And for how long would these individuals be safe if you do make an exception? Do you keep them for 3 months just to be nice then proceed with the layoff anyway? I'm not sure that's much better...
I think maybe the best thing to do here is just to give good severance packages?
I don't think I'm being heartless. I'm sat here thinking both, "man this is awful" while also having no idea what the right answer is. You can argue layoffs suck more for certain people and those people should be protected, but for a larger org needing to do mass-layoffs it seems almost impossible to make those kinds of assessments on an individual level in a way that is fair. You'd inevitably just end up protecting certain types of crappy situations (recently located) over other types of crappy situations (family member just died).
Just thinking out loud... Maybe I'm missing something here.