r/softwareengineer • • 24d ago

Developers who spent years building software before AI, how does the job feel now?

20 Upvotes

I’ve been a developer for 15 years. I started out barely knowing what I was doing, and over time became the person people came to for the harder problems.

A lot of those years were exhausting. The coding was only part of it. There were requirements to figure out, technical approaches to propose, releases to get out, and production issues to investigate when something broke at the worst possible time.

These days I use AI a lot, and the difference is hard to ignore. Things that used to take hours of searching, reading, and trying different approaches often move much faster. I still have to understand the problem and check the result, but I spend less time stuck on the first step.

It doesn’t make me feel like those 15 years were wasted. If anything, that experience helps me tell when the AI has given me something useful and when it’s confidently heading in the wrong direction. But it has definitely changed what my working day feels like.

I’m curious how other long-time developers feel about it. Are you enjoying the change, or do you miss some parts of how we used to work?


r/softwareengineer • • Sep 17 '26

Is software engineering still worth pursuing in 2026? I’m genuinely unsure

0 Upvotes

I’m a high school student trying to decide what I want to do after graduation, and software engineering is one of the paths I’m seriously considering.
I’ve started learning Python and I’m interested in programming, backend development, data/AI, etc. But honestly, I’m starting to have doubts.
I keep seeing very different opinions about the current tech industry:
junior jobs are extremely difficult to get
the market is oversaturated
AI is replacing a lot of entry-level work
you need to know much more than before to get your first job
but at the same time, people are still becoming developers and building successful careers
So I’d really like to hear from people who are **actually working in software**, especially developers with a few years of experience.
If you were starting from zero in 2026:
Would you still choose software engineering?
How difficult was it to get your first job?
How much did you have to learn before you became employable?
How has AI changed your day-to-day work?
Do you think the situation for juniors will improve, stay difficult, or simply change?
If you were my age again, would you still invest several years into learning programming?
I’m not looking for motivation or doomposting. I’d genuinely like to hear the good, the bad, and the ugly from people who are actually in the industry.
Thanks


r/softwareengineer • • Aug 28 '26

Can I become a software engineer without a CS degree? Arts student

0 Upvotes

I’m an Arts student currently doing my Bachelor’s, but I’ve wanted to become a software engineer for a long time.

I started loving coding when I was a kid, and I’ve continued learning on my own. So far, I’ve learned HTML, CSS, JavaScript, Java, and Python.

The problem is that I don’t have a CS degree.

So my question is:

Can I realistically become a software engineer without a CS degree if I build strong skills, work on good projects, and learn DSA, databases, etc.?

Will companies actually consider someone with a non-CS degree for software engineering roles?

If you’re a software engineer without a CS degree, I’d really like to hear about your experience and what you would recommend I do from here.


r/softwareengineer • • Nov 19 '25

The software engineer job market is completely broken, and both sides are lying about why

145 Upvotes

I'm an AI engineer who also runs a technical recruiting platform, so I see both sides of hiring. What's happening right now is absolutely insane, and everyone's pretending it's normal.

Companies say: "We can't find qualified engineers! There's a massive talent shortage!"

But they mean to say: "We can't find a senior engineer with 8 years of experience in our exact tech stack who will accept mid-level pay and start Monday."

Engineers say: "I've applied to 500 jobs and heard nothing back! The market is dead!"

But engineers are: Applying to everything with "software engineer" in the title regardless of fit, using generic resumes, and expecting callbacks.

Here's what I think:

For Companies:

Your "we can't find talent" problem is a "we refuse to train or pay market rate" problem. You want:

  • Senior engineers at mid-level prices

  • Someone who knows your exact stack (Rails 5.2, not Rails 7)

  • 5 years experience for an "entry-level" role

  • Perfect culture fit (aka someone who went to the same schools as your founders)

  • Immediate start date with zero ramp time

For Engineers:

Your "I can't get callbacks" problem is a "I'm not standing out" problem. You're:

  • Using the same generic resume for every application

  • Applying to 50 jobs a day instead of 5 targeted ones

  • Listing technologies without showing what you actually built

  • Competing with 500 other people doing the exact same thing

  • Hoping your 6-month bootcamp cert competes with someone's 5-year track record

Companies want proof you can do the job. They don't want "potential."

Engineers want companies to see their potential. They think "I can learn Rails in 2 weeks" should be enough.

Both are wrong, and both are right. The market is just broken.

