Your CV isn't being rejected. It isn't being read.

Forty applications. Two acknowledgements, both automated. No interviews.

At that point almost everyone reaches the same conclusion: I'm not good enough for these roles. It's a miserable place to be and it's usually wrong.

Most applications that go nowhere never reached a person. They were filtered by software, for reasons that have nothing to do with whether you could do the job. That's a formatting problem being experienced as a self-worth problem — and the two feel identical from the inside.

What actually happens when you hit submit

Your file lands in an applicant tracking system. Before any human is involved, the ATS attempts to convert your document into structured data — name, contact, employers, dates, titles, skills, education.

It reads top to bottom, left to right, and it expects a fairly conventional shape. When it can't confidently map a section, it doesn't flag it for review. It stores whatever it managed to extract and moves on.

A recruiter then filters that structured data. If your five years of relevant experience got mangled into an unreadable blob, you are not in the filtered set. Nobody rejected you. You simply weren't there.

The four things that break it

1. Two-column layouts

This is the big one, and it's painful because those templates look the most professional.

A parser reading left to right across a two-column page can interleave the columns — your sidebar skills list threaded into the middle of your job descriptions. The result is text that means nothing. The visual design that made it attractive to a human is precisely what destroyed it for the machine.

2. Text inside graphics

Skill ratings as bar charts. Your name inside a logo. A header saved as an image. Icons replacing the words "phone" and "email". To a parser, an image contains nothing. If your contact details are in a graphic, you may be unreachable even after passing every other filter.

3. Headers, footers and text boxes

Many parsers ignore header and footer regions entirely, and text boxes are frequently skipped. Contact details in the header is one of the most common ways a good CV becomes uncontactable.

4. Creative section names

"My Journey" instead of Experience. "What I Bring" instead of Skills. "Where I've Been" instead of Employment History. The parser looks for conventional headings. Creative ones don't map, and the content beneath them may be dropped.

The keyword problem — and the honest version of it

Recruiters filter by keyword. If a role requires "PPM scheduling" and your CV says "planned maintenance", you may not appear in that search — even though you've done exactly the work.

The fix is simple: use the job description's vocabulary for things you have genuinely done. If they say CAFM and you've used CAFM, write CAFM. If they say stakeholder management and that's what you did, use their phrase rather than your own.

Now the part most advice skips. Keyword stuffing — pasting the job description in white text, listing skills you don't have — is a bad strategy for a boring reason: it works exactly long enough to get you into an interview you cannot survive. You'll spend forty-five minutes being asked about a system you've never opened. Optimise to be found for what's true, not to be found for everything.

The first third of the page

Clear the parser and a human takes over — for roughly six to eight seconds on the first pass. That decision is made almost entirely in the top third of page one.

Which means the top third cannot be a generic objective statement. "Seeking a challenging role in a reputed organisation where I can utilise my skills" tells a reader nothing and costs you the only real estate that matters.

What belongs there instead:

• Who you are, in the role's language. If the ad says Facilities Manager, the line under your name should say Facilities Manager.
• Scale. Years, portfolio size, team size, budget, whatever quantifies the level you operate at.
• Two or three outcomes with numbers. Not responsibilities. Outcomes.
• Anything gating. Visa status, notice period, certifications the role requires. Answer it before it's asked.

Responsibilities versus outcomes

Most CVs describe the job. Strong ones describe what changed because you held it.

Responsibility (weak)	Outcome (strong)
Responsible for preventive maintenance scheduling	Rebuilt the PPM schedule across 340 assets; overdue work orders fell from 22% to 4% in two quarters
Handled vendor management	Renegotiated 6 service contracts at renewal, cutting annual spend by 11% with no reduction in scope
Managed a team of technicians	Led 14 technicians across 3 towers; first-time fix rate improved from 61% to 84%

Two objections come up here, and both have answers.

"I don't have numbers." You have more than you think. How many sites, units, people, tickets, square feet? How long did something take before versus after? Even approximate figures, honestly framed, beat no figures.

"My work wasn't measurable." Then measure the scope instead of the result. "Sole point of contact for 180 residential units" is a number, and it tells a reader the level you operate at.

A checklist worth an hour

1. Convert to a single column. Everything else is secondary to this.
2. Move contact details out of the header into the body.
3. Replace every graphic containing text with actual text.
4. Rename sections conventionally: Experience, Education, Skills, Certifications.
5. Rewrite the top third for the specific role.
6. Convert your three strongest bullets from responsibility to outcome.
7. Mirror the job description's exact terms for things you've genuinely done.
8. Save as .docx unless the posting specifically asks for PDF.
9. Test it: copy the entire text out of your CV and paste it into a plain notepad. If it reads as coherent, ordered text, a parser can read it. If it's scrambled, that's what the ATS receives.

That last step takes thirty seconds and is the single most informative thing you can do. Most people have never tried it.

The point

None of this makes an unqualified person qualified, and it shouldn't. What it does is stop qualified people from being invisible.

If you've been applying steadily and hearing nothing, run the Notepad test before you conclude anything about yourself. The failure is far more often mechanical than personal — and mechanical problems are the good kind, because they're fixable in an afternoon.