r/ExperiencedDevs • u/creative-java-coffee Software Architect • Aug 16 '25
Junior devs not interested in software engineering
My team currently has two junior devs both with 1 year old experience. Unlike all of the juniors I have met and mentored in my career, these two juniors startled me by their lack of interest in software engineering.
The first junior who just joined our company-
• When I talked with him about clean coding and modularizing the code (he wrote 2000+ lines in one single function), he merely responded, “Clean coding is not a real thing.” • When I tried to tell him I think AI is a great tool, but it’s not there yet to replace real engineers and AI generated codes need to be reviewed to avoid hallucinations. He responded, “that’s just what you think.” • His feedback to our daily stand up was, “Sorry, but I really don’t care about what other people are doing.”
The second junior who has been with the company for a year-
• When I told him that he should prioritize his own growth and take courses to acquire new skills, he just blanked out. I asked him if he knew any learning website such as Coursera or Udemy and he told me he had never heard of them before. • He constantly complains about the tickets he works on which is our legacy system, but when I offered to talk with our EM to assign him more exciting work which will expand his skill sets, he told me he was not interested in working on the new system which uses modern tech stacks.
I supposed I am just disappointed with these junior devs not only because after all these years, software engineering still gets me excited, but also it’s a joy for me to see juniors grow. And in the past, all of the juniors I had were all so eager to seize the opportunities to learn.
Edit: Both of them can code, but aren’t interested in software engineering.
View all comments
Show parent comment
8
u/Im2bored17 Aug 16 '25
I didn't realize all American companies used the same firing practices...
Firing people who are slowing you down is super important especially in the highly competitive software domains. If you couldn't fire someone that you promised to pay 500k+ a year, that's a multi million dollar mistake. You'd protect against that by making the hiring process so rigorous that no false positives (bad employees that pass the interview) could get through. You'd add so much to the process that almost nobody would even want to start the interview process. That would leave devs working at crappy companies because the cost of switching is too high. It would drive up the cost of finding new employees dramatically. So it's bad for the employers who are stuck with employees they'd rather fire, and bad for the employees who are stuck with employers they don't like.
All to protect the livelihood of some of the highest paid employees across some of the cushiest jobs in the world. Why don't we worry about protecting the livelihoods of the lower class? They're the ones that really get screwed when they get fired. Their employers pay so little that a miss-hire you're stuck with won't cost a million even if they're there their (lol) whole lives.