r/softwareengineer • • Oct 09 '26 Regret

Software Engineering in 2026 is degrading rapidly

2.2k Upvotes

I don't want to add my voice to those "AI is taking our jobs" doom-and-gloom posts, but something has really given me pause. I work on a software engineering team, and like so many others, we now have agents generate 100% of our new code. What strikes me, though, is the indifference that has crept in. A pull request is submitted that changes 60 files - and two minutes later, people have already approved it with LGTM - absolutely impossible that they actually reviewed the PR. We expect the code to do what it's supposed to because it was generated by Opus 5.5 anyway and the tests passed. But when you take a closer look, there are comments in the code like "correlate retry logs with code evidence" - what on earth is that supposed to mean? If you ask questions in the PR, the engineer uses AI to generate 10 paragraphs justifying that comment. Just like getting flooded with a lengthy AI generated response will shut down critical questions. Then the engineering manager asks, "Why is your review taking so long?" and everybody just seems to be fine that we generate something that looks like it does what it should but nobody cares anymore how we do it because there is time pressure and we need to deliver.

I'm not sure if I can work much longer in an environment like this and I'm wondering if this is just my team or really what the industry has become.


r/softwareengineer • • 7d ago Bravo

I Miss Coding the Way It Used to Be Before AI Changed Everything.

1.2k Upvotes

I kinda miss the days when I’d sit down and think about how I wanted to implement a certain feature. I’d research it, learn how things worked, figure out an approach, implement it, and then keep refining it until I was happy with the result.

Sometimes I’d run into a problem that felt almost impossible to solve. I’d spend hours thinking about it, maybe take a nap, and somehow wake up with an idea. Sometimes I’d even dream about possible solutions. It sounds silly, but I genuinely miss that feeling.

Now, it’s mostly just writing a prompt and hitting enter. No real implementation, barely any code reviews, and sometimes I don’t even look at what’s happening behind the scenes.

Don’t get me wrong, AI has been incredibly helpful. It saves time, helps me learn new things, and makes tackling complicated problems much easier. But it also comes with its own frustrations. Sometimes I spend more time explaining what I want to an AI agent, correcting it, and going back and forth than I would’ve spent just building the thing myself.

And honestly, I’m starting to feel like I’m losing my ability to write even simple code without assistance.

I don’t think AI is necessarily a bad thing. It’s just that somewhere along the way, I stopped enjoying the actual process of programming.

I miss figuring things out. I miss the frustration of debugging something for hours and the satisfaction of finally getting it to work. I miss building things my way, making mistakes, learning from them, and slowly getting better.

I genuinely miss the way I used to code and build things. And I think that’s what I miss the most.


r/softwareengineer • • Aug 03 '26

Today was the day I felt the industry crumbling

1.0k Upvotes

About a year ago my current employer pushed hard on AI tools adoption. They wanted everybody to use Claude/Codex/Copilot to write code because "it is so much faster".

Fast forward to 1 month ago, they introduced several contractors that are "AI specialists" and got them to build an autonomous agentic development tool. Over the month they have vibecoded (their words) this tool and today they have released it to the broader team, and leadership are mandating us that we use this tool for our work.

The tool is just a glorified workflow, it takes in a Jira ticket number as input, and vibecodes it until the thing is deployed in Production. They don't want us to open the terminal, the IDE or even Github, just this tool.

This is a medium sized company, there are clever engineers here but it is not an industry pioneer. I have the feeling my leadership team are completely delusional. If this is happening to me at this company I can't imagine how crazy it is at other companies closer to technology.

I'm 38yo, started programming at 14yo, MSc in CS, 15y professional career... I've lived through several industry-wide changes.

But today... Today I've lost hope. The craft is gone for me. The only way I see out of this is costs spiraling out of control at the industry level. I don't see this happening.

Should I look for work somewhere else, or is it the same everywhere else?

Also, how are you faring? Do you see a way out for us?