Companies that are successfully hiring:

  • Pay actually competitive rates (not "competitive" = below market)

  • Hire for potential, not perfect stack match

  • Have a 2-week interview process, not 2 months

  • Focus on "can they solve problems" not "do they know our exact tools"

  • Offer realistic job descriptions

Engineers who are getting offers:

  • Have deployed projects anyone can see/use

  • Tailor applications to specific companies

  • Network instead of just applying cold

  • Show depth in one area vs surface knowledge in 20

  • Can explain their technical decisions in plain English

The "talent shortage" and "I can't get hired" problems are THE SAME PROBLEM.

Companies and candidates are screening each other out before ever talking. Companies want seniors but post entry-level salaries. Engineers apply to everything and fit nowhere specifically.

Nobody wants to compromise. Companies won't train. Engineers won't specialize. Both sides are waiting for the other to blink.

I think the fix is for:

  • Companies: Stop requiring 5 years experience for everything. Hire smart people and give them 3 months to ramp.

  • Engineers: Stop spraying applications everywhere. Pick 5 companies you actually want to work for and make them want you.

  • Both: Get on the phone. One conversation reveals more than 10 rounds of async screening.

Are you on the "can't find talent" side or the "can't get hired" side? What's your actual experience vs. what everyone claims is happening?

Because from where I'm sitting, both sides are suffering from the same broken process, and everyone's too proud to admit it.


r/softwareengineer • • Jun 10 '26

Elon Musk: Coding Was a Top Job for Decades. It Will Be Dead By the End of the Year.

70 Upvotes

Elon Musk believes that traditional programming will soon become obsolete because advanced AI systems will directly generate highly optimized machine code and binaries, bypassing human-readable programming languages entirely.

Musk has stated that writing syntax is an intermediate step that will be phased out. Instead of compiling high-level languages, AI models will directly output machine code optimized beyond human logic. The focus of software development will shift entirely to defining system architecture, validating outcomes, and constraining AI tools to build complete applications based on human intent.

Sounds like bad news for entry-level and junior SWEs?


r/softwareengineer • • Sep 27 '26

Any real SWE here? in Uni they teach us System Design, DSA, like Bubble sort, Array, and so on. Do you think it is worth it to teach those topics to future coders in the future under AI era?

1 Upvotes

I'm sure many SWE use AI to code faster and smartly today

And in reality of programing world there is the term "distributed system" where the real SWEs use and work with it every single freaking day to build production grade codebases that sometimes you need to patch bugs when things break!

hahahahh

Joke aside

As the title says.


r/softwareengineer • • Aug 31 '26

The weirdest thing I learned about software: the hardest problems/features are often the ones users never notice

0 Upvotes

I used to think good software was mainly about adding more and more features.

More buttons.
More settings.
More integrations.
More automation.
Attractive and Catchy UI.

Then I started paying attention to the software I use every day and from what I have built till now, I realized something:

The best software often does more by showing you less.

Think about what happens when you upload a file.

You click upload and it appears within a few seconds.

You don't see the network request.
You don't see authentication.
You don't see the database.
You don't see file validation.
You don't see caching.
You don't see error handling.

And that's exactly the point.

A huge amount of good engineering is basically:

How much complexity can we remove from the user's world without removing a software capability?

This changed the way I look at software.

For example, a feature that takes a developer 3 days to build might save the user 30 seconds.

That sounds like a bad trade.

But if 100,000 people use that feature every day, those 30 seconds become 833 hours saved every single day.

Suddenly, the boring little feature is more valuable than the flashy one.

I have also started noticing the opposite.

Some software has dozens of features, but every task feels like work.

Other software has relatively few features, but somehow you can accomplish things incredibly quickly.

The difference isn't always the feature count.

It's friction.

Every unnecessary click, confusing message, slow screen, repeated input, or decision the user has to make adds a tiny amount of friction.

One second doesn't feel important.

A thousand one-second frustrations are.

So When a software is really good, you don't think:

Wow, that's some impressive engineering.

You think:

That was easy.

And ironically, easy can be one of the hardest things to engineer.

Curious what other people think on this topic:

What's a piece of software you've used where you suddenly realized, Wow, someone put a LOT of work into making this feel simple?


r/softwareengineer • • 23d ago

Why are we still defaulting to heavy front end frameworks?

0 Upvotes

I see with AI use we are spending more tokens and time on a front end issue than is actually needed.

