News for hackers. Stuff that matters.
Re:A Family Tree of Software Job Titles by probably_wrong on Saturday November 14, 2026 @05:07PM (#50501463)
Recently I spoke to someone who wanted to know what they should call themselves seeing as they never learned software development, formally or otherwise, but that's not stopping them from releasing AI-powered Python projects in GitHub. I suggested Project Manager, but they took offense to that because (I think) they wanted to hear Software Engineer in order to apply to those jobs. My counter-argument was that, legal rules aside, a S.E. should be able to differentiate good code from bad, but my suggestion wasn't super well received.

The point being: I'm always amazed at the cross-purpose impulse of arguing "the title is not important" while, simultaneously, really wanting to use the title.

Re:A Family Tree of Software Job Titles by layer8 on Saturday November 14, 2026 @05:36PM (#50501710)
You could have suggested “prompt engineer”. As in “engineering by prompting”. :)
Re:A Family Tree of Software Job Titles by Xirdus on Saturday November 14, 2026 @09:09PM (#50503301)
Prompt engineering usually means engineering the prompts themselves, and implies in depth knowledge of what makes a good prompt.
Re:A Family Tree of Software Job Titles by layer8 on Sunday November 15, 2026 @06:26AM (#50506097)
I know, but the vibe-coder in question wouldn’t have liked that.
Re:A Family Tree of Software Job Titles by gumby on Saturday November 14, 2026 @09:38PM (#50503453)
A prompt engineer is one who gets to the standup on time.
Re:A Family Tree of Software Job Titles by pcthrowaway on Saturday November 14, 2026 @06:06PM (#50501992)
As a software engineer (CS degree and ~10 years of pre-AI experience), I'd feel uncomfortable saying I was a Project Manager
Re:A Family Tree of Software Job Titles by santoshalper on Saturday November 14, 2026 @11:10PM (#50503940)
Who would want to?
Re:A Family Tree of Software Job Titles by yieldcrv on Saturday November 14, 2026 @06:12PM (#50502040)
Member of Technical Staff, Applied AI
Re:A Family Tree of Software Job Titles by Buttons840 on Saturday November 14, 2026 @06:20PM (#50502116)
Software engineers keep software on the tracks like train engineers keep the train on the tracks. Nobody thinks the train engineer built the train...
Re:A Family Tree of Software Job Titles by jelloroll42 on Saturday November 14, 2026 @06:30PM (#50502199)
Do you think the "engineer" in software engineer is etymologically closer to train engineer than it is to electrical/mechanical/civil engineer?

I don't think so.

Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @07:15PM (#50512395)
I think the bulk of software "engineers" don't actually do much if any engineering work. However I agree that actual software engineering is indeed akin to electrical engineering. Meanwhile most of the real world work being done appears to me much closer to uncertified carpentry of highly questionable quality.
Re:A Family Tree of Software Job Titles by layer8 on Saturday November 14, 2026 @06:46PM (#50502303)
We should train engineers regardless.
Re:A Family Tree of Software Job Titles by zx8080 on Saturday November 14, 2026 @07:04PM (#50502419)
Isn't it maintenance, not engineering?
Re:A Family Tree of Software Job Titles by hunter2_ on Sunday November 15, 2026 @12:21AM (#50504240)
[delayed]
Re:A Family Tree of Software Job Titles by zx8080 on Saturday November 14, 2026 @07:05PM (#50502424)
Prompt Editor (Senior)
Re:A Family Tree of Software Job Titles by apt-apt-apt-apt on Saturday November 14, 2026 @10:45PM (#50503786)
LGTM-er (100% approval rate)
Re:A Family Tree of Software Job Titles by 0c3ca83 on Saturday November 14, 2026 @08:03PM (#50502884)
I would suggest "Anthropic client", because the relationship between them and Anthropic is similar to the relationship between a client and a contractor.

You ask the contractor for what you want, iterate a little, and take what they give you. Sometimes you may read the results.

Re:A Family Tree of Software Job Titles by derektank on Sunday November 15, 2026 @11:18AM (#50508096)
Nobody calls the person that manages a company’s external contracts a client internally though, we call them something like “contract manager” or “acquisitions specialist” if the contract is with a manufacturer.
Re:A Family Tree of Software Job Titles by 0c3ca83 on Sunday November 15, 2026 @09:58PM (#50513490)
Sure, I suppose if you're doing it on behalf of a large organization.
Re:A Family Tree of Software Job Titles by person8645 on Saturday November 14, 2026 @08:06PM (#50502896)
Project Manager is a great fit. I also heard and liked Director, which brings in good analogies from filmmaking and implies nothing about technical ability either way. Could even be Software Director.
Re:A Family Tree of Software Job Titles by Xirdus on Saturday November 14, 2026 @09:05PM (#50503276)
Software Director could be confused for Director of Software Development.
Re:A Family Tree of Software Job Titles by luisfmh on Saturday November 14, 2026 @11:39PM (#50504074)
Director of Software Directing?
Re:A Family Tree of Software Job Titles by disgruntledphd2 on Sunday November 15, 2026 @03:24AM (#50505095)
Clearly Director of Software Direction.
Re:A Family Tree of Software Job Titles by anal_reactor on Saturday November 14, 2026 @08:08PM (#50502918)
"The title is not important" was a movement coming from the fact that same jobs at two companies could've had vastly different responsibilities, and vice versa. But that was rather an exception and outside that bubble, people have always paid great attention to titles.

Yours sincerely, Software Developer with 6 years of experience. Last week for the first time in my career I've actually merged application code. It was AI generated.

Re:A Family Tree of Software Job Titles by Xirdus on Saturday November 14, 2026 @09:11PM (#50503308)
...what did you do the last 6 years?
Re:A Family Tree of Software Job Titles by tipperjones on Saturday November 14, 2026 @10:55PM (#50503855)
Yeah, wait what?

I'm confused about the point he's making here with the 6 years thing.

Re:A Family Tree of Software Job Titles by anal_reactor on Sunday November 15, 2026 @03:30AM (#50505118)
Infra
Re:A Family Tree of Software Job Titles by Xirdus on Sunday November 15, 2026 @09:47AM (#50507310)
Oh I see.
Re:A Family Tree of Software Job Titles by chupchap on Saturday November 14, 2026 @08:36PM (#50503101)
As an analyst who vibe codes a lot I think it is perfect, along with Product Manager. There is a lot more to these roles, but I think they're the closest.
Re:A Family Tree of Software Job Titles by disgruntledphd2 on Sunday November 15, 2026 @03:27AM (#50505111)
Product rather than project makes much more sense for vibe coding.

It's a weird one, because recently I've been working on a JS based system when I don't know JS and it's definitely very very different from when it's a language you're familiar with.

Re:A Family Tree of Software Job Titles by TZubiri on Saturday November 14, 2026 @09:14PM (#50503325)
There's only one country to my knowledge that has historically allowed anyone to be called a software engineer without being an engineer. Now that the bar is dropping even lower, can we stop normalizing that? I never had the audacity to call my self a Software Engineer without an Engineering degree, just use any of the other dozens of words.
Re:A Family Tree of Software Job Titles by keyle on Sunday November 15, 2026 @12:09AM (#50504180)
Project engineer..?
Re:A Family Tree of Software Job Titles by isolay on Sunday November 15, 2026 @12:22AM (#50504243)
Prompt Whisperer
Re:A Family Tree of Software Job Titles by RGamma on Sunday November 15, 2026 @05:52AM (#50505895)
[delayed]
Re:A Family Tree of Software Job Titles by physicles on Sunday November 15, 2026 @12:39AM (#50504312)
If I asked Gemini to recommend a weight loss plan, does that make me a dietician?
Re:A Family Tree of Software Job Titles by egeozcan on Sunday November 15, 2026 @01:54AM (#50504640)
You're jesting, but I've seen self-claimed "dietitians" with much less involvement than asking a bot.
Re:A Family Tree of Software Job Titles by theginger on Sunday November 15, 2026 @04:37AM (#50505433)
If you earned a living by doing it for other people it would.
Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @07:13PM (#50512377)
No, it would not. It would make you a meat puppet and claude an (unqualified but likely highly effective) dietician.
Re:A Family Tree of Software Job Titles by mike50 on Sunday November 15, 2026 @07:02AM (#50506299)
A nutritionist, the non protected title / non licensed person.
Re:A Family Tree of Software Job Titles by gremlinunderway on Sunday November 15, 2026 @10:15AM (#50507496)
Except dietician is a protected job title that is licensed by legally-recognized professional standards bodies.

Software "engineers" in North America don't have any actual professional board that licenses or oversees their work. Until governments actually regulate the profession through these bodies, no one can gatekeep software development job titles.

A bunch of blog posts talking about "industry standards" is not a reference point for this.

Re:A Family Tree of Software Job Titles by julianlam on Sunday November 15, 2026 @02:46PM (#50510004)
Canadian Engineers are licensed and use of the term is protected.
Re:A Family Tree of Software Job Titles by galaxyLogic on Sunday November 15, 2026 @01:57AM (#50504661)
AI is heavy machinery. In the construction industry you need special permits to operate such machinery, and everybody driving a car needs to have a driver's license.

So I wonder if users of "heavy AI" should also need to have a license.

Re:A Family Tree of Software Job Titles by cadamsdotcom on Sunday November 15, 2026 @06:40AM (#50506176)
Do people die or get maimed if you drive your model wrong?

Will your model and harness be the same in enough time to develop a curriculum for it and disseminate that to enough people to give it enough of a reputation to be worth doing for students, before it's obsolete?

I'd argue no on both counts.

This work has key differences vs operating heavy machinery.

Re:A Family Tree of Software Job Titles by lossyalgo on Sunday November 15, 2026 @02:04PM (#50509646)
[delayed]
Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @07:10PM (#50512355)
The heavy equipment operator working at a refinery doesn't require certification as an engineer. It's the people singing off on the plans that do.

Using an LLM doesn't carry any inherent risk. It's the people working on software for safety critical systems that require relevant oversight. Irresponsibly turning an LLM loose on a safety critical codebase would be nothing short of professional negligence (at absolute minimum).

Re:A Family Tree of Software Job Titles by LtWorf on Sunday November 15, 2026 @05:47PM (#50511706)
> Do people die or get maimed if you drive your model wrong?

Well depends what your runaway AI goes hacking… people might indeed die.

Re:A Family Tree of Software Job Titles by whilenot-dev on Sunday November 15, 2026 @02:05AM (#50504701)
I'd call them a Software Conductor.
Re:A Family Tree of Software Job Titles by julianpye on Sunday November 15, 2026 @02:11AM (#50504737)
I think the role is that of a producer - similar to a music producer in the 70s and 80s integrating new synth and recording technology into ambitious outcomes where the goal was defined but the shape and detail unpredictable.
Re:A Family Tree of Software Job Titles by sznio on Sunday November 15, 2026 @02:38AM (#50504865)
i think "User" ultimately.

It depends on the way they use it. If you design an architecture and use an LLM to fill it in, I'd consider a more technical label. If you're just using what Claude made, and providing feedback, that's just how software was done 10 years ago except then they'd be talking to a guy instead. And it would be orders of magnitude more expensive.

From my perspective, Claude feels like 5 engineers in a box. you can make things that required small organizations to make.

Re:A Family Tree of Software Job Titles by cstever on Sunday November 15, 2026 @06:46AM (#50506209)
"User" makes sense. Another option would be "Client"
Re:A Family Tree of Software Job Titles by jacobsimon on Sunday November 15, 2026 @10:22AM (#50507560)
This is shortsighted (no offense). We should collectively stop personifying AI tools like this before we’ve completely lost our way.

If you’re building and producing valuable software, you are still a creator or software engineer full stop. We can argue over titles, but don’t demote your own creative process to passive consumption.

Re:A Family Tree of Software Job Titles by dan_grec on Sunday November 15, 2026 @03:07AM (#50505016)
I have a bachelor of Software Engineering that is fully accredited by the Australian institute of Engineers. It was two years longer than a C.S. Degree.

Software Engineering is about so many things other than code it was an ongoing debate if code and programming should even be taught at a university level course, and while contemplating my masters of S.E. I had many great conversations with faculty about the distinction. Writing code is much more akin to welding or wiring, therefore belongs at a trade school, not a university.

After all, the discussion goes, Aerospace and Electrical Engineers don’t learn the doing of welding or pulling wires through crawl spaces, why should Software Engineers concern themselves with the doing of code.

>a S.E. should be able to differentiate good code from bad

A software Engineer needs to have all phases of the SDLC in mind, and be thinking about and planning all of them. Code is a tiny piece of the puzzle.

I’m thinking about requirements gathering, designing, testing, deployment, maintenance, long term change strategy, hand off to a new owner, etc, etc.

I could always see the merits of both sides of the discussion. Then at my first few jobs it very quickly became clear that many CS grads were just there to write code and that’s it. They didn’t have the big picture ideas at all, and I immediately understood the difference of a Software Engineer.

Re:A Family Tree of Software Job Titles by f1shy on Sunday November 15, 2026 @03:21AM (#50505077)
Just let me give my 2ct: as somebody that did search for hiring EEs and mechanical engineers, I really searched hard for the ones that DID soldered, pulled wires and welded, even for management positions. They use to manage much better, had better communication with the team, had better feeling for quality, could look much further in the furure and had much more authority, begin way more respected by the team.

That being said,

> A software Engineer needs to have all phases of the SDLC in mind, and be thinking about and planning all of them. Code is a tiny piece of the puzzle.

I would not AT ALL call it tiny. Yes, is one part of MANY. But is your final delivery. Would be like a Toyota saying: “hey they don’t really have to understand what makes a good car, the cars we sell is a tiny portion in the whole development cycle”

Re:A Family Tree of Software Job Titles by dan_grec on Sunday November 15, 2026 @03:30AM (#50505120)
I remember a professor who used to say “If the requirements, design, test plan and acceptance criteria are done to a high enough standard, the code can be written by a monkey.”

Which is exactly what we’re seeing now with LLMs writing code.

Interestingly you’ll see the same building a mega bridge or skyscraper. As long as the plan has been done well, it can be assembled by relatively very unskilled labor.

Note the test plan and acceptance criteria could be one and the same, depending.

Re:A Family Tree of Software Job Titles by sverhagen on Sunday November 15, 2026 @07:19AM (#50506400)
> If [everything before coding] are done to a high enough standard

That "if" is doing an unrealistic amount of lifting, here, in practice, and that's probably why human coders have had a better run than monkeys.

Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @06:59PM (#50512260)
I'd disagree as we have counterexamples all over the place in the real world. For software there's LLMs - it is clearly possible to use them to implement large projects autonomously provided that your requirements are sufficiently well thought out. Zooming out to other disciplines any large construction project fits the bill. Clearly a "high enough" standard is achievable.
Re:A Family Tree of Software Job Titles by sverhagen on Sunday November 15, 2026 @07:15PM (#50512394)
Just talking about software engineering, I think that the places where requirements are strong enough to be implemented unambiguously, are few and far between. So, it's "clearly possible", but rare, in my universe, your mileage may vary.
Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @07:22PM (#50512446)
And yet somehow people are successfully leaving some projects almost entirely up to agents. Does that not run directly counter to what you're saying?

Also I will observe that something being rare is not in and of itself an indicator of whether or not it is reasonable. Many things are done a certain way because that's the conventional approach or it's more cost effective or due to some logistical concern.

In the case of software development it was previously cheaper not to exhaustively specify everything up front but I'd argue LLMs have upended that longstanding status quo within only the past year.

Re:A Family Tree of Software Job Titles by sverhagen on Sunday November 15, 2026 @08:02PM (#50512763)
I don't think that runs counter...

We had humans that were smarter than monkeys, dealing with imperfect requirements. Now we have LLMs that are smarter than monkeys, dealing with imperfect requirements.

LLMs don't work because of good requirements input, they work despite the poor requirements they're given.

Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @08:56PM (#50513102)
Okay but all you're arguing at that point is that it will continue to be rare because LLMs that exceed the capabilities of monkeys are readily available and not that much more expensive than their less capable cousins. Not that there's any inherent reason it's unrealistic to do so. With skyscrapers it's cheaper to make sure the specification is bulletproof and with software it's cheaper to kick it out the door while it still has more than a few holes in it.
Re:A Family Tree of Software Job Titles by f1shy on Sunday November 15, 2026 @07:25AM (#50506423)
> If the requirements, design, test plan and acceptance criteria are done to a high enough standard, the code can be written by a monkey.

Nice sentence. But it has 2 problems:

1) Define "high enough" - There is where good requirements start, make it measurable!

2) Related to "you’ll see the same building a mega bridge or skyscraper". I've seen enough cases where "unskilled labor" messed up building something. You will reply "that is why I said 'Acceptance Criteria'!". My take is: you are making it far more complicated than it should, taking totally unnecessary risks, and it will be invariably more expensive in the long run.

I mean, I've seen enough examples of cases where the acceptance criteria was not properly checked, because also the ones doing the test were "unskilled" and had received a "perfect plan". (Just look at any infrastructure disaster we have every year)

And even in the best case: you discover the poured cement does not meet the specifications. What now? Blow the thing and start over? Better to have skilled labor.

Again, my 2ct. experience: hire experienced people, who actually have done the work all the way down to the lowest level.

"If you think knowledge is expensive, try with ignorance"

[dead]
Re:A Family Tree of Software Job Titles by julianlam on Sunday November 15, 2026 @02:43PM (#50509983)
It's a bunch of engineers (by title) doing what they can to gatekeep those who dare not pay the piper out of the jobs.

"Engineer" is a restricted title in Canada... and so it should be, but I don't think it should be used keep people away from software eng work.

Re:A Family Tree of Software Job Titles by randomaccountpe on Monday November 16, 2026 @01:08AM (#50514555)
This was my general thought too.

I do think there should be reasonable restraints before we start labeling people, but I often see this go too far both ways.

Restraining job titles too hard in circumstances where job X is obviously qualified to do job Y, it comes across as ignorance or an emotionally driven decision.

Or not restraining hard enough (I can't think of many examples, other than where someone just obviously hasn't put in enough work to be qualified for the job).

I don't want to say it's ego-driven, but it sometimes across like that.

Re:A Family Tree of Software Job Titles by mike50 on Sunday November 15, 2026 @06:48AM (#50506223)
Electrical Engineering programs have practical labs where you build electronic projects and run wires. Most electrical engineers don't work in power or building engineering. Senior design projects (for undergraduate) have to be mostly built by the students. Metallurgical Engineers and Welding Engineers take welding courses not Aerospace.
Re:A Family Tree of Software Job Titles by dan_grec on Sunday November 15, 2026 @07:10AM (#50506354)
Absolutely , you’re right.

Of course no Electrical Engineer would be able to tell you the building code requirements for how close an outlet can be to a sink, or the ground, or a window. Every electrician can.

No Aerospace Engineer will be able to weld strange metal combinations, or be great at aluminum and thick stainless and oil pipeline pipe. Every ticketed welder can.

When you want the doing done, it’s great the Engineer has a working knowledge, which no doubt makes the project better, but no way in hell you get them to do it on the real thing. You get the ticketed tradesperson.

Re:A Family Tree of Software Job Titles by squishington on Sunday November 15, 2026 @07:29AM (#50506448)
If writing code can be considered a trade, what about debugging? What about debugging a complex embedded system? I'm not sure what i should call myself. I usually just say programmer because it's easier to say that. I did an electronics and communications degree at an Aus uni, focusing on DSP and FPGA. I had 2 FPGA jobs, one in defence and one in medical devices. Now I've been working with embeddes software for 7 years for a chip company. I'm still not sure if I should call myself a Software Engineer, even though that's what it says on my contract. I occasionally find gaps in my software engineering knowledge, but i learn as i go.
Re:A Family Tree of Software Job Titles by AQuantized on Sunday November 15, 2026 @08:32AM (#50506809)
I don't understand the view that coding is like a trade; even with a good idea of the systems involved and an intended design, I often find out things while coding that change the perceived optimal design substantially. I don't think this is nearly as likely to be the case with wiring or welding, and may even be impractical to change regardless given the less mutable nature of the metal or electrical systems you're working with.
Re:A Family Tree of Software Job Titles by giantg2 on Sunday November 15, 2026 @08:45AM (#50506904)
I think you're vastly underestimating the complexity and possible technical variations involved in welding and wiring at an industrial level.
Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @07:03PM (#50512300)
> I don't think this is nearly as likely to be the case with wiring or welding

The same thing can happen. The difference is that there's more work put into surveying ahead of time, more work put into planning in advance, and if changes do turn out to be necessary it requires a round trip with the relevant accredited architect, engineer, etc.

Re:A Family Tree of Software Job Titles by sdeframond on Sunday November 15, 2026 @12:28PM (#50508768)
I've come to think there is a good amount of BS, bikeshedding and misplaced ego in making these distinctions.

Actually, no. It is a HR concern. HR need to put people into boxes. Most people dont actually fit but whatever.

Re:A Family Tree of Software Job Titles by LtWorf on Sunday November 15, 2026 @05:32PM (#50511573)
I'm not sure how _not_ knowing how to do something very important and central to your objectives should be a quality.
Re:A Family Tree of Software Job Titles by _s_a_m_ on Sunday November 15, 2026 @04:12AM (#50505308)
the endless cycle of incompetent people wanting important titles to fake a personality they will never have
Re:A Family Tree of Software Job Titles by kakacik on Sunday November 15, 2026 @06:04AM (#50505972)
Cannot be an engineer without corresponding university title, be it mechanical, construction or software etc. Same as doctor or lawyer for example. Various emotional insecurities of wannabe-whatever are not that relevant here.
Re:A Family Tree of Software Job Titles by hkolk on Sunday November 15, 2026 @06:15AM (#50506032)
That really depends on the country and the spelling of title. In the Netherlands only the dutch version of the word is protected for instance. And other countries don't have protection.
Re:A Family Tree of Software Job Titles by mike50 on Sunday November 15, 2026 @07:00AM (#50506291)
Until recently you could get licensed as a Professional Engineer without a degree at all in my state (with the exams) and even today there is an waver process for 15 year of lawful practice elsewhere (my great uncle did this).
Re:A Family Tree of Software Job Titles by gremlinunderway on Sunday November 15, 2026 @10:17AM (#50507511)
Nope.

Actual engineers, doctors and lawyers are given that title not through education but through actual legally-recognized standards bodies. These are standards bodies that certify them, review their work, can investigate deviations from standards and even delicense people if needed.

In North America, there aren't any such bodies for software development. So trying to gatekeep this term because of a university degree is absolutely not the same thing as lawyers, doctors or mechanical engineers.

I would be fully supportive of gatekeeping this btw but pretending that its the same as doctors and lawyers is ridiculous.

Until there are actual standards bodies overseeing this, sorry, your university degree equally means the same as anyone self-taught so long as no one actually oversees the work and certifies people.

Re:A Family Tree of Software Job Titles by giantg2 on Sunday November 15, 2026 @08:41AM (#50506879)
The titles between different levels don't seem to mean much because of the variation between companies. But I do see merit to differentiating between roles.

As an example, I moved from Software Engineering to IT Controls Analyst. The pay brackets are lower and there are way fewer job postings. Even this chart of software related job completely leaves out any compliance or audit function, illustrating just how little my own profession thinks of us.

Re:A Family Tree of Software Job Titles by bagacrap on Sunday November 15, 2026 @09:49AM (#50507320)
Prompt engineer?
Re:A Family Tree of Software Job Titles by zahlman on Sunday November 15, 2026 @12:33PM (#50508836)
It's probably not worth wasting time on people who present as wanting your insight but apparently really just want your permission.
Re:A Family Tree of Software Job Titles by heresie-dabord on Sunday November 15, 2026 @03:57PM (#50510668)
This person is an Apprentice at best.
Re:A Family Tree of Software Job Titles by realaaa on Sunday November 15, 2026 @08:34PM (#50512967)
not Project manager of course, these are people who manage projects and people

Vibe Product Manager I guess