New Graduate Interview Guide: Turn Coursework Into Evidence

Expect a short "tell me about yourself", a few behavioural questions, questions about your course or projects, and time for your own questions. When you have no work history, interviewers are not checking whether you have done the job. They are checking whether you can describe how you work: what you decided, what you changed and what happened. The fix is not reassurance. It is sourcing evidence from coursework, projects, internships and part-time work, then translating it into the situation-action-result shape interviewers listen for.

This new graduate interview guide gives you that method, with worked answers you can adapt.

What actually happens in a new graduate interview

Most first-round interviews for graduates follow a predictable shape. You get a short opening question, a handful of behavioural questions (teamwork, a problem you solved, a deadline you met), some questions about your course, dissertation or projects, and five minutes for your questions. Some employers add a short task or a technical screen.

Why ask about coursework when you have no job history? Because a project is a small, complete piece of work. It has a goal, constraints, other people and a deadline. How you talk about it reveals how you think: whether you notice problems, whether you can name your own contribution, whether you learn from what went wrong.

A one-line reframe worth keeping in mind: they are not checking whether you have done the job, they are checking whether you can describe how you work. That changes what you prepare. You are not hunting for impressive experience. You are collecting specific evidence and learning to describe your decisions inside it.

Build your evidence bank before you write a single answer

An evidence bank is a plain list of real things you did, written down before you need them. Build it in four columns:

• Source: where it happened. Course, project, internship, part-time job, volunteering, society or sports team.
• What you did: your specific actions, not the group's.
• What changed: the result. A grade, a fixed rota, a shipped feature, a resolved disagreement, a deadline met.
• What you learned: one honest sentence on what you would do differently or what it taught you.

Aim for eight to ten entries. That sounds like a lot until you start. A single group project can yield three or four: your contribution, a disagreement you resolved, a deadline you protected.

Mining a group project for evidence

Group coursework is the richest source most graduates have. Ask yourself three questions about each project. What did I personally build, write, test or organise? What disagreement or obstacle came up, and what did I do about it? What did I do when the deadline got tight?

Write the answers in plain notes, not polished sentences. You are collecting material now, not performing.

Why part-time and volunteer work counts

A shift you covered, a rota you fixed, a customer complaint you handled, a stockroom you reorganised: these are real evidence of reliability and ownership. Interviewers accept them because they show how you behave when something depends on you. Do not leave them off because the job was not "career-related".

The three-part shape that makes a student example sound like experience

Use situation, action, result, usually shortened to STAR. In plain words: where you were, what you did, what happened. Keep the situation to one or two sentences. The action is the part interviewers score, so spend most of your time there, describing your decisions and why you made them. The result lands last and should be concrete.

Then add a "so what" line: one sentence on what you would do differently or what it taught you. It signals reflection, which is what an interviewer is really listening for when experience is thin.

Weak, then stronger: the same project, twice

Here is a weak version of a project answer. It describes the assignment rather than the person.

"For our group project we had to build a booking system. There were four of us and we split the work. I did the database part and we presented it at the end. We got a good grade."

Nothing here is false, but the interviewer learns almost nothing about you. Now the stronger version.

"In my second-year software course, four of us had six weeks to build a booking system. Two weeks in, our database design couldn't handle overlapping bookings, and the group wanted to patch it at the end. I suggested we fix the schema first. I mapped the conflict cases on paper, proposed a change to the booking table, and talked the team through it in a twenty-minute call. We rebuilt that part in two days, and the final system passed every overlap test the marker ran. What I'd do differently is spot the conflict in week one by writing test cases before designing."

The difference is decision description. The weak answer reports the assignment. The stronger one names a problem, a choice, a conversation and a result. For more on this pattern, see Ownership Interview Questions: How to Show You Take Responsibility.

Worked example: answering 'tell me about a time you worked in a team'

Here is a full sample answer built from a group coursework project, about 90 seconds spoken.

"In my final-year marketing module, five of us had four weeks to produce a campaign proposal for a real local business. [Situation ends here.] About ten days in, two people wanted to focus on social media and two wanted print, and we were going in circles. I asked us to spend twenty minutes writing our top priority on a card, then read them out. It turned out everyone cared most about the budget, not the channel, so I proposed we split the budget across both and assign one owner to each. I took the budget section, built the spreadsheet, and set a check-in every three days so we didn't drift. [Action ends here.] We submitted on time, the client picked two of our ideas, and the module lead used our budget sheet as an example for the next cohort. [Result lands here.] What I took from it is that naming the real disagreement early saves a week of polite circling."

Notice where the weight sits. The situation is three sentences. The action is the middle, and it is all decisions: asking for priorities, proposing a split, taking a section, setting check-ins. The result is specific and short.

If the interviewer follows up with "what was your role specifically?", keep it to two sentences: "I owned the budget section and the check-in schedule. The channel split was a group decision, but I proposed the process that got us there." That answer stays accurate and still shows your contribution.

