I submitted a take-home project, then didn’t hear back for three months. Three months was long enough that when a recruiter finally reached out, I had to dig through my own applications to remember what I’d even applied to.

Luckily, I was building Job Atlas and somewhere in its early POC lifetime, I found that app.

Once things kicked off, though, they moved fast. First round, then a live coding round, then a longer conversation with the team where I walked through two of my own projects for over an hour.

Every conversation felt warm and real. I liked the people I was talking to; I liked the industry, and the pace made it feel like I was a strong fit they wanted to move on quickly.

Then, a day before the final interview, I got a late email. Someone else had accepted the offer. They needed to cancel.

Nobody, not the recruiter, not the team, not anyone I’d spoken with across three rounds, had ever mentioned they were waiting on another candidate or that an offer was even out. I found out the process had a competing finalist the same moment I found out I’d lost to them 😞

That one experience is what pushed me to actually sit down and map out everything that feels broken about job searching right now, both from the applicant side and, since I’m a developer, from the side of what companies could actually be doing differently.

This isn’t a rant. It’s an honest look at nine specific patterns, backed by what other people are experiencing too, not just me.

The System Is Straining Under Its Own Weight

The hiring process on both sides was built for a scale of applications that no longer exists, and that gap is the pattern underneath almost every story in this post.

Candidates apply in higher volume because AI makes it easy to apply fast and wide.

Recruiters filter in higher volume because AI makes it easy to sort fast and wide.

Neither side redesigned the actual process for what that volume does to trust, communication, or basic decency along the way.

Sound familiar? Well, that’s not a sign you’re doing something wrong, but a sign the process itself is currently kind of a mess.

Related: This Is The Free Browser Extension Your Job Search Needs

1. Unpaid Take-Home Projects Before You Even Get a Real Conversation

It’s beyond frustrating that take-home projects have become the first ask at many companies. And it’s not so much the ask itself that’s always the problem but what surrounds it.

Requirements are often vague or incomplete. You’re left guessing at scope.

Then, if you do get feedback at all, it’s sometimes generic critique like “this doesn’t have strong authentication” or “no persistence layer,” things you’d expect to hear about a late-stage MVP, not a scoped demo you built on a weekend with no pay and no guarantee of an interview at the end.

There’s real disagreement in developer communities about whether take-homes are even a good interview method.

Some developers argue they’re a more honest signal than a whiteboard algorithm question, because they show how you actually build (I agree).

Others refuse to do them at all, on principle.

Both camps have a point.

However, the actual complaint isn’t “take-homes are bad.” It’s that they’re unpaid, vague, and required before you’ve had any real conversation with a human about the role.

A handful of companies have started paying for take-home work, sometimes a few hundred dollars, and those posts get noticeably positive reactions online. That tells you that the fix isn’t complicated; it’s just rare.

Tip 💁‍♀️
If a take-home doesn’t come with a clear rubric or scope, ask for one before you start. A company that can’t tell you what “done” looks like probably can’t grade it fairly either. Skip, they’re not worth your time.

Explore: This Is Why Your Engineering Role No Longer Makes Sense

2. Moving Fast Isn’t the Same as Being a Priority

In my case, I assumed that because the process was moving quickly and every conversation felt warm, I was a serious, prioritized candidate. I had no reason to think otherwise. Nobody gave me one.

What I didn’t know, and what a lot of candidates don’t know, is that speed through a pipeline often has nothing to do with how many other people are also being fast-tracked in parallel.

A recruiter posting anonymously online shared that companies frequently keep a second or third candidate moving through rounds as a backup, without ever telling that candidate they’re a backup, in case the top choice falls through or negotiates too hard.

So the signal you’d naturally read (fast rounds, warm conversations, quick scheduling) doesn’t actually mean what you think it means. It might just mean you’re in a pool, not that you’re the pick.

If a company can’t tell you where you actually stand, the least they owe you is not letting you prepare for a system design round the same week they’ve already extended an offer to someone else 😒

3. AI Is Now on Both Sides of the Table, and Nobody Trusts Anyone

Applicants using AI agents to mass-apply are running into a problem that used to be rare: fake job listings.

