Is ATS really the problem with modern hiring?

Partially. ATS systems do filter out qualified candidates when CVs aren't formatted or keyworded correctly. But they're also often blamed for outcomes that have more to do with the overall hiring volume, internal candidates, or basic supply-demand imbalance in a given field. The ATS is a tool — the system around it is the bigger story.

What do recruiters actually want to see in a CV?

Evidence that you understand the role and have done it before (or something close). That means specific achievements over generic duties, language that mirrors the job posting, and a format that makes the relevant experience easy to find quickly. Recruiters spend seconds on a first pass — the job of your CV is to survive that pass.

How much does networking actually help in a job search?

Significantly — but unevenly. Candidates with strong professional networks get referred to roles before they're posted, skip the ATS entirely, and have warmer introductions to hiring teams. Those without established networks face the full friction of the public application process. The advice to 'just network' ignores that networks take years to build and access to them is not equally distributed.

2026-05-01 · Daniel Zambrano

Your ATS Is Fine. The System Around It Isn't.

The ATS isn't the villain. It's a symptom of a hiring system designed around the employer's convenience — one where candidates spend months preparing for a process that takes seconds on the other side.

Spend five minutes in any job search forum and you'll find two warring camps. One side blames the ATS: "Algorithms are rejecting qualified people. Fix the technology." The other side dismisses the grievance: "Stop complaining and network. Build projects. Get certifications. The ATS is just a filter for people who didn't try hard enough."

Both camps have a point. Neither has the full picture.

The debate

The "ATS is broken" argument goes like this: automated screening systems reject candidates before a human ever sees the CV, keyword matching is blunt and arbitrary, and a genuinely qualified person with an unconventional background can disappear into the void simply because their CV doesn't match the exact phrasing in a job description.

The counterargument goes like this: companies get hundreds of applications for every role. Without some form of filtering, the process would be unmanageable. And plenty of people do land jobs — through referrals, through demonstrable skills, through relationships they built before the role was even posted.

Here's the thing: both of these statements are true at the same time.

Recruiters aren't wrong

The advice to network, build a portfolio, and keep certifications current isn't bad advice. It's accurate. A strong referral from someone inside the company will, in most cases, outperform a cold application — even a perfectly optimized one. In fields like software, design, and marketing, a portfolio that shows real work often carries more weight than any document.

Hiring managers are human. They remember the person who helped them in a professional forum six months ago. They notice when a candidate has contributed to open source code they actually use. Context that comes from a relationship is something a CV can't manufacture.

So yes: networking matters. Projects matter. Certifications matter (in fields where they signal real competence). None of that is wrong.

But candidates aren't wrong either

Here's what that advice glosses over: doing all of it is a second full-time job. And most people already have a first one.

Building a portfolio takes months. Getting a meaningful certification costs hundreds of dollars and dozens of hours. Growing a professional network that will actually produce referrals takes years — and it requires access to the right rooms in the first place. If you're early in your career, between jobs and burning through savings, or navigating a field where you don't have existing connections, the gap between "just network more" and something actionable is enormous.

The advice is structurally sound. The timeline is brutal. And it almost always comes from people who already have networks, portfolios, and the financial runway to invest in both.

Telling a junior candidate to "build projects on the side" while they're working a full-time job to pay rent is technically correct advice that ignores all the reasons it's easier said than done.

The asymmetry nobody talks about

The real problem isn't the ATS. It's the asymmetry baked into the entire system.

A candidate might spend four to six hours on a single application: researching the company, tailoring the CV, writing a cover letter, preparing for a potential call. Multiply that across twenty or thirty applications — which is a modest number for an active job search — and you're looking at 80 to 180 hours of unpaid labor.

On the employer's side, a recruiter might spend 10 seconds scanning each CV. An ATS might filter 90% of applicants before a human looks at anything. One hire comes out the other end.

The candidate bears almost all the cost. The employer bears almost none of the friction. That imbalance doesn't get talked about, because it's systemic and there's no obvious villain. The ATS is convenient to blame because it's concrete. The actual problem — that the system was designed around employer convenience, not candidate fairness — is harder to name and impossible to fix with a resume tip.

What you can actually control

None of that analysis changes what you have to do this week if you need a job. You can't redesign the system. What you can do is stop losing the round that's most preventable.

The CV is the threshold document. It doesn't get you the job — but a weak one will cost you the interview. And unlike building a portfolio or growing a network, improving your CV for a specific role is something you can do in an afternoon.

Specifically:

Match the language in the job description. ATS systems aren't clever — they look for the words in the posting. If the job says "stakeholder management" and your CV says "client liaison," you may not match even if your experience is identical.
Use standard section headings. "Work Experience," not "Where I've Been." The parser needs to recognize the structure.
Lead with outcomes, not duties. "Reduced onboarding time by 40%" lands differently than "Responsible for onboarding."
Tailor per role. One-size CV is better than no CV. A tailored CV is better than both.

These aren't magic. They won't overcome every structural disadvantage in the system. But they keep your application in the game long enough for a human to see it — and that's the first gate you need to clear.

Where QuillCV fits in

We built QuillCV to handle the CV side of the equation. You paste in a job description, we analyze the keywords, structure, and requirements, and generate a tailored CV that's optimized for that specific role and formatted for the hiring conventions in your target market.

We're not solving asymmetry. We're not building your network or writing your portfolio. Those are on you, and we'd be lying if we said otherwise.

What we do is make sure your CV isn't the thing that loses it for you — that you're not filtered out in round one because of a keyword gap or a formatting problem that a 20-minute rewrite would have fixed. You still have to do the hard work. We just make the document part faster and more effective.

The system is imperfect. Work within its constraints while you play the longer game. That's not defeatism — it's strategy.