Live data from Hacker News

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

stevenbuccini.com

221–230 of 594 posts

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

#221

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 don’t resort to memorized algorithms when that happens. You research.

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

#222
post #187
post #143

Earlier quoted context omitted.

I have a decent amount of savings and a side project I want to do which could potentially earn money. Are you saying if I quit my job and do this for a year or so, it'll fill a hole in my resume and not affect future interviews?

Everytime I read these comments I feel like I work in another industry. Who cares about the gaps in your resume? Truly, have recruiters commented in anything but passing? Your interviewers? I've hired candidates with large gaps in their resume and their reasoning for the most part was I wanted time off or I went traveling or N other things that have nothing to do with work. We. Did. Not. Care. Pass the interview. Thi…

I have the same feeling, unless your response to the question about the gap is "yea I was on the run from the law for a while because I killed some people while robbing a bank, then I had to spend some time in prison but I had a really good lawyer" I dont know how much impact it really has

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

#223
post #74

My advice: Have one or more side projects going all the time. If you get laid off, immediately start doing a startup, open-source project, or volunteering full time. A year of unemployment? Lonely, depressing, and not good on a resume. A year of launching an unsuccessful venture? Running coding classes for the underserved? Focusing full-time on contributing to pytorch? That's a lot better, both at the time and in ret…

This is terrible, possibly toxic advice. Software devs are people too. They burn out, take time off to travel, reflect, take care of family, or just down on their luck being unemployed. The only advice I'd consider paramount is to take stock of themselves financially and mentally, to assure themselves that they can take on the chaos and uncertainty that follows. Honestly, if someone showed up with a gap in their resu…

> The open source contribution/project would have to have a sufficiently high bar for it to be even considered. Else, I'd just assume they were being less than honest. I'd rather someone tell me they spent a year working on themselves, playing video games, hiking, etc.

You think working on a passion project and trying out a startup is toxic and then you come out with this pessimistic bucket crab viewpoint? You’d be doing people a favour not hiring them, I’d feel bad for anyone working for you.

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

#224
post #74

My advice: Have one or more side projects going all the time. If you get laid off, immediately start doing a startup, open-source project, or volunteering full time. A year of unemployment? Lonely, depressing, and not good on a resume. A year of launching an unsuccessful venture? Running coding classes for the underserved? Focusing full-time on contributing to pytorch? That's a lot better, both at the time and in ret…

The only value of having a knee-jerk 'startup' going is to not appear unemployed.

If it's for the optics, then I'd just move the dates of my previous side-projects around and call it a faux-startup. It's not lying. It is work you have previously done as a side-project/school-project at some point. But saying you did it in the last few months helps give the appearance of being continuously employed and not being rusty.

SWE interviewing IS a fulltime job. When unemployed, it is especially important to use that time to: [1] Reflect on what job you want for your future & [2] Work on achieving that job. Together, they will take up ALL your time. Tech recruitment wants to have their cake and eat it too. You are expected to have an excellent primary project and have time for the months it takes to Leetcode. It's unrealistic and leads to a period of overwork for candidates.

Jugaad is never optimal. But sometimes, Jugaad is necessary.

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

#225
I liked this quote:

> “When faced with two choices, flip a coin. When it’s in the air, you’ll know which side you’re hoping for.” —Former gangster Arnold “The Brain” Rothstien

Basically, you'll know which direction to take, after taking your first step (or you'll learn to fly, after being pushed from the nest).

In my case, this was exactly that. I got laid off from my previous job (after almost 27 years). It was entirely expected (for years), so I'd had a lot of time to prepare.

When I learned Hard Truth #9 (If you are over 40, it will be rough. If you are over 50, prepare to be humiliated -and not get a job), I was fairly panicky, at first, then, I realized that I had plenty of savings to retire early, and I already knew of some nonprofits that could use my expertise, so I didn't need to stop working.

I really wanted to retire -not to play golf, but to work harder than I ever have, in my life, doing stuff that is appreciated, effective, and untainted by bad management and "fuck it -let's ship."

So I was forced into it.

A number of companies didn't get my work, but I seriously doubt they miss me. They certainly didn't seem as if they would, during the recruiting process, and I probably would have been laid off again, tout suite.

It's actually been an amazing five years.

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

#226
post #107

Earlier quoted context omitted.

>"so if you've been looking for X months, surely there's something wrong with you - and anyway, we've already signed a contract with someone else in the 5 days since we last spoke." I think letting them know you are currently unemployed is a mistake. Frankly your current state of affairs is not their business. You can always tell them that you are ok but looking for a better job. Very simple and understandable. Yes i…

There's really no way to hide you're currently unemployed, or at least not employed in the tech field, unless you make up an entire fantasy world. Not only will you have to put the lie into your resume, and maybe provide fake references, but you'll also get tons of interview questions about skills and projects and challenges from your current job.

You're bang on - I was asked in the very first call for two references.

Also in this case I really don't mind disclosing - I was laid off because my position was made redundant entirely.

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

#227
Gosh it's so hard these days. So much of the past 10 years was easy speculation and I have certainly let that go to my head. Even as a fresh grad, I had people beating down my door. Suddenly, it's all quiet. I'm reduced to working at the grocery store- a humbling experience for sure.

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

#228

Earlier quoted context omitted.

This is a live-to-work attitude. Have some other hobbies and goals, and a year of unemployment will be neither lonely nor depressing. Personally I've gone farther in the work-to-live direction, with an easygoing, "boring" (still fulfilling enough to see some javascript doodad come to life, but not world changing) WFH job I perform well in that supports my homesteading and other hobbies.

This late in my career, I've found 5 of my 7 SIEMs are gone, and the last one is on life support. The one I'm managing now will not be around by the time I retire. You start to see the patterns and futility and cycles and think 'maybe my career is not making things better, it's keeping the mortgage paid?' That and while I'm I can get rehired past 50...do I really want to do that dance again?

SIEM?

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

#229
post #139

Earlier quoted context omitted.

What situation are people in that they have to result to this? Is this an issue with getting laid off and trying to find a FAANG job? I was laid off from one consulting company back in 2018 or so and had a new gig with more pay a week or so later. No leetcode or dev tests, just talking with people in phone interviews. It was a company I had previously done contract work for, and they called me, but nothing at the FAA…

In very large part what your interviews look like depends heavily on when and where you're searching, what type of job you want and what your background is. It's hard to overstate this. 2018 might as well be an entirely different universe. That said I would be a little suspicious as a mid/senior-level developer if I got hired at a place that didn't ask me to do any coding for them at all beforehand.

20+ years in. Don't be afraid those positions can lead to a greenfield development project or come from departments that don't have someone to vet your coding preferences. Usually these positions offer more technical freedom. A company who spends more time vetting code will generally be a place with less freedom and more micromanagement.

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

#230

Stepping back for a moment from the content, I think it is worth noting what an exceptionally well-written essay this is. Being able to write well is a super power for engineers. It is a reflection of the lucidity and clarity of one's mind, and the ability to understand the needs of the reader. Writing well is an exceptionally useful and powerful skill that can be improved with consistent practice. I would be tempted…

He is a good writer and clearly a thoughtful individual, which further reinforces truth #6 (honesty can hurt you). I subconsciously approached the article with a bit of negative bias around the fact he had been laid off. His writing has more clarity than many successful CEOs though so who knows.

How charitable of you for the poor laid off person.
Post reply on HN