I won't discuss React Vue or pick a js framework, I will just say bolting these into anything other than a node app makes zero sense to me now.

For want of a better phrase this does not really match my taste anymore and the costs it includes in tokens when needing heavy abstract trees to understand x or y framework is just a waste.

I need a framework I don't need to patch every dam day and that's where I am at.

Pre AI I would have said Vue or react or x, now I am thinking why what's the point, just move the state back to the server where it belongs.

Give me your experiences and what's working for you.


r/softwareengineer • • 27d ago

Are tech layoffs really because of AI, or is AI just part of the story?

21 Upvotes

I don't think all these layoffs are happening just because of AI. I feel like there might be more to the story.

Recently, I came across a post from a PayPal employee who mentioned that after layoffs in their team, the remaining employees were expected to take over the work of the people who were let go. Even if the roles were still needed, the company wasn't necessarily hiring replacements.

I also recently spoke to a friend who works at a product-based MNC. According to him, the situation isn't just about AI replacing people. AI is definitely helping developers write code and complete tasks more efficiently, but he believes the bigger problem is the lack of new projects and clients. He mentioned that his company hadn't acquired a new client since 2024.

This got me thinking: Are companies actually laying people off because AI can do their jobs, or are they using AI as part of the explanation for broader economic problems, reduced business demand, and cost-cutting?

Another thing I wonder about is whether companies are reluctant to openly acknowledge that their business growth or demand has slowed down, especially when they need to maintain investor confidence and stock prices.

I'm not saying AI has no impact on jobs. It clearly has the potential to change how software development works. But I find it hard to believe that AI alone explains everything happening in the job market.

For those working in IT, especially in product-based companies:

  • What is the actual situation inside your companies?

  • Are layoffs happening because AI is genuinely replacing employees, or are they mainly due to fewer projects, reduced client demand, and cost-cutting?

  • Are companies still hiring, or are they simply making existing employees do more work with fewer people?

I'd genuinely like to hear perspectives from people working in the industry rather than just relying on headlines and corporate statements.


r/softwareengineer • • Jul 30 '26

Working as an "AI Engineer" intern but Claude Code does most of the actual coding - is this the new normal?

6 Upvotes

So I'm currently interning as an AI Engineer at an AI startup (they build physics-grounded AI systems for datacenters - that kind of deep-tech B2B stuff). On paper my role is heavy engineering - working on multi-agent pipelines, RAG systems, validation layers, the works.

Here's the thing though - the company gave me Claude Code access from day one, and honestly, that's how I get most of my actual work done. Writing the code, drafting architecture docs, debugging, even structuring how the agents talk to each other - a huge chunk of it goes through Claude. My job has shifted from "writing code line by line" to "figuring out the right problem, designing the system, and directing the AI to build it correctly."

It's not that I don't know how to code - I do, and I still read/review/fix everything that comes out. But the actual muscle-memory "typing out the logic myself" skill barely gets used anymore. It feels less like traditional development and more like being an architect/reviewer who happens to know how to code.

This has me wondering - is this genuinely where the industry is heading, or is my experience specific to working at an AI-first startup?

For people working at other companies (product-based, service-based, startups, MNCs) - are you seeing Claude Code / Cursor / Copilot etc. become this central to actual day to day dev work? Or is hands-on coding (without AI doing the heavy lifting) still the norm where you work?

Genuinely curious how widespread this shift is, and whether people think it's a good thing for skill development long term or something to be a little worried about.


r/softwareengineer • • Sep 21 '26

What developer tools are still missing in 2026?

0 Upvotes

I'm a long-time software engineer and am currently between jobs. Because of the state of the job market a new role seems to be really difficult to come by. On that note, to keep my skills sharp, I’m looking at ideas for building new dev tools and I’d like to hear from people who run into problems daily.

What’s a workflow, debugging step, integration, automation, or pipeline that is difficult to use? Also, what tool do you wish existed?


r/softwareengineer • • Oct 17 '26

Just curious I saw some people they go to cafe, Startbucks or somethingl and code only using one laptop. But normally at work devs use 2-3 monitors. Isn't it uncomfrotable working with just 1 monitor?

1 Upvotes

As the title says.


r/softwareengineer • • Sep 25 '26

How much AI usage do you get a month at work?

1 Upvotes

We each get $3000 a month. I'm curious how that compares around the industry. Do you use your allotment?


