How to interview for a job you're not qualified for

Understand which gaps actually matter

Not all requirements carry equal weight. Most postings mix must-haves with nice-to-haves, and the two are rarely labeled clearly. Before the interview, read the posting line by line and sort every requirement into one of three buckets: things you can do now, things you can learn in under 90 days, and things that would take a year or more.

The third bucket is where you need to be honest with yourself. If the role requires a licensed credential you do not hold, a security clearance, or ten years of domain experience and you have two, that gap is structural. You can still interview, but you should go in knowing the odds are long. The first two buckets are where most gaps live, and those are entirely manageable.

• Must-haves are usually in the first three to five bullet points of the requirements section
• Repeated words across the posting signal priority, for example if 'stakeholder communication' appears four times, it matters
• Years of experience requirements are often negotiable, especially at companies that have been posting the same role for more than 30 days

Reframe gaps as learning evidence before you walk in

Interviewers are not looking for perfection. They are looking for evidence that you will not stall when you hit something unfamiliar. Your job before the interview is to collect that evidence and turn it into short, specific stories.

For each gap you identified, find one real example from your past where you learned something comparable from scratch and delivered a result. The skill does not have to match exactly. If the role needs Salesforce experience and you have only used HubSpot, your story is about learning a CRM under pressure, not about Salesforce specifically. The pattern of learning is what transfers.

If you have no past example, create a current one. Spend two to four hours before the interview doing a free tutorial, reading the documentation, or completing one module of a relevant course. You can then say honestly that you started learning it this week. That is not spin. That is evidence of the behavior they are hiring for.

• Use the structure: situation, what you did not know, how you learned it, what you delivered
• Keep each story under 90 seconds when spoken aloud
• Prepare one story per major gap, not one story for all gaps combined

How to address a gap when the interviewer asks directly

The worst thing you can do is deflect or oversell. Interviewers have heard 'I'm a quick learner' hundreds of times without evidence. It registers as noise. What works is a three-part answer: acknowledge the gap plainly, give the evidence that the gap is closeable, and redirect to what you bring that is directly relevant.

A template that works in practice: 'I have not used [tool or skill] in a professional setting yet. What I have done is [specific comparable experience]. I started working through [specific resource] this week and I am already [specific progress]. I am confident I can be productive with it within [realistic timeframe].'

The timeframe you give matters. Be conservative. Saying you will be proficient in two weeks when the realistic answer is two months will surface in your first 90 days and damage trust. Saying six to eight weeks and delivering in four builds it.

Lead with what you do have

Gaps get less attention when the rest of the interview is strong. Spend the majority of your preparation time sharpening your answers on the areas where you are genuinely qualified. If you are strong on three of five requirements, those three should be vivid, specific, and memorable.

Prepare a short positioning statement for the opening question, which is usually some version of 'tell me about yourself.' This statement should cover your relevant experience, one concrete result, and a direct connection to what this role needs. Do not mention your gaps here. You are setting the frame for the rest of the conversation.

A positioning statement for a candidate moving from marketing coordinator to marketing manager with no direct management experience might sound like: 'I have spent three years running campaign operations for a team of eight, coordinating timelines, budgets, and external vendors. Last year I led a product launch that brought in 40 percent of our annual pipeline. I am looking to move into a role where I own the strategy, not just the execution.'

1. Write your positioning statement in under 60 seconds of spoken time
2. Include one specific number or result
3. End with a forward-looking sentence that connects to the role

Handle the salary question when you're underqualified

If you are interviewing above your current level, the salary question can feel like a trap. In the US, Canada, the UK, and Australia, many jurisdictions now require employers to post salary ranges or share them on request. Use that information if it is available.

If the posted range is higher than your current salary, do not volunteer your current number. In many US states and Canadian provinces, employers are prohibited from asking for salary history. In the UK and Australia there is no blanket ban, but you are not obligated to anchor low. Research the market rate for the role using sources like Glassdoor, Levels.fyi for tech roles, or the government's occupational wage data. Give a range that reflects the role, not your history.

If you are genuinely underqualified and the company knows it, some will offer a lower title or a lower point in the band. That is a legitimate negotiation, not a failure. Decide in advance what your floor is and what conditions would make a lower offer acceptable, such as a six-month review clause.

Use an interview assistant to stay sharp under pressure

Even well-prepared candidates go blank when a question lands unexpectedly. Break-In Bad has an invisible on-screen interview assistant that listens to the interviewer's questions and shows suggested answers only you can see, even on a shared screen. It is useful specifically in situations like this one, where you may be asked about a gap you have prepared for but the exact phrasing catches you off guard.

The assistant does not replace preparation. It works best when you have already done the work of identifying your gaps and building your stories, because it helps you retrieve and deliver what you already know rather than improvising from nothing.

After the interview: close the gap visibly

Send a follow-up email within 24 hours. Most candidates send a generic thank-you. Use yours to do one specific thing: reference a gap that came up and show one concrete step you have taken since the conversation ended. If they asked about a tool you do not know, mention that you completed the introductory module that evening and link to a certificate or screenshot if one exists.

This is not about impressing them with speed. It is about demonstrating the exact behavior they are evaluating: what do you do when you hit something you do not know? You just showed them.