“Not a Ton of Experience” Is a Framing Problem

There's a question that comes up on an endless loop: what jobs can I even get with no degree and not a “ton” of experience? The quotation marks around “ton” are doing a lot of work in that sentence. Whoever's asking clearly has experience — just not the kind they've been taught to count. That's the actual problem, and it's fixable. Not the experience. The counting.

Experience is not a duration

The way most people describe their background is arithmetic: years in role, number of employers, seniority of title. And under that arithmetic, thin is thin — you can't talk your way from a short career to a long one, and please don't try, because interviewers can smell inflation from across the table.

But here's the thing interviewers actually do with your “experience”: they probe it. They ask what happened, what you did, what broke, what you'd do differently. Which means experience, in the room where it matters, is not a duration at all. It's a set of stories that survive questioning.

A candidate with a short history and sharp, checkable stories beats a candidate with a long history and mush.

So the job isn't to acquire more past. It's to excavate the past you have.

The inventory nobody does

Sit down with a blank page and list every system you've ever been responsible for. Not “jobs” — systems. A till at closing time is a system. A kitchen during a rush is a system. A volunteer rota, a warehouse pick route, a gaming community with feuding moderators, a family member's medical paperwork — all systems, all of which you operated, fixed, or kept from collapsing. For each one, write down the moment it nearly went wrong and what you did. Plain sentences. That list is your actual resume. The document with the dates on it is just the cover.

Watch the translation work:

None of those candidates added a day of experience. They re-narrated what was already there.

Answering the question behind the question

When an interviewer asks “tell me about a time you handled a difficult situation,” they are not asking whether that situation happened inside a company with an HR department. They're asking whether you can walk through situation, action, and outcome without dissolving into vagueness. The corporate setting is optional. The structure isn't.

So build each story to the same skeleton: where you were, what was at stake, what you specifically did — not “we,” you — and what happened after. Then say it out loud until it's boring. Out loud matters. A story that lives only in your head falls apart the first time it meets air, and you don't want that first time to be in the interview. The difference between a prepared story and an improvised one is audible within seconds, and it reads — unfairly but reliably — as the difference between competence and luck.

Here's what the skeleton sounds like when it's actually delivered, using the shift-lead story: “Mid-rush on a weekend, our floor lead walked out after a blow-up with another server. I was the most senior person left, so I split the floor between the rest of us, pulled the angriest customer aside myself, and comped exactly one dessert. After close, I messaged both people separately, heard both versions, and had them back on the same rota within the week — without escalating to the owner, who would've fired one of them.” Notice the shape: place, stake, your decisions, aftermath. No title required. No company with a lobby required.

One warning, because it's the failure mode of this whole approach: do not inflate the stakes. The screaming-match story is good because it's true-sized. The moment you promote yourself to “managed the restaurant” when you covered a shift, you've converted a strong small story into a weak lie, and interviews are machines for finding the seam in a lie. Small and solid wins. Every time.

The awkward truth about entry-level screening

Now the part that rarely gets said out loud. Candidates with thin resumes don't usually get a sympathetic human reading between the lines. They get screened — by keyword filters, by application-tracking software, and increasingly by AI interviews, because high-volume entry-level hiring is exactly where companies deploy automation first. The people with the least conventional experience are getting the most robotic evaluation. Nobody designed it that way on purpose. It's still the reality.

The relevant detail for you: most AI screens ask no follow-up questions. Whatever context didn't make it into your first answer doesn't exist — a human might tease the story out of you; the machine will not. For a candidate whose strength is context — “my experience looks thin but here's what it actually contains” — that's a hostile format unless you prepare for it directly. Your stories have to arrive pre-translated, stakes and actions up front, without a friendly interviewer's nudge. There's a full guide to that format in how to prepare for an AI interview — the short version is: practise your translated stories against something that talks back and doesn't nod along, because the nodding was doing more work for you than you think.

What to do this week

• Write the systems inventory. Every system you've run, every near-failure, one plain sentence each.
• Pick the strongest few and build them to the skeleton: situation, stake, your action, aftermath.
• Say them out loud until they bore you. Boring means ready.
• Put anything checkable — a project, a link, a person who'll vouch — where a stranger can verify it in a minute.

“Not a ton of experience” almost always means “experience nobody has helped me name yet.” Name it yourself. The people evaluating you are working from a much lazier reading of your life than the one you can give them.