> We used to have a training ground for junior engineers, but now AI is increasingly automating away that work. Both studies I referenced above cited the same thing - AI is getting good at automating junior work while only augmenting senior work. So the evidence doesn’t show that AI is going to replace everyone; it’s just removing the apprenticeship ladder.
Was having a discussion the other day with someone, and we came to the same conclusion. You used to be able to make yourself useful by doing the easy / annoying tasks that had to be done, but more senior people didn't want to waste time dealing with. In exchange you got on-the-job experience, until you were able to handle more complex tasks and grow your skill set. AI means that those 'easy' tasks can be automated away, so there's less immediate value in hiring a new grad.
I feel the effects of this are going to take a while to be felt (5 years?); mid-level -> senior-level transitions will leave a hole behind that can't be filled internally. It's almost like the aftermath of a war killing off 18-30 year olds leaving a demographic hole, or the effect of covid on education for certain age ranges.
Adding to this: it's not just that the apprenticeship ladder is gone—it's that nobody wants to deal with juniors who spit out AI code they don't really understand.
In the past, a junior would write bad code and you'd work with them to make it better. Now I just assume they're taking my feedback and feeding it right back to the LLM. Ends up taking more of my time than if I'd done it myself. The whole mentorship thing breaks down when you're basically collaborating with a model through a proxy.
I think highly motivated juniors who actually want to learn are still valuable. But it's hard to get past "why bother mentoring when I could just use AI directly?"
I don't have answers here. Just thinking maybe we're not seeing the end of software engineering for those of us already in it—but the door might be closing for anyone trying to come up behind us.
> Now I just assume they're taking my feedback and feeding it right back to the LLM.
This is especially annoying when you get back a response in a PR "Yes, you're right. I have pushed the fixes you suggested."
Part of the challenge (and I don't have an answer either) is there are some juniors who use AI to assist... and some who use it to delegate all of their work to.
It is especially frustrating that the second group doesn't become much more than a proxy for an LLM.
New juniors can progress in software engineering - but they have to take the road of disciplined use of AI and make sure that they're learning the material rather than delegating all their work to it... and that delegating work is very tempting... especially if that's what they did in college.
I get that. I think that getting to know juniors outside of work, at a recurring meetup or event, in a setting where you can suss out their motivation level and teachability level, is _a_ way of going about it. That way, if your team is hiring juniors, you have people you have already vetted at the ready.
> Just thinking maybe we're not seeing the end of software engineering for those of us already in it—but the door might be closing for anyone trying to come up behind us.
It's worth considering how aggressively open the door has been for the last decade. Each new generation of engineers increasingly disappointed me with how much more motivated they were by a big pay check than they were for anything remotely related to engineering. There's nothing wrong with choosing a career for money, but there's also nothing wrong about missing a time when most people chose it because they were interested in it.
However I have noticed a shift: while half the juniors I work with are just churning out AI slop, the other half are really interested in the craft of software engineering and understanding computer science better.
We'll need new senior engineers in a few years, and I suspect they will come from a smaller pool of truly engaged juniors today.
> I think highly motivated juniors who actually want to learn are still valuable.
But it's hard to know if a candidate is one of those when hiring, which also means that if you are one of those juniors it is hard for you to prove it to a prospective employer.
> Adding to this: it's not just that the apprenticeship ladder is gone—it's that nobody wants to deal with juniors who spit out AI code they don't really understand.
I keep hearing this and find it utterly perplexing.
As a junior, desperate to prove that I could hang in this world, I'd comb over my PRs obsessively. I viewed each one as a showcase of my abilities. If a senior had ever pointed at a line of code and asked "what does this do?" If I'd ever answered "I don't know," I would've been mortified.
I don't want to shake my fist at a cloud, but I have to ask genuinely (not rhetorically): do these kids not have any shame at all? Are they not the slightest bit embarrassed to check in a pile of slop? I just want to understand.
>Now I just assume they're taking my feedback and feeding it right back to the LLM.
seems like something a work policy can fix quickly. If not something filtered in the interview pipeline. I wouldn't just let juniors go around and try to copy-pasting non-compilable Stackoverflow code, why would I do it here?
New students are presented with agentic coding now, so it's possible that CS will become a more abstract spec refine + verify. Although I can't make it work in my head, that's what I took from speaking with a young college student.
I don't know what world you're living in but software development has always been a cut throat business. I've never seen true mentoring. Maybe a code review where some a-hole of a "senior" developer would come in having just read "clean code" and use some stupid stylistic preferences as a cudgel and go to town on the juniors. I'm cynical enough to believe that this, "AI is going to take your programming job!" is just a ploy to thin out the applicant pool.
My hottest take on this is that it might be healthy for the business. During the recent boom everyone and their grandmother's dog got a job as software engineers, and some aren't really fit for it.
AI provides a bar. You need to be at least better than AI at coding to become a professional. It'll take genuine interest in the technology to surpass AI and clear that bar. The next generation of software professionals will be smaller, but unencumbered by incompetents. Their smaller number will be compensated by AI that can take care of the mundane tasks, and with any luck it's capabilities will only increase.
Surely I'm not the only one who's had colleagues with 10+years experience who can't manage to check out a new branch in git? We've been hiring people we shouldn't have hired.
The only problem is that people need to earn a living while they’re trying to get better than that bar.
Is there bar is set at a competent mid level engineer, people entering the industry need a path from algorithms 101 to above that bar which involves getting paid.
It's not helping that in the last 10 years a culture of job-hopping has taken over the tech industry. Average tenure at tech companies is often ~2 years and after that people job hop to increase compensation.
It's clear why people do it (more pay) but it sets up bad incentives for the companies. Why would a company invest money in growing the technical skill set of an employee, just to have them leave as soon as they can get a better offer?
When I'm hiring an engineer, HR will easily let me bump up the offer by $10-20K if the candidate counters. It is nearly impossible to get that same $10-20K bump for an existing engineer that is performing extremely well. Companies themselves set up this perverse incentive structure.
When using this phrase in this context, is your sentiment positive or negative? In my experience, each time I have a job offer for more money, I go and talk to my current line manager. I explain the new job offer, and ask if they would like to counteroffer. 100% (<-- imagine 48 point bold font!) of the time, my line manager has been simultaneously emotionally hurt ("oh, he's disloyal for leaving") and unsupportive of matching compensation. In almost all cases, an external recruiter found me online, reached out, and had a great new opportunity that paid well. Who am I to look away? I'm nothing special as a technologist, but please don't fault me for accepting great opportunities with higher pay.
> Why would a company invest money in growing the technical skill set of an employee
What exactly is meant by "invest" here? In my career, my employers haven't done shit for me about training. Yet, 100% of them expect me to be up-to-date all the time on whatever technology they fancy this week. Is tech training really a thing in 2025 with so many great online resources? In my career, I am 100% self-trained, usually through blogs, technical papers, mailing lists, and discussions with peers.
One would assume the solution is to simply offer a good package and retain employees with that. I returned to an old company after a few years of floating around because I realized they had the perfect mix of culture and benefits for me, even if the pay isn't massive.
You're falling for the exact same fallacy experienced by failed salesmen. "Why would I bother investing time in this customer when they're just going to take my offer to another dealership for a better deal?"
Answer: you offer a good deal and work with people honestly, because if you don't, you'll never get a customer.
> It's not helping that in the last 10 years a culture of job-hopping has taken over the tech industry. Average tenure at tech companies is often ~2 years and after that people job hop to increase compensation.
I've started viewing developers that have never maintained an existing piece of software for over 3 years with skepticism. Obviously, with allowances for people who have very good reasons to be in that situation (just entered the market, bad luck with employers, etc).
There's a subculture of adulation for developers that "get things done fast" which, more often than not, has meant that they wrote stuff that wasn't well thought out, threw it over the wall, and moved on to their next gig. They always had a knack of moving on before management could connect the dots that all the operational problems were related to the person who originally wrote it and not the very-competent people fixing the thing. Your average manager doesn't seem to have the capability to really understand tech debt and how it impacts ability to deliver over time; and in many cases they'll talk about the "rock star" developer that got away with a glimmer in their eye.
Saw a post of someone on Hacker News the other day talking about how they were creating things faster than n-person teams, and then letting the "normies" (their words not mine) maintain it while moving on to the next thing. Thats exactly the kind of person I'd like to weed out.
Funny, I was at my previous company almost exactly two years. They never even gave me a cost of living increase, much less a "raise." So I was effectively earning less each year. Change needs to happen from both sides if extended tenure is the goal.
You have cause and effect reversed. Companies stopped training workers and giving them significant raises for experience, so we started job hopping.
Some genius MBA determined that people feel more rewarded by recognition and autonomy than pay, which is actually true. But it means that all the recognition and autonomy in the world won't make you stay if you can make 50% more somewhere else.
They have this exact problem with scientific glassblowing, and it's been decades in the making. Manufacturing improvements now mean that you can buy almost everything from a factory, and only need experienced glassblowers for fancy, one-off stuff.
But that means there's no need for entry-level glassblowers, and everyone in the field with any significant experience is super old. The pipeline has been dead for a while now.
This will naturally select for the people who are self driven learners. In a sense this is nothing new, just a continued progression of the raising of the bar of who is still able to contribute economic value to the market
> AI means that those 'easy' tasks can be automated away, so there's less immediate value in hiring a new grad.
Not disagreeing that this is happening in the industry but it still feels like a missed opportunity to not hire juniors. Not only do you have the upcoming skill gap as you mention, but someone needs to instruct AI to do these menial/easy tasks. Perhaps it's only my opinion but I think it would be prudent to instead see this as just having junior engineers who can get more menial tasks done, instead of expecting to add it to the senior dev workflow at zero cost to output.
High risk bets like that cause bubbles. If that bet doesnt pay off then there will be a talent crisis that the american tech industry may not recover from
I think the current grads are going to be shafted either way. In 5 years, there might be more opening for "fresh" young grads and the companies will prefer them over the young people who're just graduating.
“automate it away” ironically still requires a human in the chain to determine what to automate, how, and to maintain that automation. Whether it be derived from an ai or a systemd script or an Antikythera mechanism. Now if you leave that to seniors you just ate a big chunk of their day playing shephard to a dozen plus “automated” pipelines while they still have stuff to do outside the weeds. Now you need more seniors and pretty soon they want triple what you could pay a junior and I don’t think they are 3x more prolific if the junior is managed efficiently quite frankly.
The process of setting up and maintaining automation should be less labor intensive than just doing it manually (or else why would you automate it?) and almost always requires a more advanced skillset than doing the manual task.
I hope juniors will figure out how to use AI to do larger tasks that are still annoying for seniors to do, while seniors take on larger tasks still. I think it's just seniors are learning this stuff faster at the moment and adapting it faster to current work, but as all that changes I would guess juniors reclaim some value back.
That said, you hit on something I've been feeling, the thing these models are best at by far is stuff that wasn't worth doing before.
I've been making use of copilot in VSCode to make changes in a codebase that's new to me, in a language that I can read if not necessarily write unaided - it's a dialect of SQL, so I can certainly understand what's happening, but generating new queries is very time-consuming (half of which is just stupid formatting stuff). Copilot seems to understand the style of the code in my project and so I don't have to do much work to make it conform, compared to my hand-written versions.
I've also written a lot of python 2 in my career, and writing python 3 still isn't quite native-level for me - and the AI tools let me make up for my lack of knowledge of modern Python.
Some juniors do figure it out, but my experience has been that the bar for such juniors is a lot higher than pre-AI junior positions, so there is less opportunity for junior engineers overall.
We had code school grads asking for $110-$130. Meanwhile, I can hire an actual senior engineer for $200 and he/she will be easily 4x as productive and useful, while also not taking a ton of mentorship time.
Since even that $110 costs $140, it's tough to understand how companies aren't taking a bath on $700/day.
If you're hiring in SF or NY, then the problem explains itself. Even a single young new grad needs that much to so live.
you can't have rent at 3.5k a month and not expect 6 figures when requiring in-office work. old wisdom of "30% of salary goes to rent" suggest that that kind of housing should only be rented if you're making 140k. Anyone complaining about junior costs in these areas needs to join in bringing housing prices down.
Yep, the value isn't there. I'm on a very lopsided team, about 5 juniors to 1 senior. Almost all of the senior time is being consumed in "mentorship", mostly slogging through AI slop laden code reviews. There have been improvements, but it's taking a long time.
I entered the job market in late 2000. There was no reason to hire a junior engineer when every hiring manager and senior engineer knew 10 friends who recently lost their jobs. I found work on less desirable projects and yes it affected my career trajectory and it sucked. Starting out has always sucked for most people.
It's happening again now with robotics, self-driving vehicles and RL. Factory workers, truck drivers, construction work, order fulfillment, machinists, farm work, medical technicians and more are all very much at risk (same thing as OP: mostly junior roles getting automated). Some info at https://arxiv.org/pdf/2510.25137
For me the most annoying would be a technically correct solution that completely ignores the “higher-level style” of the surrounding code, at the same time defending the chosen solution by referencing some “best practices” that are not really applicable there for some higher-level reasons, or by insignificant performance concerns. Incidentally, LLMs often produce similar problems, only one doesn’t need to politely argue with them.
Writing unit tests, manual validation work, manual testing. Automating Deployments of infrastructure, DNS work, tracking down annoying one off bugs, fixing and validating dependency issues.
Basically this type of maintenance work for any sufficiently complex codebase. (Over 20k LOC)
When I was an QA intern / Software Dev Intern. I did all of that junk.
I don't know if that's it. Speaking from outside the tech space: most of my office jobs since 2012 have been "doing the easy/annoying tasks that had to be done, but more senior people didn't want to 'waste time' dealing with."
So, there are two parts to this:
The first is that a lot of those tasks are non-trivial for someone who isn't a digital native (and occasionally trivial for people who are). That is to say that I often found myself doing tasks that my bosses couldn't do in a reasonable time span; they were tasks which they had ALWAYS delegated, which is another way of saying that they were tasks in which proficiency was not necessary at their level.
This leads into the second part, which is that performing these tasks did not help me advance in relevant experience at all. They were not related to higher-level duties, nor did they endear me to the people who could have introduced me to such duties. My seniors had no interest in our growth as workers; anyone who wanted to see that growth had to take it into their own hands, at which point "junior-level" jobs are only worth the paycheck.
I don't know if it's a senior problem generally, or something specific to this cohort of Boomer/Gen-X seniors. Gun-to-my-head, I would wager the latter. They give enough examples in other arenas of public life to lend credence to the notion that that they simply don't care what happens to their juniors, or to their companies after they leave, particularly if there is added hassle in caring. This is an accusation often lobbed at my own generation, to which I say, it's one of the few things our forebears actually did teach us.
I grew up in the 70s. The hand wringing then was calculators. No one was going to be able to do math anymore! And then wrist watches with calculators came out. Everyone is going to cheat on exams, oh no!
Everything turned out fine. Turns out you don't really need to be able to perform long division by hand. Sure, you should still understand the algorithm at some level, esp. if you work in STEM, but otherwise, not so much.
There were losses. I recall my AP physics professors was one of the old school types (retired from industry to teach). He could find the answer to essentially any problem to about 1-2 digits of precision in his head nearly instantly. Sometimes he'd have to reach for his slide rule for harder things or to get a few more digits. Ain't no one that can do that now (for reasonable values of "no one"). And, it is a loss, in that he could catch errors nearly instantly. Good skill to have. A better skill is to be able to set up a problem for finite element analysis, write kernels for operations, find an analytic solution using Mathematica (we don't need to do integrals by hand anymore for the mot part), unleash R to validate your statistics, and so on. The latter are more valuable than the former, and so we willingly pay the cost. Our ability to crank out integrals isn't what it was, but our ability to crank out better jet engines, efficient cars, computer vision models has exploded. Worth the trade off.
Recently watched an Alan Guth interview, and he made a throwaway comment, paraphrased: "I proved X in this book, well, Mathematica proved...". The point being that the proof was multiple pages per step, and while he could keep track of all the sub/superscripts and perform the Einstein sums on all the tensors correctly, why??? I'd rather he use his brain to think up new solutions to problems, not manipulate GR equations by hand.
I'm ignoring AGI/singularity type events, just opining about the current tooling.
Yah, the transition will be bumpy. But we will learn the skills we need for the new tools, and the old skills just won't matter as much. When they do, yah, it'll be a bit more painful, but so what, we gained so much efficiency we can afford the losses.
> I feel the effects of this are going to take a while to be felt (5 years?);
Who knows if we'll even need senior devs in 5 years. We'll see what happens. I think the role of software development will change so much those years of technical experience as a senior won't be so relevant but that's just my 5 cents.
The way I'm using claude code for personal projects, I feel like most devs will become moreso architects and testers of the output, and reviewers of the output. Which is good, plenty of us have said for ages, devs dont read code enough. Well now you get to read it. ;)
While the work seems to take similar amounts of time, I spend drastically less time fixing bugs, bugs that take me days or God forbid weeks, solved in minutes usually, sometimes maybe an hour if its obscure enough. You just have to feed the model enough context, full stack trace, every time.
> The social contract between large companies and employees has been broken for years now. US companies are optimized for quarterly earnings, not long term investment in their employees.
Going to throw out another anecdote here. At a company that a number of my friends work for (a fortune 50), they are currently making record profits that they loudly brag about during employee townhalls. They also are in the process of gutting multiple departments as fast as possible with little regard for the long term consequences. This is not the only company that I know of acting in this way (acting like they're about to go bankrupt when in fact they are seeing record profits).
To me the societal risk is that an entire generation of employees becomes extremely jaded and unmotivated, and fairly so. We used to work under the assumption that if our company is successful, then the employees would be successful. Record profits == raises for all, bonuses for all. And while we know that that connection was never that strong, it was strong enough to let us at least pretend that it was a law of universe.
That fundamental social contract is now at its breaking point for so many workers. Who can really blame people for putting in minimal effort when they have so much evidence that it will not be rewarded?
Those of us familiar with the Dilbert comic strip of the '90s-'00s are having a good chuckle at the idea that there was ever a social contract. What you think of as a social contract was a fiction enabled only by the explosive growth of the software industry during the Internet and mobile web of the last twenty years. It's easy to be generous to employees when the profits just keep growing on their own. It's easy to overlook mediocrity (and sub-mediocrity) when as many warm bodies are possible are needed to fulfill business objectives.
That's all over now; the growth spurt of a young software industry has given way to maturity. We'll be navigating an employment environment much like what the norm is in other technical professions with tougher standards and fiercer competition for good jobs.
>It's easy to overlook mediocrity (and sub-mediocrity) when as many warm bodies are possible are needed to fulfill business objectives.
dismissing technical talent as "warm bodies" is exactly how the old guard of IBM/AT&T/Oracle fell to the new scrappy talent. I'm sure history will repeat itself again in due time.
> We'll be navigating an employment environment much like what the norm is in other technical professions with tougher standards and fiercer competition for good jobs.
if every other sector except healthcare wasn't experiencing the same thing, you may have a point. This clearly isn't a problem limited to tech, though.
I think a lot of this has to do with the explosion of CEO (and by extension CxO) pay over the past 30 years.
Today, a CEO can turn in a few quarters of really solid earnings growth, they can earn enough to retire to a life a private jets. Back when CxO pay was lower, the only way to make that kind of bank was to claw your way into the top job and stay there for a decade or more.
The current situation strongly incentivizes short-term thinking.
With today's very high, option-heavy compensation a CEO making long-term investments in the company rather than cutting staff and doing stock buybacks is taking money out of his own pocket.
CEO’s also never face consequences for destroying companies. Zaslav has run WBD into the ground and it’s currently being surrounded by vultures, and he’s still making like half a billion a year.
While I definitely agree CEO pay is quite egregious, in theory, to mitigate short-sighted quarterly earnings hyperoptimization, couldn't a board simply tie equity incentives to performance targets and timeframes though?
Lip Bu Tan, for instance, has performance targets on a five year timeline, which are all negated if the stock falls below a certain threshhold in 3 years. [1]
Or, ever controversial Elon Musk, certainly has an (also egregious) $1 Trillion dollar pay package, but it has some pretty extreme goals over 10 years, such as shipping 1 million Optimus robots [2].
All in all, we can debate about the Goodharting of these metrics (as Musk is keen to do), but I feel boards of these public companies are trying to make more long-term plans, or at least moving away from tying goals to pure quarterly metrics. Perhaps we can argue about the execution of them.
Note: I own neither of these stocks and my only vested interest is buying the S&P.
IMO it's not risk so much as foregone conclusion. You can see the hopelessness in GenZ and (to a lesser extent) millennials.
But we only care about short term metrics now, so no one cares. They don't even care to develop the tools to understand it. It might as well not exist. Blame the young people and move on.
> This is not the only company that I know of acting in this way
At this point in the tech industry, it'd be easier to name companies not doing this. Maybe Apple? I think they got aroudn it by not renewing contractors. But I might have missed something.
>To me the societal risk is that an entire generation of employees becomes extremely jaded and unmotivated, and fairly so.
I sure am jaded. But more motivated than now in my goals. They used to be to be this knowledgeable IC who can dig deep into a domain, but it's definitely been shifting to being able to sustain myself off my talents. I'll grab short term contracts and let my own products be the steady income.
(yeah, a lot easier said than done. But I have time to prepare for that).
>Who can really blame people for putting in minimal effort when they have so much evidence that it will not be rewarded?
Worse than that. Why put in effort when your reward for providing all that value is still getting the axe?
My industry is finally starting to see real moves at unionizing, but I hope tech as a whole is starting to wake up to this fact?
It's more like "this product is underperforming, let go of the team". Regardless of the reasons the product is underperforming. Could be that it was still in development and money dried, could be that they want to pull out of a region and need a product as an excuse.
You can't outwork corporate greed, unless you're working for peanuts in a 3rd world country. Then you're truly irreplacable (and still broke).
What social contract? Companies have always been for shareholders. Do you people have some kind of contract with Tesla that I don't know about?
This entire discussion sounds crazy to me. If you want socialism, vote for socialism. If you want raw unfiltered capitalism, vote for the billionaire. You can't vote for the billionaire and expect safety nets. That's madness.
> What social contract? Companies have always been for shareholders.
You are not wrong, but the contract is/was metaphorical.
For a long time people were able to make a living for themselves by studying hard (usually STEM) and end up with a career which payed off. That was the invisible "contract". Hell I went to university for things which seem like academic navel gazing, but I still got a good tech job on the other side. That's not the reality for a lot of graduates nowdays who take more practical degrees at masters and phd levels.
Again even if the literal statement is clearly false, it is the sentiment which matters, and this sentiment does not just apply to graduates. I think many just feel like working hard does not work anymore, especially in the face of housing, cost of living, job competition and social media flaunting the wealth of others.
I get the idea from my younger siblings, "Why try if you are already a looser."
Henry Ford for all his faults (and there were MANY) at least understood that you gotta have a customer base for your products, and that paying workers well helps everybody out.
It is not socialism to note that in the past, some companies have believed that their optimal relationship with their employees required recognizing their value and awarding them accordingly, thusly allowing them to attract/retain the best employees as well as maximizing the quality of the output from those employees. There has always been such a spectrum, that's not socialism. The trend to notice is that the spectrum is so strongly weighted towards the merciless, cutthroat end of things that may actually not be optimal for long term survivability of those companies whilst also as I noted, be breaking the social contract that workers have assumed for decades, which is also not socialism.
Socialism has a specific meaning, it's not just a label we get to put on behaviors that we - or rather, specifically you in this case - don't like.
Socialism is when the state (ie: the government) _owns_ industries.
A social contract is an implicit agreement that everyone more or less accepts without anything being necessarily legally binding.
For example, the courtesy of two weeks notice in the US is a social contract: there’s nothing legally requiring it, but there are _social_ consequences (ie: your reference might be less positive) if you don’t follow it.
Everything that’s kind of in an employee’s favor is not socialism. You don’t have to like the idea of “work hard, help the company do well, get rewarded,” but that isn’t socialism. It’s just a thing you don’t like.
well we can trace that back to the 1920's, for one example.
>Do you people have some kind of contract with Tesla that I don't know about?
Are you aware of what a "social contract" is? There's nothing wrong with seeking to fill in gaps of knowledge.
>This entire discussion sounds crazy to me. If you want socialism, vote for socialism.
I'd be down for it, but this is almost orthogonal to the main point of the discussion. Social contracts exist in all forms of governing. Even rampant capitism has the bare bones social contract of "don't make your customers TOO angry so you can maximize extraction".
When billionaires own the media companies that influence public opinion and have legal avenues to essentially bribe elected officials, does the public have a meaningful avenue to vote anti-billionaire?
I suspect this junior hiring crisis thing is linked to the ridiculous hoops people are put through to get a job these days.
When I was starting, you were checked for potential as a trainee. In my case, options trading. They checked over that you could do some mental arithmetic, and that you had a superficial idea of what trading was about. Along with a degree from a fancy university, that was all that was needed. I didn't know much about coding, and I didn't know much about stochastic differential equations.
A couple of weeks ago, a young guy contacted me about his interview with an options trading firm. This guy had spent half a year learning every stat/prob trick question ever. All those game theory questions about monks with stickers on their foreheads, all the questions about which card do you need to turn over, the lot. The guy could code, and had learned a bunch of ML to go with it. He prepared for their trading game with some really great questions to me about bet sizing.
I was convinced he was simply overly nervous about his prospects, because I'd never met someone so well prepared.
Didn't get the job.
Now I can assure you, he could have done the job. But apparently, firms want to hire people who are nearly fully developed on their own dime.
When they get their analyst class, I guess there is going to be nobody who can't write async python. Everyone will know how to train an ML on a massive dataset, everyone will already know how to cut latency in the system.
All things that I managed to learn while being paid.
You gotta ask yourself whether we really want a society where people have to already know the job before they get their first job. Where everyone is like a doctor: already decided at age 16 that this was the path they wanted to follow, choosing classes towards that goal, and sticking with it until well into adulthood. And they have to essentially pay to get this job, because it comes at at cost of exploring other things (as well as actual money to live).
I've found that this phenomenon exacerbates inequality too:
If you attend a well-known college that bigco's hire from frequently, there's a lot of knowledge floating around about interview prep, hiring schedules, which companies pay the best, etc. Clubs host "interview prep workshops" where they'd teach the subject matter of interviews, host events(hackathons, case competitions, etc.) to help you bolster your resume for applying to these bigco's. So just by attending a better/fancier school, you'd have pretty decent odds of eventually getting a job at one of these prestigious places.
If you were to attend a less prestigious school, regardless of your aptitude or capability, the information asymmetry is so bad that you'll never learn of the prerequisites for even being considered for some of these roles. Not many upperclassmen will have interned at fancy employers, so they won't be there to help you drill dynamic programming/black-scholes/lbo models, and won't tell you that you need to have your applications prepped by a certain date, and won't tell you that you should be working on side projects/clubs, etc.
I suppose that the apprenticeship model biases towards people that already have connections, so perhaps inequality was already bad, whereas now we just have an information asymmetry that's more easily solvable.
Currently, it is not just juniors. It is people of all seniorities, who have to jump through ridiculous hoops, to be believed, that they are any good.
Built most of the software of a company where I worked for 7y from humble beginnings to >80 people. Still gotta line up for a 4h on-site assessment! Built tons of free time projects, some more complex than anything one would usually build on the job. Still gotta have live coding interviews and no one can be arsed to even check my publicly available repos...
I'd say that "normal" (notjunior, not senior) level people have the hardest time ATM. Most jobs are either for juniors or seniors, not inbetween (anecdotal data from my experience job hunting for the last year in austria)
> You gotta ask yourself whether we really want a society where people have to already know the job before they get their first job. Where everyone is like a doctor: already decided at age 16 that this was the path they wanted to follow, choosing classes towards that goal, and sticking with it until well into adulthood. And they have to essentially pay to get this job, because it comes at at cost of exploring other things (as well as actual money to live).
With the way higher-ed works in the US, and the way certain schools opportunity hoard to an insane degree, that is effectively already the case for whole industries and has been so for decades at this point. It's practically an open secret that getting into some schools is the golden ticket rather than the grades you earn while there. Many top schools are just networking and finishing schools for whole "elite" industries.
>You gotta ask yourself whether we really want a society where people have to already know the job before they get their first job
That'd be fine... meanwhile, the new loop we come into:
- okay, so what does your company need and do
Company: "that's under NDA/trade secrets, we can't tell you"
- okay. we can't see what you want to you'll have to train them
Company: "we don't want to train people, they just need to hit the ground running"
- okay. we'll just let colleges train the fundamentals and have others figure it out
Company: "no one's training anyone anymore. Where did the juniors go?"
Even doctors have apprenticeship programs. An industry where no one wants to train the next generation is a doomed one. If the US doesn't do it, some other country will gladly take it up.
Haven’t seen anyone mention this but this is how it works in China. You have to study the same thing since you were 16 and completely ace it. If you decide during or after college that you don’t like the job path you chose (or really your parents chose) as a teenager then too bad. You’re locked into it for life or you’re stuck with never getting a job because the job market in China for young people is so horrendous. (Much higher youth unemployment rate)
They have terrible interviews there as well that go much deeper than here. They’ll analyze your family - not just you.
This is just a symptom of a really bad economy. That’s what the US is in right now. China’s youth are suffering from this as well.
Some hiring managers prioritize technical skill but its only one part of whether the interviewers "like" a candidate. There are infinite reasons someone can get turned down and only some of them are skill related.
>ridiculous hoops people are put through to get a job these days
I'm sure that's true in some areas, but our last hire I was shocked at the ridiculous lengths the applications would go to to avoid putting in even a minimum effort to apply for the job. Like the Van Halen brown M&M test, we put a line in the middle of the job advert saying "If you've read this, put your favorite color in at the top of your job application message. We had low double digits % of people who would do that.
Honestly, on our next hiring round, I think I'm going to make people fill out a google form to apply, and have any of our job posts say "Apply at <URL>" and completely ignoring any apps we get through Indeed or the like. We had a team of 3 people reviewing applications for an hour or two a day for a month and most of the responses were just human slop.
As a new college grad I might be able to add some insight.
We're stuck in a stalemate where the sheer volume of applications for employers to handle and applicants to send makes them take shortcuts, leaving both sides wonder why people aren't trying.
If somebody has to send in 300-500 applications (which is not unheard of) and answer the same questions till they go blind, it's not surprising that certain things are missing or people don't care. Applicants don't have any reason to believe their info isn't thrown in the trash by an LLM as soon as it is sent.
Lazy people will always be a problem but until there is transparency or trust developed I doubt we will see meaningful change.
> Like the Van Halen brown M&M test, we put a line in the middle of the job advert saying "If you've read this, put your favorite color in at the top of your job application message.
TBH I can't blame them. you're applying to hundreds of applications repetitively with qualifications that barely matter because you're encouraged to apply anyway. You can only spend so many hours reading HR-drivel (that at this point may or may not be ai-generated) before you focus on just finding "job title, salary , location), and then slamming apply. It's just not worth editing my resume to add some weird qualifier if I don't even think I'm going to get a reply. It's another hoop.
It's the complete inverse of hosting Van Helen at your show. It'd be more like trying to make a cashier recite their company motto. They are not that dedicated to any one role. They can't afford to be.
---
I don't know if it's feasible for your situation, but smaller teams tend to have candidates email their resume. It can still be LLM'd, but I will tend to pay more attention if I feel like I have a direct communication channel. Not yet another greenhouse application form. It leaves room to be more free form with my pitch as well.
It's not obvious to me that AI is the reason for the hiring slowdown.
ChatGPT was pretty useless when it first released. It was neat that you could talk to it but I don't think it actually became a tool you could depend on (and even then, in a very limited way) until sometime in 2024.
Basically:
- the junior hiring slowdown started in 2022.
- but LLM's have only really been useful in a work context starting around 2024.
As for this point:
> According to very recent research from Stanford’s Digital Economy Lab, published in August of this year, companies that adopt AI at higher rates are hiring juniors 13% less
The same point stands. The junior hiring slowdown existed before the AI spend.
I think the interest rate and shareholder pressure were the most immediate causes. In 2021 you could get head count to do trivial projects at many tech companies and by the end of 2022 you had layoffs and hiring freezes.
Tend to agree here. The slowdown here has more to do with the financial ecosystem. IE less capital available for some companies, higher salaries and a changed approach to work.
I think AI clouds the real issues around Junior hiring. Defective companies.
Let's say you hire your great new engineer. Ok, great! Now their value is going to escalate RAPIDLY over the next 2-3 years. And by rapidly, it could be 50-100%. Because someone else will pay that to NOT train a person fresh out of college!
What company hands out raises aggressively enough to stay ahead of that truth? None of them, maybe a MANGA or some other thing. But most don't.
So, managers figure out fresh out of college == training employees for other people, so why bother? The company may not even break even!
That is the REAL catch 22. Not AI. It is how the value of people changes early in their career.
I think this is the crux of it. When i got my first job I probably made half the salary of the senior engineer in our division. I am 100% sure I was not half as productive. Juniors take a lot of training and time and aren't very productive, but their salaries are actually not reflective of that. The first few months at your first job you're probably a net loss in productivity.
If salaries reflected productivity, you'd probably start out at near minimum wage and rapidly get raises of 100% every half year.
On top of that, if the junior is successful he'll probably leave soon after he's up-and-running b/c the culture encourages changing jobs every 1-2 years. So then you need to lock people down with vesting stock or something..
It seems not easy at all. Even if you give aggressive raises, at the next interview they can fake/inflate their experience and jump in to a higher salary bracket
Hiring and training junior developers seems incredibly difficult and like a total waste of energy. The only time I've seen it work is when you get a timid autistic-savant-type who is too intimidated with interviewing and changing jobs. These people end up pumping out tons of code for small salaries and stay of for years and years. This is hitting the jackpot for a company
>Even if you give aggressive raises, at the next interview they can fake/inflate their experience and jump in to a higher salary bracket
I don't think the kinds of people who see a 50% raise and complain that it's not 100% are the kinds of candidates you want to hire anyway. I'd like to see more of that before deciding we tried nothing and ran out of ideas.
I didn't leave my first job because I was non-autistic. I left because I was paid 50k and the next job literally tripled my total comp. Oh, and because I was laid off. but tbf I was already out the door mentally around that time after 2 years of nothing but chastising and looking at the next opportunity.
I would have (outside of said chastising) gladly stayed if I got boosted to 75k. I was still living within my means on 50k.
>Hiring and training junior developers seems incredibly difficult and like a total waste of energy
If that's the attitude at large, we're all falling into a tragedy of the commons.
> Juniors take a lot of training and time and aren't very productive, but their salaries are actually not reflective of that
In the current economic situation you can offer a junior 2x may be even 3x less and still get candidates to choose from.
Also there juniors who are ready to compensate for lack of experience by working longer hours (though that's not something you would learn during hiring).
> The first few months at your first job you're probably a net loss in productivity.
It's true for a senior too, each company is different and it takes time to learn company's specific stuff.
I actually got a major raise after 6m, and then another major raise 1y into my career, because my boss recognized my value.
Sadly this is not as common as it should be - but I've also mentored folks at FAANGs who got promoted after 1y at the new-hire level because they were so clearly excelling. The first promotion is usually not very hard to attain if you're in the top quartile.
It's like the whole idea of a company has inverted. Instead of "We'll assemble a team, then use that capability to make things, and solve problems" the idea is "the machine basically runs itself, how much can we get away with minimizing upkeep?"
Default "people have value because human attention solves problems", has become default "existing org structure has value because existing revenue streams are stable."
The idea of a company used to contain an implied optimism. "If we get capable people together, we can accomplish great things!" Now that optimism has been offloaded to the individual, to prove their worth before they can take part.
I upvoted the article for the purpose of discussion. I disagree with it. The core tenant of the article is that AI is the reason why companies aren't hiring juniors. That's just not it. Do people just blindly believe whatever some CEO or company says in their press briefings? This was all happening before the AI boom. Interest rates went up, hiring went way down, and then AI launched. Before interest rates, interviewing was getting harder and harder every year. That's usually an indication that you have more supply than demand. The bar for getting into any American tech company was getting much harder - not just FAANG. Leetcode had gone from having practiced 50-100 questions to there being a bank of over 3000+ with many people having regularly studied hundreds. It went from easy/medium to being typical in interviews to medium/hard being typical with many original hard questions now being reclassified as mediums.
Wages for your typical engineer stopped going up 5+ years ago. The joke of senior FAANG engineers making $400k has been a meme for over 5 years. Yet, inflation has done over 20% in 5 years? Look at new offers for people joining the majority of positions available at public tech companies. You're not seeing $500k offers regularly. Maybe at Jane Street or Anthropic or some other companies that are barely hiring - all of which barely employ anyone compared to FAANG. You're mostly seeing the same $350-400k/yr meme.
The reason we're not employing new grads is the same reason as the standards getting much more aggressive. Oversupply and senior talent has always been valued more.
I appreciate you adding nuance to the conversation. The problem is much more complicated than just AI, but I (original author) was using those two research studies that I cited as the basis for the conversation. While 13% hiring drop doesn't mean a catastrophic difference, it's a trend worth noting.
> Wages for your typical engineer stopped going up 5+ years ago
Not true for Western Europe. Getting more than 60k euros yearly as a software engineer was hard in 2019, it's now basically impossible to get less than that.
The problem is "Seniors" started becoming worse a decade ago. Not only wouldn't they mentor, but they wouldn't lead by example. Problem-solving on their own, collaborating with peers, sharing information/communication, doing proper due diligence, organizing and improving themselves and their team/product/business. This was around the same time bootcamps started flooding the industry with amateurs with no experience. These neophytes were then competing with more experienced people for the same jobs, because hiring in tech is more Ouija board than accurate assessment of professional engineering.
Amidst this influx of applicants, junior and intermediate staff began getting Senior titles to justify pay raises. Soon those exact same people were moving from job to job as a "Senior", but without the relevant criteria that would've qualified for that title a decade before. You can still see people get promotions without having accomplished anything, much less learned anything, but they did keep the lights on. Today there's a sea of "Senior" engineers that can basically write code (and not especially well), but lack all the other "non-coding" skills that Seniors should have.
Even if you hired 100K new Juniors tomorrow, there's nobody to train them, because most of the people working today are practically Juniors themselves. Each "generation" is getting worse than the one before, because they're learning less from the generation before, and not being required to improve. There's still good engineers around, but finding them is like playing Where's Waldo? - and you have to know what Waldo looks like, which you won't if you're not experienced!
The fix isn't going to be learning to network ("relational intelligence") and mentoring more. The fix is for us to stop letting the industry devolve. Treat it like the real engineering professions, with real school requirements, real qualifications, real apprenticeships, real achievements (and titles that aren't meaningless). Otherwise it'll continue to get worse.
God, thank you for writing this. I agree 100%. We are rapidly losing all of our "low-background" programmers in this industry. Even ten years ago, I encountered developers who could not debug a stack trace, of the application they were hired to develop. People would send me screenshots of Python errors and ask me how to fix them. I was shocked. I was a junior myself, but surely a programmer would know how to read a compiler error. I mean, that's the entire point of the computer telling you what went wrong...
I saw the title inflation happen in real time. When the boot camp floodgates opened, that was the beginning of the end of my faith in this field. I saw people with three months of create-react-app tutorials churning out garbage, while I was called upon to put out fires and fix things when they broke. I "did devops", and rapidly became shadow developer IT, helping incapable programmers fix bugs in codebases I wasn't even familiar with, better than they could. And I am truly not that great of a programmer! I just know how to read, reason, and use grep a lot. These aren't superpowers, but finding someone who can even reason through how to debug something is impossible these days.
I would love some sort of licensure or guild or standards, but I have no idea how we even begin to change that. Part of the problem is that companies don't want to change. It's cheaper to pay a few people nothing than it is to pay a lot of people a lot, and that shows no sign of changing. Maybe more planes have to fall out of the sky, I don't know. Maybe Windows has to become so buggy and unusable that multiple hospitals shut down for months on end. We don't just need a reckoning, we need a reckoning where we all wind up better on the other side.
I am squinting at the horizon, but still, all I see is darkness.
>The fix is for us to stop letting the industry devolve.
Sadly not in "our" hands. At best, some director/product owner brings it up. Executives have a nice chuckle, and they continue to outsource to anywhere else. This US industry barely wants to hire Americans to begin with at this point.
We're gonna have to divorce from big tech and push more businesses that reflect our desires if we want true change. Or collectively bargain while we have the chance. I don't know what is more likely in this community.
One of the critical flaws in the article is that the first chart only looks back 5 years, and the second only looks back 10.
The boom-bust recession cycle is roughly every 10 years. You can't say that AI is impacting hiring when your data just looks like the typical 10 year cycle. Your data needs to go back further.
That being said, what's more likely going on:
1: There are always periods where it's hard for recent college grads to get jobs. I graduated into one. Ignoring AI, how different is it now from 10, 20, and 30 years ago?
2: There are a lot of recent college grads who, to be quite frank, don't work out and end up leaving the field. (Many comments in this thread point out how many junior developers just shouldn't be hired.) Perhaps we're just seeing many companies realize it's easier to be stricter about who they hire?
>Ignoring AI, how different is it now from 10, 20, and 30 years ago?
Ignoring AI, there is simply more competition and less human interface in the process to begin with. 10 years ago, you'd throw maybe dozens of apps and study interview trivia (this was right before the "leetcdoe era" so not even that). 20 years ago you'd probably just wander around a career fair and stumble into your career. 30 years ago you were as close to shaking your managers' hand for a job as you'd ever be in the modern tech industry.
10 years ago, a reference from nearly anyone in the pipeline to the hiring manager guaranteed at least a look see at you. Now it's a 50/50 at best. "who you know" may not be enough anymore.And now career fairs are 90% advertising firms instead of actual talent aquisition.
>Perhaps we're just seeing many companies realize it's easier to be stricter about who they hire?
if you look at the hiring numbers, you see that hiring globally is in fact not slowing down. That's a bit of a tangent, but that may give a clue to the whole situation here.
Today you may not even get a human to see your resume after 100 job apps. It's not just brutal but a solitary experince. No feedback to improve upon, no advice to take.
>Most seniors today are the prior generation’s juniors with almost no increase of capabilities
I highly doubt throwing even a 3YOE "senior" of 2012 at a modern junior interview would turn out as well as you'd expect. the standards have gotten sky high. That doesn't mean they can't do the job, it means the industry created more hoops to jump through.
I agree to an extent with title inflation (and where the hell is the mid level?), but I don't think peple are confusing "juniors" here. It's new grads to at best 2 years of experience. not much controversy there. I also don' think the idea that the 2014 graduating CS class is smarter than the 2024 class would pass the sniff test.
The most frustrating thing about this whole junior position drought is how it simultaneously affects those who are passionate and get it, not only the opportunist bootcamp alumni who were lured by the prospect of high earnings.
If I were to graduate today, I'd be royally screwed.
Sadly - as I've mentioned on HN a bunch - junior salaries need to fall dramatically to somewhere in the $60k-$100k range in order to make it cost effective against automation/AI or offshoring.
The economics of providing every new grad a $150k TC offer just doesn't work in a world with the dual pressures of AI and async induced offshoring.
Heck, once you factor in YoE, salaries and TCs outside the new grad range have largely risen because having experienced developers really does matter and provides positive business outcomes.
State and local governments needs to play the same white collar subsidy game that the rest of the world is playing in order to help fix the economics of junior hiring for white collar roles. This is why Hollywood shifted to the UK, VFX shifted to Vancouver, Pharma shifted to Switzerland, and Software to India.
> The economics of providing every new grad a $150k TC offer
It was always a weird US thing driven by huge companies and VCs. In other western, developed countries ~$50k equivalent would be normal. Even adjusting for other provided social benefits, there's still a long way down...
Fall into the 60-100k range? Thats where the vast majority of them have been. Only the bay and NYC city area sees otherwise, and even in those areas I see plenty of listing for 90-110k for junior positions.
This article talks a lot about AI, but what I find odd is that in my relatively short (but long enough) ~9 yr career so far, this problem predates AI. I don't deny that it exacerbates it, but you don't kill a disease by addressing the symptoms. From the first time I was ever involved in the hiring process, senior leadership always encouraged me to hire more experienced staff, always most heavily scrutinized juniors, and had negotiations fall through with mid-level candidates the most. This was despite juniors passing technical screens with strong showings. This was not at a Fortune 500. This was a micro-cap subsidiary of a private, billion dollar company.
And although it hasn't discouraged me, I have to admit that I've been burned by juniors when caught in the middle between them and senior leadership on output expectations or strategy because frankly it's much more challenging to mentor how to navigate company politics than it is to mentor professional coding acumen. I want to be humble here. I don't think that's the junior's fault.
It feels like these problems go a lot deeper than AI. Most shops want software teams that are either silently embedded black boxes that you insert rough instructions into and get working software as output or an outsourced team. We've all experienced this. It seems silly to deny that it's directly related to why it's so hard to mentor or hire juniors.
You're not wrong! I'm the original author of the post, and yes, I've seen this trend for years now, too, but I was using those two research studies that I cited as the basis of the article, so I started looking at it from that lens. I think the problems go deeper than AI, too, which is why I touched on corporate incentives. Ultimately, my goal was just for teams to think about how it could benefit them to invest in juniors and for college students to know that they need to prepare for a challenging ride if they're majoring in an AI-adopting field.
Yes, AI isn't helping but the corporate world has been doing this for decades! Junior devs are second class citizens internally. I don't blame them for moving on after a few years.
I agree. I wonder if it's a mix of fully remote work being popular some time ago and the amount of tech one has to know now increasing (DBs, backend, frontend, cloud, observability, security, etc.). When hiring remotely, people naturally try to find candidates who are very communicative, have a high level of ownership, and can work with or without clear requirements and without oversight. That latter set of traits is often associated with senior developers rather than juniors.
>Most shops want software teams that are either silently embedded black boxes that you insert rough instructions into and get working software as output or an outsourced team
Well that explains why AI excacerbates this. It's all they ever wished for and they don't need to make do with that facsimile of "human interaction" anymore. It's not perfect but that's a sacrifice they are willing to make.
Or you know, they just really want to be as cheap as possible in production (hence, outsourcing).
>It seems silly to deny that it's directly related to why it's so hard to mentor or hire juniors.
I'll give a slight BOTD here after my disdain above and admit tha a small team probably isn't the best enviroment to train a junior. Not unless you either
a) truly believe that the skillet you need isn't out there, and you are willing to train it yourself to alleviate your workload, or
b) you are thinking long term efficiency and are willing to lose early productivity to power the future prosperity. Which, to be frank, is not how modern businesses operate.
And yes. Any teacher in any field (but especially education) will tell you that the star players make their day, week, and year. But the worst cases make you question your career. Our natural negativity bias makes the latter stick out more. Those in industry won't get star players as they are either filtered out by these stupid hoops or gobbled up for 100k above your budget by the big players. It's rough.
The idea that the only reasonable path into a software related career is through networking may be true, but it obviously signals something deeply wrong with the culture around work.
It is also something which is likely to be quite harmful, since it selects for people who are great at networking over people who have good technical skills. Obviously interpersonal communication is important, but how well a 20 year old in University performs at it should not doom or make their career.
And even people with bad social skills deserve to exist and should be allowed into their chosen career. Being someone who does good work and is respectful, but not overly social, should be good enough.
I agree with you, actually (I'm the original author of the post). It's literally one of the main reasons that I'm writing about networking so much. I have seen so many people fail up in technology because they were good at networking while so many other people who had better technical skills felt stuck. I don't believe that to be a strong networker you have to be social, though, just intentional. Technical people who may struggle with the people side of things can leverage their systems thinking strengths and apply it to stakeholder, mentee/direct report, and cross team relationships in a way that helps them move the needle on their goals. It's not easy, but I do think that intentionality and sincerity are key.
Agree, but ultimately it's a regression to the mean of most white-collar professions, where grades and network make for a significant jump-start in someone's career.
This is truly heartbreaking, programming was the last profession beside medicine doctor that guaranteed young people good start in life in my country.
It is insane how much screwed over we are. I am about to turn 30 soon with 5 YoE, PhD in ML which supposedly is the cutting edge stuff. Yet I have no prospects to even buy a tiny flat and start “normal life”. AI eats its own tail, I have no idea what I should do and what to learn to have any sensible prospects in life.
To try and add in some anecdotes without injecting too much baggage:
I am an older gen-z and launching my career has felt nigh on impossible. At my first job, the allergy toward mentorship this article mentions was incredibly palpable. None of my several managers had management experience, and one of them openly told me they didn't want to be managing me. The one annual review I got was from someone who worked alongside me for a week.
Follow that experience up with a layoff and a literally futile job search, and its hard to be optimistic about building much of a career.
I'm really sorry you went through that. For what it's worth, I'm a millennial, and then best shot I had at mentorship was an extremely overworked engineer who oversaw my work for like... a few weeks, maybe? And that was at the very beginning of my career about a decade ago. Then my mentor kinda disappeared to put out a bunch of fires all the time (I eventually became the "put the fires out all the time" guy.) Basically, the experience was neither long nor formal. After that, and at every job since, I basically had to fend for myself. This industry is outright allergic to training people, and it sounds like it's reached a fever pitch. I'm praying I don't get laid off, because on top of having no desire to job hunt in this economy, I don't really know if I care to work anywhere near this industry ever again. I can't wait until it collapses.
I have a friend of a friend in his mid 20s who finished a masters degree in data science focused on AI. There isnt a job for him and I think hes given up.
In Letters to a Young Poet Rilke responded to a young aspiring poet who asked how a person knows whether the artistic path is truly their calling:
> “There is only one thing you should do. Go into yourself. Find out the reason that commands you to write; see whether it has spread its roots into the very depths of your heart; confess to yourself whether you would have to die if you were forbidden to write. This most of all: ask yourself in the most silent hour of your night: must I write? Dig into yourself for a deep answer. And if this answer rings out in assent, if you meet this solemn question with a strong, simple "I must," then build your life in accordance with this necessity; your whole life, even into its humblest and most indifferent hour, must become a sign and witness to this impulse.”
How do I respond to this friend of a friend?
Is data science or coding in general the path for you only if you would rather die than stop merging pull requests into main every day even when nobody is paying you?
The other place you will meet struggling artists is sports. Train several times a week, neglect your social life, your studies, just learn how to chase after a ball.
Only people who are crazy driven will actually do this. The ones who don't make it, they try to climb up from lower league clubs. They go on and on, carving out a career.
But most kids do not have a burning passion for anything. They are curious, they're smart, they want to explore the world. But they haven't found a calling. If they try to go through the eye of the needle, they find it's quite hard, because those paths are taken by guys with a mental lock on a certain career.
What to tell the guy? He's picked the subject that is the most useful for learning about the world. Go around and look at things. There's so much that a person who can code and can deal with statistics can apply himself do.
given that quote, I'll tell you right now that your burning passion and calling in life will not be answered by being a corporate cog that is ultimately performing jira tasks for some project that is not your own. I made that mistake in my mid 20's. I wouldn't call my experience a waste either, but it did have me doing some soul searching on what my true "endgame" is.
I don't know what the disposition of your friend is, but I don't think many of us are ready to die cold on the streets scaping towards our goal. Survive first and then figure out how to climb from there. Don't see setbacks as a sign of weakness, but a part of life.
Yeah, it makes sense that going from a decade or so where SWE was one of the best possible career paths if you have any aptitude to a period where tech cos were staffing up aggressively (I recall reading ~60% growth), there's gonna be a hangover.
The educational pipeline probably still has a few years of oversupply to work through, and all of the people laid off post covid still need to work.
Even in a world where AI being able to automate some of the key skills required for SWE has no negative impact on employment, we'd expect a few more years of rough job prospects.
I personally think - Juniors will be okay, if they stick to *fundamentals*
lots of "seniors" via title inflation dont have fundamentals anyways - hence a lot of broken software in the wild & also perverse incentives like Resume driven development. A.I is built on badly written open source code.
because once you have the fundamentals, built a few things - you would've battle scars which makes someone a senior
not the 'senior' we see in big corps or places cosplaying where promos are based on playing politics.
you gotta go resume driven because that's what gets the job. but that distracts from proper engineering skills because the interview process isn't actually testing for engineers. It's all broken.
You're totally right. 10 minutes on /r/cscareerquestions (without even sorting by `top`, though it's more brutal if you do) is enough to confirm it.
I normally wouldn't cite Reddit as a source, but this same subreddit was overflowing with posts on fending off recruiters and negotiating already-sky-high comp packages just two years ago. Seeing how quickly the tables turned is sobering.
You're right that it's sobering to see how it's changed so much in the last 5 years. And yeah, it's not just the juniors that have to think about this but those in their cushy jobs that get hit with layoffs out of the blue, too. I don't say that to illicit fear; I say that to illicit action. We don't live in the same world anymore where you can rest on your laurels, unfortunately.
You've always been so good at all this, though! You help others, get curious about where you can add value to their situations, people know what you're about, and you exude authenticity. Poster child for what I'm trying to tell people to do to take action. :D
> That’s not to say that there aren’t people within those companies who care about employee development, but the system isn’t set up for that to be the companies’ top priority.
There has been a cultural shift too. I don't know when it got started, but at least employees in the tech companies started to get more and more obsessed with promotions. The so-called career development is nothing but a coded phrase for getting promoted. Managers use promotion as a tool to retain talent and to expand their territories. Companies adopted to this culture too. As a result, people development increasingly became a lip service.
I have, but these were generally founder types that accidentally became managers. They weren't "career managers." The career managers delegate that work.
all the time? not on technical issues, unless it's a TLM or the IC is entry level and it's pretty basic stuff they need help with, but absolutely on navigating organization, communicating, prioritization, and so on...
Wow, this elitist attitude is the problem. Assuming the worst about juniors and being totally unwilling to give people a chance, God forbid any training or mentorship. f--- software engineering. What. s--- career full of elitist pricks. Yes many of these people may not be very good, just like a lot of mediocre mids and seniors that believe they're gods gift to the world even if they've stubbornly refused to learn very little over 10 years, but many of these juniors would be extremely valuable if given a chance let alone any help.
This is just a continuation of general labor practices in US companies.
I have been unable to get a tech job for months so I’ve looked into retraining in a new field and every single one has some up front large cost via either paying for schooling or situations like mechanics needing to bring their own tools.
The standard US company has completely shed all training costs and put the expectations on laborers to train themselves. And you’re shit out of luck if their requirements change during your training as so many college graduates who picked comp sci are currently learning
From an individual senior exec point of view - all staff are replaceable. You just hire from outside the company.
People don't think in terms of shared commons and that if all companies are doing the same thing then there won't be much of a "senior" market left to hire.
> the unintended consequence of that is that we’ve spent a decade normalizing senior engineers opting out of developing the next generation.
This is because "management" includes a bunch of BS that few engineers want to actually deal with. Performance discussions, 1:1s, being hauled into mandatory upper-level meetings, not actually building things anymore, etc. If it was simply pairing with juniors from time to time to hack on things and show them cool stuff, it would be wonderful.
What you like is for yourself. What you seem to dislike are things that improve others (team/stakeholders). Seniors are such because they take on more of the latter.
This will now become even more normalized given that on technical skills seniors are no longer needed for juniors to skill up. AI and the evolving ecosystem will help and assist them way more. In the new world, the more technical and non-technical work you do towards customers/teams/organization, the more senior you become. I see many not liking it, but I'm also seeing first hand that is how it is.
> If it was simply pairing with juniors from time to time to hack on things and show them cool stuff, it would be wonderful.
I think that's a lot of it! (Author here, btw) I think that doing more of that actually makes performance discussions easier and takes the place of 1:1s a lot of times. The whole point of performance management is to nurture the relationship with the junior so that they grow into the type of senior that they need to be to be a contributing member of the team. And if you can achieve that better through hacking and pairing, then by all means.
As far as all the other BS meetings, I think that a lot of people in leadership positions aren't intentional/strategic enough about which meetings they allow themselves to get "hauled into", so they end up totally jaded and burnt out. They think they can't say no to these things, and so they lose the reins on their actual goals. If you step back and ask yourself what stakeholders actually need from you to feel heard, seen, validated, informed, etc, then it may look different from a calendar full of meetings.
Many companies have different career tracks for managers than for individual contributors (even tech leads are considered ICs). Mentoring junior engineers is absolutely in scope for what senior ICs can be recognized for.
> Imagine a tech industry where relationship skills weren’t just nice-to-have but essential. Where navigating complex human systems was seen as a core competency.
If that were to actually happen, we'd wind up excluding many of our greatest technical performers while drowning in a sea of would-be middle managers. People skills matter, but so do many other strengths that don't always overlap with being naturally good at navigating interpersonal dynamics.
I think I know what you may have in mind when you describe the "interpersonal dynamics" of a "would-be middle manager", and I probably agree with you (original author here).
But some of the best "people" people that I've seen in my career have been the most technical, also. They were really good at being able to communicate the value of their solution, the problems it solves, and risks and rewards. They could get buy-in from stakeholders and other teams. They could listen empathetically when faced with issues and blockers. And they did so with authenticity and genuine care because they were passionate about software engineering.
I believe those are skills that can be learned and practiced and that you don't have to be necessarily "social" to grow in that area.
>> we’ve spent a decade normalizing senior engineers opting out of developing the next generation.
This seems like a deeply flawed take on the dual track IC-management ladder. Senior ICs don't keep plugging away by themselves because they're not managers, they just don't get people-management tasks. I think the leadership & mentorship they provide is harder than for me (a manager) because they don't have the hammer of a "manager" job title, and need to earn all their credibility. I have not had a senior IC and above in more than 10 years that didn't have a significant amount of junior & int development explicitly defined in their role, and the easiest way to get promoted is with leverage. Try and be 20% better than your peers with your contribution (hard). Make 10 people 3% better (much easier)
Yes! Had the same instant reaction to that line. A lead engineer doesn’t get to lock himself or herself in a closet and ignore the team, and any team/company allowing that is failing its team as a result. They should be out there helping level up tech skills, and influencing code/behavior just as much as a people manager should be guiding career trajectory.
> When tech companies started giving engineers an alternative career path to management by letting them climb the ranks as individual contributors instead of having to be managers, I thought that was definitely the right move. Still do. However, the unintended consequence of that is that we’ve spent a decade normalizing senior engineers opting out of developing the next generation.
Interesting observation. I have personally tried to avoid getting into people manager positions (as I believed I'd be Peter Principled) but always took it as my duty to share knowledge and mentor the curious and the hungry (and even the ones that are not so). It's actually a very rewarding feeling when I hear good things about people who learned with me.
The biggest question that isn't being asked, "why is a university incapable of training a competent programmer in four years?"
I'm quite sure I could take my cousin who has never heard the word HTML and get her to be a better programmer than the average CS graduate within 4 years of tutelage. Why is this the case? Four years is a very long time, and the universities are wasting that time. I'm certain any driven individual would end up a mid-level candidate if they skipped college and instead trained themselves for that time, especially if they hire a senior tutor for far less than the cost of the college tuition.
It's been a while, but one of the reasons I avoided getting a CS degree a few decades ago was because it was basically mathematics. To this day, interviews are the only thing this would have benefited thanks to Leetcode.
Its a double edged sword too. I see it in my biz -- its easier to spend 40 hours training a model how to do things the way we like rather than hire someone junior and spend a month+ on onboarding. We are noticing hitting a wall to a certain point with clients still wanting to talk to a real person, but I can see that changing in the next ~5 years. Zero idea what happens to those junior folks that used to get trained (me being one that sat through a 3mo onboarding program!).
>. We are noticing hitting a wall to a certain point with clients still wanting to talk to a real person, but I can see that changing in the next ~5 years
I don't know. if we simply defer talks to LLM's, then companies will take out the middlemen. which means less clients. We'll have our own little filter bubbble of tech where everyone is talking to their black box to try and push out their ideas instead of within the industry.
Not exactly an industry I want to be in. But I don't think it'll get to that point.
I'm not sure how much is about LLMs directly. But as I've written elsewhere, there's definitely a circular pattern where a lot of junior employees think this is going to be an 18 month thing and companies allocate training and mentoring budgets accordingly.
There is a fair bit of anecdotal evidence that junior hiring--at least in the software space--is fairly difficult currently. Via internships at good schools etc. may be better but I have to believe that off the street from bootcamps and the like is pretty tough.
That's a thoughtful post, but I am skeptical of how "universal" her suggested Path Forward is. I suspect a hell of a lot of folks will have difficulty with the "people skills" stuff she mentions (and is almost certainly highly conversant in, herself).
> The most common answer from students when asked what they needed was a mentor who had just been in their shoes a few years ago, a surprising and heartening answer.
Mentoring is difficult; especially in today's world, where we are taught to despise older folks, and encouraged to treat everyone that we work with, as competitors.
For myself, I'm happily retired from the Rodent Rally, and find that LLMs have been a huge help, when learning new stuff.
I think I would also ad to the mix that young folk these days are incredibly overconfident and averse to criticism. A few years back they got a junior dev in here, and I was supposed to help him get on our stack, and ultimately mentor him.
This kid would not accept seniority, would constantly and publicly try to divert from the stack we worked with, he would not take any input on his work without actively fighting the process and will crowd the conversation at team meetings with never-ending Reddit-tier takes that contributed to nothing other than fill his ego.
In the end I managed to convince my boss to get him out, and he now works in Cyber, which will probably cause even more damage in the long run, but at least I can now say "not my problem".
People skills are so important, I agree. Intergenerational people skills are especially important; in most things that matter, the old guard are the ones keeping their eye on the younger hires, pattern matching what they see over months of observation to who they've seen succeed before.
9 times out of 10 it goes the other way around. Most young people have only had very negative interactions with their seniors, which has been wholly on the part of the senior. The current young generation is very respectful towards older people.
> Perhaps juniors (and in fact all of us) are going to seem more palatable as contractors at first
It actually might help.
This is the model used in Eastern Europe and India - the vast majority of new grads are hired by mass recruiters like EPAM, WITCH, Deloitte, and Accenture at low base salaries but also the expectation that they self train and learn how to become productive SWEs, or they just stagnate at the low rungs. Japan, Korea, and China use a similar model as well.
But honestly, even FTE isn't much of a headache if I can hire a junior SWE for $60k-80k, invest in training them, and then bumping salaries to market rate after they have matured. This is what a number of traditional F500s like Danaher [0], AbbVie [1], and Capital One [2] do via Leadership and Trainee Development Programs, and honestly, it's much easier to make a case to hire someone if they have a couple of years of real world work experience.
I don't really like the idea of "what if we get more desperate and lower our standards while billionaires continue to make record profits?" as a solution to our problem. We'll just go the way of Electrical Enineering and lose most of our talent to China.
Short term thinking and short term profit seeking are going to destroy every industry they touch. This article failed to bring up 2 important points.
Firstly, we've been here before, specifically in 2008. This was the real impact of the GFC. The junior hiring pipeline got decimated in many industries and never returned. This has created problems for an entire generation (ie the millenials) who went to college and accumulated massive amounts of debt for careers that never eventuated. Many of those careers existed before 2008.
The long-term consequences of this are still playing out. It's delaying life milestones like finding a partner, buying a house, having a family and generally just having security of any kind.
Secondly, there is a whole host of other industries this has affected that the author couldn't pointed to. The most obvious is the entertainment industry.
You may have asked "why do we need to wait 3 years between seasons of 8 episodes now when we used to put out 22 episodes a year?" It's a good question and the answer is this exact same kind of cost-cutting. Writers rooms got smaller and typically now the entire season is written and then it's produced when the writers are no longer there with the exception of the showrunner, who is the head writer.
So writers are rarely on set now. This was the training ground for future showrunners. Also, writers were employed for 9 months or more for the 22 episode run and now they're employed for maybe 3 months so need multiple jobs a year. Getting jobs in this industry is hard and time-consuming and the timing just may not work out.
Plus the real cost of streaming is how it destroyed residuals because Netflix (etc) are paying far fewer residuals (because they're showing their own origianl content) and those residuals sustained workers in the entertainment industry so they could have long-term careers and that experience wouldn't be lost. The LA entertainmen tindustry is in a dire state for these reasons and also because a lot of it is being offshored to further reduce costs.
Bear in mind that the old system produced cultural touchstones and absolute cash cows eg Seinfeld, Friends, ER.
Circling back, the entire goal of AI Is to displace workers and cut costs. That's it. It's no more compolicated than that. And yes, junior workers and less-skilled workers will suffer first and the most. But those junior engineers would otherwise be future senior engineers.
What I would like for people to understand that all of this is about short-term decisions to cut costs. It's no more complicated than that.
I've been saying this for years, since the first AI coding models came out. Where do the juniors go to learn? I'm a senior engineer because I got to do a bunch of annoying tasks and innovate just slightly to make them better.
That opportunity is now lost. In a few years we will lack senior engineers because right now we lack junior engineers.
All is not lost however. Some companies are hiring junior engineers and giving them AI, and telling them to learn how to use AI to do their job. These will be our seniors of the future.
But my bigger concern is that every year the AI models become more capable, so as the "lost ladder" moves up, the AI models will keep filling in the gaps, until they can do the work of a Senior supervised by a Staff, then the work of a Staff supervised by a Principal, and so on.
The good news is that this is a good antidote to the other problem in our industry -- a lot of people got into software engineering for the money in the last few decades, not for the joy of programming. These are the folks that will be replaced first, leaving only those who truly love solving the hardest problems.
I'm more pessimistic. It costs too much to go back to college and retrain. The result is going to be a generation of ambitious people doing a craft they hate. The results are going to be dismal.
> networking is absolutely essential for post-graduation job-placement success
Looking back, this has absolutely been the case for me personally. My first job out of school was at a startup spun off from a lab where a friend from my CS classes had been working while at school. I just referred somebody who was eventually hired that I've worked with at two other employers in the past.
Maybe chatting with a LLM with access to the codebase is equally effective as pair programming with a human. I don't have enough experience doing that yet to know. I still see it as another tool.
I've found it helps to have various levels of experience on a team. I think one reason for this is people with less experience (hopefully) ask a lot of questions to fill knowledge gaps. These conversations can lead to revisiting designs, practices, etc. and a better outcome overall.
This is true. As a startup founder I’ve invested heavily in mentoring juniors, and all of my current developers actually started as interns. They’ve grown fast and delivered real results because we gave them trust, support, and room to learn. The companies that say “there are no good juniors” are usually the ones that never bothered to train any.
One thing that I hypothesize about junior developers is that you need to leapfrog the handholding period and go straight to the medium/senior position on your own. You can acquire the medium/senior level of knowledge and experience making all the mistakes and bad choices by yourself and learning from the experience.
Sorry, these studies don’t show that AI is “good at automating away junior work” _at all_, or even claim to (and what little empirical research exists points the other way).
What they show is that hiring managers think they can use gen AI to get away with skipping juniors. The resulting collapse in software quality will either bite them in the ass causing a market correction, or massively enrich the big five and leave the rest of us to live with the consequences. Which outcome comes to pass is still yet to be seen (and partially under our control, as seniors)
What about hiring junior developers to do the work I don't want to spend time training AI to do? Humans retain context, over time learn the ins and outs of the business and will sit in a meeting with stakeholders to gain understanding of the business rules and ask the 'stupid' questions that need to be asked.
I would much rather have that junior take some hacks at building some features with AI along with my guidance than context switching over to AI just to walk it through doing a task which means having to explain the business and our business rules over and over again.
To me cutting out a junior developer adds more time for senior developers than making their work lighter.
I am genuinely baffled by the notion that experienced developers have a moral obligation to mentor junior developers in additional to their actual job-related tasks.
They do not. Mentoring is rewarding work, but it is work.
I also find it objectionable that if you're simply not interested in mentoring, you're a jerk. Some people just aren't good at it, some people are genuinely swamped with existing responsibilities, and some people might just want to focus on their goals... and that's fine. There is no but.
Some folks <gasp> just don't like other people that much, and prefer working alone. Also fine, and kudos for being self-aware enough to not inflict yourself on people who probably wouldn't enjoy your oversight either. This should be celebrated as a communications success.
All of which brings me to the truth: if a company wants to mentor junior developers - and there are many, many excellent reasons to develop talent long-term - then they should make sure that they have suitably experienced people who have opted-in to mentorship, and make sure that their success metrics and remuneration reflect the fact that a significant portion of their time is acknowledged to be dedicated to mentorship. Otherwise, you're describing a recipe for legitimate resentment.
Likewise, if you're a junior developer desperate for mentorship... I understand that your instinct is to take any offer that will have you. But if you're able to have an honest conversation with the recruiter about what kind of mentorship culture exists in a company, you might be saving everyone a lot of pain and frustration.
To me it seems that large US tech companies had a start-up behaviour until the last years (massive hiring, ambitious goals and VC money). This fades away relatively fast now and they cash out their investments.
Another reason might be the low potential of the new generation of graduates (see lower math scores and possibly IQ). They might have interviewed some and are disappointed and unwilling to hire from this pool.
Last but not least comes the current trend to substitute humans by LLMs.
Isn’t it also easier than ever to learn though? The moat that seniors built around their expertise enabled a juicy buffer of mediocre devs paid mediocre rates pushing up the value of mythical 10x engineers.
It's the bloated junior salaries that have killed their market. I never like hiring juniors, I never like working with juniors, and I'd rather pay the extra 20-30% and get someone more experienced. I'm sorry, but if you don't get into FANG, you should basically be working for nothing until you have some experience. It's cruel, it's not fair, but it's just not worth it for the employer. Especially in today's world where there is no company loyalty.
All this BS about AI taking away the stuff that juniors did, in my field, software development, that was never the case. I never worked in a place where the juniors had different work than the seniors. We all did the same things, except the juniors sucked at it, and required handholding, and it would have been faster and better if they weren't there.
The real trick is finding companies that do very simple work, simple enough that juniors can thrive on day one. It won't be the best experience, but it is experience, and the rest is what you make of it.
I don't disagree with this. (author here) I think it could help overall to lower starting salaries, but it'll never happen. It's all a math problem at the end of the day.
This is neat — I do think this is relevant to more than just the software engineering space. See also, healthcare and law (I wrote more at length here, not to derail this comment thread [1]). Our junior training on-ramps for a lot of knowledge-work fields are in some semblance of equilibrium, but it's an unstable one.
This is a good use of government due to the existing dynamics.
Instead of only funding universities, provide lower risk curves for hiring juniors where the jobs are.
The big issue is the game theory of first mover disadvantage at play.
Whoever trains the junior loses all the investment when the junior jumps ship. This creates a natural situation of every company holding until the ‘foolish ones’ (in their eyes) waste resources on training.
Second mover advantage is real. This is what the government can fix.
This problem is not new. No one's wanted to give juniors the time of day since at least 2018 when it took me 8 months to land my first software developer role.
It sucks if you're looking for entry level work, of course. However, I'm a TL/manager with mostly entry-level reports and I have told them for a while the other side of this mentioned here - by the time they get to senior level they are going to be able to name their price in the shortage.
I'm gonna get some downvote, but I'll say this. Over the last 10 years, the quality of the juniors trends opposite of salary curve. We don't have a crazy interview process, nor are we working on anything ground breaking. By any measurement, we are a run of the mill company that don't offer top end salary but market competitive. The quality of junior engineers I've interviewed has been abysmal. Maybe because we don't have the name nor the high end salary, or maybe our recruiting firms and HR suck in general. My no-hire/hire ratio is literally 50:1. Most of them can't even answer basic computer science questions such as under what condition that a binary search is useful, what's the difference between NoSQL database and relational database, or converting binary to decimal, etc.. They all talk about cloud and distributed computing, etc..
We have an intern that is finishing a four year computer science degree that has no clue what git is, never used a log and all he presents is AI garbage.
I find it profoundly depressing to try and teach someone who has no interest in the craft.
80% of the candidate I interview pass (leetcode style coding interview, as mandated by the company). This is actually annoying because I'll probably have to raise the bar and start rejecting very good candidates.
> The quality of junior engineers I've interviewed has been abysmal. Maybe because we don't have the name nor the high end salary, or maybe our recruiting firms and HR suck in general. My hire/no-hire ratio is literally 50:1.
I'm sorry but to me this part reads like a humorous phrase that's popular in some circles in my region which goes:
"Maybe <list of negative things, usually correct characterizations of the speaker>, but at least <something even worse>"
The companies I worked for used automated coding quizzes like Codility to weed out the worst applicants, but I suspect you're already doing that.
How is them knowing when binary search is useful relevant to what they'll be doing at work should they get hired?
It feels like there is a psyop going on. Blaming job loss and less entry level jobs on "AI". The real simple reason... Jobs are going overseas, many of them junior level jobs. They are laying off people and then hiring a proportional amount of people overseas. Why are folks falling for this AI nonsense?
We are all systems analysts now. We are all business people. Or we're out of a job. Programming as a skill in itself is largely obsolete. It's all about understanding the business: what it needs, how it operates. That takes holistic thinking and people skills that programmers historically just didn't have. They'll adapt, or they'll leave the field.
AI companies could never make any money (statement about the future, and about AI companies, and finances). And AI could be having a visible effect on hiring today (statement about now, and about non-AI companies, and about employment).
They don't have to both be true, but they do not inherently contradict each other.
As an unhired junior, I think this stems from a lack of unions and the ability of the workforce to make demands of capital (e.g. to prevent offshoring or discriminatory hiring processes)
> "Companies replace junior positions with AI
+
Senior engineers have been excused from mentorship responsibilities
+
Companies optimize for immediate results
=
A systemic issue that no one person can fix"
They forgot to add in "Aging billionaires spend a trillion dollars on longevity research" which results in "110 year old Senior engineers still working"
genuinely asking, how do you network to get a job? esp. if you’re a new grad
where do you network? what do you network with these other humans on?
I do think I could get a job from my network because I’ve worked in the industry for years and done good work; I’m a little skeptical of advice to network to junior/new grads. I at least ignore those LinkedIn requests
The comments here amuse me because there's a strong scent of resentment towards people using AI, along with people who copied from SO. I am a mid level developer that started using AI about 4 months ago, and view it as justice against unreasonable and constant micromanagement through estimates on every single task. You want a robot? You're getting your robot now.
Not to mention I'm the only white person on my team other than the owner/operator. They already brought in bots of sorts from overseas. The constant drive to cheaper labor and gutting of the American middle class has been vast compared to the suffering the industry will have under junior developers using AI. It's definitely made my job easier. And I really don't care. No one cared about me. I have relatively low pay, no health insurance, and no 401K. When the last person left, management replied to his goodbye email saying he'd be replaced in a week. And then they proceeded to try to hire someone in Mexico City. Maintain the same time zone, but pay 3rd world wages and likely to have coercive control over them through desperation. Never found anyone.
I have no love for this industry or any of the "woes" it'll have with AI. Overall it's going to lead to lower wages and less jobs. For those out there producing "AI slop", I support you. It's hardly what they deserve, but they've earned it.
After graduating with a bachelor's degree in Computer Science in December of 2024, my career path so far has been doing sex work and then a minimum wage job once I got finically stable enough to not do sex work, but my financial situation is precarious enough I still have to do sex work off and on when unexpected costs come up. I spent a few months applying to everything I could after getting my degree, but got nothing but automated rejections back if anything.
I didn't have the best networking skills to be fair, but I spent most of my college doing remote classes and didn't have much of a chance to network or whatever. I'm thinking about doing grad school so I can have another chance at developing some kind of network or make myself more attractive to employers. My grades were good and I genuinely enjoy computer science so spending half a year improving my portfolio sounds like a fun time. But going to grad school wouldn't really about getting employment, I just want to use my brain for something. Just working a job makes me feel completely insane, like I know that I can do so much more. I feel like I'm wasting the best years of my life and there's no place in this market where I can be useful. The only value I have is selling my body or being a human stand in for a robot at my "real" job.
Maybe this isn't the best place to post this. I have very little hope that I will ever get a job programming, and I'm just sad. What a waste of a life the past 5 years have been.
On a kind of funny note, I would say that doing sex work is genuinely less humiliating than applying to jobs as a new compsci grad. At least I have some signal that I have some value selling myself.
This isn't the first time that the industry has foot-gunned itself.
The continued reliance on say, COBOL, and the complete lack of those developers comes to mind.
Even before LLMs, there were periods recently where multiple companies had "senior only" hiring policies. That just inflated what "senior" was until it was basically 5 years of experience.
This time seems a bit different, however. There are both supply and demand side problems. The supply of students it tainted with AI "learning" now. Colleges haven't realized that they absolutely have to effectively crack down on AI, or the signal of their degrees will wither to nothing. The demand side is also low, of course, since the candidates aren't good, and AI seems to be a good substitute for a newly graduated hire, especially if that hire is just going to use the AI badly.
> The continued reliance on say, COBOL, and the complete lack of those developers comes to mind.
So the irony here is that LLMs are actually going to be decent at COBOL by default. And other uncommon/esoteric codebases. For example I vibe-ported some Apple ii assembly to modern C/SDL and... it works. It's stuff that I just wouldn't even attempt at manual development speed. It may be actually an easier path than training someone to do things, as long as you have a large enough test suite or detailed enough requirements.
for anyone with children, dont waste their time with traditional school, that path is stone dead and is leading nowhere but the abyss of the permanent underclass
apologise for inflicting this era on them and teach them to be entrepreneurial, teach them how to build, teach them rust on the backend, teach them postgres, teach them about assets maintaining value while money loses its
tell them to never under any circumstances take on a mortgage, especially not the 50 year variety. tell them to stay at home for as long as possible and save as much as possible and put it into assets: gold, silver, bitcoin, monero
they must escape the permanent underclass, nothing else matters
Crazy that you're getting downvoted. You're right about everything. Well, maybe about rust on the backend...
The world is fundamentally different than it was 50 years ago and the same boomer platitudes no longer make sense. We are going to suffer a global economic collapse in the near future (conveniently when the generations to blame are retired or dead) and it's going to reshape our world and what labor looks like.
I just hope that my generation will be kinder to future generations than the last.
We're not hiring a lot of rotary phone makers these days.
Who is hiring their own shoe-smith? It's been 30-ish years since my carpenter father last had work boots resoled.
It's almost as if... technology and economy evolve over time.
For all the arguments software people make about freedom to use their property as they see fit, they ignore non-programmers use of personal technology property is coupled to the opinions of programmers. Programmers ignore how they are middlemen of a sort they often deride as taking away the programmer's freedom! A very hypocritical group, them programmers.
What's so high tech about configuration of machines with lexical constructs as was the norm 60+ years ago? Seems a bit old fashioned.
Programmers are biology and biology has a tendency to be nostalgic, clingy, and self selecting. Which is all programmers are engaged in when they complain others won't need their skills.
As said before, we are not hiring juniors anymore. Or last hire was last year.
As far as I hear from all projects from out customers (finance, insurances, government etc) are neither hiring juniors anymore.
In one of the meetings someone asked: when I go or retire, we won't have anyone to replace me, cause we don't hire juniors, management replied: that is not our problem to discuss.
Nothing has changed. The problem is the same as it always was.
There is an unbounded amount of opportunity available for those who want to grab hold of it.
If you want to rely on school and get the approval of the corporate machine, you are subject to the whims of their circumstance.
Or, you can go home, put in the work, learn the tech, become the expert, and punch your own ticket. The information is freely available. Your time is your own.
this is the end game of capitalism, where the greed driven pursuit of profit wins over social maintenance and development. we see it very clearly with the incredibly socially damaging mass immigration to replenish the slave class and maintain the mythical GDP growth, which is only "necessary" because the native slave classes have been squeezed out of breeding
new grads will be fed to the meat grinder with no regards, its a closed shop unless you know someone
This is entirely due to sociopaths that stole trillions in assets from the general population then bought out law makers to not outlaw their blatant copyright infringement so they can make themselves richer with some self-proclaimed 'noble' aim.
The general population is being rapidly sacked as a 'necessary' expense of criminal elites.
This article is an advertisement for what appears to be a networking service, something which is not really made clear until near the end.
The article is self-serving in identifying the solutions ("do things related to the service we offer, and if that doesn't work, buy our service to help you do them better"), but it is a subject worth talking about, so I will offer my refutation of their analysis and solution.
The first point I'd like to make is that while the hiring market is shrinking, I believe it was long overdue and that the root cause is not "LLMs are takin' our jerbs", but rather the fact that for probably the better part of two decades, the software development field has been plagued by especially unproductive workers. There are a great deal of college graduates who entered the field because they were promised it was the easiest path to a highly lucrative career, who never once wrote a line of code outside of their coursework, who then entered a workforce that values credentialism over merit, who then dragged their teams down by knowing virtually nothing about programming. Productive software engineers are typically compensated within a range of at most a few hundred thousand dollars, but productive software engineers generally create millions in value for their companies, leading to a lot of excess income, some of which can be wasted on inefficient hiring practices without being felt. This was bound for a correction eventually, and LLMs just happened to be the excuse needed for layoffs and reduced hiring of unproductive employees[1].
Therefore, I believe the premise that you need to focus entirely on doing things an LLM can't -- networking with humans -- is deeply faulty. This implies that it is no longer possible to compete with LLMs on engineering merit, and I could not possibly disagree more. Rather than following their path forward, which emphasises only networking, my actual suggestion to prospective junior engineers is: build things. Gain experience on your own. Make a portfolio that will wow someone. Programming is a field that doesn't require apprenticeship. There is not a single other discipline that has as much learning material available as software development, and you can learn by doing, seeing the pain points that crop up in your own code and then finding solutions for them.
Yes, this entails programming as a hobby, doing countless hours of unpaid programming for neither school nor job. If you can't do that much, you will never develop the skills to be a genuinely good programmer -- that applied just as much before this supposed crisis, because the kind of junior engineer who never codes on their own time was not being given the mentorship to turn into a good engineer, but rather was given the guidance to turn them into a gear that was minimally useful and only capable of following rote instructions, often poorly. It is true that the path of the career-only programmer who goes through life without spending their own time doing coding is being closed off. But it was never sustainable anyways. If you don't love programming for its own sake, this field is not likely to reward you going forward. University courses do not teach nearly effectively enough to make even a hireable junior engineer, so you must take your education into your own hands.
[1] Of course, layoff processes are often handled just as incompetently as hiring processes, leading to some productive engineers getting in the crossfire of decisions that should mostly hurt unproductive engineers. I'm sympathetic to people who have struggled with this, but I do believe productive engineers still have a huge edge over unproductive engineers and are highly likely to find success despite the flaws in human resource management.
Hey there, I'm the developer of the app along with my wife, the author of the post. We quit our jobs over a year ago to work on a problem we care about and helping people connect to their goals through people is what we landed on. That being said, we spend most of our time on the tech! And I think your advice is spot on, that a portfolio of projects really is THE MOST IMPORTANT THING. It's where I would tell people to start. But from there, connecting people to others who care about that portfolio, is also important. I think a lot of technical people pay attention to the former, and tend to ignore the latter. Which is me too! So rather than "this is the only true way" I hope it comes across like a potential piece of the puzzle to some people.
Thanks for giving it some thought and for your perspectives, they really help.
> This article is an advertisement for what appears to be a networking service, something which is not really made clear until near the end.
I have been seeing an uptick of articles on HN where someone identifies a problem, then amps it up a bit more and then tells you that they are the right ones to solve it for a fee.
These things should not be taken seriously and upvoted.
The problem is that praying that someone stumbles upon your brilliant hobby projects and offers you a job is a terrible bet. Yes, you have to be good a software development, but being good at software development doesn't land you job. Being good at software development, and cutting through the noise gets you a job. Because even if all those laid off people are incompetent, they're still applying for the same jobs you are, and it is very difficult to identify who's who.
So, from a individual's perspective, figuring out how to meet people who will help you sidestep the "unwashed masses" pile of applications is probably the next most important thing after technical competence (and yeah, ranking above technical excellence).
The first graph is interesting: it showed all groups about the same until late 2022 when they start to diverge. Around that time, we were talking about "greedflation" and "over hired during covid", and probably most important, the first year after expiration of Section 174 R&D was 2022.
Good luck with causation/correlation vs the rise of LLM.
This topic requires analysis to a greater depth than most comments I've seen so far.
It wasn't too long ago that it was common to read threads on HN and other tech fora about universities graduating software engineers seriously lacking coding skills. This was evidenced by often-torturous interview processes that would herd dozens to hundreds of applicants through filters to, among other things, rank them based on their ability to, well, understand and write software.
This process is inefficient, slow and expensive. Companies would much rather be able to trust that a CS degree carries with it a level of competence commensurate with what the degree implies. Sadly, they cannot, still, today, they cannot.
And so, the root cause of the issue isn't AI or LLM's, it's universities churning people through programs and granting degrees that often times mean very little other than "spent at least four years pretending to learn something".
If you are thinking that certain CS-degree-granting universities could be classified as scams, you might be right.
And so, anyone with half a braincell, will, today, look at the availability of LLM tools for coding as a way to stop (or reduce) the insanity and be able to get on with business without having to deal with as much of the nonsense.
Nobody here makes a product or offers a service (hardware, software, anything) for the love of the art. We make things to solve problems for people and services. That's why you exists. Not to look after a social contract (as a comment suggested). Sorry, that's nonsense. The company making spark plugs makes spark plugs, they are not on this planet to support some imaginary public good. Solving the problem is how they contribute.
And, in order to solve problems, you need people who are capable of deploying the skills necessary to do so. If universities are graduating people who can barely make a contribution to the mission at hand, companies are going to always look for ways to mitigate that blocking element. Today, LLM's are starting to provide that solution.
So it isn't about greed or some other nonsense idealistic view of the universe. If I can't hire capable people, I will gladly give senior engineers more tools to support the work they have to do.
As is often the case, the solution to so many problems today --including this one-- is found in education. Our universities need to be setup to succeed or fail based on the quality of the education they deliver. This has almost never been the case. Which means you have large scale farming operations granting degrees that can easily be dwarfed by an LLM.
And don't think that this is only a problem a the entry level. I recently worked with a CTO who, to someone with experience, was so utterly unqualified for the job it was just astounding that he had been give the position in the first place. It was clearly a case of him not knowing just how much he didn't know. It didn't take much to make the case for replacing him with a qualified individual or risk damage to the company's products and reputation going forward.
A knowledgeable entry-level professional who also has solid AI-as-a-tool skills is invaluable. Note that first they have to come out of university with real skills. They cannot acquire those after the fact. Not any more.
NOTE:
To the inevitable naive socialist/communist-leaning folks in our mix. Love your enthusiasm and innocence, but, no, companies do not exist to make a profit. Try starting one for once in your naive life with that specific mission as your guiding principle and see how far you'll get.
Companies succeed by solving problems for people and other companies. Their clients and customers exchange currency for the value they deliver. The amount they are willing to pay is proportionate to the value of the problem being solved as perceived by the customer --and only the customer.
Company management has to charge more than the mere raw cost of the product or service for a massive range of reasons that I cannot possibly list here. A simple case might be having to spend millions of dollars and devote years (=cost) to creating such solutions. And, responsible companies, will charge enough to be able to support ongoing work, R&D, operations, etc. and have enough funds on hand to survive the inevitable market downturns. Without this, they would have to let half the employees go every M.N years just because of natural business cycles.
So, yeah, before you go off talking about businesses like you've never started or ran a non-trivial anything (believe me, it is blatantly obvious when reading your comments), you might want to make an attempt to understand that your stupid Marxists professors or sources had absolutely no clue, were talking out of their asses, never started or ran a business, and everything they pounded into your brains fails the most basic tests with objective, on-the-ground, skin-in-the-game reality.
A lot of this may be due to the recent far left changes in curriculum at many universities. A degree used to sort of a certificate an employer could rely upon that someone had basic skills. That is no longer the case. This makes older employees where the certificate was still reliable more attractive.
> We used to have a training ground for junior engineers, but now AI is increasingly automating away that work. Both studies I referenced above cited the same thing - AI is getting good at automating junior work while only augmenting senior work. So the evidence doesn’t show that AI is going to replace everyone; it’s just removing the apprenticeship ladder.
Was having a discussion the other day with someone, and we came to the same conclusion. You used to be able to make yourself useful by doing the easy / annoying tasks that had to be done, but more senior people didn't want to waste time dealing with. In exchange you got on-the-job experience, until you were able to handle more complex tasks and grow your skill set. AI means that those 'easy' tasks can be automated away, so there's less immediate value in hiring a new grad.
I feel the effects of this are going to take a while to be felt (5 years?); mid-level -> senior-level transitions will leave a hole behind that can't be filled internally. It's almost like the aftermath of a war killing off 18-30 year olds leaving a demographic hole, or the effect of covid on education for certain age ranges.
Adding to this: it's not just that the apprenticeship ladder is gone—it's that nobody wants to deal with juniors who spit out AI code they don't really understand.
In the past, a junior would write bad code and you'd work with them to make it better. Now I just assume they're taking my feedback and feeding it right back to the LLM. Ends up taking more of my time than if I'd done it myself. The whole mentorship thing breaks down when you're basically collaborating with a model through a proxy.
I think highly motivated juniors who actually want to learn are still valuable. But it's hard to get past "why bother mentoring when I could just use AI directly?"
I don't have answers here. Just thinking maybe we're not seeing the end of software engineering for those of us already in it—but the door might be closing for anyone trying to come up behind us.
> Now I just assume they're taking my feedback and feeding it right back to the LLM.
This is especially annoying when you get back a response in a PR "Yes, you're right. I have pushed the fixes you suggested."
Part of the challenge (and I don't have an answer either) is there are some juniors who use AI to assist... and some who use it to delegate all of their work to.
It is especially frustrating that the second group doesn't become much more than a proxy for an LLM.
New juniors can progress in software engineering - but they have to take the road of disciplined use of AI and make sure that they're learning the material rather than delegating all their work to it... and that delegating work is very tempting... especially if that's what they did in college.
I get that. I think that getting to know juniors outside of work, at a recurring meetup or event, in a setting where you can suss out their motivation level and teachability level, is _a_ way of going about it. That way, if your team is hiring juniors, you have people you have already vetted at the ready.
> Just thinking maybe we're not seeing the end of software engineering for those of us already in it—but the door might be closing for anyone trying to come up behind us.
It's worth considering how aggressively open the door has been for the last decade. Each new generation of engineers increasingly disappointed me with how much more motivated they were by a big pay check than they were for anything remotely related to engineering. There's nothing wrong with choosing a career for money, but there's also nothing wrong about missing a time when most people chose it because they were interested in it.
However I have noticed a shift: while half the juniors I work with are just churning out AI slop, the other half are really interested in the craft of software engineering and understanding computer science better.
We'll need new senior engineers in a few years, and I suspect they will come from a smaller pool of truly engaged juniors today.
> I think highly motivated juniors who actually want to learn are still valuable.
But it's hard to know if a candidate is one of those when hiring, which also means that if you are one of those juniors it is hard for you to prove it to a prospective employer.
> Adding to this: it's not just that the apprenticeship ladder is gone—it's that nobody wants to deal with juniors who spit out AI code they don't really understand.
I keep hearing this and find it utterly perplexing.
As a junior, desperate to prove that I could hang in this world, I'd comb over my PRs obsessively. I viewed each one as a showcase of my abilities. If a senior had ever pointed at a line of code and asked "what does this do?" If I'd ever answered "I don't know," I would've been mortified.
I don't want to shake my fist at a cloud, but I have to ask genuinely (not rhetorically): do these kids not have any shame at all? Are they not the slightest bit embarrassed to check in a pile of slop? I just want to understand.
>Now I just assume they're taking my feedback and feeding it right back to the LLM.
seems like something a work policy can fix quickly. If not something filtered in the interview pipeline. I wouldn't just let juniors go around and try to copy-pasting non-compilable Stackoverflow code, why would I do it here?
New students are presented with agentic coding now, so it's possible that CS will become a more abstract spec refine + verify. Although I can't make it work in my head, that's what I took from speaking with a young college student.
Some juniors are even using AI for communication in Slack channels or even DMs. It's so uncanny.
I don't know what world you're living in but software development has always been a cut throat business. I've never seen true mentoring. Maybe a code review where some a-hole of a "senior" developer would come in having just read "clean code" and use some stupid stylistic preferences as a cudgel and go to town on the juniors. I'm cynical enough to believe that this, "AI is going to take your programming job!" is just a ploy to thin out the applicant pool.
My hottest take on this is that it might be healthy for the business. During the recent boom everyone and their grandmother's dog got a job as software engineers, and some aren't really fit for it.
AI provides a bar. You need to be at least better than AI at coding to become a professional. It'll take genuine interest in the technology to surpass AI and clear that bar. The next generation of software professionals will be smaller, but unencumbered by incompetents. Their smaller number will be compensated by AI that can take care of the mundane tasks, and with any luck it's capabilities will only increase.
Surely I'm not the only one who's had colleagues with 10+years experience who can't manage to check out a new branch in git? We've been hiring people we shouldn't have hired.
The only problem is that people need to earn a living while they’re trying to get better than that bar.
Is there bar is set at a competent mid level engineer, people entering the industry need a path from algorithms 101 to above that bar which involves getting paid.
It's not helping that in the last 10 years a culture of job-hopping has taken over the tech industry. Average tenure at tech companies is often ~2 years and after that people job hop to increase compensation.
It's clear why people do it (more pay) but it sets up bad incentives for the companies. Why would a company invest money in growing the technical skill set of an employee, just to have them leave as soon as they can get a better offer?
When I'm hiring an engineer, HR will easily let me bump up the offer by $10-20K if the candidate counters. It is nearly impossible to get that same $10-20K bump for an existing engineer that is performing extremely well. Companies themselves set up this perverse incentive structure.
One would assume the solution is to simply offer a good package and retain employees with that. I returned to an old company after a few years of floating around because I realized they had the perfect mix of culture and benefits for me, even if the pay isn't massive.
You're falling for the exact same fallacy experienced by failed salesmen. "Why would I bother investing time in this customer when they're just going to take my offer to another dealership for a better deal?"
Answer: you offer a good deal and work with people honestly, because if you don't, you'll never get a customer.
> It's not helping that in the last 10 years a culture of job-hopping has taken over the tech industry. Average tenure at tech companies is often ~2 years and after that people job hop to increase compensation.
I've started viewing developers that have never maintained an existing piece of software for over 3 years with skepticism. Obviously, with allowances for people who have very good reasons to be in that situation (just entered the market, bad luck with employers, etc).
There's a subculture of adulation for developers that "get things done fast" which, more often than not, has meant that they wrote stuff that wasn't well thought out, threw it over the wall, and moved on to their next gig. They always had a knack of moving on before management could connect the dots that all the operational problems were related to the person who originally wrote it and not the very-competent people fixing the thing. Your average manager doesn't seem to have the capability to really understand tech debt and how it impacts ability to deliver over time; and in many cases they'll talk about the "rock star" developer that got away with a glimmer in their eye.
Saw a post of someone on Hacker News the other day talking about how they were creating things faster than n-person teams, and then letting the "normies" (their words not mine) maintain it while moving on to the next thing. Thats exactly the kind of person I'd like to weed out.
Funny, I was at my previous company almost exactly two years. They never even gave me a cost of living increase, much less a "raise." So I was effectively earning less each year. Change needs to happen from both sides if extended tenure is the goal.
You have cause and effect reversed. Companies stopped training workers and giving them significant raises for experience, so we started job hopping.
Some genius MBA determined that people feel more rewarded by recognition and autonomy than pay, which is actually true. But it means that all the recognition and autonomy in the world won't make you stay if you can make 50% more somewhere else.
Why didn't companies just grant raises more aggressively? Was the ease of poaching engineers not a clear market signal?
Arguably, the cross-pollination of developers moving around is good for employers.
People have been saying this for at least 30 years.
They have this exact problem with scientific glassblowing, and it's been decades in the making. Manufacturing improvements now mean that you can buy almost everything from a factory, and only need experienced glassblowers for fancy, one-off stuff.
But that means there's no need for entry-level glassblowers, and everyone in the field with any significant experience is super old. The pipeline has been dead for a while now.
This will naturally select for the people who are self driven learners. In a sense this is nothing new, just a continued progression of the raising of the bar of who is still able to contribute economic value to the market
How will they learn without opportunity?
> AI means that those 'easy' tasks can be automated away, so there's less immediate value in hiring a new grad.
Not disagreeing that this is happening in the industry but it still feels like a missed opportunity to not hire juniors. Not only do you have the upcoming skill gap as you mention, but someone needs to instruct AI to do these menial/easy tasks. Perhaps it's only my opinion but I think it would be prudent to instead see this as just having junior engineers who can get more menial tasks done, instead of expecting to add it to the senior dev workflow at zero cost to output.
> mid-level -> senior-level transitions will leave a hole behind that can't be filled internally.
Tech companies are betting that in 5 years, AI should be good enough to replace mid-levels.
Rinse and repeat with seniors 5 years after that.
Hard to say if that bet will pay off, or what the endgame would be; just the CEO commanding an company of AIs?
High risk bets like that cause bubbles. If that bet doesnt pay off then there will be a talent crisis that the american tech industry may not recover from
I think the current grads are going to be shafted either way. In 5 years, there might be more opening for "fresh" young grads and the companies will prefer them over the young people who're just graduating.
“automate it away” ironically still requires a human in the chain to determine what to automate, how, and to maintain that automation. Whether it be derived from an ai or a systemd script or an Antikythera mechanism. Now if you leave that to seniors you just ate a big chunk of their day playing shephard to a dozen plus “automated” pipelines while they still have stuff to do outside the weeds. Now you need more seniors and pretty soon they want triple what you could pay a junior and I don’t think they are 3x more prolific if the junior is managed efficiently quite frankly.
The process of setting up and maintaining automation should be less labor intensive than just doing it manually (or else why would you automate it?) and almost always requires a more advanced skillset than doing the manual task.
I hope juniors will figure out how to use AI to do larger tasks that are still annoying for seniors to do, while seniors take on larger tasks still. I think it's just seniors are learning this stuff faster at the moment and adapting it faster to current work, but as all that changes I would guess juniors reclaim some value back.
That said, you hit on something I've been feeling, the thing these models are best at by far is stuff that wasn't worth doing before.
I've been making use of copilot in VSCode to make changes in a codebase that's new to me, in a language that I can read if not necessarily write unaided - it's a dialect of SQL, so I can certainly understand what's happening, but generating new queries is very time-consuming (half of which is just stupid formatting stuff). Copilot seems to understand the style of the code in my project and so I don't have to do much work to make it conform, compared to my hand-written versions.
I've also written a lot of python 2 in my career, and writing python 3 still isn't quite native-level for me - and the AI tools let me make up for my lack of knowledge of modern Python.
Some juniors do figure it out, but my experience has been that the bar for such juniors is a lot higher than pre-AI junior positions, so there is less opportunity for junior engineers overall.
My 2 cents: they're too expensive.
We had code school grads asking for $110-$130. Meanwhile, I can hire an actual senior engineer for $200 and he/she will be easily 4x as productive and useful, while also not taking a ton of mentorship time.
Since even that $110 costs $140, it's tough to understand how companies aren't taking a bath on $700/day.
If you're hiring in SF or NY, then the problem explains itself. Even a single young new grad needs that much to so live.
you can't have rent at 3.5k a month and not expect 6 figures when requiring in-office work. old wisdom of "30% of salary goes to rent" suggest that that kind of housing should only be rented if you're making 140k. Anyone complaining about junior costs in these areas needs to join in bringing housing prices down.
Good new-grads in expensive areas are going to cost $100-$130k. This is a bargain considering a few years back they could get $200-$350k.
Bear in mind these types can explain things like why word-alignment matters and train themselves into being net productive within a few weeks.
Yep, the value isn't there. I'm on a very lopsided team, about 5 juniors to 1 senior. Almost all of the senior time is being consumed in "mentorship", mostly slogging through AI slop laden code reviews. There have been improvements, but it's taking a long time.
I entered the job market in late 2000. There was no reason to hire a junior engineer when every hiring manager and senior engineer knew 10 friends who recently lost their jobs. I found work on less desirable projects and yes it affected my career trajectory and it sucked. Starting out has always sucked for most people.
Anyone reccomend an analysis, article or book or video, of this effect on the blue collar industry decades ago?
It's happening again now with robotics, self-driving vehicles and RL. Factory workers, truck drivers, construction work, order fulfillment, machinists, farm work, medical technicians and more are all very much at risk (same thing as OP: mostly junior roles getting automated). Some info at https://arxiv.org/pdf/2510.25137
> AI means that those 'easy' tasks can be automated away, so there's less immediate value in hiring a new grad
Plenty of skilled work requires a master’s or PhD. CS, for those who want a safe, secure job, looks like it’s going that way.
Do you mind giving some examples of the work that annoys seniors?
For me the most annoying would be a technically correct solution that completely ignores the “higher-level style” of the surrounding code, at the same time defending the chosen solution by referencing some “best practices” that are not really applicable there for some higher-level reasons, or by insignificant performance concerns. Incidentally, LLMs often produce similar problems, only one doesn’t need to politely argue with them.
Writing unit tests, manual validation work, manual testing. Automating Deployments of infrastructure, DNS work, tracking down annoying one off bugs, fixing and validating dependency issues.
Basically this type of maintenance work for any sufficiently complex codebase. (Over 20k LOC)
When I was an QA intern / Software Dev Intern. I did all of that junk.
We might need a lot of young adults for war in the near future, according to some.
Larger scale war happens when the lives of young people are more valuable as fodder for the war machine than in a field or behind a desk.
I don't know if that's it. Speaking from outside the tech space: most of my office jobs since 2012 have been "doing the easy/annoying tasks that had to be done, but more senior people didn't want to 'waste time' dealing with."
So, there are two parts to this:
The first is that a lot of those tasks are non-trivial for someone who isn't a digital native (and occasionally trivial for people who are). That is to say that I often found myself doing tasks that my bosses couldn't do in a reasonable time span; they were tasks which they had ALWAYS delegated, which is another way of saying that they were tasks in which proficiency was not necessary at their level.
This leads into the second part, which is that performing these tasks did not help me advance in relevant experience at all. They were not related to higher-level duties, nor did they endear me to the people who could have introduced me to such duties. My seniors had no interest in our growth as workers; anyone who wanted to see that growth had to take it into their own hands, at which point "junior-level" jobs are only worth the paycheck.
I don't know if it's a senior problem generally, or something specific to this cohort of Boomer/Gen-X seniors. Gun-to-my-head, I would wager the latter. They give enough examples in other arenas of public life to lend credence to the notion that that they simply don't care what happens to their juniors, or to their companies after they leave, particularly if there is added hassle in caring. This is an accusation often lobbed at my own generation, to which I say, it's one of the few things our forebears actually did teach us.
Yet again, AI is just a cover for mismanagement.
I grew up in the 70s. The hand wringing then was calculators. No one was going to be able to do math anymore! And then wrist watches with calculators came out. Everyone is going to cheat on exams, oh no!
Everything turned out fine. Turns out you don't really need to be able to perform long division by hand. Sure, you should still understand the algorithm at some level, esp. if you work in STEM, but otherwise, not so much.
There were losses. I recall my AP physics professors was one of the old school types (retired from industry to teach). He could find the answer to essentially any problem to about 1-2 digits of precision in his head nearly instantly. Sometimes he'd have to reach for his slide rule for harder things or to get a few more digits. Ain't no one that can do that now (for reasonable values of "no one"). And, it is a loss, in that he could catch errors nearly instantly. Good skill to have. A better skill is to be able to set up a problem for finite element analysis, write kernels for operations, find an analytic solution using Mathematica (we don't need to do integrals by hand anymore for the mot part), unleash R to validate your statistics, and so on. The latter are more valuable than the former, and so we willingly pay the cost. Our ability to crank out integrals isn't what it was, but our ability to crank out better jet engines, efficient cars, computer vision models has exploded. Worth the trade off.
Recently watched an Alan Guth interview, and he made a throwaway comment, paraphrased: "I proved X in this book, well, Mathematica proved...". The point being that the proof was multiple pages per step, and while he could keep track of all the sub/superscripts and perform the Einstein sums on all the tensors correctly, why??? I'd rather he use his brain to think up new solutions to problems, not manipulate GR equations by hand.
I'm ignoring AGI/singularity type events, just opining about the current tooling.
Yah, the transition will be bumpy. But we will learn the skills we need for the new tools, and the old skills just won't matter as much. When they do, yah, it'll be a bit more painful, but so what, we gained so much efficiency we can afford the losses.
This assumes there will still be a demand for software developers in 5 years. I believe we'll be out of jobs much sooner than that.
> I feel the effects of this are going to take a while to be felt (5 years?);
Who knows if we'll even need senior devs in 5 years. We'll see what happens. I think the role of software development will change so much those years of technical experience as a senior won't be so relevant but that's just my 5 cents.
The way I'm using claude code for personal projects, I feel like most devs will become moreso architects and testers of the output, and reviewers of the output. Which is good, plenty of us have said for ages, devs dont read code enough. Well now you get to read it. ;)
While the work seems to take similar amounts of time, I spend drastically less time fixing bugs, bugs that take me days or God forbid weeks, solved in minutes usually, sometimes maybe an hour if its obscure enough. You just have to feed the model enough context, full stack trace, every time.
[dead]
> The social contract between large companies and employees has been broken for years now. US companies are optimized for quarterly earnings, not long term investment in their employees.
Going to throw out another anecdote here. At a company that a number of my friends work for (a fortune 50), they are currently making record profits that they loudly brag about during employee townhalls. They also are in the process of gutting multiple departments as fast as possible with little regard for the long term consequences. This is not the only company that I know of acting in this way (acting like they're about to go bankrupt when in fact they are seeing record profits).
To me the societal risk is that an entire generation of employees becomes extremely jaded and unmotivated, and fairly so. We used to work under the assumption that if our company is successful, then the employees would be successful. Record profits == raises for all, bonuses for all. And while we know that that connection was never that strong, it was strong enough to let us at least pretend that it was a law of universe.
That fundamental social contract is now at its breaking point for so many workers. Who can really blame people for putting in minimal effort when they have so much evidence that it will not be rewarded?
Those of us familiar with the Dilbert comic strip of the '90s-'00s are having a good chuckle at the idea that there was ever a social contract. What you think of as a social contract was a fiction enabled only by the explosive growth of the software industry during the Internet and mobile web of the last twenty years. It's easy to be generous to employees when the profits just keep growing on their own. It's easy to overlook mediocrity (and sub-mediocrity) when as many warm bodies are possible are needed to fulfill business objectives.
That's all over now; the growth spurt of a young software industry has given way to maturity. We'll be navigating an employment environment much like what the norm is in other technical professions with tougher standards and fiercer competition for good jobs.
>It's easy to overlook mediocrity (and sub-mediocrity) when as many warm bodies are possible are needed to fulfill business objectives.
dismissing technical talent as "warm bodies" is exactly how the old guard of IBM/AT&T/Oracle fell to the new scrappy talent. I'm sure history will repeat itself again in due time.
> We'll be navigating an employment environment much like what the norm is in other technical professions with tougher standards and fiercer competition for good jobs.
if every other sector except healthcare wasn't experiencing the same thing, you may have a point. This clearly isn't a problem limited to tech, though.
The last social contract between companies and employees was during the New Deal era. It's been downhill ever since.
I think a lot of this has to do with the explosion of CEO (and by extension CxO) pay over the past 30 years.
Today, a CEO can turn in a few quarters of really solid earnings growth, they can earn enough to retire to a life a private jets. Back when CxO pay was lower, the only way to make that kind of bank was to claw your way into the top job and stay there for a decade or more.
The current situation strongly incentivizes short-term thinking.
With today's very high, option-heavy compensation a CEO making long-term investments in the company rather than cutting staff and doing stock buybacks is taking money out of his own pocket.
It's a perverse incentive.
CEO’s also never face consequences for destroying companies. Zaslav has run WBD into the ground and it’s currently being surrounded by vultures, and he’s still making like half a billion a year.
While I definitely agree CEO pay is quite egregious, in theory, to mitigate short-sighted quarterly earnings hyperoptimization, couldn't a board simply tie equity incentives to performance targets and timeframes though?
Lip Bu Tan, for instance, has performance targets on a five year timeline, which are all negated if the stock falls below a certain threshhold in 3 years. [1]
Or, ever controversial Elon Musk, certainly has an (also egregious) $1 Trillion dollar pay package, but it has some pretty extreme goals over 10 years, such as shipping 1 million Optimus robots [2].
All in all, we can debate about the Goodharting of these metrics (as Musk is keen to do), but I feel boards of these public companies are trying to make more long-term plans, or at least moving away from tying goals to pure quarterly metrics. Perhaps we can argue about the execution of them.
Note: I own neither of these stocks and my only vested interest is buying the S&P.
[1] https://www.cnbc.com/2025/03/14/new-intel-ceo-lip-bu-tan-to-... [2] https://www.bbc.com/news/articles/cwyk6kvyxvzo
IMO it's not risk so much as foregone conclusion. You can see the hopelessness in GenZ and (to a lesser extent) millennials.
But we only care about short term metrics now, so no one cares. They don't even care to develop the tools to understand it. It might as well not exist. Blame the young people and move on.
> This is not the only company that I know of acting in this way
At this point in the tech industry, it'd be easier to name companies not doing this. Maybe Apple? I think they got aroudn it by not renewing contractors. But I might have missed something.
>To me the societal risk is that an entire generation of employees becomes extremely jaded and unmotivated, and fairly so.
I sure am jaded. But more motivated than now in my goals. They used to be to be this knowledgeable IC who can dig deep into a domain, but it's definitely been shifting to being able to sustain myself off my talents. I'll grab short term contracts and let my own products be the steady income.
(yeah, a lot easier said than done. But I have time to prepare for that).
>Who can really blame people for putting in minimal effort when they have so much evidence that it will not be rewarded?
Worse than that. Why put in effort when your reward for providing all that value is still getting the axe?
My industry is finally starting to see real moves at unionizing, but I hope tech as a whole is starting to wake up to this fact?
Any CEO that retains underperforming teams just because the overall company is doing well is a fool.
If you want to avoid getting laid off, make sure the product of your work is more valuable than your salary.
It's more like "this product is underperforming, let go of the team". Regardless of the reasons the product is underperforming. Could be that it was still in development and money dried, could be that they want to pull out of a region and need a product as an excuse.
You can't outwork corporate greed, unless you're working for peanuts in a 3rd world country. Then you're truly irreplacable (and still broke).
"Show me the incentive and I will show you the outcome" - Charlie Munger
What social contract? Companies have always been for shareholders. Do you people have some kind of contract with Tesla that I don't know about?
This entire discussion sounds crazy to me. If you want socialism, vote for socialism. If you want raw unfiltered capitalism, vote for the billionaire. You can't vote for the billionaire and expect safety nets. That's madness.
> What social contract? Companies have always been for shareholders.
You are not wrong, but the contract is/was metaphorical. For a long time people were able to make a living for themselves by studying hard (usually STEM) and end up with a career which payed off. That was the invisible "contract". Hell I went to university for things which seem like academic navel gazing, but I still got a good tech job on the other side. That's not the reality for a lot of graduates nowdays who take more practical degrees at masters and phd levels.
Again even if the literal statement is clearly false, it is the sentiment which matters, and this sentiment does not just apply to graduates. I think many just feel like working hard does not work anymore, especially in the face of housing, cost of living, job competition and social media flaunting the wealth of others.
I get the idea from my younger siblings, "Why try if you are already a looser."
Henry Ford for all his faults (and there were MANY) at least understood that you gotta have a customer base for your products, and that paying workers well helps everybody out.
It is not socialism to note that in the past, some companies have believed that their optimal relationship with their employees required recognizing their value and awarding them accordingly, thusly allowing them to attract/retain the best employees as well as maximizing the quality of the output from those employees. There has always been such a spectrum, that's not socialism. The trend to notice is that the spectrum is so strongly weighted towards the merciless, cutthroat end of things that may actually not be optimal for long term survivability of those companies whilst also as I noted, be breaking the social contract that workers have assumed for decades, which is also not socialism.
Socialism has a specific meaning, it's not just a label we get to put on behaviors that we - or rather, specifically you in this case - don't like.
Socialism is when the state (ie: the government) _owns_ industries.
A social contract is an implicit agreement that everyone more or less accepts without anything being necessarily legally binding.
For example, the courtesy of two weeks notice in the US is a social contract: there’s nothing legally requiring it, but there are _social_ consequences (ie: your reference might be less positive) if you don’t follow it.
Everything that’s kind of in an employee’s favor is not socialism. You don’t have to like the idea of “work hard, help the company do well, get rewarded,” but that isn’t socialism. It’s just a thing you don’t like.
>Companies have always been for shareholders.
well we can trace that back to the 1920's, for one example.
>Do you people have some kind of contract with Tesla that I don't know about?
Are you aware of what a "social contract" is? There's nothing wrong with seeking to fill in gaps of knowledge.
>This entire discussion sounds crazy to me. If you want socialism, vote for socialism.
I'd be down for it, but this is almost orthogonal to the main point of the discussion. Social contracts exist in all forms of governing. Even rampant capitism has the bare bones social contract of "don't make your customers TOO angry so you can maximize extraction".
When billionaires own the media companies that influence public opinion and have legal avenues to essentially bribe elected officials, does the public have a meaningful avenue to vote anti-billionaire?
I suspect this junior hiring crisis thing is linked to the ridiculous hoops people are put through to get a job these days.
When I was starting, you were checked for potential as a trainee. In my case, options trading. They checked over that you could do some mental arithmetic, and that you had a superficial idea of what trading was about. Along with a degree from a fancy university, that was all that was needed. I didn't know much about coding, and I didn't know much about stochastic differential equations.
A couple of weeks ago, a young guy contacted me about his interview with an options trading firm. This guy had spent half a year learning every stat/prob trick question ever. All those game theory questions about monks with stickers on their foreheads, all the questions about which card do you need to turn over, the lot. The guy could code, and had learned a bunch of ML to go with it. He prepared for their trading game with some really great questions to me about bet sizing.
I was convinced he was simply overly nervous about his prospects, because I'd never met someone so well prepared.
Didn't get the job.
Now I can assure you, he could have done the job. But apparently, firms want to hire people who are nearly fully developed on their own dime.
When they get their analyst class, I guess there is going to be nobody who can't write async python. Everyone will know how to train an ML on a massive dataset, everyone will already know how to cut latency in the system.
All things that I managed to learn while being paid.
You gotta ask yourself whether we really want a society where people have to already know the job before they get their first job. Where everyone is like a doctor: already decided at age 16 that this was the path they wanted to follow, choosing classes towards that goal, and sticking with it until well into adulthood. And they have to essentially pay to get this job, because it comes at at cost of exploring other things (as well as actual money to live).
I've found that this phenomenon exacerbates inequality too:
If you attend a well-known college that bigco's hire from frequently, there's a lot of knowledge floating around about interview prep, hiring schedules, which companies pay the best, etc. Clubs host "interview prep workshops" where they'd teach the subject matter of interviews, host events(hackathons, case competitions, etc.) to help you bolster your resume for applying to these bigco's. So just by attending a better/fancier school, you'd have pretty decent odds of eventually getting a job at one of these prestigious places.
If you were to attend a less prestigious school, regardless of your aptitude or capability, the information asymmetry is so bad that you'll never learn of the prerequisites for even being considered for some of these roles. Not many upperclassmen will have interned at fancy employers, so they won't be there to help you drill dynamic programming/black-scholes/lbo models, and won't tell you that you need to have your applications prepped by a certain date, and won't tell you that you should be working on side projects/clubs, etc.
I suppose that the apprenticeship model biases towards people that already have connections, so perhaps inequality was already bad, whereas now we just have an information asymmetry that's more easily solvable.
Currently, it is not just juniors. It is people of all seniorities, who have to jump through ridiculous hoops, to be believed, that they are any good.
Built most of the software of a company where I worked for 7y from humble beginnings to >80 people. Still gotta line up for a 4h on-site assessment! Built tons of free time projects, some more complex than anything one would usually build on the job. Still gotta have live coding interviews and no one can be arsed to even check my publicly available repos...
I'd say that "normal" (notjunior, not senior) level people have the hardest time ATM. Most jobs are either for juniors or seniors, not inbetween (anecdotal data from my experience job hunting for the last year in austria)
> You gotta ask yourself whether we really want a society where people have to already know the job before they get their first job. Where everyone is like a doctor: already decided at age 16 that this was the path they wanted to follow, choosing classes towards that goal, and sticking with it until well into adulthood. And they have to essentially pay to get this job, because it comes at at cost of exploring other things (as well as actual money to live).
With the way higher-ed works in the US, and the way certain schools opportunity hoard to an insane degree, that is effectively already the case for whole industries and has been so for decades at this point. It's practically an open secret that getting into some schools is the golden ticket rather than the grades you earn while there. Many top schools are just networking and finishing schools for whole "elite" industries.
>You gotta ask yourself whether we really want a society where people have to already know the job before they get their first job
That'd be fine... meanwhile, the new loop we come into:
- okay, so what does your company need and do
Company: "that's under NDA/trade secrets, we can't tell you"
- okay. we can't see what you want to you'll have to train them
Company: "we don't want to train people, they just need to hit the ground running"
- okay. we'll just let colleges train the fundamentals and have others figure it out
Company: "no one's training anyone anymore. Where did the juniors go?"
Even doctors have apprenticeship programs. An industry where no one wants to train the next generation is a doomed one. If the US doesn't do it, some other country will gladly take it up.
I feel like only the biggest companies can afford to put up all these roadblocks to employment.
A smaller size company, perhaps in a lower COL city, might have a more "human" side to them, simply because they can't afford all the nonsense.
Sadly, tarriffs are making those companies scared at best and defunct at worst, so they also aren't hiring.
Haven’t seen anyone mention this but this is how it works in China. You have to study the same thing since you were 16 and completely ace it. If you decide during or after college that you don’t like the job path you chose (or really your parents chose) as a teenager then too bad. You’re locked into it for life or you’re stuck with never getting a job because the job market in China for young people is so horrendous. (Much higher youth unemployment rate)
They have terrible interviews there as well that go much deeper than here. They’ll analyze your family - not just you.
This is just a symptom of a really bad economy. That’s what the US is in right now. China’s youth are suffering from this as well.
This is the replacement for credentialism, love it or hate it.
You don't need a fancy school to get into a top firm anymore. You have to master the hell out of the interview.
no point mastering an interview you're never even invited to because you lack connections or can't get past the ATS.
Some hiring managers prioritize technical skill but its only one part of whether the interviewers "like" a candidate. There are infinite reasons someone can get turned down and only some of them are skill related.
>ridiculous hoops people are put through to get a job these days
I'm sure that's true in some areas, but our last hire I was shocked at the ridiculous lengths the applications would go to to avoid putting in even a minimum effort to apply for the job. Like the Van Halen brown M&M test, we put a line in the middle of the job advert saying "If you've read this, put your favorite color in at the top of your job application message. We had low double digits % of people who would do that.
Honestly, on our next hiring round, I think I'm going to make people fill out a google form to apply, and have any of our job posts say "Apply at <URL>" and completely ignoring any apps we get through Indeed or the like. We had a team of 3 people reviewing applications for an hour or two a day for a month and most of the responses were just human slop.
As a new college grad I might be able to add some insight.
We're stuck in a stalemate where the sheer volume of applications for employers to handle and applicants to send makes them take shortcuts, leaving both sides wonder why people aren't trying.
If somebody has to send in 300-500 applications (which is not unheard of) and answer the same questions till they go blind, it's not surprising that certain things are missing or people don't care. Applicants don't have any reason to believe their info isn't thrown in the trash by an LLM as soon as it is sent.
Lazy people will always be a problem but until there is transparency or trust developed I doubt we will see meaningful change.
> Like the Van Halen brown M&M test, we put a line in the middle of the job advert saying "If you've read this, put your favorite color in at the top of your job application message.
TBH I can't blame them. you're applying to hundreds of applications repetitively with qualifications that barely matter because you're encouraged to apply anyway. You can only spend so many hours reading HR-drivel (that at this point may or may not be ai-generated) before you focus on just finding "job title, salary , location), and then slamming apply. It's just not worth editing my resume to add some weird qualifier if I don't even think I'm going to get a reply. It's another hoop.
It's the complete inverse of hosting Van Helen at your show. It'd be more like trying to make a cashier recite their company motto. They are not that dedicated to any one role. They can't afford to be.
---
I don't know if it's feasible for your situation, but smaller teams tend to have candidates email their resume. It can still be LLM'd, but I will tend to pay more attention if I feel like I have a direct communication channel. Not yet another greenhouse application form. It leaves room to be more free form with my pitch as well.
I'm pretty sure that if I was interviewing for my current job at my current company now, I wouldn't get it.
It's not obvious to me that AI is the reason for the hiring slowdown.
ChatGPT was pretty useless when it first released. It was neat that you could talk to it but I don't think it actually became a tool you could depend on (and even then, in a very limited way) until sometime in 2024.
Basically:
- the junior hiring slowdown started in 2022.
- but LLM's have only really been useful in a work context starting around 2024.
As for this point:
> According to very recent research from Stanford’s Digital Economy Lab, published in August of this year, companies that adopt AI at higher rates are hiring juniors 13% less
The same point stands. The junior hiring slowdown existed before the AI spend.
No one wants to say we're in a recession yet, so we gotta deal with beating around the bush for another few years.
But yeah, it's bad in general. seniors are struggling too. This was cooking for even longer, but more mess got added to the stack.
I think the interest rate and shareholder pressure were the most immediate causes. In 2021 you could get head count to do trivial projects at many tech companies and by the end of 2022 you had layoffs and hiring freezes.
Tend to agree here. The slowdown here has more to do with the financial ecosystem. IE less capital available for some companies, higher salaries and a changed approach to work.
The AI wave didn't start yet. Will hit in 26/27
I think AI clouds the real issues around Junior hiring. Defective companies.
Let's say you hire your great new engineer. Ok, great! Now their value is going to escalate RAPIDLY over the next 2-3 years. And by rapidly, it could be 50-100%. Because someone else will pay that to NOT train a person fresh out of college!
What company hands out raises aggressively enough to stay ahead of that truth? None of them, maybe a MANGA or some other thing. But most don't.
So, managers figure out fresh out of college == training employees for other people, so why bother? The company may not even break even!
That is the REAL catch 22. Not AI. It is how the value of people changes early in their career.
I think this is the crux of it. When i got my first job I probably made half the salary of the senior engineer in our division. I am 100% sure I was not half as productive. Juniors take a lot of training and time and aren't very productive, but their salaries are actually not reflective of that. The first few months at your first job you're probably a net loss in productivity.
If salaries reflected productivity, you'd probably start out at near minimum wage and rapidly get raises of 100% every half year.
On top of that, if the junior is successful he'll probably leave soon after he's up-and-running b/c the culture encourages changing jobs every 1-2 years. So then you need to lock people down with vesting stock or something..
It seems not easy at all. Even if you give aggressive raises, at the next interview they can fake/inflate their experience and jump in to a higher salary bracket
Hiring and training junior developers seems incredibly difficult and like a total waste of energy. The only time I've seen it work is when you get a timid autistic-savant-type who is too intimidated with interviewing and changing jobs. These people end up pumping out tons of code for small salaries and stay of for years and years. This is hitting the jackpot for a company
>Even if you give aggressive raises, at the next interview they can fake/inflate their experience and jump in to a higher salary bracket
I don't think the kinds of people who see a 50% raise and complain that it's not 100% are the kinds of candidates you want to hire anyway. I'd like to see more of that before deciding we tried nothing and ran out of ideas.
I didn't leave my first job because I was non-autistic. I left because I was paid 50k and the next job literally tripled my total comp. Oh, and because I was laid off. but tbf I was already out the door mentally around that time after 2 years of nothing but chastising and looking at the next opportunity.
I would have (outside of said chastising) gladly stayed if I got boosted to 75k. I was still living within my means on 50k.
>Hiring and training junior developers seems incredibly difficult and like a total waste of energy
If that's the attitude at large, we're all falling into a tragedy of the commons.
> Juniors take a lot of training and time and aren't very productive, but their salaries are actually not reflective of that
In the current economic situation you can offer a junior 2x may be even 3x less and still get candidates to choose from.
Also there juniors who are ready to compensate for lack of experience by working longer hours (though that's not something you would learn during hiring).
> The first few months at your first job you're probably a net loss in productivity.
It's true for a senior too, each company is different and it takes time to learn company's specific stuff.
I actually got a major raise after 6m, and then another major raise 1y into my career, because my boss recognized my value.
Sadly this is not as common as it should be - but I've also mentored folks at FAANGs who got promoted after 1y at the new-hire level because they were so clearly excelling. The first promotion is usually not very hard to attain if you're in the top quartile.
>not very hard to attain if you're in the top quartile.
No biggie, just be the best in the interview stage and continue to be the best for years after that. It's that simple.
"Winner take all" environment
What you are saying is not a hiring problem, but an education one.
If colleges stayed up to date, and teach valuable skills, the jump wouldn't be so steep!
It's like the whole idea of a company has inverted. Instead of "We'll assemble a team, then use that capability to make things, and solve problems" the idea is "the machine basically runs itself, how much can we get away with minimizing upkeep?"
Default "people have value because human attention solves problems", has become default "existing org structure has value because existing revenue streams are stable."
The idea of a company used to contain an implied optimism. "If we get capable people together, we can accomplish great things!" Now that optimism has been offloaded to the individual, to prove their worth before they can take part.
I upvoted the article for the purpose of discussion. I disagree with it. The core tenant of the article is that AI is the reason why companies aren't hiring juniors. That's just not it. Do people just blindly believe whatever some CEO or company says in their press briefings? This was all happening before the AI boom. Interest rates went up, hiring went way down, and then AI launched. Before interest rates, interviewing was getting harder and harder every year. That's usually an indication that you have more supply than demand. The bar for getting into any American tech company was getting much harder - not just FAANG. Leetcode had gone from having practiced 50-100 questions to there being a bank of over 3000+ with many people having regularly studied hundreds. It went from easy/medium to being typical in interviews to medium/hard being typical with many original hard questions now being reclassified as mediums.
Wages for your typical engineer stopped going up 5+ years ago. The joke of senior FAANG engineers making $400k has been a meme for over 5 years. Yet, inflation has done over 20% in 5 years? Look at new offers for people joining the majority of positions available at public tech companies. You're not seeing $500k offers regularly. Maybe at Jane Street or Anthropic or some other companies that are barely hiring - all of which barely employ anyone compared to FAANG. You're mostly seeing the same $350-400k/yr meme.
The reason we're not employing new grads is the same reason as the standards getting much more aggressive. Oversupply and senior talent has always been valued more.
I appreciate you adding nuance to the conversation. The problem is much more complicated than just AI, but I (original author) was using those two research studies that I cited as the basis for the conversation. While 13% hiring drop doesn't mean a catastrophic difference, it's a trend worth noting.
> Wages for your typical engineer stopped going up 5+ years ago
Not true for Western Europe. Getting more than 60k euros yearly as a software engineer was hard in 2019, it's now basically impossible to get less than that.
The problem is "Seniors" started becoming worse a decade ago. Not only wouldn't they mentor, but they wouldn't lead by example. Problem-solving on their own, collaborating with peers, sharing information/communication, doing proper due diligence, organizing and improving themselves and their team/product/business. This was around the same time bootcamps started flooding the industry with amateurs with no experience. These neophytes were then competing with more experienced people for the same jobs, because hiring in tech is more Ouija board than accurate assessment of professional engineering.
Amidst this influx of applicants, junior and intermediate staff began getting Senior titles to justify pay raises. Soon those exact same people were moving from job to job as a "Senior", but without the relevant criteria that would've qualified for that title a decade before. You can still see people get promotions without having accomplished anything, much less learned anything, but they did keep the lights on. Today there's a sea of "Senior" engineers that can basically write code (and not especially well), but lack all the other "non-coding" skills that Seniors should have.
Even if you hired 100K new Juniors tomorrow, there's nobody to train them, because most of the people working today are practically Juniors themselves. Each "generation" is getting worse than the one before, because they're learning less from the generation before, and not being required to improve. There's still good engineers around, but finding them is like playing Where's Waldo? - and you have to know what Waldo looks like, which you won't if you're not experienced!
The fix isn't going to be learning to network ("relational intelligence") and mentoring more. The fix is for us to stop letting the industry devolve. Treat it like the real engineering professions, with real school requirements, real qualifications, real apprenticeships, real achievements (and titles that aren't meaningless). Otherwise it'll continue to get worse.
God, thank you for writing this. I agree 100%. We are rapidly losing all of our "low-background" programmers in this industry. Even ten years ago, I encountered developers who could not debug a stack trace, of the application they were hired to develop. People would send me screenshots of Python errors and ask me how to fix them. I was shocked. I was a junior myself, but surely a programmer would know how to read a compiler error. I mean, that's the entire point of the computer telling you what went wrong...
I saw the title inflation happen in real time. When the boot camp floodgates opened, that was the beginning of the end of my faith in this field. I saw people with three months of create-react-app tutorials churning out garbage, while I was called upon to put out fires and fix things when they broke. I "did devops", and rapidly became shadow developer IT, helping incapable programmers fix bugs in codebases I wasn't even familiar with, better than they could. And I am truly not that great of a programmer! I just know how to read, reason, and use grep a lot. These aren't superpowers, but finding someone who can even reason through how to debug something is impossible these days.
I would love some sort of licensure or guild or standards, but I have no idea how we even begin to change that. Part of the problem is that companies don't want to change. It's cheaper to pay a few people nothing than it is to pay a lot of people a lot, and that shows no sign of changing. Maybe more planes have to fall out of the sky, I don't know. Maybe Windows has to become so buggy and unusable that multiple hospitals shut down for months on end. We don't just need a reckoning, we need a reckoning where we all wind up better on the other side.
I am squinting at the horizon, but still, all I see is darkness.
>The fix is for us to stop letting the industry devolve.
Sadly not in "our" hands. At best, some director/product owner brings it up. Executives have a nice chuckle, and they continue to outsource to anywhere else. This US industry barely wants to hire Americans to begin with at this point.
We're gonna have to divorce from big tech and push more businesses that reflect our desires if we want true change. Or collectively bargain while we have the chance. I don't know what is more likely in this community.
> Not only wouldn't they mentor, but they wouldn't lead by example.
Because their jobs were being outsourced.
ding ding ding
One of the critical flaws in the article is that the first chart only looks back 5 years, and the second only looks back 10.
The boom-bust recession cycle is roughly every 10 years. You can't say that AI is impacting hiring when your data just looks like the typical 10 year cycle. Your data needs to go back further.
That being said, what's more likely going on:
1: There are always periods where it's hard for recent college grads to get jobs. I graduated into one. Ignoring AI, how different is it now from 10, 20, and 30 years ago?
2: There are a lot of recent college grads who, to be quite frank, don't work out and end up leaving the field. (Many comments in this thread point out how many junior developers just shouldn't be hired.) Perhaps we're just seeing many companies realize it's easier to be stricter about who they hire?
>Ignoring AI, how different is it now from 10, 20, and 30 years ago?
Ignoring AI, there is simply more competition and less human interface in the process to begin with. 10 years ago, you'd throw maybe dozens of apps and study interview trivia (this was right before the "leetcdoe era" so not even that). 20 years ago you'd probably just wander around a career fair and stumble into your career. 30 years ago you were as close to shaking your managers' hand for a job as you'd ever be in the modern tech industry.
10 years ago, a reference from nearly anyone in the pipeline to the hiring manager guaranteed at least a look see at you. Now it's a 50/50 at best. "who you know" may not be enough anymore.And now career fairs are 90% advertising firms instead of actual talent aquisition.
>Perhaps we're just seeing many companies realize it's easier to be stricter about who they hire?
if you look at the hiring numbers, you see that hiring globally is in fact not slowing down. That's a bit of a tangent, but that may give a clue to the whole situation here.
Today you may not even get a human to see your resume after 100 job apps. It's not just brutal but a solitary experince. No feedback to improve upon, no advice to take.
There are two problems here.
1. The industry cannot define the terms junior or senior.
2. Most seniors today are the prior generation’s juniors with almost no increase of capabilities, just more years on a resume.
The article asks about what happens when today’s seniors retire in the future. I would argue we are at that critical juncture now.
Retire? I can never retire. I'll likely die at my keyboard. Software has not provided the future I was hoping for.
>Most seniors today are the prior generation’s juniors with almost no increase of capabilities
I highly doubt throwing even a 3YOE "senior" of 2012 at a modern junior interview would turn out as well as you'd expect. the standards have gotten sky high. That doesn't mean they can't do the job, it means the industry created more hoops to jump through.
I agree to an extent with title inflation (and where the hell is the mid level?), but I don't think peple are confusing "juniors" here. It's new grads to at best 2 years of experience. not much controversy there. I also don' think the idea that the 2014 graduating CS class is smarter than the 2024 class would pass the sniff test.
The most frustrating thing about this whole junior position drought is how it simultaneously affects those who are passionate and get it, not only the opportunist bootcamp alumni who were lured by the prospect of high earnings.
If I were to graduate today, I'd be royally screwed.
/r/cscareerquestions the horror eg. applied to 2000 jobs got 1 offer
> If I were to graduate today, I'd be royally screwed.
I feel that too. I am a self-taught dev. Got a degree, but not in CS. I don't know if I could get hired today.
Not sure how to fix it; feels like the entire industry is eating the seed corn.
Sadly - as I've mentioned on HN a bunch - junior salaries need to fall dramatically to somewhere in the $60k-$100k range in order to make it cost effective against automation/AI or offshoring.
The economics of providing every new grad a $150k TC offer just doesn't work in a world with the dual pressures of AI and async induced offshoring.
Heck, once you factor in YoE, salaries and TCs outside the new grad range have largely risen because having experienced developers really does matter and provides positive business outcomes.
State and local governments needs to play the same white collar subsidy game that the rest of the world is playing in order to help fix the economics of junior hiring for white collar roles. This is why Hollywood shifted to the UK, VFX shifted to Vancouver, Pharma shifted to Switzerland, and Software to India.
> The economics of providing every new grad a $150k TC offer
It was always a weird US thing driven by huge companies and VCs. In other western, developed countries ~$50k equivalent would be normal. Even adjusting for other provided social benefits, there's still a long way down...
Fall into the 60-100k range? Thats where the vast majority of them have been. Only the bay and NYC city area sees otherwise, and even in those areas I see plenty of listing for 90-110k for junior positions.
My fear is that isn't low enough.
This article talks a lot about AI, but what I find odd is that in my relatively short (but long enough) ~9 yr career so far, this problem predates AI. I don't deny that it exacerbates it, but you don't kill a disease by addressing the symptoms. From the first time I was ever involved in the hiring process, senior leadership always encouraged me to hire more experienced staff, always most heavily scrutinized juniors, and had negotiations fall through with mid-level candidates the most. This was despite juniors passing technical screens with strong showings. This was not at a Fortune 500. This was a micro-cap subsidiary of a private, billion dollar company.
And although it hasn't discouraged me, I have to admit that I've been burned by juniors when caught in the middle between them and senior leadership on output expectations or strategy because frankly it's much more challenging to mentor how to navigate company politics than it is to mentor professional coding acumen. I want to be humble here. I don't think that's the junior's fault.
It feels like these problems go a lot deeper than AI. Most shops want software teams that are either silently embedded black boxes that you insert rough instructions into and get working software as output or an outsourced team. We've all experienced this. It seems silly to deny that it's directly related to why it's so hard to mentor or hire juniors.
You're not wrong! I'm the original author of the post, and yes, I've seen this trend for years now, too, but I was using those two research studies that I cited as the basis of the article, so I started looking at it from that lens. I think the problems go deeper than AI, too, which is why I touched on corporate incentives. Ultimately, my goal was just for teams to think about how it could benefit them to invest in juniors and for college students to know that they need to prepare for a challenging ride if they're majoring in an AI-adopting field.
Yes, AI isn't helping but the corporate world has been doing this for decades! Junior devs are second class citizens internally. I don't blame them for moving on after a few years.
I agree. I wonder if it's a mix of fully remote work being popular some time ago and the amount of tech one has to know now increasing (DBs, backend, frontend, cloud, observability, security, etc.). When hiring remotely, people naturally try to find candidates who are very communicative, have a high level of ownership, and can work with or without clear requirements and without oversight. That latter set of traits is often associated with senior developers rather than juniors.
>Most shops want software teams that are either silently embedded black boxes that you insert rough instructions into and get working software as output or an outsourced team
Well that explains why AI excacerbates this. It's all they ever wished for and they don't need to make do with that facsimile of "human interaction" anymore. It's not perfect but that's a sacrifice they are willing to make.
Or you know, they just really want to be as cheap as possible in production (hence, outsourcing).
>It seems silly to deny that it's directly related to why it's so hard to mentor or hire juniors.
I'll give a slight BOTD here after my disdain above and admit tha a small team probably isn't the best enviroment to train a junior. Not unless you either
a) truly believe that the skillet you need isn't out there, and you are willing to train it yourself to alleviate your workload, or
b) you are thinking long term efficiency and are willing to lose early productivity to power the future prosperity. Which, to be frank, is not how modern businesses operate.
And yes. Any teacher in any field (but especially education) will tell you that the star players make their day, week, and year. But the worst cases make you question your career. Our natural negativity bias makes the latter stick out more. Those in industry won't get star players as they are either filtered out by these stupid hoops or gobbled up for 100k above your budget by the big players. It's rough.
The idea that the only reasonable path into a software related career is through networking may be true, but it obviously signals something deeply wrong with the culture around work.
It is also something which is likely to be quite harmful, since it selects for people who are great at networking over people who have good technical skills. Obviously interpersonal communication is important, but how well a 20 year old in University performs at it should not doom or make their career.
And even people with bad social skills deserve to exist and should be allowed into their chosen career. Being someone who does good work and is respectful, but not overly social, should be good enough.
I agree with you, actually (I'm the original author of the post). It's literally one of the main reasons that I'm writing about networking so much. I have seen so many people fail up in technology because they were good at networking while so many other people who had better technical skills felt stuck. I don't believe that to be a strong networker you have to be social, though, just intentional. Technical people who may struggle with the people side of things can leverage their systems thinking strengths and apply it to stakeholder, mentee/direct report, and cross team relationships in a way that helps them move the needle on their goals. It's not easy, but I do think that intentionality and sincerity are key.
Agree, but ultimately it's a regression to the mean of most white-collar professions, where grades and network make for a significant jump-start in someone's career.
This is truly heartbreaking, programming was the last profession beside medicine doctor that guaranteed young people good start in life in my country.
It is insane how much screwed over we are. I am about to turn 30 soon with 5 YoE, PhD in ML which supposedly is the cutting edge stuff. Yet I have no prospects to even buy a tiny flat and start “normal life”. AI eats its own tail, I have no idea what I should do and what to learn to have any sensible prospects in life.
To try and add in some anecdotes without injecting too much baggage:
I am an older gen-z and launching my career has felt nigh on impossible. At my first job, the allergy toward mentorship this article mentions was incredibly palpable. None of my several managers had management experience, and one of them openly told me they didn't want to be managing me. The one annual review I got was from someone who worked alongside me for a week.
Follow that experience up with a layoff and a literally futile job search, and its hard to be optimistic about building much of a career.
I'm really sorry you went through that. For what it's worth, I'm a millennial, and then best shot I had at mentorship was an extremely overworked engineer who oversaw my work for like... a few weeks, maybe? And that was at the very beginning of my career about a decade ago. Then my mentor kinda disappeared to put out a bunch of fires all the time (I eventually became the "put the fires out all the time" guy.) Basically, the experience was neither long nor formal. After that, and at every job since, I basically had to fend for myself. This industry is outright allergic to training people, and it sounds like it's reached a fever pitch. I'm praying I don't get laid off, because on top of having no desire to job hunt in this economy, I don't really know if I care to work anywhere near this industry ever again. I can't wait until it collapses.
> The social contract between large companies and employees has been broken for years now. US companies are optimized for quarterly earnings
I started in tech in the late 70s. I can say this break happened during the Reagan Years with a bit of help from the Nixon Years.
I'd attach a different name and org to that change - https://en.wikipedia.org/wiki/Jack_Welch#General_Electric
Ask HN:
I have a friend of a friend in his mid 20s who finished a masters degree in data science focused on AI. There isnt a job for him and I think hes given up.
In Letters to a Young Poet Rilke responded to a young aspiring poet who asked how a person knows whether the artistic path is truly their calling:
> “There is only one thing you should do. Go into yourself. Find out the reason that commands you to write; see whether it has spread its roots into the very depths of your heart; confess to yourself whether you would have to die if you were forbidden to write. This most of all: ask yourself in the most silent hour of your night: must I write? Dig into yourself for a deep answer. And if this answer rings out in assent, if you meet this solemn question with a strong, simple "I must," then build your life in accordance with this necessity; your whole life, even into its humblest and most indifferent hour, must become a sign and witness to this impulse.”
How do I respond to this friend of a friend? Is data science or coding in general the path for you only if you would rather die than stop merging pull requests into main every day even when nobody is paying you?
Is coding the new poetry?
What do I tell this guy?
Having a data science degree doesn't really mean much by itself. There's a lot of graduates that come out of it with no marketable skills.
And no, coding is not the new poetry. I wish people would stop spamming this website with doomer nonsense like this.
99% of us can't live like that.
The other place you will meet struggling artists is sports. Train several times a week, neglect your social life, your studies, just learn how to chase after a ball.
Only people who are crazy driven will actually do this. The ones who don't make it, they try to climb up from lower league clubs. They go on and on, carving out a career.
But most kids do not have a burning passion for anything. They are curious, they're smart, they want to explore the world. But they haven't found a calling. If they try to go through the eye of the needle, they find it's quite hard, because those paths are taken by guys with a mental lock on a certain career.
What to tell the guy? He's picked the subject that is the most useful for learning about the world. Go around and look at things. There's so much that a person who can code and can deal with statistics can apply himself do.
given that quote, I'll tell you right now that your burning passion and calling in life will not be answered by being a corporate cog that is ultimately performing jira tasks for some project that is not your own. I made that mistake in my mid 20's. I wouldn't call my experience a waste either, but it did have me doing some soul searching on what my true "endgame" is.
I don't know what the disposition of your friend is, but I don't think many of us are ready to die cold on the streets scaping towards our goal. Survive first and then figure out how to climb from there. Don't see setbacks as a sign of weakness, but a part of life.
Over the timeline in this post, ZIRP and the pandemic seem like equally important factors to LLMs in explaining hiring trends.
Yeah, it makes sense that going from a decade or so where SWE was one of the best possible career paths if you have any aptitude to a period where tech cos were staffing up aggressively (I recall reading ~60% growth), there's gonna be a hangover. The educational pipeline probably still has a few years of oversupply to work through, and all of the people laid off post covid still need to work. Even in a world where AI being able to automate some of the key skills required for SWE has no negative impact on employment, we'd expect a few more years of rough job prospects.
I personally think - Juniors will be okay, if they stick to *fundamentals*
lots of "seniors" via title inflation dont have fundamentals anyways - hence a lot of broken software in the wild & also perverse incentives like Resume driven development. A.I is built on badly written open source code.
because once you have the fundamentals, built a few things - you would've battle scars which makes someone a senior
not the 'senior' we see in big corps or places cosplaying where promos are based on playing politics.
Unfortunately short of making a startup or monetizing projects it’s hard to get paid purely from the fundamentals
you gotta go resume driven because that's what gets the job. but that distracts from proper engineering skills because the interview process isn't actually testing for engineers. It's all broken.
Annie! Good to see you hit front on here!
You're totally right. 10 minutes on /r/cscareerquestions (without even sorting by `top`, though it's more brutal if you do) is enough to confirm it.
I normally wouldn't cite Reddit as a source, but this same subreddit was overflowing with posts on fending off recruiters and negotiating already-sky-high comp packages just two years ago. Seeing how quickly the tables turned is sobering.
CN! Nice to cross paths!
You're right that it's sobering to see how it's changed so much in the last 5 years. And yeah, it's not just the juniors that have to think about this but those in their cushy jobs that get hit with layoffs out of the blue, too. I don't say that to illicit fear; I say that to illicit action. We don't live in the same world anymore where you can rest on your laurels, unfortunately.
You've always been so good at all this, though! You help others, get curious about where you can add value to their situations, people know what you're about, and you exude authenticity. Poster child for what I'm trying to tell people to do to take action. :D
> That’s not to say that there aren’t people within those companies who care about employee development, but the system isn’t set up for that to be the companies’ top priority.
There has been a cultural shift too. I don't know when it got started, but at least employees in the tech companies started to get more and more obsessed with promotions. The so-called career development is nothing but a coded phrase for getting promoted. Managers use promotion as a tool to retain talent and to expand their territories. Companies adopted to this culture too. As a result, people development increasingly became a lip service.
> “I’m an IC not a manager,” became an acceptable argument to avoid this work
Has anyone ever seen a manager mentoring ICs? I haven't. This is a senior/staff/principal responsibility.
I have, but these were generally founder types that accidentally became managers. They weren't "career managers." The career managers delegate that work.
all the time? not on technical issues, unless it's a TLM or the IC is entry level and it's pretty basic stuff they need help with, but absolutely on navigating organization, communicating, prioritization, and so on...
Wow, this elitist attitude is the problem. Assuming the worst about juniors and being totally unwilling to give people a chance, God forbid any training or mentorship. f--- software engineering. What. s--- career full of elitist pricks. Yes many of these people may not be very good, just like a lot of mediocre mids and seniors that believe they're gods gift to the world even if they've stubbornly refused to learn very little over 10 years, but many of these juniors would be extremely valuable if given a chance let alone any help.
[dead]
This is just a continuation of general labor practices in US companies.
I have been unable to get a tech job for months so I’ve looked into retraining in a new field and every single one has some up front large cost via either paying for schooling or situations like mechanics needing to bring their own tools.
The standard US company has completely shed all training costs and put the expectations on laborers to train themselves. And you’re shit out of luck if their requirements change during your training as so many college graduates who picked comp sci are currently learning
The companies that are abandoning junior roles are making a life-or-death bet that AI will eventually replace ALL work.
Because those senior people will NOT be around forever. And they have killed their talent development and knowledge transfer pipelines.
Either direction you take it, this feels like a lose-lose situation for everyone.
From an individual senior exec point of view - all staff are replaceable. You just hire from outside the company.
People don't think in terms of shared commons and that if all companies are doing the same thing then there won't be much of a "senior" market left to hire.
> the unintended consequence of that is that we’ve spent a decade normalizing senior engineers opting out of developing the next generation.
This is because "management" includes a bunch of BS that few engineers want to actually deal with. Performance discussions, 1:1s, being hauled into mandatory upper-level meetings, not actually building things anymore, etc. If it was simply pairing with juniors from time to time to hack on things and show them cool stuff, it would be wonderful.
What you like is for yourself. What you seem to dislike are things that improve others (team/stakeholders). Seniors are such because they take on more of the latter.
This will now become even more normalized given that on technical skills seniors are no longer needed for juniors to skill up. AI and the evolving ecosystem will help and assist them way more. In the new world, the more technical and non-technical work you do towards customers/teams/organization, the more senior you become. I see many not liking it, but I'm also seeing first hand that is how it is.
> If it was simply pairing with juniors from time to time to hack on things and show them cool stuff, it would be wonderful.
I think that's a lot of it! (Author here, btw) I think that doing more of that actually makes performance discussions easier and takes the place of 1:1s a lot of times. The whole point of performance management is to nurture the relationship with the junior so that they grow into the type of senior that they need to be to be a contributing member of the team. And if you can achieve that better through hacking and pairing, then by all means.
As far as all the other BS meetings, I think that a lot of people in leadership positions aren't intentional/strategic enough about which meetings they allow themselves to get "hauled into", so they end up totally jaded and burnt out. They think they can't say no to these things, and so they lose the reins on their actual goals. If you step back and ask yourself what stakeholders actually need from you to feel heard, seen, validated, informed, etc, then it may look different from a calendar full of meetings.
Many companies have different career tracks for managers than for individual contributors (even tech leads are considered ICs). Mentoring junior engineers is absolutely in scope for what senior ICs can be recognized for.
> Imagine a tech industry where relationship skills weren’t just nice-to-have but essential. Where navigating complex human systems was seen as a core competency.
If that were to actually happen, we'd wind up excluding many of our greatest technical performers while drowning in a sea of would-be middle managers. People skills matter, but so do many other strengths that don't always overlap with being naturally good at navigating interpersonal dynamics.
I think I know what you may have in mind when you describe the "interpersonal dynamics" of a "would-be middle manager", and I probably agree with you (original author here).
But some of the best "people" people that I've seen in my career have been the most technical, also. They were really good at being able to communicate the value of their solution, the problems it solves, and risks and rewards. They could get buy-in from stakeholders and other teams. They could listen empathetically when faced with issues and blockers. And they did so with authenticity and genuine care because they were passionate about software engineering.
I believe those are skills that can be learned and practiced and that you don't have to be necessarily "social" to grow in that area.
>> we’ve spent a decade normalizing senior engineers opting out of developing the next generation.
This seems like a deeply flawed take on the dual track IC-management ladder. Senior ICs don't keep plugging away by themselves because they're not managers, they just don't get people-management tasks. I think the leadership & mentorship they provide is harder than for me (a manager) because they don't have the hammer of a "manager" job title, and need to earn all their credibility. I have not had a senior IC and above in more than 10 years that didn't have a significant amount of junior & int development explicitly defined in their role, and the easiest way to get promoted is with leverage. Try and be 20% better than your peers with your contribution (hard). Make 10 people 3% better (much easier)
Yes! Had the same instant reaction to that line. A lead engineer doesn’t get to lock himself or herself in a closet and ignore the team, and any team/company allowing that is failing its team as a result. They should be out there helping level up tech skills, and influencing code/behavior just as much as a people manager should be guiding career trajectory.
> When tech companies started giving engineers an alternative career path to management by letting them climb the ranks as individual contributors instead of having to be managers, I thought that was definitely the right move. Still do. However, the unintended consequence of that is that we’ve spent a decade normalizing senior engineers opting out of developing the next generation.
Interesting observation. I have personally tried to avoid getting into people manager positions (as I believed I'd be Peter Principled) but always took it as my duty to share knowledge and mentor the curious and the hungry (and even the ones that are not so). It's actually a very rewarding feeling when I hear good things about people who learned with me.
We're still in the early days. It's gonna get a lot worse, if the LLM scaling laws are to be believed.
https://metr.org/blog/2025-03-19-measuring-ai-ability-to-com...
>The most common answer from career services professionals when asked what they needed was more staff.
Administrators want to hire more administrators? Shocking!
The biggest question that isn't being asked, "why is a university incapable of training a competent programmer in four years?"
I'm quite sure I could take my cousin who has never heard the word HTML and get her to be a better programmer than the average CS graduate within 4 years of tutelage. Why is this the case? Four years is a very long time, and the universities are wasting that time. I'm certain any driven individual would end up a mid-level candidate if they skipped college and instead trained themselves for that time, especially if they hire a senior tutor for far less than the cost of the college tuition.
It's been a while, but one of the reasons I avoided getting a CS degree a few decades ago was because it was basically mathematics. To this day, interviews are the only thing this would have benefited thanks to Leetcode.
I think the simple answer is you can't do this with most people. Bootcamps have tried for a while and mostly failed.
Frankly, I think Universities are still turning out great programmers. The problem is industry doesn't want good programmers and doesn't promote them.
My team wrote about this same phenomenon in marketing: https://www.behindthecmo.com/p/the-seniorification-of-market...
Its a double edged sword too. I see it in my biz -- its easier to spend 40 hours training a model how to do things the way we like rather than hire someone junior and spend a month+ on onboarding. We are noticing hitting a wall to a certain point with clients still wanting to talk to a real person, but I can see that changing in the next ~5 years. Zero idea what happens to those junior folks that used to get trained (me being one that sat through a 3mo onboarding program!).
>. We are noticing hitting a wall to a certain point with clients still wanting to talk to a real person, but I can see that changing in the next ~5 years
I don't know. if we simply defer talks to LLM's, then companies will take out the middlemen. which means less clients. We'll have our own little filter bubbble of tech where everyone is talking to their black box to try and push out their ideas instead of within the industry.
Not exactly an industry I want to be in. But I don't think it'll get to that point.
I'm not sure how much is about LLMs directly. But as I've written elsewhere, there's definitely a circular pattern where a lot of junior employees think this is going to be an 18 month thing and companies allocate training and mentoring budgets accordingly.
There is a fair bit of anecdotal evidence that junior hiring--at least in the software space--is fairly difficult currently. Via internships at good schools etc. may be better but I have to believe that off the street from bootcamps and the like is pretty tough.
That's a thoughtful post, but I am skeptical of how "universal" her suggested Path Forward is. I suspect a hell of a lot of folks will have difficulty with the "people skills" stuff she mentions (and is almost certainly highly conversant in, herself).
> The most common answer from students when asked what they needed was a mentor who had just been in their shoes a few years ago, a surprising and heartening answer.
Mentoring is difficult; especially in today's world, where we are taught to despise older folks, and encouraged to treat everyone that we work with, as competitors.
For myself, I'm happily retired from the Rodent Rally, and find that LLMs have been a huge help, when learning new stuff.
I think I would also ad to the mix that young folk these days are incredibly overconfident and averse to criticism. A few years back they got a junior dev in here, and I was supposed to help him get on our stack, and ultimately mentor him.
This kid would not accept seniority, would constantly and publicly try to divert from the stack we worked with, he would not take any input on his work without actively fighting the process and will crowd the conversation at team meetings with never-ending Reddit-tier takes that contributed to nothing other than fill his ego.
In the end I managed to convince my boss to get him out, and he now works in Cyber, which will probably cause even more damage in the long run, but at least I can now say "not my problem".
People skills are so important, I agree. Intergenerational people skills are especially important; in most things that matter, the old guard are the ones keeping their eye on the younger hires, pattern matching what they see over months of observation to who they've seen succeed before.
> especially in today's world, where we are taught to despise older folks, and encouraged to treat everyone that we work with, as competitors
What world is this? This not match my experiences at all. Is this a common sentiment among your peers?
> where we are taught to despise older folks
9 times out of 10 it goes the other way around. Most young people have only had very negative interactions with their seniors, which has been wholly on the part of the senior. The current young generation is very respectful towards older people.
Perhaps juniors (and in fact all of us) are going to seem more palatable as contractors at first?
Single-Payer health care would help our industry immensely if it came to pass.
Imagine having no fear any more.
> Perhaps juniors (and in fact all of us) are going to seem more palatable as contractors at first
It actually might help.
This is the model used in Eastern Europe and India - the vast majority of new grads are hired by mass recruiters like EPAM, WITCH, Deloitte, and Accenture at low base salaries but also the expectation that they self train and learn how to become productive SWEs, or they just stagnate at the low rungs. Japan, Korea, and China use a similar model as well.
But honestly, even FTE isn't much of a headache if I can hire a junior SWE for $60k-80k, invest in training them, and then bumping salaries to market rate after they have matured. This is what a number of traditional F500s like Danaher [0], AbbVie [1], and Capital One [2] do via Leadership and Trainee Development Programs, and honestly, it's much easier to make a case to hire someone if they have a couple of years of real world work experience.
[0] - https://jobsblog.danaher.com/blog/leadership-development-pro...
[1] - https://www.abbvie.com/join-us/student-programs.html
[2] - https://www.capitalonecareers.com/get-ahead-with-early-caree...
I don't really like the idea of "what if we get more desperate and lower our standards while billionaires continue to make record profits?" as a solution to our problem. We'll just go the way of Electrical Enineering and lose most of our talent to China.
Short term thinking and short term profit seeking are going to destroy every industry they touch. This article failed to bring up 2 important points.
Firstly, we've been here before, specifically in 2008. This was the real impact of the GFC. The junior hiring pipeline got decimated in many industries and never returned. This has created problems for an entire generation (ie the millenials) who went to college and accumulated massive amounts of debt for careers that never eventuated. Many of those careers existed before 2008.
The long-term consequences of this are still playing out. It's delaying life milestones like finding a partner, buying a house, having a family and generally just having security of any kind.
Secondly, there is a whole host of other industries this has affected that the author couldn't pointed to. The most obvious is the entertainment industry.
You may have asked "why do we need to wait 3 years between seasons of 8 episodes now when we used to put out 22 episodes a year?" It's a good question and the answer is this exact same kind of cost-cutting. Writers rooms got smaller and typically now the entire season is written and then it's produced when the writers are no longer there with the exception of the showrunner, who is the head writer.
So writers are rarely on set now. This was the training ground for future showrunners. Also, writers were employed for 9 months or more for the 22 episode run and now they're employed for maybe 3 months so need multiple jobs a year. Getting jobs in this industry is hard and time-consuming and the timing just may not work out.
Plus the real cost of streaming is how it destroyed residuals because Netflix (etc) are paying far fewer residuals (because they're showing their own origianl content) and those residuals sustained workers in the entertainment industry so they could have long-term careers and that experience wouldn't be lost. The LA entertainmen tindustry is in a dire state for these reasons and also because a lot of it is being offshored to further reduce costs.
Bear in mind that the old system produced cultural touchstones and absolute cash cows eg Seinfeld, Friends, ER.
Circling back, the entire goal of AI Is to displace workers and cut costs. That's it. It's no more compolicated than that. And yes, junior workers and less-skilled workers will suffer first and the most. But those junior engineers would otherwise be future senior engineers.
What I would like for people to understand that all of this is about short-term decisions to cut costs. It's no more complicated than that.
Are you really saying the production turn around time of a multi-camera sitcom compared to full on movie quality TV shows is due to more writers?
I've been saying this for years, since the first AI coding models came out. Where do the juniors go to learn? I'm a senior engineer because I got to do a bunch of annoying tasks and innovate just slightly to make them better.
That opportunity is now lost. In a few years we will lack senior engineers because right now we lack junior engineers.
All is not lost however. Some companies are hiring junior engineers and giving them AI, and telling them to learn how to use AI to do their job. These will be our seniors of the future.
But my bigger concern is that every year the AI models become more capable, so as the "lost ladder" moves up, the AI models will keep filling in the gaps, until they can do the work of a Senior supervised by a Staff, then the work of a Staff supervised by a Principal, and so on.
The good news is that this is a good antidote to the other problem in our industry -- a lot of people got into software engineering for the money in the last few decades, not for the joy of programming. These are the folks that will be replaced first, leaving only those who truly love solving the hardest problems.
I'm more pessimistic. It costs too much to go back to college and retrain. The result is going to be a generation of ambitious people doing a craft they hate. The results are going to be dismal.
> networking is absolutely essential for post-graduation job-placement success
Looking back, this has absolutely been the case for me personally. My first job out of school was at a startup spun off from a lab where a friend from my CS classes had been working while at school. I just referred somebody who was eventually hired that I've worked with at two other employers in the past.
Maybe chatting with a LLM with access to the codebase is equally effective as pair programming with a human. I don't have enough experience doing that yet to know. I still see it as another tool.
I've found it helps to have various levels of experience on a team. I think one reason for this is people with less experience (hopefully) ask a lot of questions to fill knowledge gaps. These conversations can lead to revisiting designs, practices, etc. and a better outcome overall.
This is true. As a startup founder I’ve invested heavily in mentoring juniors, and all of my current developers actually started as interns. They’ve grown fast and delivered real results because we gave them trust, support, and room to learn. The companies that say “there are no good juniors” are usually the ones that never bothered to train any.
One thing that I hypothesize about junior developers is that you need to leapfrog the handholding period and go straight to the medium/senior position on your own. You can acquire the medium/senior level of knowledge and experience making all the mistakes and bad choices by yourself and learning from the experience.
Are you saying this plan is realistic or more like a pipe dream?
This is kind of like saying “Get your flight hours in on Microsoft Flight Simulator and then Delta Airlines will hire you.”
All unpaid and in your spare time between your two minimum wage jobs, of course.
Sorry, these studies don’t show that AI is “good at automating away junior work” _at all_, or even claim to (and what little empirical research exists points the other way).
What they show is that hiring managers think they can use gen AI to get away with skipping juniors. The resulting collapse in software quality will either bite them in the ass causing a market correction, or massively enrich the big five and leave the rest of us to live with the consequences. Which outcome comes to pass is still yet to be seen (and partially under our control, as seniors)
What about hiring junior developers to do the work I don't want to spend time training AI to do? Humans retain context, over time learn the ins and outs of the business and will sit in a meeting with stakeholders to gain understanding of the business rules and ask the 'stupid' questions that need to be asked.
I would much rather have that junior take some hacks at building some features with AI along with my guidance than context switching over to AI just to walk it through doing a task which means having to explain the business and our business rules over and over again.
To me cutting out a junior developer adds more time for senior developers than making their work lighter.
I am genuinely baffled by the notion that experienced developers have a moral obligation to mentor junior developers in additional to their actual job-related tasks.
They do not. Mentoring is rewarding work, but it is work.
I also find it objectionable that if you're simply not interested in mentoring, you're a jerk. Some people just aren't good at it, some people are genuinely swamped with existing responsibilities, and some people might just want to focus on their goals... and that's fine. There is no but.
Some folks <gasp> just don't like other people that much, and prefer working alone. Also fine, and kudos for being self-aware enough to not inflict yourself on people who probably wouldn't enjoy your oversight either. This should be celebrated as a communications success.
All of which brings me to the truth: if a company wants to mentor junior developers - and there are many, many excellent reasons to develop talent long-term - then they should make sure that they have suitably experienced people who have opted-in to mentorship, and make sure that their success metrics and remuneration reflect the fact that a significant portion of their time is acknowledged to be dedicated to mentorship. Otherwise, you're describing a recipe for legitimate resentment.
Likewise, if you're a junior developer desperate for mentorship... I understand that your instinct is to take any offer that will have you. But if you're able to have an honest conversation with the recruiter about what kind of mentorship culture exists in a company, you might be saving everyone a lot of pain and frustration.
To me it seems that large US tech companies had a start-up behaviour until the last years (massive hiring, ambitious goals and VC money). This fades away relatively fast now and they cash out their investments.
Another reason might be the low potential of the new generation of graduates (see lower math scores and possibly IQ). They might have interviewed some and are disappointed and unwilling to hire from this pool.
Last but not least comes the current trend to substitute humans by LLMs.
Isn’t it also easier than ever to learn though? The moat that seniors built around their expertise enabled a juicy buffer of mediocre devs paid mediocre rates pushing up the value of mythical 10x engineers.
It's easier than ever to learn, if you want to learn. It's also easier than ever to not learn anything, if you only do what's expected from you.
Alright, bring on the downvotes.
It's the bloated junior salaries that have killed their market. I never like hiring juniors, I never like working with juniors, and I'd rather pay the extra 20-30% and get someone more experienced. I'm sorry, but if you don't get into FANG, you should basically be working for nothing until you have some experience. It's cruel, it's not fair, but it's just not worth it for the employer. Especially in today's world where there is no company loyalty.
All this BS about AI taking away the stuff that juniors did, in my field, software development, that was never the case. I never worked in a place where the juniors had different work than the seniors. We all did the same things, except the juniors sucked at it, and required handholding, and it would have been faster and better if they weren't there.
The real trick is finding companies that do very simple work, simple enough that juniors can thrive on day one. It won't be the best experience, but it is experience, and the rest is what you make of it.
I don't disagree with this. (author here) I think it could help overall to lower starting salaries, but it'll never happen. It's all a math problem at the end of the day.
This is neat — I do think this is relevant to more than just the software engineering space. See also, healthcare and law (I wrote more at length here, not to derail this comment thread [1]). Our junior training on-ramps for a lot of knowledge-work fields are in some semblance of equilibrium, but it's an unstable one.
[1] https://blog.jordan.matelsky.com/AI-doctors-bum-me-out/
This is a good use of government due to the existing dynamics.
Instead of only funding universities, provide lower risk curves for hiring juniors where the jobs are.
The big issue is the game theory of first mover disadvantage at play.
Whoever trains the junior loses all the investment when the junior jumps ship. This creates a natural situation of every company holding until the ‘foolish ones’ (in their eyes) waste resources on training.
Second mover advantage is real. This is what the government can fix.
This problem is not new. No one's wanted to give juniors the time of day since at least 2018 when it took me 8 months to land my first software developer role.
It sucks if you're looking for entry level work, of course. However, I'm a TL/manager with mostly entry-level reports and I have told them for a while the other side of this mentioned here - by the time they get to senior level they are going to be able to name their price in the shortage.
I'm gonna get some downvote, but I'll say this. Over the last 10 years, the quality of the juniors trends opposite of salary curve. We don't have a crazy interview process, nor are we working on anything ground breaking. By any measurement, we are a run of the mill company that don't offer top end salary but market competitive. The quality of junior engineers I've interviewed has been abysmal. Maybe because we don't have the name nor the high end salary, or maybe our recruiting firms and HR suck in general. My no-hire/hire ratio is literally 50:1. Most of them can't even answer basic computer science questions such as under what condition that a binary search is useful, what's the difference between NoSQL database and relational database, or converting binary to decimal, etc.. They all talk about cloud and distributed computing, etc..
I feel this pain.
We have an intern that is finishing a four year computer science degree that has no clue what git is, never used a log and all he presents is AI garbage.
I find it profoundly depressing to try and teach someone who has no interest in the craft.
> My hire/no-hire ratio is literally 50:1
80% of the candidate I interview pass (leetcode style coding interview, as mandated by the company). This is actually annoying because I'll probably have to raise the bar and start rejecting very good candidates.
> The quality of junior engineers I've interviewed has been abysmal. Maybe because we don't have the name nor the high end salary, or maybe our recruiting firms and HR suck in general. My hire/no-hire ratio is literally 50:1.
I'm sorry but to me this part reads like a humorous phrase that's popular in some circles in my region which goes:
"Maybe <list of negative things, usually correct characterizations of the speaker>, but at least <something even worse>"
The companies I worked for used automated coding quizzes like Codility to weed out the worst applicants, but I suspect you're already doing that.
How is them knowing when binary search is useful relevant to what they'll be doing at work should they get hired?
It feels like there is a psyop going on. Blaming job loss and less entry level jobs on "AI". The real simple reason... Jobs are going overseas, many of them junior level jobs. They are laying off people and then hiring a proportional amount of people overseas. Why are folks falling for this AI nonsense?
Meh, multinational businesses are multinational.
They don't have to hire in any given country.
Given the current state of affairs in the US, I'd be moving the balance elsewhere too.
We are all systems analysts now. We are all business people. Or we're out of a job. Programming as a skill in itself is largely obsolete. It's all about understanding the business: what it needs, how it operates. That takes holistic thinking and people skills that programmers historically just didn't have. They'll adapt, or they'll leave the field.
We have articles that are very skeptical about whether AI companies will ever make any money.
And then we have others claiming that AI is already having such a significant impact on hiring that the effects are clearly visible in the statistics.
Those two phenomena can be true at the same time.
Those two are not contradictory.
AI companies could never make any money (statement about the future, and about AI companies, and finances). And AI could be having a visible effect on hiring today (statement about now, and about non-AI companies, and about employment).
They don't have to both be true, but they do not inherently contradict each other.
In 2000 a lot of internet companies went under while the internet had a huge impact on business and wider society.
Instead the: Come up with you new job instead of doing old peoples job opportunity
As an unhired junior, I think this stems from a lack of unions and the ability of the workforce to make demands of capital (e.g. to prevent offshoring or discriminatory hiring processes)
> "Companies replace junior positions with AI + Senior engineers have been excused from mentorship responsibilities + Companies optimize for immediate results = A systemic issue that no one person can fix"
They forgot to add in "Aging billionaires spend a trillion dollars on longevity research" which results in "110 year old Senior engineers still working"
touché (author here)
Want to stand out in a world where all the job applications are AI slop? Network. The original kind.
Furthermore, this is why the humanities matter: because human relationships matter.
genuinely asking, how do you network to get a job? esp. if you’re a new grad
where do you network? what do you network with these other humans on?
I do think I could get a job from my network because I’ve worked in the industry for years and done good work; I’m a little skeptical of advice to network to junior/new grads. I at least ignore those LinkedIn requests
The comments here amuse me because there's a strong scent of resentment towards people using AI, along with people who copied from SO. I am a mid level developer that started using AI about 4 months ago, and view it as justice against unreasonable and constant micromanagement through estimates on every single task. You want a robot? You're getting your robot now.
Not to mention I'm the only white person on my team other than the owner/operator. They already brought in bots of sorts from overseas. The constant drive to cheaper labor and gutting of the American middle class has been vast compared to the suffering the industry will have under junior developers using AI. It's definitely made my job easier. And I really don't care. No one cared about me. I have relatively low pay, no health insurance, and no 401K. When the last person left, management replied to his goodbye email saying he'd be replaced in a week. And then they proceeded to try to hire someone in Mexico City. Maintain the same time zone, but pay 3rd world wages and likely to have coercive control over them through desperation. Never found anyone.
I have no love for this industry or any of the "woes" it'll have with AI. Overall it's going to lead to lower wages and less jobs. For those out there producing "AI slop", I support you. It's hardly what they deserve, but they've earned it.
Yes, I do need a mentor. :<
At this point we all know the problem. What’s the solution?
After graduating with a bachelor's degree in Computer Science in December of 2024, my career path so far has been doing sex work and then a minimum wage job once I got finically stable enough to not do sex work, but my financial situation is precarious enough I still have to do sex work off and on when unexpected costs come up. I spent a few months applying to everything I could after getting my degree, but got nothing but automated rejections back if anything.
I didn't have the best networking skills to be fair, but I spent most of my college doing remote classes and didn't have much of a chance to network or whatever. I'm thinking about doing grad school so I can have another chance at developing some kind of network or make myself more attractive to employers. My grades were good and I genuinely enjoy computer science so spending half a year improving my portfolio sounds like a fun time. But going to grad school wouldn't really about getting employment, I just want to use my brain for something. Just working a job makes me feel completely insane, like I know that I can do so much more. I feel like I'm wasting the best years of my life and there's no place in this market where I can be useful. The only value I have is selling my body or being a human stand in for a robot at my "real" job.
Maybe this isn't the best place to post this. I have very little hope that I will ever get a job programming, and I'm just sad. What a waste of a life the past 5 years have been.
On a kind of funny note, I would say that doing sex work is genuinely less humiliating than applying to jobs as a new compsci grad. At least I have some signal that I have some value selling myself.
This isn't the first time that the industry has foot-gunned itself.
The continued reliance on say, COBOL, and the complete lack of those developers comes to mind.
Even before LLMs, there were periods recently where multiple companies had "senior only" hiring policies. That just inflated what "senior" was until it was basically 5 years of experience.
This time seems a bit different, however. There are both supply and demand side problems. The supply of students it tainted with AI "learning" now. Colleges haven't realized that they absolutely have to effectively crack down on AI, or the signal of their degrees will wither to nothing. The demand side is also low, of course, since the candidates aren't good, and AI seems to be a good substitute for a newly graduated hire, especially if that hire is just going to use the AI badly.
> The continued reliance on say, COBOL, and the complete lack of those developers comes to mind.
So the irony here is that LLMs are actually going to be decent at COBOL by default. And other uncommon/esoteric codebases. For example I vibe-ported some Apple ii assembly to modern C/SDL and... it works. It's stuff that I just wouldn't even attempt at manual development speed. It may be actually an easier path than training someone to do things, as long as you have a large enough test suite or detailed enough requirements.
for anyone with children, dont waste their time with traditional school, that path is stone dead and is leading nowhere but the abyss of the permanent underclass
apologise for inflicting this era on them and teach them to be entrepreneurial, teach them how to build, teach them rust on the backend, teach them postgres, teach them about assets maintaining value while money loses its
tell them to never under any circumstances take on a mortgage, especially not the 50 year variety. tell them to stay at home for as long as possible and save as much as possible and put it into assets: gold, silver, bitcoin, monero
they must escape the permanent underclass, nothing else matters
Just don't have children. All this churn (learning whatever) isn't worth it (for them).
Crazy that you're getting downvoted. You're right about everything. Well, maybe about rust on the backend...
The world is fundamentally different than it was 50 years ago and the same boomer platitudes no longer make sense. We are going to suffer a global economic collapse in the near future (conveniently when the generations to blame are retired or dead) and it's going to reshape our world and what labor looks like.
I just hope that my generation will be kinder to future generations than the last.
Maybe... that's fine?
We're not hiring a lot of rotary phone makers these days.
Who is hiring their own shoe-smith? It's been 30-ish years since my carpenter father last had work boots resoled.
It's almost as if... technology and economy evolve over time.
For all the arguments software people make about freedom to use their property as they see fit, they ignore non-programmers use of personal technology property is coupled to the opinions of programmers. Programmers ignore how they are middlemen of a sort they often deride as taking away the programmer's freedom! A very hypocritical group, them programmers.
What's so high tech about configuration of machines with lexical constructs as was the norm 60+ years ago? Seems a bit old fashioned.
Programmers are biology and biology has a tendency to be nostalgic, clingy, and self selecting. Which is all programmers are engaged in when they complain others won't need their skills.
As said before, we are not hiring juniors anymore. Or last hire was last year.
As far as I hear from all projects from out customers (finance, insurances, government etc) are neither hiring juniors anymore.
In one of the meetings someone asked: when I go or retire, we won't have anyone to replace me, cause we don't hire juniors, management replied: that is not our problem to discuss.
Aka a problem for future and someone else
Nothing has changed. The problem is the same as it always was.
There is an unbounded amount of opportunity available for those who want to grab hold of it.
If you want to rely on school and get the approval of the corporate machine, you are subject to the whims of their circumstance.
Or, you can go home, put in the work, learn the tech, become the expert, and punch your own ticket. The information is freely available. Your time is your own.
Put. In. The. Work.
this is the end game of capitalism, where the greed driven pursuit of profit wins over social maintenance and development. we see it very clearly with the incredibly socially damaging mass immigration to replenish the slave class and maintain the mythical GDP growth, which is only "necessary" because the native slave classes have been squeezed out of breeding
new grads will be fed to the meat grinder with no regards, its a closed shop unless you know someone
This is entirely due to sociopaths that stole trillions in assets from the general population then bought out law makers to not outlaw their blatant copyright infringement so they can make themselves richer with some self-proclaimed 'noble' aim.
The general population is being rapidly sacked as a 'necessary' expense of criminal elites.
No one should be happy about this.
Yes, and that.
This article is an advertisement for what appears to be a networking service, something which is not really made clear until near the end.
The article is self-serving in identifying the solutions ("do things related to the service we offer, and if that doesn't work, buy our service to help you do them better"), but it is a subject worth talking about, so I will offer my refutation of their analysis and solution.
The first point I'd like to make is that while the hiring market is shrinking, I believe it was long overdue and that the root cause is not "LLMs are takin' our jerbs", but rather the fact that for probably the better part of two decades, the software development field has been plagued by especially unproductive workers. There are a great deal of college graduates who entered the field because they were promised it was the easiest path to a highly lucrative career, who never once wrote a line of code outside of their coursework, who then entered a workforce that values credentialism over merit, who then dragged their teams down by knowing virtually nothing about programming. Productive software engineers are typically compensated within a range of at most a few hundred thousand dollars, but productive software engineers generally create millions in value for their companies, leading to a lot of excess income, some of which can be wasted on inefficient hiring practices without being felt. This was bound for a correction eventually, and LLMs just happened to be the excuse needed for layoffs and reduced hiring of unproductive employees[1].
Therefore, I believe the premise that you need to focus entirely on doing things an LLM can't -- networking with humans -- is deeply faulty. This implies that it is no longer possible to compete with LLMs on engineering merit, and I could not possibly disagree more. Rather than following their path forward, which emphasises only networking, my actual suggestion to prospective junior engineers is: build things. Gain experience on your own. Make a portfolio that will wow someone. Programming is a field that doesn't require apprenticeship. There is not a single other discipline that has as much learning material available as software development, and you can learn by doing, seeing the pain points that crop up in your own code and then finding solutions for them.
Yes, this entails programming as a hobby, doing countless hours of unpaid programming for neither school nor job. If you can't do that much, you will never develop the skills to be a genuinely good programmer -- that applied just as much before this supposed crisis, because the kind of junior engineer who never codes on their own time was not being given the mentorship to turn into a good engineer, but rather was given the guidance to turn them into a gear that was minimally useful and only capable of following rote instructions, often poorly. It is true that the path of the career-only programmer who goes through life without spending their own time doing coding is being closed off. But it was never sustainable anyways. If you don't love programming for its own sake, this field is not likely to reward you going forward. University courses do not teach nearly effectively enough to make even a hireable junior engineer, so you must take your education into your own hands.
[1] Of course, layoff processes are often handled just as incompetently as hiring processes, leading to some productive engineers getting in the crossfire of decisions that should mostly hurt unproductive engineers. I'm sympathetic to people who have struggled with this, but I do believe productive engineers still have a huge edge over unproductive engineers and are highly likely to find success despite the flaws in human resource management.
Hey there, I'm the developer of the app along with my wife, the author of the post. We quit our jobs over a year ago to work on a problem we care about and helping people connect to their goals through people is what we landed on. That being said, we spend most of our time on the tech! And I think your advice is spot on, that a portfolio of projects really is THE MOST IMPORTANT THING. It's where I would tell people to start. But from there, connecting people to others who care about that portfolio, is also important. I think a lot of technical people pay attention to the former, and tend to ignore the latter. Which is me too! So rather than "this is the only true way" I hope it comes across like a potential piece of the puzzle to some people.
Thanks for giving it some thought and for your perspectives, they really help.
> This article is an advertisement for what appears to be a networking service, something which is not really made clear until near the end.
I have been seeing an uptick of articles on HN where someone identifies a problem, then amps it up a bit more and then tells you that they are the right ones to solve it for a fee.
These things should not be taken seriously and upvoted.
The problem is that praying that someone stumbles upon your brilliant hobby projects and offers you a job is a terrible bet. Yes, you have to be good a software development, but being good at software development doesn't land you job. Being good at software development, and cutting through the noise gets you a job. Because even if all those laid off people are incompetent, they're still applying for the same jobs you are, and it is very difficult to identify who's who.
So, from a individual's perspective, figuring out how to meet people who will help you sidestep the "unwashed masses" pile of applications is probably the next most important thing after technical competence (and yeah, ranking above technical excellence).
The first graph is interesting: it showed all groups about the same until late 2022 when they start to diverge. Around that time, we were talking about "greedflation" and "over hired during covid", and probably most important, the first year after expiration of Section 174 R&D was 2022.
Good luck with causation/correlation vs the rise of LLM.
This topic requires analysis to a greater depth than most comments I've seen so far.
It wasn't too long ago that it was common to read threads on HN and other tech fora about universities graduating software engineers seriously lacking coding skills. This was evidenced by often-torturous interview processes that would herd dozens to hundreds of applicants through filters to, among other things, rank them based on their ability to, well, understand and write software.
This process is inefficient, slow and expensive. Companies would much rather be able to trust that a CS degree carries with it a level of competence commensurate with what the degree implies. Sadly, they cannot, still, today, they cannot.
And so, the root cause of the issue isn't AI or LLM's, it's universities churning people through programs and granting degrees that often times mean very little other than "spent at least four years pretending to learn something".
If you are thinking that certain CS-degree-granting universities could be classified as scams, you might be right.
And so, anyone with half a braincell, will, today, look at the availability of LLM tools for coding as a way to stop (or reduce) the insanity and be able to get on with business without having to deal with as much of the nonsense.
Nobody here makes a product or offers a service (hardware, software, anything) for the love of the art. We make things to solve problems for people and services. That's why you exists. Not to look after a social contract (as a comment suggested). Sorry, that's nonsense. The company making spark plugs makes spark plugs, they are not on this planet to support some imaginary public good. Solving the problem is how they contribute.
And, in order to solve problems, you need people who are capable of deploying the skills necessary to do so. If universities are graduating people who can barely make a contribution to the mission at hand, companies are going to always look for ways to mitigate that blocking element. Today, LLM's are starting to provide that solution.
So it isn't about greed or some other nonsense idealistic view of the universe. If I can't hire capable people, I will gladly give senior engineers more tools to support the work they have to do.
As is often the case, the solution to so many problems today --including this one-- is found in education. Our universities need to be setup to succeed or fail based on the quality of the education they deliver. This has almost never been the case. Which means you have large scale farming operations granting degrees that can easily be dwarfed by an LLM.
And don't think that this is only a problem a the entry level. I recently worked with a CTO who, to someone with experience, was so utterly unqualified for the job it was just astounding that he had been give the position in the first place. It was clearly a case of him not knowing just how much he didn't know. It didn't take much to make the case for replacing him with a qualified individual or risk damage to the company's products and reputation going forward.
A knowledgeable entry-level professional who also has solid AI-as-a-tool skills is invaluable. Note that first they have to come out of university with real skills. They cannot acquire those after the fact. Not any more.
NOTE: To the inevitable naive socialist/communist-leaning folks in our mix. Love your enthusiasm and innocence, but, no, companies do not exist to make a profit. Try starting one for once in your naive life with that specific mission as your guiding principle and see how far you'll get.
Companies succeed by solving problems for people and other companies. Their clients and customers exchange currency for the value they deliver. The amount they are willing to pay is proportionate to the value of the problem being solved as perceived by the customer --and only the customer.
Company management has to charge more than the mere raw cost of the product or service for a massive range of reasons that I cannot possibly list here. A simple case might be having to spend millions of dollars and devote years (=cost) to creating such solutions. And, responsible companies, will charge enough to be able to support ongoing work, R&D, operations, etc. and have enough funds on hand to survive the inevitable market downturns. Without this, they would have to let half the employees go every M.N years just because of natural business cycles.
So, yeah, before you go off talking about businesses like you've never started or ran a non-trivial anything (believe me, it is blatantly obvious when reading your comments), you might want to make an attempt to understand that your stupid Marxists professors or sources had absolutely no clue, were talking out of their asses, never started or ran a business, and everything they pounded into your brains fails the most basic tests with objective, on-the-ground, skin-in-the-game reality.
A lot of this may be due to the recent far left changes in curriculum at many universities. A degree used to sort of a certificate an employer could rely upon that someone had basic skills. That is no longer the case. This makes older employees where the certificate was still reliable more attractive.
Irrelevant.
I went to a very bottom-tier school with a piss-poor reputation (but no debt!).
That didn’t stop me from getting employed, because employees were looking for workers when I started my employment journey.
"far left changes"? What are you even talking about? You think there's some new "woke" CS curriculum which doesn't actually teach algorithms?