Last week I saw a junior developer listing with over 200 applications in less than three days. I opened a few out of curiosity and a good chunk of them had five, six years of experience on the resume. People who had already led a squad, already shipped a project alone from zero to deploy, competing for space with someone trying to land their very first opportunity in the field. And the worst part is that this isn't the exception, it's basically the rule for a lot of junior listings these days. It's not an accident. Hiring someone senior for a junior role is, in practice, buying senior output while paying entry-level salary. In a tight market, with a lot of people out of work and willing to accept pretty much anything just to pay the bills, that temptation gets even stronger on the hiring side. The company saves money, gets someone who delivers fast with almost no learning curve, and on paper it looks like a smart call. The problem is that junior and senior aren't competing for the same thing, even when the job title on the posting is identical. A senior delivers value almost immediately, solves problems with little or no supervision, has already made enough mistakes to know how to avoid the expensive ones. A junior is a different kind of bet entirely: the company invests time, patience and mentorship hoping to grow someone who'll mature there and, with luck, stick around. When a senior professional takes that seat just because they needed any income at all, they usually don't stay. They leave the moment something closer to their actual level and pay shows up, and the company loses exactly the investment it made trying to develop someone. There's also an effect almost nobody stops to think about in the short term, but that changes everything down the line. If seniors are filling junior seats out of necessity, the people who should be entering the field simply don't. The pipeline for developing new talent clogs up. And a few years from now there's going to be a shortage of senior people, because nobody got the chance to start as a junior and grow into one. Kind of ironic, honestly: the same market that today accepts seniors in junior roles is the one that'll complain about a senior talent shortage down the road. Worth being clear that the senior applying for a junior role isn't the villain of this story. They're surviving, and that's completely legitimate — nobody should be blamed for trying to make rent. The real problem sits somewhere else entirely: in the crooked way the role gets designed, in the company's lack of honesty about what it actually needs to hire, and in a market that normalized using junior titles to describe jobs that in practice demand senior experience. That pushes an obstacle onto the real junior, the one trying for their first shot, that shouldn't even exist: competing against someone who's already lived through everything this person hasn't even started yet. There's a different path here. Companies being more transparent about the actual level of the role and attaching a salary range that matches it. Hiring processes that filter for learning potential instead of just resume length, because a longer resume doesn't always mean the right fit for that specific context. And the market itself — recruiters, tech leads, dev communities — talking about this openly instead of treating it as taboo, because normalizing it in silence just makes it worse with every cycle. So here's the question I don't think anyone really wants to answer: if you had to choose between hiring the desperate senior willing to work for junior pay just to survive, or the actual junior who might take longer to deliver but is exactly what that role was supposed to develop, which one would you pick knowing that either way someone loses? And more to the point: who's actually at fault here — the senior who takes the job to avoid going hungry, the company that designs the role on purpose to fish for that kind of candidate, or the market that let this become normal?