---

EDIT

Thanks everyone for your comments. From what you shared I can gather several things that you all seem to agree on: I see it is clear it is an industry thing and not just my company. I wanted to clarify that I do not have an issue with using AI tools at the individual level, just with the mandate to reduce the entire work to just "managing a clanker". There is a clear worry that following that path leads to an inevitable degradation of quality and maintainability of the products we put forward. I believe writing the code was already the easiest part of the job, and as such these tools are not truly speeding up development. The bottleneck was and remains outside of the actual programming. Whatever happens to this industry, I wish you all the best.


r/softwareengineer • • Sep 02 '26

AI is terrible for making documentation

855 Upvotes

Yes, it makes a lot of text real fast and at a glance it looks thorough and comprehensive but have any of you actually tried reading this shit?

It's painfully verbose while communicating next to nothing. It's a real struggle to not have your eyes glaze over. It's not enough to just produce a lot of text if the readability is crap. There's a skill to creating concise, well organised information that's been lost here.


r/softwareengineer • • Jun 23 '26 Bravo Popcorn

AI is ruining my job as Tech Lead

853 Upvotes

I hope this post won't be removed.

I'm a Tech Lead.

A year ago, my developers were writing their own code.
Today, more and more PRs feel like they're 90% AI-generated.

The ticket says A, the code does B.
Business rules get ignored.
There are AI comments everywhere.
Tests exist, but don't actually test anything useful.
Random abstractions appear for problems nobody was trying to solve.

The company I work for is very pro-AI. Every time I complain about this stuff, I feel like I'm seen as the old guy not being able to live his time (I'm 28 btw).

The answer is always the same: "Well, you're the Tech Lead. Manage your team."

The problem is that AI made my developers faster, but it made me slower:

They generate code, open a PR, and move on.
I review it.
I leave 10 comments.
They ask the AI to fix the comments.
I review it again.
Half the fixes are still wrong.
Repeat.

My review time has easily tripled over the last year. And since I'm the one responsible for what goes to production, I can't just approve it and hope for the best.

What frustrates me the most is that nobody seems to count this cost. The developers save time. The Tech Leads and senior engineers pay for it.

Honestly, I'm starting to lose motivation.
I liked reviewing code written by developers.
I don't like reviewing code written by an LLM through a developer.

Has anyone else been dealing with this?
And if so, how did you get your team to understand the problem?


r/softwareengineer • • Sep 12 '26

Am I the only one that is not impressed with AI coding?

696 Upvotes

I ‘m a software engineer for the past 12 years.

Since AI-assisted coding began to appear I ‘ve been reading about those huge productivity gains and how the whole job will change.

When I try to work with Claude Code (from Opus 4.6 -> Fable 5.1) i often get verbose, bug ridden code that before the appearance of AI nobody would have make anyone ashamed of adding to a PR.

The biggest issue I have is that you just can’t trust it to not mess up even the easiest task and you have to review every line. This seems often much slower then the whole process od writing it myself since I have a better understanding of the code base if I write it myself.

If I try to keep the changes minimal and only change a class or method I feel by the time I gave the right context I could ‘ve changed it in a similar time.

If I give it a larger scope I get a wall of code I have to test and make sure it’s working whatever happens.

Only part where I can find value is UI design, mostly because it’s pretty easy to review the changes and test them.

Does anyone has the same experience or is it a skill issue?


r/softwareengineer • • Oct 12 '26

I feel like I'm in Truman show.

682 Upvotes

Hello. I see a lot of people, who are on Reddit that claim they don't write code anymore and do 100% of the work using agents. On the other hand, everyone I know in person that is working in the field, doesn't trust AI as much, and uses it as a buddy, uses it for boilerplate code or lets it write methods at most.

How come opinions are so vastly different?

EDIT: I've noticed that comments that say stuff like "if you still coding, you are doing something wrong" are all 1 year old, have their comments and posts set to private... 😮‍💨


