Why Am I Applying for Jobs But Not Getting Interviews?
You've applied for 40, 50, maybe 60 jobs.
You're qualified for them. In some cases, you know you could do the job standing on your head.
But you're barely getting interviews.
So you start wondering what's wrong with you.
Maybe you're too old. Too senior. Too expensive. Perhaps your experience isn't as valuable as you thought it was. Maybe the job market has simply decided it doesn't want you anymore.
Before you decide any of that, I want you to look at the process.
Because the first thing I'd want to know isn't how many jobs you've applied for.
It's what happened to those applications.
60 applications doesn't tell me very much If you told me you'd made 60 applications, I'd want to split them into different outcomes.
How many were:
rejected quickly?
rejected after someone had apparently reviewed them?
completely ghosted?
followed by contact from a recruiter?
followed by a recruiter screening call?
submitted to the hiring manager?
converted into an interview?
Those numbers tell me far more than “I've applied for 60 jobs.”
I use roughly three weeks without contact as a diagnostic yardstick for ghosting.
Recruitment is messy. I've worked with people who applied for a role in May and suddenly got contacted about it in September.
But we need a consistent point at which we can look at your job search and say: that application didn't convert. Three weeks gives us something useful to work with.
And once we have that data, we can start looking for patterns.
If you're being rejected very quickly
A very fast rejection can sometimes happen before anybody has properly considered your CV.
Employers can use application questions and screening criteria around things such as right to work, location, salary expectations or other essential requirements.
If you're repeatedly receiving very fast rejections, I'd start there.
What questions are you answering?
Is there a mandatory requirement you don't meet?
Are your salary expectations outside the range they're working with?
Is your location creating an issue?
Don't immediately conclude:
“They've read my CV and decided I'm not good enough.”
That might not be what happened at all.
If most of your applications disappear into a black hole
This is where I become interested in a different part of the process.
If you've made 60 applications and 49 of them have disappeared without any human contact, I don't interpret that as 49 recruiters personally deciding they don't want you.
I'd start investigating whether enough people are seeing and understanding your application in the first place.
And that means we need to talk about applicant tracking systems.
What ATSs actually do — without the internet nonsense
There is an extraordinary amount of nonsense online about applicant tracking systems.
So let's be precise.
There isn't one universal ATS that every employer uses in exactly the same way.
Different systems have different capabilities. Employers buy different functionality. Systems are configured differently. Recruiters use them differently. And the recruiter you're speaking to may not even know every feature their organisation has enabled.
But that doesn't mean ATS technology is just an electronic filing cabinet.
Workday, for example, documents a configurable Candidate Skills Match feature that compares skills derived from a candidate's application and CV with skills associated with the job requisition. Workday says required skills can be given greater weight and applications can receive match scores such as Strong, Good, Fair or Low. Workday Documentation
Workday also says its recruitment technology can derive information from across a CV — including experience, company, education, qualifications and skills — rather than simply looking at a little “Skills” section. Workday Documentation
And Workday itself uses AI in its own recruitment process to extract information including skills, experience, location and education, assess how closely an application aligns with a role and provide suggested grades that help its recruiters shortlist and prioritise applications. Workday
Greenhouse offers different functionality. Its Talent Filtering feature allows recruiters dealing with large numbers of applications to search CVs using things such as job titles, skills and locations, and to specify required and preferred keywords. Greenhouse
So when somebody tells you:
“ATSs don't do that.”
The sensible answer is:
Their ATS may not do that. Their organisation may not have configured it to do that. Their recruiters may not use that functionality.
But major recruitment systems demonstrably can parse, search, filter, compare and, in some configurations, score or prioritise candidate information.
As a candidate, you don't know exactly what is waiting behind the Apply button.
So I don't teach people to “beat the ATS”.
I teach them to build a CV that gives them the best chance of being understood whether the next gate is software, a recruitment person or a hiring manager.
And yes, your beautiful Canva CV may be causing problems
This is another area where I don't want to make blanket claims.
A PDF isn't automatically ATS-unfriendly. Workday, for example, lists PDF among the file formats it can process. Greenhouse accepts PDF, DOC, DOCX, RTF and TXT. Workday Documentation
But design and structure can matter.
Workday's own administrator documentation says resume-parsing results can vary depending on the format and order of words and specifically recommends resumes without images or image-based styles for best results. Workday Documentation
Greenhouse acknowledges that resumes sometimes fail to import correctly because of file type, insufficient information or characters its parsing technology doesn't recognise. Greenhouse Support
So I am not going to tell you that every CV made in Canva, InDesign or another design package will fail.
I'm going to ask a much simpler question:
Why take the risk?
For most corporate job applications, your CV isn't a graphic-design competition.
Make it clear. Make it readable. Make the structure straightforward. Make the important information easy for both technology and humans to find.
Your CV has to get through three gates
I think about the process in three broad stages.
Gate 1: The application process and technology
Can the system process your document? Do you meet the mandatory criteria? Is the relevant information there? Can your skills and experience be found?
Gate 2: The recruitment person
Can a busy recruiter quickly understand what you do, your level and why you make sense for this vacancy?
Gate 3: The hiring manager
Is there enough evidence, scale, context and credibility to make them want to meet you?
A CV that works brilliantly for Gate 3 but never gets through Gates 1 and 2 isn't a successful CV.
“But my CV is really good”
I'm sure it might be.
But who told you it was good?
Often, when someone tells me everybody loves their CV, the people they've shown it to are friends, colleagues or hiring managers.
They're reading it with a cup of tea.
They're interested in you. They know your profession. They may know the companies you've worked for. They're prepared to spend time understanding it.
That's not necessarily how your CV is being encountered during recruitment.
A recruitment person may be moving quickly through a very large number of applications.
And they're often a generalist.
One day they're recruiting somebody in HR. The next it's marketing. Then IT.
They don't necessarily understand the deep technical detail of your profession.
Don't make them work you out.
Positioning matters because being capable isn't enough
Let's say you meet 80–90% of the requirements.
That's pretty good.
But you're competing against other people who may also be capable of doing the job.
The recruiter isn't sitting there thinking:
Let me investigate this person's entire career and see whether I can find a clever reason they might fit.
They need to recognise the fit quickly.
That means using language they recognise.
If the vacancy says stakeholder management and your CV describes the same experience as managing internal clients, ask yourself why you're making somebody translate it.
If you've worked for a company nobody is likely to recognise, explain briefly what the company does.
If your official job title was:
Director of Enterprise Enablement
but the role was effectively equivalent to a Head of Business Transformation position, don't falsify your job title.
Translate it.
For example:
Director of Enterprise Enablement (Head of Business Transformation)
Or make the equivalent scope immediately clear underneath.
Your official title remains there for referencing.
But the recruiter doesn't have to conduct an investigation to understand what you actually did.
Your company name and job title don't prove very much
This becomes particularly important with experienced professionals.
Take:
Marketing Manager — Coca-Cola
It sounds impressive.
But what does it actually tell me?
One brand or several?
One country or 20?
A £100,000 budget or £10 million?
Did you manage nobody or a team of 30?
Were you responsible for a small part of one product line or something enormous?
That's why I look for metrics, scale and context.
And metrics don't have to mean:
“I saved the company £27 million.”
Useful metrics might be:
number of people in your team
number of markets or countries
size of budget
number of customers
number of sites
size of programme
number of stakeholders
volume of transactions
percentage improvement
timescale
size of portfolio
Don't just tell me what you did.
Help me understand how big the job was.
Applying directly and using recruitment agencies are not the same thing
This distinction gets lost in a lot of job-search advice.
Applying through an employer's recruitment process and building a relationship with an agency recruiter are different routes into the market.
Recruitment businesses can and do use sophisticated recruitment databases and ATS/CRM technology too.
But the relationship matters enormously.
An agency recruiter needs to understand where they can place you and why a client should meet you.
If your positioning is fuzzy, making them decipher it isn't going to help.
That's why I don't believe registering with an agency six months ago means:
“They've got my CV. They'll call me if anything suitable comes up.”
You need to remain visible, relevant and understandable.
If recruiters call you but you still don't get interviews
This is where we need another split in the data.
Who said no?
Did the recruitment person screen you and decide not to progress you?
Or did they put you forward and the hiring manager reject your CV?
Those are different problems.
If you're regularly having recruiter screening calls but aren't being submitted, I'd look at what is happening during those conversations.
Are you giving clear answers?
Does your story make sense?
Is the recruiter uncovering something that makes you less suitable than they initially thought?
If recruiters are submitting you but hiring managers aren't interviewing you, I'd look differently.
Is there enough technical evidence?
Enough scale?
Enough relevant detail?
Are other candidates simply presenting stronger evidence of the experience the manager wants?
Ask your recruiter for feedback.
“Rejected” isn't enough information. Find out where the rejection happened.
Changing sector makes this harder
This is particularly difficult in the current market.
You may be absolutely right when you say:
“Transformation is transformation. My skills are transferable.”
But recruitment isn't only about whether you could do the job.
It's also about perceived risk.
Imagine a recruiter has hundreds of applications and several candidates already have:
the right job title + the right level + the same sector + similar company experience.
Then they reach your CV.
You might be brilliant.
But you're asking them to make another leap.
If you're moving from retail into automotive, don't simply declare your experience transferable.
Demonstrate why it is transferable.
Make the similarities obvious.
Address the apparent risk.
A cover letter can sometimes help. So can a referral, your network or approaching the hiring manager directly.
Because sometimes your challenge isn't capability.
It's getting through a gate where you're not the obvious choice.
More experience can actually make you look riskier
This is another place where people can jump to the wrong diagnosis.
I've worked with experienced professionals who assume:
“I'm over 50 and I'm being rejected. It must be my age.”
Age discrimination exists. I'm not dismissing it.
But before deciding that's what's happening, look at the data.
Are people actually seeing your CV?
Are you being ghosted?
Are you passing the initial stages?
Is your positioning right?
If most applications are disappearing without meaningful human contact, don't immediately assume dozens of recruiters have looked at your age and rejected you.
And there's another issue.
Having more experience doesn't automatically make you safer.
If you've been a Director and you're applying for a Head of role, the employer may wonder:
Why?
You might have an entirely sensible answer.
Perhaps you don't want the global travel anymore. You want less responsibility. You want to be closer to delivery. Your priorities have changed.
But they don't know that.
They may be wondering whether you'll leave when another Director role appears, whether you'll be happy reporting to somebody with less experience, whether you'll get bored or whether your salary expectations will fit.
Don't leave them to invent the explanation.
Applying for jobs is not a numbers game
This is one of the biggest mistakes I see.
Someone applies for 60 jobs and gets almost nothing back.
So they decide:
I'll apply for 100 next month.
Why?
If you repeat exactly the same process, why would you expect a completely different outcome?
You're not improving your job search.
You're simply repeating the same mistakes more often.
And what usually happens next is that the quality of the jobs deteriorates.
Your first 20 might have been genuinely good opportunities.
By application 80, you're applying for things because you could probably do them.
Then comes exhaustion.
Then frustration.
Then confidence starts disappearing.
Because 100 applications with almost nothing back starts to feel very personal.
Don't increase the volume. Diagnose the process.
Not every job you could do is a job you should apply for
This works in both directions.
Yes, the employer needs to think you're a good fit.
But you should be assessing whether they're a good fit for you too.
Inside the Job Search Sprint, I use decision criteria and a Role Fit Scorecard to take some of the emotion out of this.
Before somebody spends time on an application, I want them thinking about things such as:
target role
salary
location
flexibility
sector
organisation
non-negotiables
personal priorities
potential red flags
A job advert won't tell you everything.
Job descriptions are often pretty crap descriptions of the actual job.
But you can still ask:
Is there enough here to justify spending my time pursuing this opportunity?
Not every role needs to be perfect.
But every application should have a reason.
Then make the good applications better
Suppose you've found 45 genuinely worthwhile opportunities rather than 60 vaguely possible ones.
Now spend your time improving those 45.
Tailor properly.
Look at your network.
Can somebody refer you?
Who might the hiring manager be?
Who already works there?
Can you connect with relevant people?
Is there information about what's happening inside the organisation that helps you understand why they're hiring?
The more you know, the better.
But don't become so clever about guessing what the hiring manager secretly wants that you forget the basics.
First, demonstrate what they've explicitly asked for.
That's what helps you through those first gates.
Then use your deeper research, evidence and understanding to make the application more compelling to the hiring manager.
Use AI to make a good job search faster — not a bad one bigger
AI has made it possible to do an enormous amount of this work faster.
But that doesn't mean:
Paste job description into ChatGPT → ask it to write CV → Apply.
That's not a job-search strategy.
AI can help you research companies, analyse vacancies, compare terminology, assess opportunities, interrogate your evidence and speed up good tailoring.
Used properly, it gives you more time to do the human things that matter.
The goal isn't more applications because AI makes more applications possible.
It's better applications, faster.
What I'd do tomorrow morning
If your job search isn't converting, don't begin tomorrow by opening LinkedIn and applying for another ten jobs.
Do this instead.
1. Diagnose what's happening.
Look at your existing applications. Separate rejections, ghosting, recruiter contact, submissions and interviews. Find where the conversion is breaking.
2. Start tracking properly.
Stop using number of applications as your main measure of progress.
3. Reset the search itself.
Make sure you're actually finding the right roles. Use better search terms and Boolean searches rather than relying entirely on whatever an algorithm decides to show you.
4. Decide whether a role is worth pursuing before tailoring for it.
Being capable of doing a job isn't enough reason to apply.
5. Strengthen your master CV.
Go through it sentence by sentence. Add scale, scope, context and metrics wherever you reasonably can.
6. Match the language of the vacancy .
Go through the requirements carefully. If their terminology accurately describes your experience, use it. Don't make technology or recruiters translate your language into theirs.
7. Check your positioning.
Could somebody unfamiliar with you understand quickly what you do, your level and why you're relevant? Are unusual titles explained? Are dates and locations clear? Are your phone number and email correct and easy to find?
8. Don't rely solely on the Apply button.
Look at your network. Look for possible referrals. Identify relevant people. Where appropriate, connect with the likely hiring manager.
And then see what happens to your conversion.
Because the answer to a broken job-search process isn't more of the same process.
It's finding the part that's broken and fixing it.
Still not sure where your job search is breaking?
That's exactly why I created the Job Search Reset Workshop.
Rather than telling you to apply for more jobs, we'll look at what's actually happening across your search and help you identify where you're losing traction — so you know what to change next.
Comments