How to answer 'you have no experience' without apologising

When the question comes, use the honest bridge: name what you have not done, then name the closest thing you have done and what it proves. Do not pretend, and do not shrink.

"I haven't managed a client portfolio in a commercial setting. The closest thing I've done is run the ticketing for our student society's events: I handled refunds, kept a shared spreadsheet of every request, and when two events clashed I rebuilt the schedule so neither was cancelled. That taught me how to keep commitments visible when several people depend on them. I'd expect to learn your systems quickly, and I'd rather show you that than claim it."

That answer works because it is checkable. It names a real limit, offers adjacent evidence and states a learning approach without overclaiming.

Words to avoid: "just", "only", and "I haven't really". They shrink your evidence before the interviewer has judged it. Say "I haven't done X yet; the closest I've done is Y" instead. For more on structuring these answers, see Communication Interview Questions: Honest, Clear Answers.

Turning an internship into three or four usable stories

Even a short internship holds more than it seems. Extract three things: one task you owned end to end, one problem you spotted, and one person you worked with closely. Each becomes a story.

If the internship was mostly shadowing, say so honestly and describe what you observed and what you asked. "I mostly observed client calls, but I kept a list of recurring questions and asked my supervisor why two of them were handled differently. That conversation is where I learned how their escalation process worked." That is evidence of curiosity and attention, which is what shadowing can prove.

For "what did you actually do day to day?", use a short accurate script: "I supported the team with data entry and meeting notes, and from week three I ran the weekly stock check myself." Accurate beats impressive, because follow-up questions expose anything inflated.

The three mistakes that sink new graduate answers

• Telling the whole story of the assignment instead of your part in it. The fix: after every sentence, ask "did I do that, or did the group?" and say which.
• Staying abstract. "I'm a good communicator" with no example attached is a claim, not evidence. The fix: attach one specific moment within the same breath.
• Borrowing a story that isn't yours. It collapses under one follow-up question, and the interviewer will ask one. The fix: use your own smaller story and describe it precisely.

Each of these fails for the same reason: the interviewer cannot see you in the answer. Specific, owned detail is what makes a thin CV sound like real experience.

A two-week practice routine you can actually keep

Week one. Build the evidence bank. Write four answers in the three-part shape: a team project, a problem you solved, a deadline you met, and why this role. Say each one out loud once. Out loud, because reading silently hides the places where you ramble.

Week two. Practise follow-ups. Record yourself, listen back, and cut each answer to about 90 seconds. Then run this self-review checklist on each one:

• Did I name my action, not just the group's?
• Did I give a concrete result?
• Did I answer the actual question that was asked?
• Did I add one "so what" line?

If you want help sounding natural rather than recited, see Sound Natural With Talking Points Interview Guide.

Your questions for them, and how to close

Ask three questions that show interest without pretending to know the industry. For example: "What does a strong first six months look like in this role?", "How is training handled in the first few weeks?", and "What's the most common thing new joiners find hardest?" Each invites a real answer and tells you something useful.

Then close simply: "Thank you for the time. I'm interested in the role, and I'd be glad to answer anything else." That restates interest without overclaiming.

Before you walk in

The one takeaway: your evidence already exists, it just lives in projects, coursework and part-time work, and your job is to describe your decisions inside it. The one thing to do next: open a document and write five evidence-bank entries before you write a single full answer. If you want a structured way to rehearse, our blog has answer frameworks for many roles and question types.

Frequently asked questions

What if all my projects were done alone and I have no teamwork examples?

Use the closest real equivalent: a group assignment, a society event, a shared household task or a part-time shift where you coordinated with someone. If genuinely nothing fits, say so and describe how you would handle a disagreement, clearly labelled as your approach rather than an example. Interviewers accept honesty about a gap far more readily than an invented story.

Should I mention my grades or my dissertation in the interview?

Mention them when they support the question being asked. A strong grade in a relevant module is evidence of how you work; a dissertation is a project with a goal, constraints and a result, so it fits behavioural questions well. Lead with what you did and decided, and use the grade as the result line rather than the headline.

How long should each answer be when I have little to say?

Aim for 60 to 90 seconds, which is roughly 150 to 220 spoken words. Shorter answers sound thin; longer ones lose the interviewer. If your material is limited, spend the time on your action and result rather than padding the situation with background.

What do I do if the interviewer asks about a tool or system I have never used?

Say plainly that you have not used it, then name the closest tool you have used and what transferred: the concepts, the workflow or the way you learned the last one. Offer to walk through how you would get up to speed. Interviewers usually expect graduates to learn tools on the job; what they are testing is whether you are honest and quick to learn.

Is it okay to use the same story for more than one question?

Yes, if you reframe it for the question asked. One group project can answer a teamwork question, a conflict question and a deadline question, as long as you draw out the relevant part each time. Avoid repeating the identical telling twice in one interview; it makes your evidence look thinner than it is.

Practise your evidence-bank answers out loud before the real interview.