Some of these listings are outright fraud, built to harvest resumes or personal information. Others are just recruiters testing the market with a role that doesn’t really exist yet (or product managers, courtesy of a recent viral LinkedIn post).

At the same time, most hiring teams are now using AI just as heavily to manage the flood of applications. Recent hiring industry research puts AI-assisted or fraudulent candidates as the single biggest anticipated hiring challenge for 2026, ranked above even the talent shortage itself.

Adoption of AI tools on the recruiting side is now close to universal.

What’s left is a trust vacuum.

Recruiters can point at bot-generated applications and ask how they’re supposed to know who’s real.

Candidates can point at fake listings and ask the same question back.

Application volume on platforms like LinkedIn has reportedly jumped sharply year over year, which only makes both problems worse at the same time.

As a developer (and a candidate), I don’t think any of this is some unsolvable, exotic problem. Detecting patterns, ranking incoming data, and flagging anomalies is normal engineering work.

The tools to build a better triage system already exist. What’s missing isn’t the technology but the will to build it well instead of just fast.

Note 📍
For anyone job hunting right now, you can usually identify a fake listing if there’s no company name, a generic domain in the reply-to address, and urgency to move the process along fast. But take it with a grain of salt because one characteristic alone isn’t proof. A cluster of them is worth pausing on.

Explore: Why LinkedIn’s Quiet AI Overhaul Makes It Suddenly Feel Broken

4. Does the ATS Really Reject Your Resume, or Is It Something Else?

There’s a popular claim that applicant tracking systems (ATS) auto-reject the majority of resumes before a human ever sees them, sometimes cited as high as 75 percent. However, that specific number doesn’t hold up well under scrutiny.

Most ATS filtering is configured by actual humans setting keyword or qualification rules, not some opaque AI silently discarding candidates.

Even when a human configured the filter, though, the practical effect on you as a candidate is identical.

If your resume gets filtered out for missing a keyword a person decided mattered, you still never get seen by anyone. The mechanism isn’t a mysterious AI villain, yet the outcome still feels like screaming into a void.

So both things are true at once. The dramatic “AI is eating your resume” story isn’t quite accurate. And the feeling that nobody’s actually looking at what you built is, frustratingly, often correct anyway 😔

5. Vague Recruiter DMs and the Quota Problem

You’ve probably gotten the message. Something like “I have an exciting opportunity, are you open to new roles?” No company name. No details. Just enough to make you wonder if it’s worth replying to.

Some of this is just recruiters filling a quota, casting a wide net without much personalization behind it.

But some of it ties into a bigger problem: job scams.

The volume of job scams has climbed sharply in recent years, with reported losses in the hundreds of millions of dollars tied to fake recruiter outreach and fraudulent listings.

Vague, urgent-sounding DMs are one of the most common patterns scammers use, which means the instinct to be cautious isn’t paranoia. It’s rational.

That overhead, the extra step of verifying whether a recruiter and a company are even real before you’ll share your resume, is exhausting on top of everything else.

It’s a cost that didn’t exist in the same way, and it’s a direct downstream effect of how cheap it’s become to fake outreach at scale.

Related: Here Is The Real AI Workflow Companies Keep Ignoring

6. Getting Recruited for a Job You Already Got Rejected From

This one throws me off every time it happens (and it’s happened too many times). A recruiter reaches out about a role, and you realize you already applied to that exact company months ago and got rejected.

Sometimes it’s the same role. Sometimes it’s a near-identical one.

Maybe a human actually reconsidered you. Maybe an auto-reject fired without anyone looking at your application at all.

Or maybe they needed to hit an outreach quota and pulled from an old list without checking status first.

There isn’t a clean, universal answer.

Some people in developer communities say to just be upfront about the previous rejection when you respond.

Others say don’t bring it up at all, just treat it as a fresh shot.

Both are reasonable.

The real problem isn’t what to do about it. It’s that companies have built systems opaque enough that even the recruiter reaching out to you might not know why you’re back in front of them.

7. The Bait and Switch Call

You get a message from a recruiter about a specific role. You’re interested, so you take the call. And then, on the call, you find out that role is either already closed or was never really the one they wanted to talk to you about.

