You sent forty applications. Back came two automated emails and one "we'll keep your CV on file". Nobody has ever seen that file.
Before you decide the problem is you, let's read the logs.
Why am I not getting job interviews? Usually your applications stop at one particular stage, and each stage breaks for its own reason. If you hear nothing at all, it's often a knockout question, bad timing or a poor fit. If you get rejected after someone read your CV, the CV didn't show what that job needed. Find the stage first. Then fix that one.
TL;DR
- A bot probably didn't reject you. 23 of 25 recruiters in one survey said their ATS doesn't auto-reject on formatting. A busy human did, in about the time it takes to read this line.
- Tailored CVs got interviews almost twice as often in Huntr's data: 5.71% against 3.09%.
- Applying to one company eight times doesn't wear them down. Your interview rate per application drops from 6.07% to 1.91%.
- "No reply", "rejected on the CV" and "no offer" are three different bugs. Don't try to fix them all in one release.
Blame the robot? Not so fast
Everyone has heard that 75% of CVs get binned by software before a person sees them. I tried to find the study behind that number. Lots of people have. It seems the internet raised it, like most of us.
What we do have: in late 2025, Enhancv asked 25 US recruiters how their systems behave. 23 said their applicant tracking system doesn't reject anyone for formatting, design or content. 25 people, asked by a company that sells CV tools, is not a census. Treat it as a hint. It's a useful hint, though.
Most automatic rejections come from knockout questions. Can you work in this country? Do you live within reach? Do you have the degree? Click "no" and you're out. Nobody opens the lovely CV you attached.
The rest is a queue. The recruiters in the survey described 400 to 600 applicants for an entry-level opening, and more than 2,000 for some tech roles. One called it "first-come, first-served". Another rejects CVs that still name the job the candidate applied for last time. Fair.
So the gatekeeper is mostly a tired person with a long queue and cold coffee. I find that oddly comforting. You can't reason with a regex. A tired person, on the other hand, warms to a clear page that arrives early.
Find the hop where the packets drop
When a trading system gets slow, the person on call doesn't post "the system is slow" in the incident channel. (Well, someone did. Once.) You follow the request until you find the hop where it dies.
A job search is the same kind of pipeline. Most people track only the total ("40 sent, 0 interviews"). That's debugging production from the status page. Write down where each application stopped instead:
- Applied, then nothing. Check the knockouts first: work permit, location, hard requirements. Then check your timing. In a first-come queue, applying on day five is turning up while they stack the chairs. Instant job alerts help with that.
- Read, then rejected. Someone opened your CV and wasn't convinced. That's tailoring; more below.
- Interviewed, then silence. Good news: the CV works. The bottleneck has moved to the interview, and a new font won't fix it. Practice will.
- Offer, then regret. The nicest bug on this list. Negotiate before you sign.
Log 15 to 20 applications and a pattern usually shows. If they all die at step 1, rewriting your summary for the ninth time won't help.
A word on volume. A reader once told Mac's List she had sent 1,884 CVs in four months and got three phone interviews. The article puts that at 0.016%. It's actually 0.16%, so somebody shipped an off-by-ten. (We've all done it. Mine tend to go out on a Friday.) The point survives the bug fix: sending more of the same is load testing, not debugging.
Tailor, don't spam
Huntr, a job-tracking app, published numbers on almost two million applications its users saved. Among those sent with a tailored CV, 5.71% were marked as interviewed. Without one, 3.09%.
To be fair to the data, that's a correlation. Huntr says the gap shrinks when you compare the same people's applications with each other. People who bother to tailor may also be pickier about where they apply. My bet is that both effects are real. (I used to be a trader. I'll bet on most things. I just size the bet.)
Their Q1 2026 report shows what happens with the opposite habit. One application at a company: 6.07% got an interview. Eight or more: 1.91%. Hitting the same endpoint with the same request never turned a 400 into a 200. Changing the request might.
Tailoring isn't pasting the job ad into your CV in white text (people have tried). It's smaller and more boring than that:
- Put what this job cares about at the top. That's where a skimming reader looks first.
- Borrow their word when it describes what you did. If you managed stakeholders, call it stakeholder management.
- Add the facts you left out. How big was the team? Which number moved? You knew. The page didn't.
And don't invent anything. The interview is the integration test, and it runs in production.
What we built for this
We kept seeing the same thing: good people, generic CVs, silence. So we added two things to the SlashHash chat.
The first is Tailor my CV. Open a job, tap the button, and it reads the job next to your CV. It shows what the job asks for and what your CV doesn't show yet. Then it suggests rewrites of your own sentences, and you accept, edit or skip each one.
When a fact is missing, it asks instead of guessing: "Have you built dashboards or reports? With which tools?" Only your answer goes in, in your words. If you haven't done it, there's a button that says exactly that, and it moves on. If your CV and the job barely overlap, it tells you so and offers to talk about your fit instead. No amount of rewording turns a backend developer into a nurse, and we'd rather not try. Your main CV stays as it is. The tailored version is saved for that one job.
The second is coaching. Slash, our assistant, keeps an eye on your saved jobs and suggests the next useful step for each:
- Before you apply, Discuss my fit puts your CV next to the role: strengths, gaps, what to prepare.
- Before an interview, a practice round: technical, HR, manager or a mix. Five questions, feedback on each answer, and a strong example answer when you're stuck. A rubber duck that talks back.
- After a rejection, a debrief. Rejected on the CV, after an interview or after the final round are different problems with different fixes. It also helps you write that short note asking for feedback, the one everyone means to send.
- After an offer, negotiation prep, including a role-play of the call. Your first "that's lower than I expected" goes better rehearsed with a chatbot than live with your future manager.
Neither tool can make a job fit you when it doesn't. What they can do is show you the stage where you keep losing.
FAQ
Why am I not getting any job interviews? Find the stage where applications stop. Silence often means a knockout question (work permit, location, a required degree), late timing or a poor fit. A rejection after review means the CV doesn't show what this job needs.
Do applicant tracking systems reject most CVs automatically? Probably not. In Enhancv's survey of 25 US recruiters, 92% said their system doesn't auto-reject on formatting, design or content. Knockout questions are the main automatic filter.
Does tailoring my CV really help? In Huntr's data, 5.71% of applications with a tailored CV were marked interviewed, against 3.09% without. It's an association, not proof, but the direction holds across their reports.
How many applications before I change my approach? Track 15 to 20 applications with the stage each one reached. If they all stop at the same stage, fix that stage before you send more.
Should I apply to many jobs at the same company? Be selective. Huntr found the interview rate per application falls from 6.07% for one application at a company to 1.91% for eight or more.
Your move this week
- Open a spreadsheet. List your last 20 applications and where each one stopped: silence, CV rejection, interview or offer.
- Fix only the worst stage. Silence? Check the knockouts and apply within a few days of the posting. CV rejections? Tailor for three roles you'd actually take.
- Say your answers out loud, once. Do an interview practice round before the real interview, not after it. For the Dutch quirks, read our guide to Dutch job interviews.
New to all this? Start with how to write a Dutch tech CV, then see how a job matching algorithm reads it.
Figures: Enhancv, Does ATS reject resumes?, 25 US recruiters, September–October 2025. Huntr, Job Search Trends Q2 2026 (1,994,555 applications, October 2024–June 2026) and Q1 2026; self-reported, directional. Jenny Foss, 12 Reasons You Didn't Get the Job Interview, Mac's List.