r/softwareengineer • • 6d ago

We stopped hiring juniors. I think we just cancelled the residency.

501 Upvotes

This hiring cycle is the first one where I've watched teams leave the junior seat empty because AI does what they used to do.

The junior seat was never mainly about the output. It was where you learned the things no school teaches: how to debug something that lies to you, when a design is wrong even though it works, and the habit of refusing to leave a thing at a B. You learned it on dull tickets, with a senior reading your diffs and asking why.

The model took the dull tickets and the diffs. In my shop bots file issues and open PRs for small fixes around the clock, and a human merges a dozen of them each morning. The fixes are good because a human thought about the system and wrote down what good looks like. Someone has to become that human. I don't see where they're being made now.

Is anyone deliberately keeping an apprenticeship running alongside the tools? What does it look like?


r/softwareengineer • • Aug 25 '26

Was Just Told That Code Quality No Longer Matters

495 Upvotes

I'm a freelance developer. I have been for almost 20 years. My most recent project has been moved to Fable, and I'm still trying to adapt and get my head around working like this. I am no longer allowed to make architecture decisions, or clean up slop.

My PM says: "We worry about the 'what'; let Claude worry about the 'how'. Tell it what to do; let it do it. If the feature works, leave it alone." He is very much of the opinion that I should be able to prompt something like "Install Stripe via Laravel Cashier" and just let Claude run.

I mean, why do you need me at this point? Just prompt it yourself until it does what you want? I don't get it. I fought for every inch of my knowledge, every process is written in blood. How do I just throw all of that out the window? Where's the line?

At the risk of another "how are you adapting" post... How CAN I adapt? I mentally cannot just say "Fuck it". I care about my code. It's how I learned, it's how I've always practiced. I have a huge mental block with "just let it go".

Now, granted, I don't know all of the ins and outs of Claude. I don't know what I can do to make it better at its job. I got thrown into the middle of the Pacific Ocean in the middle of a Tusnami with no life support. I'm sure that I can put guardrails in place, but how much does that help?

I would really appreciate any advice that any one can provide on changing my mental model. I can't ignore Claude and just keep doing things my way. If I do that, I feel like my career dies. I need to adapt and I'm unsure how to do so.


r/softwareengineer • • Sep 24 '26

Anyone Still Manual Coding?

427 Upvotes

My company still lets employees manually code because they want people to understand the codebase. We have Claude accounts which we can use as much as we want, for generation, testing and reviewing. The one rule we have is all code must be capable of being reviewed by a human (so no several thousand line PRs, where the only solution is to let AI review).

Given the increasing use of AI (as perpetuated by the media and all CEOs who claim to have fired their engineers), how many of you are working like this? I feel like it's very rare now.

EDIT: quite surprised at how many people still manually code and are loving it (acknowledging this is a minuscule sub-set of all SWE out there). The meat proxies are growing though under corporate pressure to ship fast. I shall enjoy while I can!


r/softwareengineer • • 25d ago Regret

Modern code reviews suck

415 Upvotes

I hate getting pinged on code reviews now. You're handed 50+ file PR's that are 100% AI generated, and whenever you ask someone to explain what's going on, there's a conspicuous 90 second gap as they clearly re-ask claude to give you an explanation to what they just did. It's brutal.


r/softwareengineer • • Sep 27 '26

The Great Cluster F.... is Coming

347 Upvotes

Lets "try" and consider Microsoft Access. Here was an application handed to office workers who had zero training in coding, application design, workflow, reporting or database design.
Anyone could do it. Just use the "Wizard"

IT shunned the product
All self written products were not supported
When the person who wrote them left no one had any idea how. to maintain them.......

DE JA VU

Now image MSA on steroids, every time you ask an AI to write some code it returns something slightly different. Imagine the writer has never done any application development before.

Recently I came across a club that was getting its software rewritten by a super hero (who has never written an app before).

