When You Don't Meet One of the Requirements

You match most of a posting and fail one line of it. The question is whether to mention the gap or hope it goes unnoticed, and the answer depends on whether the reader will notice — which, for anything on your resume, they will.

Name it if it’s visible, name it once, and spend more words on what you’d do about it than on the fact of it.

First, work out which kind of gap it is

Requirement lists are not uniform. Three different things hide in them.

Hard gates. A licence, a certification, a legal right to work, a security clearance, a degree in a regulated profession. These are usually genuinely binary and there’s no letter that argues past them. If the posting says the role requires a licence you don’t hold, the letter can’t help, and applying anyway is mostly a donation of your own time.

Proxies. “Five years of experience,” “a degree in a relevant field,” “experience in the insurance sector.” These stand in for a capability rather than being the capability. They’re negotiable in principle, because what the employer wants is the underlying thing.

Wishes. Everything in the bottom third of a long list, and anything under “nice to have.” Frequently added in a meeting by someone who won’t interview you. Missing several of these is normal and usually not worth a sentence.

Most applicant anxiety is spent on wishes. Most letters that fail on a gap fail on a proxy they didn’t address.

The proxy is the one to answer

A proxy gap is where a letter can genuinely change an outcome, because you can supply the underlying evidence the proxy was standing in for.

Years of experience. The proxy is for having seen enough situations. Answer with situations.

The posting asks for five years and I have three. What I’d offer instead of the two years is that all three were at a company with no other analyst, so I’ve owned the full cycle — collection, modelling, and the weekly conversation where someone disputes the number — rather than one slice of it.

A named tool. The proxy is for being able to work in that class of tool. Answer with the adjacent one and a real assessment of the transfer.

I’ve not used Looker. I’ve built and maintained about forty dashboards in Tableau and written the SQL underneath them, and I’d expect the modelling layer to be the part that takes real learning rather than the interface. I’d rather flag that than have it surface in a screening call.

Sector experience. The proxy is for understanding the domain’s constraints. Answer with whichever constraints you do understand.

I’ve not worked in insurance. I have spent four years in a regulated environment where every number had a defined source and an audit trail, which I gather is most of what makes the reporting slow here. The domain vocabulary I’d have to learn.

Note the pattern in all three: concede plainly, substitute specifically, assess honestly. The third part — saying which bit would actually be hard — is what makes the first two credible.

How to phrase the concession

Don’t apologise. Unfortunately I lack direct experience with… invites agreement. I’ve not used Looker is a fact.

Don’t pad. One clause, then move. A paragraph about the gap is a paragraph about your weakest attribute.

Don’t claim it’s equivalent. Tableau is essentially the same as Looker will be read by someone who knows both, and the claim is doing you less good than the honest comparison.

Don’t hedge into meaninglessness. I am a fast learner and confident I could pick it up quickly is what everyone writes. Replace it with the specific reason you think the transfer is tractable, or cut it.

Don’t lead with it. The opening sentence should be your strongest match, not your weakest. Put the gap in the middle — after the evidence has established that you’re worth reading — unless the gap is the whole story, as with a career change.

When to say nothing

Silence is right more often than the anxious reader thinks.

Wishes at the bottom of the list. Missing three of eight “nice to haves” doesn’t need a sentence, and volunteering it draws attention to a shortfall the reader may not have been counting.

Anything not visible on your resume. If the gap isn’t apparent from the record, mentioning it is a pure cost. This is a genuine judgement call and it isn’t dishonesty — you’re under no obligation to audit yourself against their list in writing. Lying if asked directly is different and not on the table.

Gaps that a single line elsewhere already answers. If the posting wants a tool and your resume lists it under a project, the letter doesn’t need to defend it.

The rule of thumb: name a gap when the reader can already see it, because then the choice is between your account of it and their guess. Otherwise write about what you have.

The version that works better than any argument

If the missing item is something you could plausibly have started already, having started is worth more than any sentence about willingness.

Not a certificate — a thing you made. Two evenings in the tool, a small working artefact, and one sentence about what surprised you:

I’ve been working through Looker on a personal instance for a couple of weeks, mostly to see how different the modelling layer is. It’s more different than I expected, which is the useful thing to have found out before an interview rather than after.

That sentence can’t be written by someone who hasn’t done it, which is exactly why it lands.

Multiple gaps

If you’re missing several proxies at once, the letter has a harder job and probably shouldn’t try to answer them individually — a letter that concedes four times reads as a list of reasons not to hire you.

Instead, make one strong positive case and one general statement about the shape of the difference:

I’m coming at this from a different direction than the posting describes: not agency-side, no insurance background, no Looker. What I have is four years of owning a regulated reporting stack end to end. If the role is mostly about that ownership, I’m worth a conversation; if it’s mostly about sector fluency, I’m probably not the right person and no letter would change that.

That last clause is unusual and it works, because it demonstrates the judgement to know when you’re not the answer. It’s also the honest position, and a reader who’s been sent forty letters claiming perfect fit will notice.

The underlying point

A gap named well becomes evidence of self-assessment, which is a quality employers have no other way to test from an application.

A gap hidden badly becomes a surprise in a screening call, where it costs more. And a gap padded with fast learner boilerplate is just a wasted paragraph. The move is the same one that works everywhere in this document: replace the claim with the specific — see the paragraph that shows judgement for why that substitution does so much work.