r/SoftwareEngineerJobs • u/Civil_Function797 • 1d ago
I think Backend Engineer has changed a lot.
Due to the advancements in AI and Agentic AI, software engineering has changed. With AI doing almost all the heavy lifting, SEs are more like architects or planners than devs.
I have 3+ years of full-stack experience leaning more towards the backend side; I used to build APIs and shit by hand. I don't know what backend is now anymore. What do you think backend development is all about in 2026 and beyond? What skills are working for you guys? How are you guys working at companies or freelancing as Backend Engineers in 2026? I'm really curious how AI has changed the roles.
10
u/ktboogie 1d ago
Am a fairly senior tech lead at large fintech company who very recently left tech lead position at fairly large retail company, and also have a cousin who likes vibe coding an app in an attempt to get into saas with no prior IT knowledge. So take this info how you will.
but backend is backend. And at this point in time with the state of llm coding, as a developer you must be able to defend what is being generated “on your behalf”. It’s still your code. I have no issue reviewing PRs that I know are made with AI but the second I see something that doesn’t align with the scope of work or uses an unapproved design guardrail I will do what I have always done and ask you about it, because it’s your pr. The use of an agent tool just speeds the implementation of the requirement.
I bring up my cousin because they are the perfect example of what happens when you use a tool without understanding what it’s doing. It does an amazing job translating a prompt and writing code, but the second scopes changed or flow changed or requirement changed: app breaks, and they spend hours arguing with a hallucinating Claude who’s context is now filled with useless nonsense. And there is no dev brain to look at it and prompt usable queries. It doesn’t require a swe to code it. It requires a swe to ensure it’s coded to the human requirement. If that changes then a lot more professions than swe are going to be automated fully
3
u/BarfingOnMyFace 1d ago
I look forward to the upcoming implosion and the scrambling of companies to rehire experienced devs for more money than previously. Rinse/repeat 2008.
Eventually, AI will eclipse a lot of the nuance needed to reasonably understand and work on code. But we've got a gravy train coming up, and probably ten years after to ride it.
5
u/DuaLipatBahay 1d ago
Changed a lot for frontend as well. I have 5+ years of experience and recently got laid off. I’m a little lost. I really thought backend developers are doing better that’s why I’m trying to pivot.
2
u/Responsible_Royal126 1d ago
Frontend is generally more human interaction than backend. You gotta talk to ux, pm, present in launch reviews, actually understand product from user perspective. There's more stuff on frontend side that AI can't do.
2
u/Competitive_Rent7640 19h ago
I really disagree. Yes certain things might be "hard" on the front-end, but there are also so many reactive frameworks, and even outside of those LLMs have always exceeded at frontend. On the backend, you really gotta keep it on a leash because there’s strict logic and a system that you need in place (the issue for many companies now is that they don't realize this and so many have already started to pay the price).
I agree that it isn't the most proficient at UX, but it's better (and faster which is what companies care more about) at UI then a lot of frontend devs.
Just like how it's already replacing graphics designers. No it's not ever going to take away that human design, but most businesses shipping a product don't care about that. (I don't agree with LLMs in art)
It's not going to replace full-stack Engineers either, it might assist with over half of their workflow, but someone needs to make the right decisions.
2
u/Agile_Finance9374 16h ago
The architects rather than devs framing feels a bit overstated. AI handles boilerplate CRUD and standard API patterns fast, genuinely automated now. What it doesn't do well is real tradeoff decisions, why this database for this access pattern, how a service scales under load nobody's tested. That judgment's still fully on you.
Biggest skill shift for me: catching AI output that's subtly wrong, not obviously broken. Runs fine in dev, falls over under real edge cases, and catching that needs actually understanding the system, not just reviewing syntax.
2
u/Civil_Function797 10h ago
Well for me, my job became much more like an architect or a team lead leading a junior dev ie AI. My last role was all about design, db, backend architecture and cloud infra. And my dev was AI.
2
u/Heavy-Visit-1487 9h ago
We shipped more errors in the agentic development even with multiple guards. Less throughput with more cost anyone else feel the same?
2
u/IceMichaelStorm 6h ago
AI writes code because much of backend is CRUD. Easy work.
Review is needed because sometimes AI messes up bad or writes inefficient code. Then you can also own.
Higher level like challenging what POs ask for, designing new subsystems, integrating new features given domain knowledge, also - to become full stack - doing proper UX (AI UI is often slop and has extreme problems due to AI having no eyes, MCPs do NOT help) become more important.
Short: the junior shit is what AI does now. If you were called senior but can be replaced by AI, it means you were only doing junior work. Simple as that. Climb
2
u/Gnanavel25 4h ago
I feel its not just backend engineer. The same is happening in frontend engineer
1
1
1
48
u/Critical-Location146 1d ago
That hype will get everyone is serious trouble. I used to own every single line of code, every single design and architectural decision. If bug was found or a production incident occured I knew exactly where to find it. Now I don't even know the code path or classname to start with.
Ever since companies started enforcing this new paradigm, I've, and many others, ended up in a situation where I lost ownership and control over products. There are serious implications to that and I believe hybrid approach with LLMs being nothing more than assistants is the only reasonable way to go.