The app included: live web pages

Bankingdetails includingcredit card numbers and automated banking
Personal details including DOB, Address etc.

and more with NO testing plan.

This was all put on a web server and linked to cloud services. Even the author had no idea how it worked. Al generated the lot by prompts.

Now image the world with "millions" of these insecure poorly designed "CRAP" systems everywhere.

This is the great CF....

Be happy AI will create a job for you for the next 30 years ......


r/softwareengineer • • Sep 03 '26

Never work on a completely vibe coded project

342 Upvotes

I've now made a same mistake twice.

Previously, I worked at a startup where the website was completely vibe-coded. Now I'm working on a college website, and it's the same story: the entire thing was vibe-coded.

The common pattern I've noticed is that no engineer actually knows the codebase. Nobody really understands the architecture, the reasoning behind certain decisions, or how all the pieces fit together.
And eventually, even the AI I'm using can't help much because it doesn't have the context that the original developer's agent had while building the project.

I am basically stuck where I know nothing, the existing engineers know something about it but aren't necessarily sure whether their understanding is correct, and the agent hallucinates and wastes a lot of tokens just because it can't understand a huge AI written codebase.

So now I'm the new engineer, under a lot of pressure with a lot of work to do, but before I can even fix anything, I have to reverse-engineer what the hell the previous AI generated. That wastes a lot of time.

The frustrating part is that I'm not really learning much engineering from this. I'm just spending my time trying to understand an undocumented system that nobody else understands either.

I'm not against AI-assisted development at all. If an experienced engineer uses AI properly, reviews the code, understands the architecture, writes tests, documents important decisions, etc., I think it's incredibly useful. Even I use AI to code faster, but I review and understand the code. I know what is happening in my software.

But a codebase that nobody understands is a codebase that nobody can safely maintain, regardless of whether AI or humans wrote it.

At this point, I've decided I'd never want to work on a heavily vibe-coded project again unless there's at least one person on the team who genuinely understands and owns the codebase.

How do you guys handle inheriting a vibe-coded/AI-generated codebase that nobody on the team actually understands?


r/softwareengineer • • Jul 24 '26

Developers from the pre-AI era: do you miss the dopamine of solving hard problems?

315 Upvotes

Genuine question for developers who were building software before AI became part of our daily workflow.

Do you remember spending days (or even weeks) solving a difficult programming problem or building a feature that felt impossible at first?

Reading documentation, trying different approaches, debugging, rewriting parts of the implementation… until everything finally clicked.

AI has made me much more productive, and I wouldn’t want to go back.

But sometimes I feel we’ve traded part of that dopamine for speed.

Does anyone else feel this way, or is it just me?


r/softwareengineer • • Oct 17 '26

genuinely asking, is anyone's workload actually smaller because of AI or is it just me who is baffled.

284 Upvotes

so my manager sent a message in standup last week that was basically "this should be quick with cursor right" about a migration that touched like 40 files. and I just stared at it for a bit because yeah, cursor wrote most of it in 15 min. then I spent the rest of tuesday and half of wednesday figuring out which parts it quietly got wrong. it renamed a column in one place and not the other three. no error, just wrong data in staging for a day until someone noticed.

that's not the point though. the point is a year ago that migration would have been estimated at a week and nobody would've blinked. now the number everyone has in their head is "quick". because they also have copilot and they've seen it do the magic trick.

I keep seeing people say AI made them 3x more productive and I believe them honestly. but then I look at their calendar and its worse than mine. so where did the time go lol

what I think happened at least at my place

the typing part got fast. the checking part got slow and also nobody counts it as work. reviewing 400 lines someone else (something else) wrote is more tiring than writing 100 lines yourself, idk why, it just is. but on a timesheet it looks like I did nothing for 3 hours

and every hour it saved just got a new ticket dropped in it. the backlog didn't shrink. it never shrinks. it's not a thing that shrinks