r/softwareengineer • • Jul 14 '26

I'm eyeing a software engineer career, where did you learn your essential skills to land a job?

1 Upvotes

I'm having a hard time processing where I should learn all skills that the jobs want. I don't even know what are all the skills I need to get a job so if someone could enlighten me what skills got you a job and where you learned those, I'd appreciate it immensely.

Also, since I'm just starting to get in touch with what software engineering is, I ought to have some misconceptions and holes in what I know so I want these misconceptions pointed out and what I should know before I pursue this career.


r/softwareengineer • • 5d ago

SWE in the age of AI: what is the difference between senior SWE and entry level now since AI can deliver?

0 Upvotes

Hi everyone, Im 21, just graduated in Bachelor of Computer Science.

I am currently having an internship for a startup, and I have been thinking a lot about this career lately.

Unlike some of you guys who may have years of experience in this field, I have completely none. And I started my career when frontier models are getting better and better, and most of the code (in my company) are now delivered by agents all the time.

My main goal is to get better as a SWE, by all means.

But I am a bit confused right now, so forgive me if my question is a bit nonsense. but: What differentiates a Senior SWE and a Junior/lower level SWE right now?

I have been reading a lot recently, and almost everything I see is that Senior can review, have more knowledge, etc. But from what I see, I believe that when given a task, I can still deliver it, probably as good as what the company expects, since I will have all my agents running for me.

So I really want to know what is the difference, what I can learn to be a better SWE, instead of running agents all the time. I can see that there will be advice on learning the fundamentals, learning the system design, but how accurate is that since now I can still ask AI to give me options and then choose from it?

Once again, sorry if this is stupid, but forgive me since I am new to the industry, and have this question on my mind for a while, which makes me really confused.

I appreciate all the advice and would love to hear opinions on this!


r/softwareengineer • • Sep 14 '26

is that normal for a software or ide at all to be over 60gb?

0 Upvotes

talking about visual studio that is 67gb packed and i believe more than double after install.

here is a screenshot of it and few other versions of vs:

https://ibb.co/hxgzxBFx

it just caught my attention seeing software like visual studio being so big.

is that reasonable for the work you are doing? do you think it should be normal having to have such a puffed up bag slamming your harddrive to just code?

what is it that has to be so big inside a code editor?

i left win and mac long time ago and only use the lightest software that are out there and of cause open source like sublime or vim for developing or ffmpeg, krita, gimp, blender etc.

i get when games reach sizes beyond 20gb for flight simulation and stuff. but as software engineers. is it not the point to be as efficient as possible?

what is the point of "stack overflowing" the hardware of ppl, before even doing anything with the app. just starting the app eats up half your ressources. that somehow feels wrong to me.

do you have an opinion? i really would appreciate it a lot, sharing your thoughts with world:)


r/softwareengineer • • Aug 29 '26

Hot take: most developers don't need another framework.

0 Upvotes

They need to get better at understanding the business they're building for.

You can write beautiful .NET/Angular code.

But if the software doesn't solve the actual business problem...

It doesn't matter.

Agree or disagree?


r/softwareengineer • • Aug 19 '26

I'm feeling guilty from using AI to code

4 Upvotes

I'm graduating computer science this year from uni, and for the majority of it, I did not use AI at all. I learned a lot of things from different branches of computer science, so I felt okay applying to any jobs, but this year I got a part-time job at a small software development company. For the first couple of months I barely used any AI, I used it sometimes to check some of my code, but the majority of it I did myself (learning new frameworks and sorts). But now I'm almost a year into the job, I use Claude Code for everything, and it makes me feel kinda shitty. It feels like an inevitable change since, competitively, if you don't do this, your company will fall behind. Everyone is getting dozens of pull requests every hour because of this tool, but then again, I feel like my brain is "getting smoother" the more I use it. The most complex thing I have to do is usually understand the business behind what we're developing, and know how to make prompts as precise and clear as possible.

Of course, what I'm doing is more than just programming, but what's the point of telling the AI to do the things for me after studying these things many years? What's my job gonna look like in a year, or two, or ten? Am I going to keep telling AI to do things for me? I'm having a bit of a small crisis on this idea and I wanna know what people from different perspectives think about it.


r/softwareengineer • • Jun 28 '26

AI writes most of my code at work. Am I hurting my career?

14 Upvotes

Hi everyone,

