Interview guide for entry-level roles: a short, fair loop when candidates have little work history

Entry-level hiring has a different problem from experienced hiring. Candidates have little work history, many have never been interviewed for an office job, and the ones who interview best are often the ones who have had the most coaching. A loop built for experienced hires asks for evidence these candidates cannot give. This guide gives hiring managers a short, fair loop for entry-level roles such as coordinator, assistant, junior associate or trainee: three stages, who owns which competency, questions any candidate can answer with what to listen for, a 30-minute job task, example weights and a fast decision rule.

This page covers the loop. For the interview itself with recent graduates, including age-related cautions, read how to interview new graduates. For candidates moving from another field, see how to interview career changers. Internships have their own loop in the interview guide for internships.

The loop at a glance

An example for an entry-level operations or office coordinator. The structure works for most entry-level roles; change the job task.

Stages 2a and 2b happen in the same visit or video call block, so the candidate takes one time slot off from their current job or classes. Why fewer stages is usually better is in the interview process template.

Stage 1: the short screen (15–20 minutes)

• "This role works these hours, in this location, at this pay. Does that work for you?" Say the facts first rather than asking the candidate to guess. Listen for: a clear yes, or a constraint you can discuss.
• "What made you apply for this job in particular?" Listen for: anything specific about the work, the team or the path it leads to. "I need a job" is honest and not disqualifying; probe what kind of work they enjoy.
• "Tell me about something you have done in the last year that you are proud of. It can be from work, school or anywhere else." Listen for: a specific example. This also tells the candidate that non-work evidence counts, which helps in stage 2.

Tell every candidate what stage 2 will include, how long it takes and that you will ask for examples from any part of their life.

Stage 2a: structured interview (40 minutes)

Same questions, same order, for every candidate. Each question says out loud that examples can come from a job, school, a team, volunteering, family responsibilities or a personal project.

1. Reliability: "Tell me about a time you had to keep a commitment when it became inconvenient." Listen for: a specific commitment, what made it hard, what they did, and how they communicated if they could not keep it. Strong answers include telling someone early.
2. Learning: "Tell me about something you had to learn quickly. How did you go about it?" Listen for: a method (asking, practicing, breaking it into steps) and a result. More questions on this are in interview questions for learning agility.
3. Working with others: "Tell me about a time you worked with someone you found difficult." Listen for: their own actions, an attempt to understand the other person, and an outcome. Avoid scoring down a short answer from a nervous candidate; follow up instead.
4. Handling mistakes: "Tell me about a mistake you made and what happened next." Listen for: owning it, fixing what they could, and a change afterward.
5. Questions from the candidate (5 minutes). Do not score this. Candidates with less experience often do not know what to ask; that is not a signal about the job.

Follow every first answer with "What did you do next?" or "What did you say?" Entry-level candidates often give the outline first and the evidence only when asked.

Stage 2b: the job task (30 minutes)

The task is a small, realistic version of the job, done during the visit with the same written instructions and materials for everyone. Make sure it needs no knowledge of your company or software.

An example task for a coordinator role

• A list of 12 incoming requests by email, with names, dates and needs.
• Part 1 (15 minutes): "Sort these into today, this week and later, and mark any you would ask your manager about."
• Part 2 (10 minutes): "Write a short reply to one request that you cannot fulfill this week."
• Part 3 (5 minutes): "What did you find unclear in the instructions?"
• Plant two items that conflict (for example, two people booking the same room) and one with a missing detail.

What to look for

• Following instructions: did they do what was asked, in the format asked?
• Accuracy: did they notice the conflict and the missing detail?
• Judgment: sensible priorities, and asking rather than guessing where the brief was unclear.
• Writing: a reply that is polite, clear and offers an alternative.

For other roles, swap the task: a short data entry and check exercise for an administrative role, a role-played customer question for a front-desk role, or a short document to proofread for a junior communications role. Offer adjustments to anyone who asks; how to handle requests is in ADA accommodations in interviews.

Scorecard competencies and weights

Example weights for an entry-level coordinator. Set yours at intake and lock them before the first candidate.

The job task carries the most weight because it is the evidence least affected by interview coaching. Anchors for the interview questions: 1 no example, 2 a general description, 3 a specific example with their own actions and an outcome, 4 the same plus something they changed. Build the sheet in the scorecard builder.

The decision rule

1. Score before discussing. The hiring manager and team member score independently, right after the visit.
2. Gate: job task at 3 or above.
3. Floor: no 1 on reliability. Everything else can be taught faster than showing up as agreed.
4. Weighted total: in this example, 2.6 or higher on the 1–4 scale is an offer. The bar is lower than for experienced roles because you are hiring for what someone can learn, but it is set in advance and kept for the whole search.
5. Decide within two working days. Entry-level candidates apply widely and accept the first good offer.

If you are hiring for several openings at once, the scheduling and batching advice in high-volume hiring process applies.

Keeping it fair

• Do not score polish. Confidence, vocabulary and a firm handshake are interview skills. Score what the candidate did in their examples and in the task.
• Do not ask for graduation years or ages. They are not needed to assess the role. If the role has a minimum age, ask only whether the candidate meets it, and if you may hire anyone under 18, read hiring minors: work permits and hours first.
• Accept non-work evidence equally. Caring for a relative or holding a part-time job through school shows reliability as well as an internship does.
• Explain what happens next. Many entry-level candidates do not know how hiring works; a clear timeline reduces drop-out.

Common mistakes in entry-level loops

• Copying the experienced-hire loop. Five rounds and a take-home for an entry-level role loses most of the pool.
• Unstructured "tell me about yourself" interviews. They reward the practiced and tell you little about the job.
• Requiring experience for the entry-level job. If you need two years of experience, the role is not entry-level; change the posting or the loop. More on judging what someone can grow into is in how to interview for potential.