How to Interview Candidates With No Work Experience

The CV is basically empty. Now what?

You've got a stack of applications and half of them are graduates or career-switchers with nothing under "experience" except a part-time job at a coffee shop and a final-year project. The usual interview playbook — "walk me through a time you handled conflict at work" — falls flat because they haven't had a job long enough to have a war story.

This is where a lot of interviewers give up and just go on gut feel: who seemed sharp, who dressed well, who reminded them of themselves at that age. That's how you end up hiring the most confident talker in the room instead of the person who'd actually be good at the job.

The fix isn't to lower your standards. It's to change what you're measuring.

You're not testing experience. You're testing trainability.

With an experienced candidate, you're checking whether their track record predicts they can do your job. With someone junior, there's no track record to check — so you're really asking three narrower questions:

1. Can they learn fast when they don't already know something?
2. Do they think in a structured way, even about small problems?
3. Will they actually show up and follow through, or fade after week two?

Every question you ask should be aimed at one of those three, not at fishing for a résumé line that doesn't exist.

Questions that work when there's no work history

Drop "tell me about a time you..." — it assumes a career's worth of anecdotes. Ask about smaller, real moments instead.

• "What's something you taught yourself in the last year, and how did you go about it?" This isn't about the subject — it could be a language, a video game mechanic, cooking. You're listening for method: did they just watch videos passively, or did they set a goal, hit a wall, and figure out a way through it?
• "Tell me about the last time a group project or assignment went badly. What actually happened?" Students always have this story. Listen for whether they can describe their own part in the mess honestly, or whether it's entirely someone else's fault.
• "What's the hardest thing about [a task central to this role] that you think you'd need to get better at?" A candidate who can name a real weakness in the work itself, rather than a rehearsed "I'm a perfectionist," is showing you they've actually thought about the job, not just about getting the job.
• "Walk me through how you'd figure out X" — pick something small and concrete from the actual role, and let them think out loud. You're not grading the answer. You're watching whether they ask clarifying questions, break the problem down, or freeze.

None of these need a career to answer. All of them are hard to fake with a rehearsed script, because the follow-up questions expose whether the story is real.

Give them something to actually do

For junior roles especially, a short work sample tells you more in twenty minutes than an hour of conversation. It doesn't need to look like the real job yet — it needs to isolate the one or two things that actually matter early on.

• Hiring a junior admin or ops person? Give them a messy, half-organised spreadsheet and ask them to clean it up and flag anything odd. Watch what they notice.
• Hiring an entry-level marketer? Give them a product description and ask for three different headline options aimed at three different audiences.
• Hiring a junior developer? A small, scoped bug or a short coding problem beats asking them to describe their "favourite project" — most portfolio projects were built with heavy tutorial help, and that's fine, but it doesn't tell you what they can do unassisted.

Keep it short. Juniors don't have the confidence yet to push back on an unpaid four-hour "test project," and asking for one anyway is a bad look that costs you good candidates before you even meet them.

What "no experience" is sometimes hiding

Be honest with yourself about two failure modes that go the opposite way:

• Over-crediting confidence. Someone who interviews smoothly at 22 has often just had more practice interviewing — more mock interviews, more career-services coaching, more privilege of time to prepare. That's a real skill, but it's not the job.
• Under-crediting the quiet ones. A nervous, awkward answer from someone who's never sat across a hiring manager before doesn't mean they can't do the work. If English isn't their first working language, or this is their first formal interview ever, some of what looks like weak communication is just unfamiliarity with the format, not a signal about the job.

A structured set of questions — the same ones, same order, for everyone — helps you catch yourself doing either of these, because you're comparing answers to the same prompt instead of comparing overall impressions.

Scoring candidates who all look thin on paper

When every CV is short, you can't score on résumé weight. Score on the answers instead, using a simple rubric before you start interviewing:

• For each question, decide in advance what a strong, adequate, and weak answer looks like.
• Score right after each interview, not at the end of the day when they've blurred together.
• Weight the work sample heavily — it's the closest thing you have to real evidence.

If you want a second, independent signal before the interview stage — something that doesn't depend on how well someone writes a CV or performs in a room — a short skills or reasoning assessment can help here, since it's judging the work itself rather than the polish around it. AssessFit keeps CV weight capped at 30% of a candidate's score for exactly this reason: with junior hires, the CV is often the least informative part of the whole application.

The honest limit

None of this removes uncertainty. A great interview and a solid work sample still won't tell you for certain how someone performs after six months of real pressure, deadlines, and a manager who isn't watching their every move. That's what probation periods are for. Treat the interview as a filter for potential, not a guarantee — and build in a real check-in at 30 and 60 days to see if the potential you saw is showing up in the actual work.