Re:Thoughts on getting laid off after nine years at Twilio
by paradox460 on Tuesday February 14, 2023 @05:04PM
(#34796820)
This happened to me. Was the sole developer on a certain service. Other engineers would use the service at the company, but no one else really wanted to get into it and work on it.
Was working on fixing an issue one morning, got roped into a meeting, and escorted from the building. Next week, saw an email from a coworker asking how to do something with the service. Told him, politely (don't burn bridges) that I didn't work there anymore and wasn't interested in helping that company without payment. Yeah, it might be thought of that I hung him out to dry, but that wasn't my intent. I just won't work for free, particularly when I was booted without much chance to get my affairs sorted
Re:Thoughts on getting laid off after nine years at Twilio
by fzeroracer on Tuesday February 14, 2023 @05:08PM
(#34796867)
This happens all the time and the downstream effects of hazardous layoffs are often not seen or felt until Jim the resident container expert isn't around to restart the critical containers that all of your other services need, so you start losing a lot of money and time as John the replacement scrambles to figure out how the system works and what to do.
Or they get hired back as a contractor for 3x-4x the hourly wage as you mentioned.
The company terminates access effective immediately (maybe with gardening leave) for security reasons.
The immediate loss of institutional knowledge causes fucking havoc across the board.
So some people will be taken back on as contractors for a while at extremely expensive rates.
This also means there's a weird incentive to start hoarding knowledge if you suspect layoffs are coming down the pipe...