also we hired nobody this year. team of 5 doing what was planned for 8 and the 3 missing people are "AI". ok

im not even anti AI, I use it all day. I just think the people most excited about it are the ones who never have to debug the output at 9pm. my founder is thrilled. linkedin is thrilled. me, less so

anyway. not output, I know output went up. hours. have your actual hours gone down. because if the answer is no then what exactly got "automated"


r/softwareengineer • • Jul 17 '25

Why do so many engineers plateau at mid-level?

282 Upvotes

Hey everyone — I’ve been thinking a lot about this lately.

I've seen plenty of smart, capable engineers doing solid work… but still getting stuck around the mid-level. They’re not getting promoted, not moving up, and not really sure why.

Curious to hear from this community:

What do you think holds engineers back from reaching senior roles?

Some ideas I’ve seen come up:

  • Not being clear on what’s actually expected

  • Doing good work, but not getting visibility or recognition

  • Confidence issues or imposter syndrome

  • Lack of mentorship or guidance

  • Something else?

If you’ve gone through this yourself, or are currently going through this — or seen others get stuck or grow past it — I’d love to hear your perspective.

What helped you (or them) break through?

EDIT: Seeing a lot of gold here! Will use ChatGPT to summarise the discussions into key points and update the post for others to see!

This is the high-level ChatGPT summary of all the discussions and thoughts below in the threads:

1. Senior titles vary by company
Some companies grant senior titles based on tenure or vague criteria, while others require clearly defined senior-level work.

2. Many settle into meeting expectations
Engineers often do solid work—but simply meeting expectations doesn’t translate into promotions.

3. Senior level requires different behavior
It’s not more coding—it’s stepping up by leading discussions, mentoring, and taking broader ownership—even if that doesn't come naturally.

4. Visibility is key
If your work isn’t seen or tied to business outcomes, it often gets overlooked—even if it’s technically solid.

5. Soft skills become essential
Things like communication, influencing decisions, and building relationships become more important than raw coding as you move up.

6. Title inflation exists
At some companies, a senior title might mean less than a mid-level one elsewhere—so progression depends heavily on how each company defines levels.

7. Plateauing can be intentional
Plenty of devs hit a comfortable mid-level and choose to stay there—sometimes that’s by design or due to other priorities.


r/softwareengineer • • Oct 17 '26

Management says anyone can become a Software Dev with AI. But what about anyone can become a manager with nothing?

278 Upvotes

Our senior management is thinking of laying off 60% of our Software Devs. They are saying today anyone can become a Dev with AI.

Many devs will be laid off and they are only keeping 2 senior devs + one junior dev.

How is this idea that "Anyone can be a Dev" been thrown around easily?

Seriously!?? Like any profession, software dev is a craft! AI can write code but someone needs to design, set it up, communicate with stake holders, etc...

And what about Senior Management itself?

Can I not say anyone can become a Senior Manager since... like forever??

Why is that not thrown around?


r/softwareengineer • • Jun 09 '26

I realised this might be the end for me

257 Upvotes

I’ve been playing the dev game for over 15y combined now, though it had been a hobby already for years prior to that. Not unlike many others who became interested in computers at a young age and naturally made it their job later on.

Mostly it’s been fullstack, riding the many hype waves, until my lay off nearly a year ago. Did many startups, scaleups, corporate, in place and remote – the lot.

The current armageddon is not something I’ve seen before, not even during 2008/2009. I had loads of interviews (lucky I guess considering other don’t even get them), some good, some bad, some great, but it doesn’t seem to matter, I still don’t have a job. And soon it will be a year, and after a ton of grinding and studying, I start to peacefully realise this might be the end of my career wave.

The fact is, even if I finally by some miracle of nature got a job, I‘d be just as screwed, knowing that the timer is ticking and any day could be my last, eventually sending me back to unemployment. It just looks so dreadful.

