Live data from Hacker News

I analyzed 180M jobs to see what jobs AI is replacing today

bloomberry.com

51–60 of 156 posts

Re: I analyzed 180M jobs to see what jobs AI is replacing today

#51

Earlier quoted context omitted.

Also decline in Security engineer by 0.35% doesn't make sense by conventional wisdom. Shouldn't it be increasing due to increased demand for security in all ai integrations?

I wouldn't be surprised by a drop in security postings. Quite a few companies view security as an "overhead" so the siren call of reducing that overhead by introducing AI is a thing. Also for a lot of jobs in security it's pretty hard to measure how well it's being done, so if the AI based solutions are worse, that might not show up for a while

Security products and practitioners are the classic snake oil salesmen. They are actually sales and marketing roles for help closing deals by emphasizing some security aspect. True security comes from general IT practices followed by engineers themselves.

Re: I analyzed 180M jobs to see what jobs AI is replacing today

#52
post #43

Earlier quoted context omitted.

> When using a pen you become a poet ? No. By definition, a poet writes poems. Not all pen use leads to poems. By definition, engineers build systems. What else can you do with code (and LLMs; same thing) other than build systems?

You can make a lot of slop of all different sorts with LLMs. That has very little in common with building systems.

"Slop" suggests that the only difference is in quality, but the definition of engineer says nothing of quality.

Perhaps you might consider using an LLM to build a system that creates a response that is more coherent?

Re: I analyzed 180M jobs to see what jobs AI is replacing today

#53

>180M jobs I doubt they have this data. I highly doubt they have this data.

OP here. You're right to be skeptical, there's an API here if you want to see a sample of the data: https://docs.bloomberry.com/reference/get_signals-jobs-json#...

Thanks! Great data source.

It's just that 180M seemed a bit high.

10x more than this one (also yours): https://bloomberry.com/blog/how-ai-is-disrupting-the-tech-jo...

Btw. I'm not arguing about the quality of your posts, which I consider really good :).

Re: I analyzed 180M jobs to see what jobs AI is replacing today

#54
post #2

I found this interesting: "Still, despite all the hype about how AI coding tools will replace software engineers, software engineering is still one of the most secure jobs you can have today, relative to most other white-collar jobs."

There is a lot of induced demand in software engineering. We are still in the realm where cheaper software means that people want more and more complex software. And that demand increase is more than enough to offset any efficiency increases

Meanwhile the amount of accounting that has to be done is pretty inelastic. Whenever accounting gets more efficient you just reduce the number of accountants instead of doing more accounting

Creative is somewhere in between. Not completely static demand, but not extremely elastic either. The healthy rise in postings for creative directors indicates that the cost reduction has lead to more art being done, but the increase in demand isn't big enough to offset the job losses in the rank and file positions

Re: I analyzed 180M jobs to see what jobs AI is replacing today

#55
post #26

Earlier quoted context omitted.

as of today that's probably true, but if the labs manage to keep increasing the 50% time horizon (defined by METR as 'the length of tasks (measured by how long they take human professionals) that it can complete autonomously with 50% probability') at the current pace, it might not be for long. Exponentials are hard enough to forecast if you kinda sorta know the parameters, and we don't have that comfort today.

sorry, new to this, any helpful links on what metr is?

https://metr.org/blog/2025-03-19-measuring-ai-ability-to-com...

Re: I analyzed 180M jobs to see what jobs AI is replacing today

#56
post #43
post #19

Earlier quoted context omitted.

> When using AI, you become a software engineer. When using a pen you become a poet ? lol Most people who code aren't software engineers, you certainly can't extend the definition to every AI users

> When using a pen you become a poet ? No. By definition, a poet writes poems. Not all pen use leads to poems. By definition, engineers build systems. What else can you do with code (and LLMs; same thing) other than build systems?

idk man, plenty of people have "ai" gf/bf/therapist, ask "ai" for vacation trip ideas, recipes, gym workouts, &c. I wouldn't even be surprised if most tokens were used on non software engineering tasks.

I have a zombie developer, coder, idk how to call them, in my team who doesn't talk to anyone, writes shit tier PRs and spends all day long talking to chatgpt. They're a prompter, a chatter, a waste of money, but certainly not an engineer

Re: I analyzed 180M jobs to see what jobs AI is replacing today

#57
post #52

Earlier quoted context omitted.

You can make a lot of slop of all different sorts with LLMs. That has very little in common with building systems.

"Slop" suggests that the only difference is in quality, but the definition of engineer says nothing of quality. Perhaps you might consider using an LLM to build a system that creates a response that is more coherent?

Slop doesn't suggest the difference is only in quality, but also in form. Words have meanings, ya know?

I can have an LLM generate me code-like text all day long, but that doesn't means it's building a system. Just like I can eat Chicken McNuggets all day long, but that doesn't mean I'm eating a roast chicken.

Re: I analyzed 180M jobs to see what jobs AI is replacing today

#58
post #52

Earlier quoted context omitted.

You can make a lot of slop of all different sorts with LLMs. That has very little in common with building systems.

"Slop" suggests that the only difference is in quality, but the definition of engineer says nothing of quality. Perhaps you might consider using an LLM to build a system that creates a response that is more coherent?

> the definition of engineer says nothing of quality

The definition you used makes someone who maintain a twitter account or use a coffee machine an "engineer"... everyone is an engineer by that definition really

Re: I analyzed 180M jobs to see what jobs AI is replacing today

#59
post #4
post #2

I found this interesting: "Still, despite all the hype about how AI coding tools will replace software engineers, software engineering is still one of the most secure jobs you can have today, relative to most other white-collar jobs."

At the end of the day, "AI" is just another programming language, albeit one that is much more accessible to the layman. When using AI, you become a software engineer. So it stands to reason that software engineering jobs are strong. But what about pay? Elevator operator jobs have never been more prevalent, but increased accessibility to the layman pushed the price to zero.

> When using AI, you become a software engineer.

Stopped reading.

VR flight simulator software is accessible to the layman. Does that make them qualified to be a captain (pilot-in-command) for a commercial passenger plane?

Re: I analyzed 180M jobs to see what jobs AI is replacing today

#60
post #52

Earlier quoted context omitted.

"Slop" suggests that the only difference is in quality, but the definition of engineer says nothing of quality. Perhaps you might consider using an LLM to build a system that creates a response that is more coherent?

Slop doesn't suggest the difference is only in quality, but also in form. Words have meanings, ya know? I can have an LLM generate me code-like text all day long, but that doesn't means it's building a system. Just like I can eat Chicken McNuggets all day long, but that doesn't mean I'm eating a roast chicken.

> I can have an LLM generate me code-like text all day long, but that doesn't means it's building a system.

I don't follow. An LLM doesn't magically output code-like text, or anything else for that matter, on a whim. You have to build a system that describes your intent to the machine. Only then might it output code-like text, if that's what your system describes. It's not the execution of your code that makes you an engineer. It's building a system that can be executed in the first place that makes you a (software) engineer.

Post reply on HN