How to answer interview questions about a requirement you don't meet

Prepare for two or three gaps, not all of them

Before the interview, list the posting's requirements and mark each one honestly: met, partial, or missing. Then decide which gaps to prepare for with a simple order.

1. Missing, under the main requirements heading. These are the ones an interviewer is most likely to raise, because someone wrote them down as needed.
2. Partial, where your resume makes it look missing. If you have the experience but it is buried in one bullet, the interviewer may still ask. Prepare to show it.
3. Missing, under "nice to have". Skip these unless you have spare time. If one comes up, a short honest answer is enough.

Stop at two or three. If you rehearse eight gaps, you will be tempted to bring them up unprompted, so don't. Outside the hard blockers covered below, never raise a gap the interviewer did not ask about. Your job in prep is to make sure the answer is ready, not to confess it.

The three-part answer

Every good gap answer has the same shape, and it should take under a minute to say.

1. Name the gap in one sentence. Plainly, without apology. "I haven't run Kafka in production." Dodging the question makes the interviewer ask it again, and the second time it sounds worse.
2. Give the closest real evidence. Something you actually did that overlaps with what the requirement is really testing. Include a concrete detail: the system, the team size, what broke, what you shipped. This is the part that does the work.
3. Say how you would close it. One or two sentences on what you would do in your first weeks, or what you have already started. Specific beats eager.

The middle part matters most because a requirement is usually standing in for something underneath it. "Production Kafka experience" often means "has operated an event pipeline that other teams depend on". If you have done that with a different tool, say so and say what it involved.

Three worked answers

These follow the three-part shape. They are examples, so swap in your own real details; never borrow a detail you can't back up in a follow-up question.

A tool gap. The posting asks for production Kafka experience. You have used a different message queue.

I haven't run Kafka in production. What I have run is our RabbitMQ setup for order events at my last job: I owned the consumers, handled a backlog incident during a sale when a downstream service went down, and added the dead-letter handling we used afterwards. The concepts I'd need to learn for Kafka are partitions and consumer groups, and I've started on that with a local cluster this month.

A domain gap. A payments company wants fintech experience. You have built checkout flows in e-commerce.

I haven't worked at a payments company. I've worked next to one: I designed our checkout and the refund flow, so I've dealt with failed charges, partial refunds and the support tickets they create. What I'd need to learn here is the compliance side, so in my first weeks I'd want to sit with whoever owns disputes and see where the product causes them.

A years gap. The posting says seven years and you have five.

I have five years, not seven. In the last two I led the design system rebuild, which meant setting the review process for four product teams, not just my own work. I think that's what the seven years is asking for, and I'm happy to walk through how it went.

Notice what the years answer does: it names the number, then points at the responsibility the number stands for. Arguing that years don't matter rarely persuades anyone who wrote the requirement.

Phrasings that make a gap sound bigger

Most bad gap answers fail the same few ways. Check your prepared answer against this list.

• Only "I'm a fast learner". Most candidates say it. Replace it with a time you learned something similar under a deadline, and what you shipped.
• Over-apologizing. "I'm so sorry, I know that's a big part of the role" tells the interviewer how to score you. State the gap once and move to the evidence.
• Claiming the adjacent thing is the same thing. "RabbitMQ is basically Kafka" invites a technical follow-up you will lose. Say what transfers and what doesn't.
• Hypotheticals instead of history. "I would probably approach it by..." is weaker than "Last year I...". Use the hypothetical only for the closing part.
• A long run-up. If the first thirty seconds are context, the interviewer is still waiting for the answer. Lead with the one-sentence admission.

When the gap is a real blocker

Some requirements can't be answered with framing: work authorization, a required license or certification, a security clearance, or an on-site location you can't move to. No interview answer changes these.

Use a simple rule. If the requirement is a condition no answer can change and you don't meet it, raise it with the recruiter before you spend time preparing, in one line:

Before we go further, I want to check one thing: the posting lists [requirement]. I [your actual situation]. Is that a hard requirement for this role?

Sometimes the answer is that it's flexible, and you have saved yourself an awkward moment in a later round. Sometimes it isn't, and you have saved a week of preparation for a role you couldn't take.

Finding your gaps with Lamr

If you track applications in Lamr, most of the gap list is already written. Fit screening (1 credit) grades the posting's main requirements as met, partial or missing, weights each as critical, important or nice, and shows a short evidence note for each. That breakdown is the list from the first section: start with critical items marked missing.

If you tailored your resume for the role, Lamr also recorded the gaps it found. Interview prep (2 credits) uses those gaps, along with the posting, your master resume and profile, to suggest 8 to 10 likely questions, each with why it is likely and a suggested angle from your real experience, plus a notes field per question where you can draft the three-part answer. An application that was only screened has no gaps for prep to draw on, so tailor first if you want gap questions in the list.

The angles are a starting point. Rewrite them in your own words with the details only you know, then say them out loud until they fit in a minute. See how tailoring and fit scoring work or how Lamr tracks each application.