Now you’re being pitched on something else, often something you didn’t apply for and might not even qualify for.

This shows up often enough to be a known pattern, not a fluke.

There are real accounts of candidates completing full interview loops for a role, only to be told afterward the role had closed and they’re now up for a different, lower-level position instead, sometimes with a request to interview all over again for it.

The fix costs nothing. If the original role closed before the call, say so in advance.

Let the candidate decide if they still want that 15 or 30 minutes to talk about something else.

Springing it on someone mid-call wastes their time and reads as either disorganized or a little manipulative, even if that’s not the intent.

Tip 👀
If a recruiter pivots you to a different role mid-call, it’s fine to ask for a day to think it over instead of deciding on the spot. You’re allowed to want time, even if the conversation felt friendly.

8. Recruiter Ghosting After Final Round Has No Excuse Left

Ghosting after a final round, sometimes after hours of live coding and system design conversations, is close to universal across companies right now.

Recruiters posting anonymously about their own industry have admitted that a lot of this silence isn’t mysterious. It’s usually just waiting on a preferred candidate to accept or decline before circling back to anyone else 🤦‍♀️

I don’t buy the volume excuse anymore, and I say that as someone who builds software for a living.

If a company can adopt AI tools fast enough to filter thousands of resumes a day, that same company has the technical capability to build a system that ranks, groups, and flags candidates for a two-line status update instead of total silence.

This isn’t a hard engineering problem. It’s a workflow that hasn’t been prioritized, because ghosting costs companies nothing and costs candidates everything.

There’s a real, recurring wish across developer and job-seeker communities for some kind of recruiter accountability or reputation tracking.

People don’t just want to vent about this. They want it fixed structurally, which tells you it’s not a fringe complaint.

Explore: Developer Job Market 2026: Why JDs are Broken & How to Win with AI

9. Being Strung Along Under the Cover of “Internal Talks”

You’re not told no. You’re told things are still “in internal talks,” which sounds like progress but often means you’ve been parked as a backup while someone else moves through the real process.

Let’s be real: It’s ghosting, just quieter and meaner.

Sometimes you’re even advanced another step while still functioning as the backup option, which makes it feel like real momentum when it might not be.

Recruiters themselves have described this pattern from the inside as usually less about real uncertainty and more about not wanting to lose a backup candidate before the preferred one is locked in.

This was close to what happened to me. Everything moved. Everything felt warm and specific and real. And the entire time, there may have been a second track happening that nobody thought I deserved to know about.

What I Actually Took Away From All This

None of these nine things exist in isolation. The same AI-driven volume that’s flooding recruiters with applications feeds the scam anxiety around vague outreach. It also gives cover to ghosting when nobody can be bothered to send a two-line update.

The speed that reads as a false priority signal is the same root cause behind a recruiter pivoting you to a different role mid-call.

Pull on any one thread, and you find the same tangle underneath due to a hiring process built for a much smaller, slower version of itself, now straining under volume nobody redesigned it to handle.

I don’t think candidates using AI to apply faster are the villains here.

I don’t think every recruiter ghosting a final-round candidate is acting in bad faith either.

Most of this looks like two sides making rational, self-protective choices inside a broken system, and neither side is fully responsible for fixing it alone.

I wish I had a clean five-step fix to hand you at the end of this. I don’t. What I have is a clearer picture of the pattern, and that’s most of what got me through processing my own experience with it.

It’s a Wrap

Thanks for sticking with me through all nine of these. If any resonated because it matched something you’re going through right now, I want you to know it’s not just you, and it’s not something you’re doing wrong.

You can be the best candidate for the job, but I’m sorry to say it doesn’t matter.

It’s come down to mostly luck, word of mouth, or networking, and plain faith to keep going.

Everyone agrees the process is broken. Nobody is doing anything. Someone is bound to make a difference at some point (hopefully soon).

If you’ve been through a version of the story I opened with, or you’ve found something that actually worked against the grain of all this, I’d like to hear it. Drop it in the comments. We can commiserate together 🥲

Best of luck, cheers!