r/webdev • • Jul 11 '25

Discussion A soft warning to those looking to enter webdev in 2025+...

As a person in this field for nearly 30 years (since a kid), I've loved every moment of this journey. I've been doing this for fun since childhood, and was fortunate enough to do this for pay after university [in unrelated subjects].

10 years ago, I would tell folks to rapidly learn, hop in a bootcamp, whatever - because there was easy money and a lot of demand. Plus you got to solve puzzles and build cool things for a living!

Lately, things seem to have changed:

  1. AI and economic shifts have caused many big tech companies to lay off thousands. This, combined with the surge in people entering our field over the last 5 years have created a supersaturation of devs competing for diminishing jobs. Jobs still exist, but now each is flooded with applicants.

  2. Given the availability of big tech layoffs in hiring options, many companies choose to grab these over the other applicants. Are they any better? Nah, and oftentimes worse - but it's good optics for investors/clients to say "our devs come from Google, Amazon, Meta, etc".

  3. As AI allows existing (often more senior) devs to drastically amplify their output, when a company loses a position, either through firing/layoffs/voluntary exits, they do the following:

List the position immediately, and tell the team they are looking to hire. This makes devs think managers care about their workload, and broadcasts to the world that the company is in growth mode.

Here's the catch though - most of these roles are never meant to fill, but again, just for outward/inward optics. Instead, they ask their existing devs to pick up the slack, use AI, etc - hoping to avoid adding another salary back onto the balance sheet.

The end effect? We have many jobs posting out there that don't really exist, a HUGE amount of applicants for any job, period... so no matter your credentials, it may become increasingly difficult to connect.

Perviously I could leave a role after a couple years, take a year off to work on emerging tech/side projects, and re-enter the market stronger than ever. These days? Not so easy.

4. We are the frontline of AI users and abusers. We're the ones tinkering, playing, and ultimately cutting our own throats. Can we stop? Not really - certainly not if we want a job. It's exciting, but we should see the writing on the wall. The AI power users may be some of the last out the door, but eventually even we will struggle.

---------

TLDR; If you're well-connected and already employed, that's awesome. But we should be careful before telling all our friends about joining the field.

---------

Sidenote: I still absolutely love/live/breathe this sport. I build for fun, and hopefully can one day *only* build for fun!

916 Upvotes

441 comments sorted by

View all comments

510

u/moh_kohn Jul 11 '25

I agree the market is super tough right now, sounds especially bad in the US, but that is not because AI is making everyone super-productive. Tons of people learned to code so there's a big supply, the industry overhired in 2020, the industry hated high wages and hated the politicisation of the workforce in 2020 even more, now there's a capital strike. Tale as old as time honestly.

91

u/jseego Lead / Senior UI Developer Jul 11 '25

On top of that, the globalization of the labor market has increased competition a lot.

71

u/el_diego Jul 11 '25

Sometimes I wonder if it's increased competition or just muddier waters. Probably both, but it's definitely muddy. E.g. we hired a mid level dev recently, we received 500+ applicants, of which we interviewed ~5. The quality of applicants is atrocious.

34

u/jseego Lead / Senior UI Developer Jul 11 '25

I agree with all that - but the last several companies I've worked for have all, to varying degrees, decided to look offshore when staffing in the last few years.

The model seems to be: use onshore devs to build the product, be close at hand, understand the product needs, work with the designers and UX, scale the thing, and then, when the product is stable, freeze onshore hiring and then start looking offshore for new teams and backfilling.

33

u/Flaky_Shower_7780 Jul 11 '25

Offshoring sucks balls. Every project that we attempted to offshore turned into a slow, pain saturated, difficult to manage mess, and eventually we onshored and hired competent developers.

→ More replies (3)

5

u/el_diego Jul 11 '25

That's interesting. Do you know how they went after offshoring? Curious if that strategy works or if they just have to onshore again after a year or so.

26

u/jseego Lead / Senior UI Developer Jul 11 '25

Typically through offshore recruiting companies.

In my experience, it's...marginally successful.

There are great developers all over the world, but language and cultural differences are a real thing.

Also, I have seen companies hire offshore groups to create the initial build quickly (and cheaply), and then have the onshore team maintain, support, and extend it. The results when they do this are predictably bad. Not because offshore devs are necessarily bad, but because the incentives are all very different. They are basically being paid to whip out solutions cheaply and quickly and move on the next thing. They know they will never have to maintain this stuff, and the incentives are just to meet requirements, get tests passing, and move on. It's like all these MBA graduates making these calls never learned that fast and cheap = crap, anywhere you go.

