Live data from Hacker News

Hard truths I learned when I got laid off from my SWE job

stevenbuccini.com

251–260 of 594 posts

Re: Hard truths I learned when I got laid off from my SWE job

#251
I was laid off in April 2020 as well, and while some of my experience matches the author's some of it was very different.

Being laid off was not a relief -- it was terrifying. All indications were that a severe recession was coming. Frankly, it was quite surprising to me that companies were hiring at all given the uncertainty. It was not obvious at the time that broad sectors of the economy could seamlessly move to 100% WFH. It was also my first experience in fully remote interviewing.

I am a software engineer over fifty. I also have three children two of whom were in college, and my wife works in a travel related industry which was very much affected by the pandemic.

Given those things I approached my job search aggressively and with a sense of urgency, and I made it out OK. I was out of work for about two months and accepted a role at flat comp.

Being laid off is profoundly lonely. I was part of a mass layoff (approximately 2/3 of my company was laid off.) So while I was not alone in that sense, we were all very much alone together. Where you had been a team, you were now five people looking for jobs, each with their own problems and constraints. My wife could not have been more supportive, and yet the process of interviewing and landing a job is one you have to do by yourself. One of the hardest things is to maintain an upbeat outlook, and yet it is so necessary because no one is going to hire a miserable sad sack.

On the other hand, I had no stigma whatsoever attached to the fact that I had been laid off. Part of that might have been that the size of the layoff was such that anyone with any glancing familiarity with the place I was at would know that 2/3 of the company were laid off.

One thing that I would emphasize would be maintain your professional network in good times and in bad. I got a number of good leads that way.

Re: Hard truths I learned when I got laid off from my SWE job

#252

Earlier quoted context omitted.

I've taken time off between jobs without taking on any meaningful projects, and I generally haven't found it to be an issue. When I tell recruiters I just wanted time off to relax, they're sometimes skeptical, but hiring managers more often than not either respond with some variety of "Oh yeah, I did that too and it was amazing" or "Oh man that sounds so great, I'm jealous." I do apply almost entirely to smaller star…

hiring managers more often than not either respond with some variety of "Oh yeah, I did that too and it was amazing" or "Oh man that sounds so great, I'm jealous." This only works if you get to even talk to a hiring manager. Most applications are filtered by automatic systems. Many of those will penalize or discard your application for gaps. The same AI bots we built when we were employed are now being used against u…

True, though I don't think it has anything to do with AI - the filtering mechanisms are much simpler than that.

That said, I like early-stage startups, so less of a problem with that kind of thing.

Re: Hard truths I learned when I got laid off from my SWE job

#253
I just got laid off and I went through a layoff in the early 2000s and it was brutal. Had to do contract work with tech I didn't like and now with the added pressure of having kids that I have to care for financially it's definitely more stressful.

One thing I'm doing different this time around is that I'm building a project that could be useful for some friends and might actually scratch an itch. It allows me to get back in the latest technologies and adds something to my portfolio.

Re: Hard truths I learned when I got laid off from my SWE job

#254

Earlier quoted context omitted.

Seeing that I work at the alphabetically sorted first “A” in FAANG, I don’t think it could be considered a “tier 3” company. When a recruiter from Amazon Retail reached out to me about an SDE position, I wasn’t interested in either relocating, working as a software developer at any large company or doing the prerequisite DS&A monkey dance. We kept talking and she suggested that I apply for a fully remote role consult…

That's a long story to hide the fact that by refusing to do LeetCode interviews you were not offered a software engineering position. You most likely are an SA, which is a position open even to business degree holders and is barely technical, no wonder you didn't have to LeetCode.

If you read his past post history he has had what you would call "technical" jobs before, even if you don't count this one.

Re: Hard truths I learned when I got laid off from my SWE job

#256
post #68

Being laid off can and will forever change your career risk tolerance. When I got laid off in 2008, I stayed at the next job probably 10 years longer than I should have because of effects of being laid off.

That's a good point, and I had a similar reaction. I got laid off from my first job out of college in late 2006. Unemployed for 3 months, found a role with a new company 2 hours away, moved, and stayed there over 12 years because I didn't want to take the risk of moving. That, and I let myself be too intimidated by the interview process.

I eventually got laid off from there and found a new job after a ~2 month stint of unemployment; stayed with my new company for about 18 months and then changed to my current job of my own volition to find something I was happier with rather than sitting around being miserable.

Re: Hard truths I learned when I got laid off from my SWE job

#257

Coincidentally(?), "Laid off tech workers quickly find new jobs" ( https://news.ycombinator.com/item?id=34161528 ) is also on the HN front page right now.

It very much depends on their specialty. Some niche position are available once a year or less, in my country, while regular developers are hired by the thousand every month.

Re: Hard truths I learned when I got laid off from my SWE job

#258
post #209

Earlier quoted context omitted.

> OP was unemployed a year. Time adds up, that's a lot of money. Luckily my government gives me a full year of unemployment benefits at 2/3rds of my salary besides my savings. Obviously, I don't wish to test my luck regardless, but not everywhere is as cutthroat as the US.

More accurately: your government takes your money and then, maybe, gives it back to you in the form of unemployment benefits and the like, minus significant processing fees. The alternative is to use the money the government doesn't take and save it for your future "unemployment benefit".

The government would give me more than I would be able to save myself in a year. Over multiple years, I would be able to save more efficiently than the government, true. That's assuming everything goes perfectly however, so I view it as a form of insurance: I make less in order to have less anxiety that I will not be able to provide for myself and my dependents if the overlords decide I am no longer worthy of my job. It's a tradeoff, but one that I will gladly make. As a social good, that money also goes into helping those that were not as lucky as me to be able to make good easy money. And perhaps one day I might be like them too, who knows?

Re: Hard truths I learned when I got laid off from my SWE job

#259

The lesson here is to be overemployed, do at least one interview process a quarter, and understand that companies don't give AF about you.

That is a big lesson I learned. I worked at a job for 8 years without looking elsewhere and when I got laid off I was really stuck because the market and interviewing circuit had completely changed.

Re: Hard truths I learned when I got laid off from my SWE job

#260

Earlier quoted context omitted.

Memorizing decks of leetcode problems improved your engineering skills?

Shockingly, sometimes Software Engineers are asked to write algorithms for their job.

And you would never plunk down a memorized verbatim fix in such a scenario.
Post reply on HN