Live data from Hacker News

Tech employment now significantly worse than the 2008 or 2020 recessions

twitter.com

531–540 of 720 posts

Re: Tech employment now significantly worse than the 2008 or 2020 recessions

#531
post #502

Earlier quoted context omitted.

They're incorrect, and my reply to a sibling covers why in detail. But to reword it: if you think the reason 0 to 1 work is typically a duct-taped mess is because of a lack of experience or understanding from greenfield devs, you'll probably fail at 0 to 1 work yourself. Not that a noob developer great at selling has never landed 0 to 1 work, crapped out a half working mess and left with a newly padded resume... but…

You must be “that person” who joins a team, creates IMPACT!!!, reaps the review-time award, and fucks off to some other new team to do it all again before any of the difficult maintenance issues arise. I've spent far too much time cleaning up after people like that to ever tolerate it again.

"Build one to throw away" comes to mind.

You'll figure out what you should have built after it's been used in prod for a while. Possibly years.

Re: Tech employment now significantly worse than the 2008 or 2020 recessions

#532
post #38

Earlier quoted context omitted.

I don’t believe this is true. There are plenty of roles that are happy to hire remotely. Sure, there is an in person requirement for many job listings but Ive found EMs/companies to be very flexible if they need to hire talent. For people that can’t/dont want to move to the “hubs”, just know that there is absolutely still a career path. I will say though that you need to have above average communication skills and pr…

There absolutely are remote first roles in the US, but the competition is also extremely intense. The median SWE and HNer wouldn't make the cut. It also requires a level of maturity, clear thinking, self-starterness, and independence that is hard to come by without a proven track record and experience. My advice is for the median/average SWE and HNer, not for the truly exceptional. Spending a 7-10 years in a hub and…

7-10 years is too much. 2-4 is around the range I would give.

Its also nothing new; new grads gravitated towards these hubs anyway. Previously, they would settle down in the burbs. Now they're migrating anywhere in the US.

Re: Tech employment now significantly worse than the 2008 or 2020 recessions

#533
post #10

The chart in the tweet represents year-on-year growth. Based on these figures alone the actual number of people employed in tech is still really high, and the numbers can't just go up forever. Also this only captures 6 industries, which is a narrow view of what would define "tech" these days. Not to say that the job market isn't tough but this graph is a very narrow view

> The chart in the tweet represents year-on-year growth. Can’t believe how many people are commenting without looking at what the chart means. We’ve lost 50k jobs last two years after decades of adding 100k+ every year including the pandemic highs of 300k+ per year. Total employment remains way above 2000s, 2008 and 2020 unlike the title suggests.

Yes, but how many people have tried to enter the field since then? Is the economy that supports current number of tech workers really better than one that supports 10x?

Re: Tech employment now significantly worse than the 2008 or 2020 recessions

#534

Earlier quoted context omitted.

So what do you attribute your success in getting interviews to? What are you doing right, or better than other people?

I honestly have no idea. The last place I worked is pretty well-known. Not big tech, but a recognizable name to most people. I send out a lot of applications: those 25 interviews are the result of 150 applications in the last two months or so. And then I have my linkedin set to be discoverable and looking for a job. Basically just fiddle with the options under Visibility and Data Privacy in the linkedin settings and…

In my experience anyone who went to Ivy+ or worked at Big N never has any problem getting a job.

Re: Tech employment now significantly worse than the 2008 or 2020 recessions

#535
post #532

Earlier quoted context omitted.

There absolutely are remote first roles in the US, but the competition is also extremely intense. The median SWE and HNer wouldn't make the cut. It also requires a level of maturity, clear thinking, self-starterness, and independence that is hard to come by without a proven track record and experience. My advice is for the median/average SWE and HNer, not for the truly exceptional. Spending a 7-10 years in a hub and…

7-10 years is too much. 2-4 is around the range I would give. Its also nothing new; new grads gravitated towards these hubs anyway. Previously, they would settle down in the burbs. Now they're migrating anywhere in the US.

2-4 is too little - not enough time to show value nor build an entrenched network that can refer you long term.

Re: Tech employment now significantly worse than the 2008 or 2020 recessions

#536
post #351

People constantly tell me "oh you're a dev it's easy to find work" I'm a c++ dev, with excellent senior tests, but low experience, and no degree in France. 3 years without a job. I yearn for a new pandemic. Fortunately, I learned how to live without a job, found other things to do and how to live a life. Welfare is generous, and I have good savings. Honestly I don't really want to work in software anymore. If there i…

I think you are smarter than me because I continue to work in computer programming even when there is no money to be made!

Re: Tech employment now significantly worse than the 2008 or 2020 recessions

#537
post #235
post #214

Earlier quoted context omitted.

> I'm very much a "builder" type dev that has more fun going from 0-v1 than maintaining and expanding scalable, large systems. Maintaining and expanding is more challenging, which is why I’ve grown to prefer that. Greenfield and then leaving is too easy, you don’t learn the actually valuable lessons. As experience shows that projects won’t stay in the nice greenfield world, building them can feel like doing illusory…

Yup. You learn the most valuable information from watching how things break and then fixing them. It's kind of like when the FAA does crash investigation -- a stunning amount of engineering and process insights have been generated by such work to the benefit of all of us.

Yep. I have loved fixing problems in systems and the processes that the people working on them use for years.

Re: Tech employment now significantly worse than the 2008 or 2020 recessions

#538
post #46

Anyone else's inbox slammed with recruiters, more than it ever has been in the past? Feels like there's 10x the jobs available, but perhaps it's just that LLMs have automated a recruiter's job and they're letting the slop fly

I get lots of AI companies in my inbox, not much else. Surprisingly I got a bite recently because my linkedin says I have worked with eBPF.

Re: Tech employment now significantly worse than the 2008 or 2020 recessions

#539
post #15

In my experience, tech employment is incredibly bimodal right now. Top candidates are commanding higher salaries than ever, but an "average" developer is going to have an extremely hard time finding a position. Contrary to what many say, I don't think it's simple as seniors are getting hired and juniors aren't. Juniors are still getting hired because they're still way cheaper and they're just as capable as using AI a…

I generally tend to interview every year to see what's out there in the world (sometimes I find something worth switching for, other times not). I'm not even looking very hard but have had 4 interviews in the last month. Personally I think it's a bit more nuanced than senior vs junior (though it is very hard for juniors right now). What I've seen a lot of hunger for is people with a track record of getting their hand…

Interviews are easy to get, going through 4-8 rounds and making it through is not.

Re: Tech employment now significantly worse than the 2008 or 2020 recessions

#540
post #70

Earlier quoted context omitted.

> While this could be done by junior or senior, I think junior usually has the slight advantage in being more AI-native and knowing how to effectively prompt and work with AI, though not always. But juniors don't (usually) have the knowledge to assess if what the AI has produced is ok or not. I agree that anybody (junior or senior) can produce something with AI, the key question is whether the same person has the ski…

I don't see the value of a junior instructing an AI, because I as a senior can also instruct an AI. I perceive the AI itself as a very fast junior that I pair program with. So you basically need the seniority to be able to work with a "junior ai". The bar for human juniors is now way higher than it used to be.

Perhaps in a year or so the AI will tell the human juniors what to do
Post reply on HN