Part of me eventually came to realise that I might have finally found peace, in a way. I might not need to worry anymore.

If dev is completely over saturated/broken and is likely to be so for many years (no-one knows where all of this is heading, except that AI as a technology AND the AI economy has disrupted everything), then there might not be a need to worry about it anymore. The wave was great, it gave me an awesome lifestyle for the last 15 years, but it’s changed, and that’s OK.

With this peace comes the next question: What now? I’m 38. If retirement is at 65 (thats a big maybe), I still have 27 years to go.

Thats more than I’ve been working!!!

This is another realisation which I only happen to crack after a few weeks of: “might be too late to invest in a career move, I’m screwed”.

So, lots of time ahead, and that’s great for two things. For one, it gives me enough leeway to pick on another wave and hopefully ride it for another bunch of years. For two, I’m actually excited about doing something new.

See, that’s what turning your hobby into a profession and then living out from it for 2 decades does to you. You attach your whole identity to it, at least professionally, to the point where you don’t think you’d be able to do anything else. I’ll be honest – software dev/IT/computers fitted my personality traits so well, and on top of that I really just liked it. It was hard to imagine myself doing anything else.

Yet life goes on. Society evolves, the economy morphs, and technology progresses. It’s part of life and it’s all good this way, but it means we must adapt.

But again: What now?

I’ve been exploring other fields last week, and for some reason have become very interested in maths as of late. Which has made me think of Economics/Finance/Accounting/etc. these are all fields that I actually would have an interest in, yet they’re all fields where it seems that AI is coming in full force too!

I keep wondering myself - if AI is able to evaluate and “think“ about complex algorithms in code, it must be even better at anything that is spreadsheet-y, where logic or complexity the likes of deep branching doesnt even play a role!

Would I be screwing myself twice by trying to star a new career in those fields? Sure - my software eng skills would give me an edge - but how much really?

Anyway, just wanted to blow some steam off. I’m lost but hopeful at the same time, none of these issues change one fact: I love life, and want more of it.

BTW if you’re reading this and have or are in the process of transitioning off from software leave a comment - I’d appreciate any ideas that could help me!


r/softwareengineer • • Aug 21 '26

Thoughts of skill atrophy due to overuse of LLMs

253 Upvotes

I was not prepared for that I've witnessed. People with 10+ years of experience showing evident decline of reasoning and even understanding of basic stuff. Someone like that just implemented some library that no one of us ever used or even understanding it. PR has thousands of lines of code. The comment was "now we finally implemented this, thanks to AI". I was shocked. No one suggested that maybe we should first get familiar with the library.

The same person asked me recently why it had some errors in console even though console error message was basic stuff, which happens daily. I was shocked, honestly. I've never wound have thought that brain rot can happen so fast. Codebase is becoming the mess. I am afraid what will happen to the product in near future.

Also, other people, with same career length just nonchalantly said about new feature "AI did it all", like he didn't even checked. I asked colleague doing code review why did he approve it, considering it's not very optimally implemented. He just said to me: "don't ask me anything please", like he had no choice.

I feel like I'm living in a bad dream. It's very demotivating. It feels like all my efforts are meaningless - double checking everything, thinking for hours about most optimal solutions - while many others just don't bother. Lines of cognitive depth are piling up. It's like this has became the opposite of what software engineering really is.

Where will all this go? What do you think? Is there a chance that things may eventually go back to normal. Because, now, it feels like many are going crazy.


r/softwareengineer • • Jan 27 '26

Opinion: Skilled Software Engineers will become exponentially more valuable due to AI

247 Upvotes

As the title says. I believe skilled software engineers will become more and more valuable to companies as AI slop continues to be pumped out.

AI is currently trained mostly on human written code - be it from existing codebases, github repos, stack overflow and is getting better and better right now.

However, as more and more code is written by AI, and new languages come out, future models will be trained on low quality ‘AI slop’ and will get worse and worse over time in a doom loop.


