OfferDrill.

Interview questions

The hard ones

How to interview for a job you're underqualified for.

You're missing one or two things the posting asked for, and they called you anyway. This page shows you how to name the gap in one clean sentence, back it with the closest true thing you've actually done, and spend the rest of the hour on the part of the job you can already do.

Why they ask it

First, understand what happened. Postings are wish lists. Hiring managers write them with everything they'd love, then interview the people who come close. If you're in the room, someone already decided the gap was worth a conversation. You are not sneaking in.

So when they ask about the thing you're missing — and they will, usually as "I see you haven't worked with X" or "walk me through your experience with Y" — they're not trying to catch you. They're trying to price the risk. How long until you're useful? How much hand-holding? And the quieter one: does this person know what they don't know?

That last part is most of the test. People who oversell a gap become people who hide mistakes later. People who name it flatly and have a plan look like people who'll say "I need help with this" on a Tuesday in March instead of blowing a deadline. Your honesty about the gap is evidence about your character, and they're reading it that way.

What not to say

"I'm a fast learner."

Every single candidate says it, including the ones who aren't. It's a claim with no proof attached, so it registers as nothing. Replace it with a time you actually learned something hard on the job: what you didn't know, how long it took, and what you could do at the end.

Leading with the apology. "I know I don't have the five years, and I'm probably not what you're looking for, but..."

You just made the gap the headline of the interview and told them not to hire you. They'll believe you. Say what you're missing once, in a plain sentence, in the middle of your answer — not at the front, and not with an apology wrapped around it.

Stretching. Saying you've "worked with" something you read about, or letting a small project sound like a job.

It falls apart on the second follow-up question, and when it falls apart you lose the whole interview, not just that question. It's also the one thing they can't un-hear. A truthful "I haven't used it" survives; a caught exaggeration doesn't.

Waving the requirement off. "Honestly, that tool is pretty easy, I could pick it up in a weekend."

You just told a room full of people who use that tool every day that their work is trivial. Even if it's a fair guess, you don't know their setup. Respect the thing, then show them your plan for learning it.

Going quiet and letting them fill the silence.

A long pause after "you haven't done this" reads as agreement. Have a prepared sentence — not a script, a sentence — so you're never caught flat-footed on the one question you knew was coming.

How to build a strong answer

  1. Map the gap before you walk in.
    Print the posting. Go line by line and mark each requirement one of three ways: I've done this, I've done the neighbor of this, I've never touched this. Most people walk in thinking they're missing four things and find out they're missing one. Knowing exactly which one is what lets you stop feeling generally unqualified and start answering one specific question.
  2. Find the nearest true thing.
    For each real gap, name the closest work you've actually done. Different CRM, same job. Managed three people, not eleven. Built the report by hand instead of with the tool they use. Ran the project without the certification. This is not spin — it's the honest answer to "how far is the jump?" and it's the number they're trying to figure out. Be ready with one concrete story, not a category.
  3. Answer in three beats, then stop.
    Beat one: name the gap plainly, in under ten words. "I haven't used [the tool]." Beat two: the nearest true thing, with a detail that proves it's real. Beat three: how you'd close it, with a specific action and a rough timeline you actually believe. Then stop talking. The stopping matters as much as the words. If you keep going, you'll drift back into apologizing.
  4. Bring proof if you have time, but only real proof.
    If the interview is days out, you can make one of these true before you sit down: finish the free intro course, build a small thing, read the documentation, talk to someone who uses it. Then you get to say "I started the [course] last week and I'm through [where you actually are]." Small, verifiable, and it shows you move. Don't claim a course you haven't opened.
  5. Spend the rest of the hour on the eighty percent.
    One gap does not deserve half your air time. For every other question, answer from the parts of the job you've genuinely done, with specifics — numbers, dates, outcomes. They hire on the whole picture. Someone who's strong on four things and learning one beats someone who's mediocre at five, and interviewers know it.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career, missing a specific tool or system the posting named.

"I haven't used [the tool] directly. I spent [number] years running the same work in [the system you actually used] — I owned [the specific thing, like the monthly pipeline reporting] for a team of [the actual size], so I know what the job needs the tool to do, which is usually the harder half. When we switched from [old system] to [the one you learned], I was up and running in about [the real timeframe] and ended up writing the how-to doc for the rest of the team. I've started [whatever you've actually started, or cut this sentence]. My honest guess is I'd need a few weeks of real use before I'd be fast in it, and I'd rather tell you that now than surprise you in month two."

The gap is named in the first six words and never mentioned again. The proof is a real migration with a real outcome, which answers "how long until you're useful" better than any adjective. The last line is the character point — you're the kind of person who flags things early. Adapt the structure; don't memorize the words, and don't use a sentence that isn't true for you.

Missing years of experience, or the scope — posting says eight years or a bigger team, you have less.

"You're right that I'm at [your actual number] years, not [what they asked for], and I've managed [the real number] people rather than [their number]. What I'd point to is the shape of the work. In [year], I took over [the specific project or function] after [what actually happened — a departure, a reorg], which put me on [the harder thing you handled] about two years earlier than I'd have gotten there otherwise. [The outcome, with a number if you have one.] Going from [your team size] to [theirs] is a real step up, mostly in how much I'd be managing through other people instead of directly. That's the part I'd want coaching on, and it's the first thing I'd ask my manager to be blunt with me about."

It agrees with the fact instead of fighting it, which stops the argument. Then it does the thing years-of-experience is a proxy for — proving you've been through hard situations. Naming the specific part of the jump that's hardest shows you understand the bigger job, which is exactly what they're unsure about.

Early career, one internship, applying to a role that asked for two or three years.

"I've got [what you actually have — one internship, six months, whatever it is], so I'm coming in under the experience line on the posting. Here's what I did have my hands on: at [the internship], I [the specific task you genuinely owned], and by the end I was [the real level of independence — running it without review, handling the weekly one on my own]. I made a real mistake on [the thing], caught it, and [what you did], and that's when I learned to [the actual lesson]. I know I'll need more direction in the first few months than someone with three years. I'd rather be the person who asks the question early than the one who guesses. What does ramp-up usually look like here?"

It doesn't inflate an internship into a career, which is the trap most new grads fall into. The owned task and the mistake are what make it credible — anyone can claim they helped, almost nobody volunteers what they got wrong. Ending with a question turns the moment into a conversation instead of a verdict. Swap in your own specifics; a borrowed story reads as borrowed.

What comes next

Answer this one well and the interviewer usually goes here:

  • "How would you get up to speed on [the thing you're missing]? Walk me through your first month."
  • "What would your first ninety days look like?"
  • "Why should we hire you over someone who's already done this exact job?"
  • "What's the hardest thing you've had to learn on the job, and how long did it take?"
  • "How do you handle being the least experienced person in the room?"
  • "Is there anything on this job description you'd struggle with?"
  • "What kind of support would you need from your manager?"
  • "What are you looking for in terms of salary?" — expect this, and answer with your number based on the role and the market, not on how qualified you feel.

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

They called you in knowing what's on your resume, so the only thing left to prove is that you can talk about the gap like an adult — and that's a thing you can practice tonight.