Why do I keep getting rejected for jobs when I'm qualified?

Last updated July 2026 · Written by the HappyHire team

Short answer

In most cases it is one of three things: your CV is not being parsed or found in the employer's database, your experience is written as duties rather than measurable results, or your interview answers are structured for a different cultural norm than the one you are being assessed against. All three are fixable in a few hours of work. Your accent and your English level are almost never the real reason.

First, work out where you are losing

The fix depends entirely on which stage fails, and the stages have completely different causes. Before changing anything, count your last twenty applications.

What is happeningWhere the problem isWhat to fix
Applying a lot, almost no repliesCV and targetingATS parsing, keyword match, and whether you meet the stated bar
Getting first calls, not getting second interviewsHow you tell your storyAnswer structure, evidence, and claiming credit
Reaching final rounds, then losingFit and negotiation signalsCultural read of the room, questions you ask, salary conversation

A rough benchmark for a well-targeted application in a normal market is a 5–15% interview rate. Below about 3% over twenty-plus applications, the problem is the CV or the targeting, and no amount of interview practice will help yet.

Gap one: nobody is reading your CV

This is the most common and the least visible. Your CV parses badly into the employer's system, so you never appear in the recruiter's search. Or it parses fine but describes your experience in words that do not match the advert, so the search still misses you.

There is a specific version of this that hits internationally-trained candidates hardest: the recruiter cannot calibrate your background. They do not know your former employer, they do not know what your degree is equivalent to, and they cannot tell whether your job title means what the same words mean locally. Faced with a CV that requires research and a CV that does not, they pick the one that does not — not out of prejudice, but because they have ninety seconds and forty applications.

The fix is to do the decoding for them, in brackets, on the line itself. Company size and sector after an unfamiliar employer. Stated equivalence after a qualification. The local job title, with yours in brackets. This one change reliably moves reply rates more than anything else on this page.

Gap two: you are describing duties, not results

In many education and work cultures, the correct way to describe your job is to describe your responsibilities. It is accurate, it is modest, and it is what your reference letter would say. In UK, US and Northern European hiring, it reads as if you occupied a role rather than achieved anything in it.

  • Duties version: 'Responsible for the social media channels of the company.'
  • Results version: 'Grew the company's LinkedIn following from 4k to 31k in 14 months, which became the second-largest source of inbound leads.'

Same job. The second version is the one that gets a call. The information in it was always true — it simply was not on the page. Go through every bullet and ask: what changed because I did this, and can I put a number on it? If you genuinely have no number, describe the scale instead — team size, budget, number of markets, volume handled.

Gap three: your answers are structured for a different room

Interviewers in these markets are usually taking notes against a scorecard with named competencies. They are listening for a specific shape: a situation, what you personally did, and what resulted. If your answer describes the context at length and arrives at the outcome late — a completely normal and often more polite structure elsewhere — the interviewer runs out of listening budget before you reach the part they need to write down.

The most costly habit is the collective 'we'. Saying 'we launched', 'we improved', 'the team delivered' is accurate and appropriately modest in a great many cultures. In a scorecard interview, it is unscoreable — the interviewer cannot credit you for something you have attributed to a group. You are not claiming more than your share by saying 'I ran the migration and the team handled rollout'. You are answering the question that was asked.

Rule of thumb: set the scene in one sentence, spend three or four on what you specifically did, and finish with the outcome and a number. Under two minutes.

What is usually not the problem

  • Your accent. Interviewers in these markets work with international colleagues daily. Clarity and pace matter; accent, on its own, does not.
  • Grammatical perfection. Occasional errors are unremarkable. Long, hesitant pauses while you search for a perfect sentence do more damage than the imperfect sentence would have.
  • Not having lived in the country. It is a factor for roles needing local market knowledge and largely irrelevant elsewhere. If you have the right to work, say so plainly on the CV — ambiguity about status costs more than the status itself.

Discrimination is real and it does happen. But it is not the explanation for most rejections, and it is not the useful place to start, because the three gaps above are entirely within your control and produce measurable results within weeks.

What to do this week

  1. Work out which stage you are losing at, using the table above. Fix only that stage.
  2. If it is the CV: run it through a scanner, fix the parsing, add the context brackets, and rewrite your top five bullets as results with numbers.
  3. If it is the interview: record yourself answering 'tell me about a time you solved a difficult problem' and count how many seconds pass before you say 'I'.
  4. Change one thing at a time and give it ten applications before judging it. Changing everything at once tells you nothing about what worked.

Frequently asked questions

Is my accent hurting my job applications?

Very rarely. Interviewers in the UK, US and EU work with international colleagues as a matter of routine. What does hurt is speaking too fast under stress, which happens to everyone and makes any accent harder to follow. Slowing down deliberately fixes far more than accent training would.

Should I mention my visa or work authorisation on my CV?

Yes, in one short line, if you already have the right to work — 'UK work authorisation, no sponsorship required' or similar. Employers assume the worst when it is unstated, and that assumption is more expensive than the fact. If you do need sponsorship, be upfront and target employers who are licensed sponsors rather than spending applications on those who are not.

How many applications should it take to get an interview?

For well-targeted applications where you meet most of the stated requirements, roughly one interview per seven to twenty applications is normal. Consistently worse than one in thirty points at the CV or at applying for roles that are a poor match, not at bad luck.

Is it worth paying for help, or can I fix this myself?

The CV problems on this page are genuinely self-fixable with a checker and a couple of hours. The interview structure problems are harder alone, because the issue is usually something you cannot hear in your own answers — that is what a coach or a recorded mock interview is actually for.

Related answers