You sent 200 applications. You heard back from three. Two were rejections and one was a "we've moved forward with other candidates" that you're pretty sure was automated.
You did the thing. The degree, or the bootcamp, or the self-taught grind. You learned the stack, you built the projects, you ground the LeetCode. And the door that everyone promised would open is just… not opening. Meanwhile the news is a steady drip of layoffs, and every post about "breaking into tech" either tells you to never give up or tells you it's already over.
So somewhere underneath the exhaustion, there's a quiet, scary question you maybe haven't said out loud: is this even worth it anymore? Do I keep trying, or do I go do something else?
That's a completely reasonable question to be asking right now. It isn't weakness, it isn't impatience, and it isn't you being dramatic. And anyone who answers it for you with a slogan — "grind harder!" or "tech is dead, run!" — is wasting your time, because they're answering a question you didn't ask.
I'm not going to tell you to stay, and I'm not going to tell you to go. I don't know your life. What I can do is give you honest information and an honest way to think it through, so that whatever you decide is a decision and not a panic. Let's do that.
First, the honest reality — no sugar, no doom
You deserve the real picture before you decide anything, so here it is, both halves.
The brutal half is real, and it's not in your head. Entry-level hiring has genuinely collapsed. Depending on which report you read, junior developers have fallen from around 15% of tech hiring to about 7%, and entry-level postings sit something like 40% below where they were a few years ago. Layoffs have continued in waves, tens of thousands per quarter, with AI increasingly cited as a factor. And there's a genuinely cruel twist called the "experience paradox": companies cut their junior roles and say they want experienced people — which leaves beginners asking how you're supposed to get experience from a door that's closed. If you feel like the game got harder right as you showed up to play it: you're right. It did. This is not a personal failing, and I need you to actually believe that part before you make any decision, because deciding out of shame leads you somewhere different than deciding out of clarity.
But the other half is also real, and you need it to decide honestly. The market didn't die — it split. Overall tech employment is still projected to grow modestly. AI and ML roles are booming — some postings up 59%, 85%, even higher year over year. And the most important nuance, the one almost nobody says clearly: entry-level tech jobs didn't vanish so much as move and change shape. The specific tasks juniors used to be hired for — boilerplate, scripted testing, routine bug fixes — got automated. So companies stopped hiring for those, and the hiring shifted toward problem-solving, AI-augmented work, smaller companies, and specializations. One way people put it: the junior role isn't being eliminated, the entry bar is being raised. That's harder. It is not the same as "closed."
Hold both of those at once, because the decision you're about to make depends on seeing the whole board, not just the half that matches your current mood.
(All of these figures come from 2025–2026 industry and labor reports; treat them as directional and current-as-of-writing — they move. Sources at the end.)
The reframe: you're actually asking two different questions
Here's the thing that will make this decidable instead of just scary. "Should I give up on tech?" is really two questions wearing one coat, and people panic because they've mashed them together. Pull them apart and it gets a lot clearer.
Question one: is the path broken, or the field?
The old path in — grind the fundamentals, mass-apply to hundreds of listings, get hired — is genuinely broken right now. That spray-and-pray approach worked when companies were hiring aggressively and a warm body with the right keywords got interviews. It mostly doesn't work anymore. But "the path I was using stopped working" is a completely different statement from "the field is closed to me." One is an approach problem. The other is a field problem. People quit over the first thinking it's the second.
Question two: do you actually want this — or did you want what it promised?
Be honest with yourself here, because nobody's watching. A lot of people came into tech for the rewards — the salary, the stability, the status of a "safe, future-proof" career. There is nothing wrong with that; those are good reasons to pick a field. But when the rewards get shaky — when "safe" stops feeling safe — it's worth asking whether you actually like the work itself, separate from what it was supposed to pay and provide. Because the answer changes everything about what you should do next.
Most people never separate these two. They feel the pain, collapse it into "should I quit tech," and either grind blindly or bail in a panic. Separating them is where an actual decision becomes possible.
A framework for deciding — honestly, either way
So here are the questions to actually sit with. I've tried to write them so that both answers are respectable, because they are. There's no correct destination here; there's only the honest one for you.
1. Do you enjoy the actual work on a normal day — reward aside? Not the dream of the job. The doing of it: building the thing, chasing the bug, the moment it finally runs. If yes — if some part of you likes this even when nobody's paying you for it — that's a strong signal, because that motivation is exactly what survives a brutal market. If honestly no — if the work itself is a slog you tolerate for the paycheck — that's not a character flaw, it's extremely useful information.
2. Is your struggle an approach problem or a fit problem? Be precise. Two hundred applications into a void that aren't landing is an approach problem — the method is wrong, not you, and methods can change. Dreading every hour you actually spend coding is a fit problem — and no change of approach fixes a fit problem. These feel the same from the inside (both are "it's not working") and they have opposite solutions.
3. What did you actually want — the work, or the life it promised? And the follow-up: is that life still realistically on offer here, or is it more available somewhere else now? If what you wanted was stability and good pay, it's fair to ask honestly where those are most reachable for you in the next few years. That might be an adapted path in tech. It might not be. Both are legitimate answers to an honest question.
4. What's your actual runway and risk tolerance right now? This one isn't about passion, it's about reality, and it matters. Someone with a year of savings and no dependents can afford to keep pushing on a hard path. Someone supporting a family on a shrinking timeline is making a completely different, equally reasonable calculation. There is no brave answer and no cowardly answer here — there's only your real situation, which you're allowed to factor in without guilt.
Sit with those four. Where they point is different for different people, and that's the whole point — this isn't a test with a right answer.
If you're leaning stay: then change the path, because the old one broke
If those questions point you toward staying — you like the work, your struggle is an approach problem, the life you want is still reachable here — then the single most useful thing to internalize is this: the reason it's not working is probably the old approach, so adapt the approach.
Briefly, because this isn't a full guide: differentiate instead of mass-applying (a hundred tailored, targeted efforts beat a thousand sprayed ones now). Build a visible body of real work that proves you can do the job, since "I can build things" travels further than "I have a certificate." Learn to work with AI rather than pretending it isn't there — that's literally the raised bar now, and AI-fluent juniors are the ones commanding a premium. Look at smaller companies and adjacent or specialized roles, which is where a lot of the entry-level hiring actually still is, rather than only the big names everyone's spraying. And network into opportunities instead of applying cold, because referrals cut through a pile that algorithms are filtering ruthlessly.
The door isn't open the way it was. But it's a different door now, not a wall — and most people are still knocking on where the old one used to be.
If you're leaning go: that is not failure, and I mean that
If those questions point you the other way — the work itself doesn't move you, or it's a fit problem, or what you wanted is more reachable elsewhere, or your runway just doesn't allow the long grind — then hear this clearly, because a scared beginner rarely gets told it: choosing something else is not quitting, and it is not losing.
Sometimes a brutal market does you an actual favor. It forces a question you'd have spent years avoiding if things had been easy: is this really what I want? Plenty of people would have drifted into a tech career they didn't love simply because the money was good and the path was smooth — and a hard market shook them awake to go find something that fits them better. That's not defeat. That's clarity you got the hard way.
And it's rarely a total loss of what you've built. The problem-solving, the logical thinking, the comfort with tools and systems — those transfer. Into tech-adjacent roles, into other industries that badly need technically-literate people, into something entirely different you'd genuinely rather do. Leaving because you realized you want a different thing is one of the more mature moves a person can make. You're allowed to make it without calling it failure, because it isn't one.
The takeaway
You don't need me, or a motivational post, or a doom thread, to make this choice for you. You need honest information and permission to decide — so here's both.
The reality: it is genuinely hard right now, it is largely not your fault, and it is not hopeless — the field didn't close, it moved, and whether that move is one you want to follow is a real and personal question. Staying and adapting is a respectable answer. Leaving or pivoting is an equally respectable answer. The only bad outcome is letting fear quietly make the choice for you — drifting on in a panic, or bailing in one — instead of deciding on purpose.
So think clearly, be honest with yourself about the four questions, and then choose. Both doors are open. Both are allowed. Make it yours.
Honest question, and I'd genuinely like real answers rather than the motivational kind: if you're a beginner in this market, are you doubling down, pivoting, or genuinely not sure yet — and what's the thing that'll actually decide it for you? And if you're already in tech: what would you honestly tell someone starting out right now — not the LinkedIn version, the real one?
Sources & further reading: figures are drawn from 2025–2026 labor-market and industry reporting, including Stanford HAI's AI Index (entry-level developer employment down ~20% from its 2024 peak), SignalFire and ARDURA analyses (junior share of hiring falling from ~15% to ~7%), Ravio / Resume.org / CompTIA / Dice / Indeed Hiring Lab data (entry-level posting declines, AI-role growth of 59–134%, net tech employment still projected to grow modestly, AI-skill salary premiums), and Challenger, Gray & Christmas layoff tracking (AI cited as a rising share of tech cuts in 2026). These numbers vary by source and methodology and are moving quickly — treat them as directional and current-as-of-writing, and check the primary reports for the latest.
Top comments (3)
james, this is the most grounded, necessary take on the current tech market i've read. the distinction between "the path is broken" and "the field is closed" is the exact mental shift beginners need to hear.
to answer your question directly: as a 12-year-old developer building entirely on a $150 android phone with spotty 3g, the "old path" (mass-applying, generic bootcamps, grinding leetcode) was never an option for me. it was already broken.
so i had to build a new door. i focused on radical constraints: building a 142kb, zero-bloat ai code mentor (koda) designed specifically for budget devices, and i documented the entire chaotic process in public. instead of hiding behind a generic resume, i let the constraint-driven engineering speak for itself.
the result? i just hit 24 real, active users globally (including developers in poland and my local community in tamil nadu) who actually use the tool.
my advice to other beginners: stop trying to walk through the door that slammed shut. find a radical constraint you can embrace (a specific niche, a unique hardware limitation, a hyper-local problem), build something tiny and useful for it, and share the chaos-run log. differentiation beats mass-application every single time.
thank you for giving us permission to think clearly and choose our own path. 🐯🚪
Some comments may only be visible to logged-in visitors. Sign in to view all comments.