How to interview new graduates when there is little work history to go on

To interview new graduates, assess the evidence they actually have: projects, part-time jobs, internships, volunteering and study. Tell them up front that non-work examples count, ask behavioral questions that fit those settings, add a short work sample for the core skill, and score everything against the same rubric. Look for how they learn, own work and handle problems, not for experience they could not have yet.

This page is for hiring managers who interview graduates now and then and want a fair, consistent way to do it. For candidates with years of experience in a different field, see how to interview career changers; the evidence you look for is different.

What you can and cannot assess at this stage

The usual interview asks for proof of doing the job before. A new graduate mostly cannot give that, so change what you look for rather than lowering the bar.

Before the interview: set it up so everyone can show evidence

• Tell every candidate that non-work examples count. Put it in the invitation: "Examples from study, part-time work, volunteering or anything else are all welcome." Graduates who worked through school or cared for family often assume those examples do not count, and those are often the strongest.
• Define the core skill and test it the same way for everyone. A 20-minute exercise in the interview, or a take-home capped at two hours. See how to evaluate a take-home assignment.
• Read the resume for what they did, not where. A school's name tells you little about the person; what they built, ran or fixed tells you more.
• Agree the rubric in advance, especially if several managers are interviewing graduates for the same intake.

Questions, strong answers and red flags

Each question works with any kind of example. Probe with "what did you do, specifically?" and "what happened next?" until you have enough to score.

1. Learning something hard

Ask: "Tell me about something you had to learn quickly that did not come easily. How did you go about it?"

• Strong answer: names the specific thing, describes a method (practice problems, asking someone, breaking it down), and says how they knew they had learned it.
• Red flags: only examples of things that came easily; "I just studied harder" with no method; blames the teacher or course throughout.

2. Owning a piece of work

Ask: "Tell me about a project or piece of work where you were responsible for the outcome. What were the decisions you made?"

• Strong answer: clear about their part versus the group's, names two or three decisions and why they made them, and is honest about the result.
• Red flags: "we" throughout with no individual contribution; cannot name a decision; the result was perfect and nothing was learned.

3. Working with other people

Ask: "Tell me about a time someone on a team you were part of was not doing their share. What did you do?"

• Strong answer: spoke to the person directly or found out why first, adjusted the plan, and escalated only when needed.
• Red flags: quietly did all the work and resents it; went straight to the professor or manager; describes the teammate with contempt.

4. Handling a mistake

Ask: "Tell me about a mistake you made at work, in study or in a project. What happened, and what did you change afterwards?"

• Strong answer: a real mistake with consequences, told without excessive self-criticism, and a specific change in how they work now.
• Red flags: a disguised strength ("I work too hard"); cannot think of one; the mistake was someone else's.

5. Part-time or service work

Ask: "In your job at [employer], what was the hardest part of a busy shift, and how did you handle it?"

• Strong answer: concrete detail about prioritizing, dealing with difficult customers, or covering for absent colleagues. Reliability and composure under pressure show up here more clearly than in most project stories.
• Red flags: dismissive of the job as irrelevant; no detail.

6. Why this role

Ask: "What do you think you would actually be doing in your first three months here? What appeals to you about that?"

• Strong answer: a realistic picture of entry-level work, drawn from the job description or conversations, and a specific reason it appeals.
• Red flags: expects to be doing the senior version of the job immediately; interested only in the company name.

A rubric for graduate interviews

Score each line with one quote or example as evidence, before you discuss the candidate with anyone. The behavioral interview scoring rubric explains how to write anchors for other competencies. Writing down exact phrases while listening to a nervous graduate is hard; Interview Signal can keep the transcript and attach the quotes to each score, with the candidate told at the start.

A scored example

Age, graduation dates and other cautions

• Not every graduate is young. The Age Discrimination in Employment Act protects people aged 40 or older, and the EEOC's page on prohibited employment policies and practices gives a job ad seeking "recent college graduates" as an example that may discourage people over 40 from applying. Describe the level of the role ("entry-level", "no prior experience required") instead.
• Do not ask for graduation year or age. Ask whether they hold, or will hold by the start date, the qualification the job requires.
• Avoid "culture fit" as a stand-in for "like us at that age". Social background, hobbies and which school someone attended are not job criteria. See how to assess values without culture fit bias.
• Pay: some states and cities restrict asking about pay history. Ask about expectations instead; the salary expectation questions page has wording.

Running the interview

0:00  Welcome (3 min)
      Who you are, the format, that you'll take notes, and that
      examples from study, jobs and anything else all count.

0:03  Their path so far (5 min)
      "Walk me through what you've done in the last few years that
      is most relevant to this role." Listen for what to probe.

0:08  Behavioral questions (25 min)
      Four or five of the questions above, probed properly.

0:33  Work sample discussion (10 min)
      If done beforehand: "Walk me through your approach. What would
      you change with more time?"

0:43  The role, honestly (7 min)
      What the first three months really involve, training, who
      they'd work with.

0:50  Their questions (8 min)

0:58  Next steps and date (2 min)

Graduates often have little interview practice. A clear structure, said out loud at the start, gets you better evidence from nervous candidates without making it easier for anyone.

After the interview: move quickly and sell honestly

• Decide within days, not weeks. Graduates are often in several processes at once, especially near the end of the academic year.
• Explain the training and support the hire will get. For a first job, that can matter to the candidate as much as a small difference in salary.
• Give a reasonable deadline for an offer and avoid pressure tactics. A graduate who accepts under pressure and keeps interviewing is a risk to your start date.
• For those you reject, a short, job-related note on what would strengthen a future application is remembered. Keep it consistent with your organization's feedback policy.