How to interview with no experience — a new grad's game plan

"We're looking for someone with experience" is the line that makes new grads panic — but almost nobody actually means a prior job title. What they mean is proof you can do the work. You have more of that than you think: coursework, class projects, a part-time job, a club you ran, a thing you built on your own time. The skill isn't getting experience you don't have — it's translating what you do have into proof the interviewer can use. Here's how.

Why "no experience" worries interviewers less than you think

Entry-level postings that ask for experience are usually screening for a capability, not a résumé line — can you communicate clearly, handle ambiguity, learn fast, work with other people. Every one of those shows up outside a job: in a group project, a part-time shift, a volunteer role, a side project you kept going for months after the grade was in. The interviewer already expects a new grad in this seat and has a mental model for how to evaluate one. Your job isn't to pretend you have a career history — it's to show the capability clearly, from wherever it actually happened.

The framework: Relevant → Evidence → Trajectory

1. Relevant. Before you answer, map the question to the skill it's really testing (ownership, communication, handling pressure, working with others) and pick whichever part of your life — class, work, clubs, side projects — actually demonstrates it. Don't default to "I don't really have an example for that."
2. Evidence. Tell it as a real situation with specifics: what the task was, what you did, what happened. Specifics are what separate proof from a claim. "I'm organized" is a claim; "I ran a 20-person event on a $200 budget and tracked every vendor in a shared sheet" is evidence.
3. Trajectory. Close with a line that shows you're already moving in the direction the job needs — a related course you're taking, a skill you picked up since, a way you've already started closing the gap. This is what makes "new" read as "ready," not "unfinished."

The whole shift is refusing to treat non-job experience as lesser. A real story from a class project, told with specifics, beats a vague summary of an actual internship every time — interviewers are evaluating the evidence, not the letterhead it came from.

A worked example

Asked "Tell me about a time you had to learn something quickly," a new grad with no formal tech job answered: "In my capstone project, our team's data pipeline broke two weeks before the deadline because of a library change none of us had used before. I spent a weekend going through the new docs and a few open issues on the project's GitHub, rebuilt the broken piece myself, and wrote a short README so the rest of the team could use it without hitting the same wall. We shipped on time, and I've kept using that same debugging approach — docs first, then real examples — on every project since."

Relevant (a learning-under-pressure story, from a class project since there was no job to pull from) → Evidence (specific obstacle, specific action, specific outcome) → Trajectory (a habit they've kept using since). Nothing here apologizes for the lack of a job title — it doesn't need to.

Where to find "experience" when you've never had the job title for it

Look in four places: capstone or major class projects (anything with a deliverable, a deadline, or a team), any part-time or retail job (customer conflict, juggling tasks, training someone newer than you — all real material), clubs or student organizations you held any responsibility in, and personal projects you built or maintained without being asked to. None of these need to be dressed up as more than they were — they just need to be told with the same specificity you'd use for a "real" job, because to the interviewer, they are one. Structuring these into tight, repeatable stories ahead of time — rather than improvising in the moment — is exactly what the STAR method is built for.

Common mistakes to avoid

• Apologizing up front. "I know I don't have much experience, but..." plants the doubt before you've even made your case. Just answer the question.
• Only citing coursework. Grades and class names aren't evidence of a skill — the project you did inside the class is. Lead with that.
• A bare "I'm a fast learner." Every candidate says this. It only works with a specific example attached, like the one above.
• Undervaluing non-job experience. A club, a part-time job, or a personal project that actually demonstrates the skill in question beats a vague internship that doesn't.
• Comparing yourself to experienced candidates. You're not meant to outcompete them on years — you're meant to prove the capability. Stay in your own lane.

The bottom line

"No experience" is a résumé-line problem, not an interview-answer problem — the capability the question is testing almost always exists somewhere in your life already. Find it, tell it with real specifics, and close with where you're headed next. That's a complete answer, with or without a job title attached to it.

Related: Behavioral interviews and the STAR method · How to calm interview nerves · How to research a company before an interview