r/softwareengineer • • Sep 24 '26

Skill Atrophy Is Real!

246 Upvotes

I'm a software engineer with about 7 years of experience doing full-stack development. I consider myself a "T-shaped" developer. I specialize in the backend, with the ability to produce frontend deliverables. I also have a good understanding of infrastructure and have always contributed to infrastructure and team practice improvements through the introduction of continuous integration and continuous deployment best practices.

This past year, our product manager has set ridiculous expectations and deadlines. Through the power of politics, he has convinced leadership that ANY feature is achievable in a short period of time, usually less than a quarter.

Our director of engineering has great technical wits but is fairly new to actual management and, from the looks of it, politics as well. The reason that matters is because, despite his attempts to get a hold on things, it's a facade. The train is running at full speed, and he can't stop it.

With that said, the whole team has been using AI heavily. Let me expand on what I mean by heavily: none of us have written code by hand in months! We are using AI to plan out features, execute said features, and then using AI to review AI-generated pull requests.

We're at a point where the unwritten/unspoken rule is: DO NOT WRITE CODE BY HAND. The engineers who resisted using AI were pulled to the side and strongly encouraged to start using AI.

Due to all this, I know I am getting dumber. I started struggling with communicating technical decisions, making architecture trade-offs on the fly, and even thinking ideas through beyond a few chains of thought.

Here's the beautiful part: the company isn't paying for our token usage, so technically, we're paying for our own destruction.

Overall, I know this just means I need to spend time staying sharp.

I just hate the position I'm in. I've dug myself into a hole where I have to fight my way to the top just to jump ship.


r/softwareengineer • • Jun 19 '26

This feels (and is) different

241 Upvotes

I've been a software developer for nearly 50 years.

I lived through mainframes, minicomputers, personal computers, the Internet, smartphones, cloud computing, and more programming languages than I can remember.
Every technological revolution changed the tools, but the core of my profession remained the same: understanding problems, designing solutions, and writing software.
This feels different.
For the first time, it seems the technology is learning parts of the craft itself.
In previous transitions, I always knew what to do next: learn the new platform, the new language, the new framework.
Now I'm not sure what "next" even means.
I'm not afraid of learning AI. I use it every day.
What unsettles me is realizing how much of what I considered my profession may become abundant.
I'm curious whether other long-time developers are experiencing something similar.

Does anyone else feel like this transition is fundamentally different from the ones that came before?


r/softwareengineer • • Oct 02 '26 Bravo

After 8 months of searching, I finally landed my first software engineering job

240 Upvotes

I graduated from WGU with a B.S. in Computer Science in December of last year. Since then, I’ve spent the better part of nine months working as diligently as I could to find my first opportunity in the field. It hasn’t been easy. The tech industry is incredibly difficult to break into right now, particularly at the entry level.

Over these past several months, I’ve come to understand and resonate with many of the frustrations I see expressed here every day, the applications that go nowhere, the rejections, the uncertainty, and the feeling that sometimes your best efforts simply aren’t enough to get your foot in the door. Today, I received some of the best news I’ve had in a long time, I was hired for an entry level SDE I position.

I’m incredibly grateful for the opportunity, and I intend to give it everything I have. I also recognize how fortunate I am to have received this opportunity in such a difficult market. I will never take that for granted. I’ve seen countless posts from talented people who are struggling to find work, people who are discouraged, and people offering meaningful criticism of the current state of the industry. This post isn’t meant to dismiss any of those experiences. Many of those frustrations are completely understandable.

I just wanted to contribute a little hope alongside them. If you’ve committed yourself to this career and you’re currently facing a wall of rejection, don’t let that wall convince you that you have nothing to offer. Keep learning. Keep improving. Keep applying. Be realistic about the challenges in front of you, but don’t allow those challenges to make the decision for you about what you’re capable of becoming.

