Earlier quoted context omitted.
Nope, I need that time to grind leetcode.
This is exactly what happened to me when I quit. “Now I’ll have time for my projects!!” Instead it’s been “Grokking Algorithms”, “The Competitive Programmers Handbook”, Alex Xu’s “System Design”, and enough leetcode that I’m actually doing more than I did at work. What sucks is that there are still lots of medium problems I cannot do. Hards are right out. Dunno what I’ll do.
Hard truths I learned when I got laid off from my SWE job
181–190 of 594 posts
Re: Hard truths I learned when I got laid off from my SWE job
#182Earlier quoted context omitted.
The intent is to learn and produce and be an able to talk about rather than try to make money.
So if you aren’t “learning and producing” at your day job, what are you doing 40 hours a week?
Re: Hard truths I learned when I got laid off from my SWE job
#1831) You should not be broke if you’ve worked a few years as a software engineer. You’ve been earning good money and it is important to save during the good times so you’re prepared for the bad. I’m not saying this necessarily applies to OP, but it’s generally good advice to keep some money lying around for a rainy day.
2) If you feel secure financially and get laid off, it’s a great time to do something time consuming. I have a toddler, so it’s been a lot of fun to hang out and bond with her. Friends have made video games or picked up a new hobby. Most people I know who got laid off who felt secure financially love it.
3) Your network is your best asset. After the layoff, multiple old contacts reached out with job offers. I was very grateful for these, but declined them for the reasons above.
TLDR: being laid off can be a blessing if you’re financially prepared.
Re: Hard truths I learned when I got laid off from my SWE job
#184Re: Hard truths I learned when I got laid off from my SWE job
#185Re: Hard truths I learned when I got laid off from my SWE job
#186Earlier quoted context omitted.
This is exactly what happened to me when I quit. “Now I’ll have time for my projects!!” Instead it’s been “Grokking Algorithms”, “The Competitive Programmers Handbook”, Alex Xu’s “System Design”, and enough leetcode that I’m actually doing more than I did at work. What sucks is that there are still lots of medium problems I cannot do. Hards are right out. Dunno what I’ll do.
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…
Part of it is that I’m pivoting from systems software (Linux kernel) to webstuff. I have zero network here, if I wanted to do systems again I’d have an easier time of it.
Re: Hard truths I learned when I got laid off from my SWE job
#187My 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…
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?
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. This is the only thing we cared about at Big Tech Co.
Re: Hard truths I learned when I got laid off from my SWE job
#188> Very few of us are going to bat 1.000 during our careers, especially with the industry reshaping itself under our feet. This feels like it may be an iceberg. Could you expand more on what "reshaping" you're seeing? Are you referring to the mass layoffs specifically or is there some broader context to this comment?
Re: Hard truths I learned when I got laid off from my SWE job
#189Earlier 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.
I'd be suspicious if they didn't ask me to do any coding, but I'd be just as suspicious if the coding they asked me to do was leetcode.
Re: Hard truths I learned when I got laid off from my SWE job
#190Getting laid off is a great introduction into class solidarity with your fellow workers. We have literally nothing in common with the capitalists at the top. You are closer to homelessness than you are to being a billionaire.