> slowed its hiring amid rumors of potential layoffs
From a Silicon Valley veteran: if you work there and read this, and you don't already have your resume circulating, it's too late. You want to be out there before all the other Meta employees.
From a Silicon Valley veteran: if you work there and read this, and you don't already have your resume circulating, it's too late. You want to be out there before all the other Meta employees.
This may not have been a problem in 2018, but it's definitely a problem in today's current environment with large amounts of bay area companies slowing their hiring.
If you look for a job before all this, you're in a much better position at least.
I wasn't around during the dot com era, but there were stories of devs ending up taking any job (programming or not) to make ends meet.
The word "facing" is present tense, which is not the appropriate context for this scenario. Everyone will have trouble if Meta fires a bunch of engineers. People from Meta may have a little less trouble, and some companies will even open up new reqs to absorb some for cheaper. But there are a limited number of open positions out there. No real imagination or speculation is required here, since this has all happened many times before.
Unfortunately these times can be a bit rough to navigate. It can be tempting to cling to one's current position rather than move to a new company & be first on the chopping block
By the time layoffs or a mass exodus actually happen, you're competing with 100s of other good devs for the best jobs (not that you won't find some job).