I'm a software engineer at an early-stage product startup, and the company provides Cursor AI Ultra, which I use extensively for development, debugging, and planning. Most of the implementation is AI-generated, and my job is primarily to review, understand, and refine the code.

Over the past month, I've also learned a lot about AI-assisted development—writing better prompts, optimizing token usage, creating effective rules, using plugins, and building reusable AI workflows. While these skills have improved significantly, I feel like I'm growing more as an AI-assisted developer than as a software engineer.

Outside of work, I'm studying system design, databases, and software architecture.

My biggest concern is switching jobs in the future. Most companies still assess candidates on DSA and system design. I can continue learning system design, but I'm not strong at DSA, and AI has reduced the need for me to practice coding from scratch.

Should I spend a significant amount of time on DSA, even though I rarely use it at work? In the AI era, what should an early-career software engineer focus on to become a strong engineer and stay competitive?


r/softwareengineer • • Aug 09 '26

How are some software engineers earning more than many highly complex professions?

0 Upvotes

I work in tech and sometimes wonder how some software engineers end up earning more than people in roles like airline pilots, air traffic controllers, aerospace engineers (Boeing/Airbus), nuclear engineers, surgeons, naval officers, or engineers working on major infrastructure projects.

Many of these jobs require years of training, licensing, and carry much higher responsibility.

Is it mainly because software can scale globally and generate revenue at a much larger scale, or is there something else I’m missing?


r/softwareengineer • • Jul 05 '26

Feeling like a "vibe coder" while trying to learn low-level development (OS dev, Bootloaders)

2 Upvotes

I’m really into low-level programming (C, C++, x86 ASM, Rust). Since it's hard to find comprehensive video tutorials on YouTube for advanced topics, I usually resort to searching the web. However, I often find the documentation and resources quite overwhelming and hard to grasp.

​To bridge the gap, I’ve been using AI tools (like Gemini and Claude Code) to guide me through building things like a bootloader and a kernel from scratch using C and Assembly.

​While it works, I can't shake the feeling that I'm becoming a "vibe coder"—just pasting code and hoping it works without truly understanding the core concepts under the hood.

​Has anyone else been in this loop? How can I transition from relying on AI to actually understanding low-level documentation and OSDev independently? Would love some advice or resource recommendations!


r/softwareengineer • • Oct 03 '26

My fav perk of being a software engineer

0 Upvotes

one thing i really like about being a software engineer is that whenever something starts annoying me enough i can just build something for it. Few personal examples, would like to hear about yours:

  1. few weeks back i started posting on instagram. i wanted people to get a dm automatically when they commented a keyword. looked at few tools, all of them wanted monthly money, didnt feel worth it. so i spent my sunday afternoon and built it myself.

works exactly how i wanted and most importantly, if i want to change something i just change the code.

2) same thing happened with another problem. in this era of information overload,i save way too much stuff: reels. youtube videos. bookmarks. reddit posts. screenshots. random notes etc. etc.

saving was never the problem, finding them again was. i remembered what i saved, but never remembered where.

after getting frustrated enough i built a small tool for myself. now i dont care where i save things. i just dump everything there, later i ask stuff like: "what should i pack for my next trip?" or "show me that reel about storytelling i saved last month" and it finds it.

i realized i use these random little tools more than a lot of apps on my phone. none of them were startup ideas. i just got tired of doing the same annoying thing again and again.i think thats my fav perk of this job.

you dont have to wait for someone else to build the thing you want. you can just build it yourself.


r/softwareengineer • • Jul 25 '26

Will experienced engineers still have a meaningful advantage over AI-native vibe coders in 5–10 years?

17 Upvotes

Today, experienced engineers still have a clear advantage when it comes to architecture, scalability, robustness, trade-offs, debugging, and operating software in production.

But what about 5–10 years from now?

If AI keeps improving at its current pace, will the experience of the engineer behind it still be the biggest differentiator?

Or will an AI-native beginner be able to deliver software that’s just as scalable, robust, and maintainable?

Where do you think the moat for experienced engineers will be?


r/softwareengineer • • Jul 26 '26

What would happen if every AI coding tool disappeared tomorrow?

3 Upvotes

Hypothetical scenario.

Every AI coding tool disappears tomorrow.

How long would it take you to readapt?

What happens to developers who started their careers after the AI boom?

Would juniors struggle to get their first job?

Would senior engineers suddenly become much more valuable?

Would salaries go up or down?

Would the software industry slow down for a while?