There’s a difference between recognizing how difficult the road is and deciding that the road leads nowhere. I’ve only just begun my career, and I certainly don’t know what challenges the future will bring. I’m not writing this from a position of wisdom or self congratulation. Eight months of searching followed by one opportunity certainly doesn’t make me an authority on anyone else’s journey. I’m simply someone who was discouraged many times along the way and finally received the opportunity I’d been working toward.

So for anyone who needs to hear something positive today.....hold steadfast. Keep improving. Keep putting yourself out there. Control the things you can control, and don’t let rejection determine your perception of your own potential. Sometimes the opportunity you’ve been working toward really does come.


r/softwareengineer • • Aug 05 '25

If you’ve ever felt like your work goes unnoticed, hope this helps

233 Upvotes

For all the engineers that are feeling invisible, stuck or plateaued, this is for you and hope it helps / guides you into the next steps. 

I am a senior software engineer who got to this position pretty fast, and got promoted over other engineers with 3-4x my YoE, so whatever I say in this post contributed massively to my growth, making my impact visible, getting me recognized, and eventually promoted. 

As a junior engineer, I was always awed by these senior+ engineers who seemed to make such an impact by whatever they did. This led me to start observing and building relationships with some of these really senior engineers around me (staff/principal) and learn how they operated, built that authority around them, and got stuff done, and something clicked. 

I realized it wasn’t just about technical skill and crushing tickets. What moved the needle was learning to communicate clearly, understand what impacts the business, build trust, build alignment between stakeholders, and be proactive (taking initiatives) instead of just reactive (wait to get assigned work).

There is usually a misconception, that to stand out, you just need to work on your technical skills. That is wrong. To get to senior+ you need to hone in on your non-technical skills like communication, how you take initiatives, how you build alignment etc. These are absolutely crucial to be seen as someone with authority, and something most engineers neglect and plateau.

A lot of engineers think that these skills are only required for managers etc, but they are wrong - even ICs require them. 

For these soft-skills (the real game changer), I would recommend focusing on good documentation (and I don't mean writing wikis/docs that no one reads, but being strategic with it) like writing summary docs to summarize complex discussions, writing well-thought-out design discussion tradeoff analysis docs to promote healthy, structured discussions and building alignment, etc. Taking time to write these up can not only promote healthy structured offline discussions (google docs for eg) but also act as an information aggregator for knowledge sharing (instead of being scattered on slack for eg or lost in meetings) and for having an audit log of important decisions - so in the future anyone can refer back to why a decision was taken and one doesn’t have to scramble to remember it, etc. 

The documents that you write now also help you to present your ideas and propose changes in a better manner in live meetings, where you can present that doc during the meetings and walk everyone through it - you don't need to memorize anything since all the information is already there in front of you, in a clean structured manner.

Speech is equally important - the phrasings used, the tonality used etc can immediately set an authority apart from a noob - this also translates 1:1 into slack threads, and code reviews as well. Small tweaks like that can instantly make someone come off as authoritative and knowledgeable.

I worked heavily on my speech. I was afraid to speak in meetings because I was introverted and had confidence issues because I had a bit of stuttering problem, I used to use too many filler words, lose track of thought etc. But I took time to work on it, and over time I started speaking more eloquently and fluently which made such a massive difference in my confidence, and whenever I had to propose something or even speak during meetings, it made a difference. 

Don’t get me wrong, technical skills are also important, but as you go up, your mastery of these other non-technical skills starts to matter more. They will make you more visible, your impact more visible, and eventually get you promoted. 

So I urge you to start working on them, you will be surprised just how much difference they make. 

If you are an introvert like me, if I can do it so can you. I used to think these soft skills are reserved for extroverts but I was extremely wrong, and these are most definitely learnable. 

Looking forward to hearing in the comments what has worked for other engineers out there as well!

Happy to answer any questions in the comments and DMs! I am an open book and happy to help however I can!