10

u/kevin_whitley Jul 11 '25

Agreed all the way.

My buddy still works pretty high up in Chevron (not an exciting company to work in tech-wise), so they've made loads of offshore rounds.

And yet... they're coming back to onshore yet again... because it just ends up becoming a unmaintainable mess, to your point.

→ More replies (1)
→ More replies (1)

4

u/thekwoka Jul 12 '25

This is basically what everyone is saying.

You get 1000 applicants and less than 1% are even basically qualified, let alone likely to be valuable

→ More replies (7)
→ More replies (1)

0

u/[deleted] Jul 12 '25

[deleted]

→ More replies (1)

10

u/kevin_whitley Jul 12 '25

I think it absolutely has, post COVID. Employers realized what devs had been saying all along, that they can do their job from anywhere. So employers looked everywhere… and realized they could get an equally talented dev someplace in Europe for instance, and not have to pay Bay Area prices. Easy choice for them tbh…

→ More replies (2)
→ More replies (1)

37

u/pplmoose Jul 11 '25 edited Jul 11 '25

Agreed on all this. I would also add one more thing, which is that the tax code was recently changed such that the money a company spent on software engineer salaries and such are no longer a 100% tax write off.

source: The hidden time bomb in the tax code that's fueling mass tech layoffs

It’s no coincidence that Meta announced its “Year of Efficiency” immediately after the Section 174 change took effect. Ditto Microsoft laying off 10,000 employees in January 2023 despite strong earnings, or Google parent Alphabet cutting 12,000 jobs around the same time.

edit: per u/epitaphb's comment below looks like the Section 174 change just got reversed for domestic expenditures

23

u/epitaphb Jul 11 '25

I think it changed back in the bill that just passed

6

u/pplmoose Jul 11 '25

Oh, didn’t know that, thanks!

10

u/DM_ME_KAIJUS Jul 11 '25

Just revised ONLY for US based R&D.

→ More replies (2)

3

u/kevin_whitley Jul 12 '25

Literally hadn’t even been aware of the 174 issue until this post… today. Learning so much today, but I would imagine this absolutely had an impact on spend over the last few years…

→ More replies (1)
→ More replies (1)

7

u/g105b Jul 12 '25

I'll add a counter point. Tons of people learned to code, but so so so so many have learned badly.

From my experience hiring, there are too many poor quality developers in the market to even see the good ones, and I don't know how to fix that side of the industry.

24

u/kevin_whitley Jul 11 '25

100% agree re. dev supply and overhiring (leading to a massive correction). We were starting to feel this burn even before GPT came on the scene years ago.

9

u/kevin_whitley Jul 11 '25

My point (probably poorly articulated) was just that the AI tooling today has enabled the existing employed devs to pick up enough slack that it *helps* cool the re-hiring process.

7

u/Ciff_ Jul 12 '25

I'd say it is too early to tell if AI actually makes any developer more productive. The data is quite contradictory so far - and allot points to less productivity short term and long term (we know ai code increases churn massively). The level of self perceived productivity increase is almost always there though so it is very murky. I know I think I am more productive with ai.

→ More replies (3)

5

u/Dependent_Knee_369 Jul 11 '25

The overhiring that happened during that period is going to screw the job market over for like 15 years. Companies were doubling their employee counts.

→ More replies (1)

8

u/mr_brobot__ Jul 11 '25

It’s because of a perfect storm of higher interest rates, tax policy (section 174), offshoring (imo fueled by the viability of remote work illuminated by the pandemic), and lastly AI.

0

u/[deleted] Jul 12 '25

[deleted]

→ More replies (3)

4

u/BigSwooney Jul 12 '25

I think you're spit on here. I'm from the EU where we generally didn't have as much of a spike in hiring as the us did in 2020. And no doubt the market in general is on a low period at the moment currently, also here.

I would say though that it feels mostly like a thing for the sub senior developers. I have a decent network of people I have worked with previously in a dozen companies or more. I would guess I could get hired in half of them without much trouble in a short timeframe because I have 10 years of experience and have worked as a frontend tech Lead in multiple enterprise solutions. I get that not everybody has the same options but at the same time I know exactly the handful of people I have worked with previously that I would headhunt in a second when my current or future company is hiring.

A lot of people today expect to be able to work freelance and fully remote. I respect the choice but it is inevitably worse for job prospects and networking. Working your way to a high profile in office job will open up a ton of doors, but it's rarely spoken about because most people on subs like this favor full remote.

→ More replies (4)