Six question sets for hiring someone with little or no work history: core questions, reliability, coachability, a no-resume set, a customer-facing set, and a scorecard. Every question states why it is worth asking and what a good answer sounds like. Download as DOCX.
The first entry level interview I ran was a disaster, and it took me twenty minutes to work out why. I had prepared questions about previous roles, previous managers, and previous results, and I was interviewing a nineteen year old whose resume had one line on it. Every question I asked, they had no way to answer. I was testing whether they had a work history, which I already knew from the application.
Hiring entry level is a different exercise. You are not measuring what someone has done. You are trying to predict whether they will show up, pick things up fast, take correction without drama, and still be here in six months. That needs different questions, and it needs somewhere for the evidence to come from when the resume is empty.
At FirstHR, we build for owners and managers who hire without an HR department, and for many of them the entry level hire is the one they make most often. These six sets give you the questions, the reason each one is worth asking, what a good answer sounds like, and a scorecard so the decision rests on evidence rather than on who was easiest to talk to.
TL;DR
Interview entry level candidates on five things: motivation for this job, reliability (commute, availability, commitments kept), coachability, learning speed, and responsibility shown anywhere, including school or caregiving. Lean on situational questions rather than behavioral ones, since there is no work history, and score everyone on the same 1-to-5 rubric. Download six question sets and a scorecard.
What to Assess When There Is No Work History
Assess five things: motivation for this particular job, reliability, coachability, learning speed, and responsibility held anywhere at all. Skills are deliberately absent from that list. Anything you can teach in a week is not a selection criterion, and weighting it just filters for candidates who happened to get an earlier start.
Reliability comes first, because attendance rather than ability is what usually ends a first job. A candidate who cannot describe how they will get to work is telling you something more useful than any answer about strengths and weaknesses. Coachability is second, because you will be correcting this person daily for the first month and the response to that decides how the month goes.
What to assess
The question that gets at it
What a good answer contains
Motivation for this job
What made you apply for this job specifically?
Something concrete about your business or the work
Reliability
How will you get here, and how long does it take?
A route, a travel time, and a backup plan
Coachability
How do you handle being told you did something wrong?
A real correction and what changed afterward
Learning speed
Teach me something you know how to do.
Steps in order, checking that you are following
Responsibility
What is the most responsibility you have been given, anywhere?
A real duty with consequences, held over time
Judgment
You are stuck and nobody is free to help. What do you do?
Tries alone, then asks when the cost of error is real
Notice that every one of those questions can be answered from school, a team, a volunteer shift, or looking after a younger sibling. That is the design. A question only an employed person could answer is a question that tests for having been employed.
Which Question Set Should You Use?
Use the core set for every entry level role, then add one more that matches the job. The reliability set fits any shift-based role, the customer-facing set fits retail, food service, and front desk work, and the no work history set is for candidates whose application has nothing on it but school.
Core Questions
Start here, any first job
Eight questions that work for any entry level role: why this job, what they think it involves, learning something new, responsibility anywhere, taking correction, and availability. Each one with why it is worth asking.
Motivation and Reliability
Can they be here?
The attendance set. Commute plan, what time they would leave home, commitments kept, what they do when they are going to be late, and the informal work most candidates forget to mention.
Coachability and Learning
How fast do they pick it up?
Teach me something you know, the first attempt that went wrong, what they do when stuck and nobody is free, and how they would know they were doing well after a month.
No Work History Set
First job, empty resume
Situational questions plus evidence from school, teams, volunteering, and caregiving, for candidates with nothing to point at. Includes how to score a hypothetical answer without being fooled by a nice one.
Customer-Facing and Teamwork
Retail, food, front desk, warehouse
The upset customer, saying no, the busiest hour, the coworker not pulling their weight, and honest questions about repetitive work. Pair it with the core set.
Scorecard and Red Flags
Score, do not guess
Six scoring areas with written anchors for what a 5 looks like at entry level, an eight-item red flag checklist, and a decision box with the minimum bar you set before the first interview.
Match the Set to the Hire
Any first job: Core Questions, always. A shift-based role where attendance is everything: add Motivation and Reliability. A role with real training behind it: add Coachability and Learning. A candidate with a genuinely empty resume: add the No Work History Set. Retail, food service, front desk, or warehouse: add Customer-Facing and Teamwork. Then use the Scorecard with whichever combination you chose. Two sets and thirty minutes is the right size for this hire.
6 Free Question Sets and a Scorecard to Download
Download all six as one Word document or copy the sets you need. Every question in every set carries three things: why it is worth asking, what a strong answer sounds like, and what a weak one sounds like. The last file is the scorecard with a red flag checklist.
Download All 6 Entry Level Question Sets
Core, reliability, coachability, no work history, customer-facing, and a scorecard with red flags. All in one DOCX.
Set 1: Core Entry Level Questions
The eight questions that work for any first job: why this role, what they think it involves, learning something new, responsibility anywhere, taking correction, and availability. Start here for every candidate.
Core Entry Level Interview Questions
ENTRY LEVEL INTERVIEW: CORE QUESTIONS
Candidate: __
Interviewer: __
Date: __
Role: __
Use this set for any first job. Ask all eight of every candidate, in the same
order, and take notes as you go.
1. What made you apply for this job specifically?
Why ask it: it separates the candidate who wants this job from the candidate
who applied to forty postings in one evening. At entry level almost nobody has
relevant experience, so genuine interest is one of the few real signals left.
A strong answer: names something concrete about your business, the location,
the schedule, or the kind of work, and connects it to what they want.
A weak answer: cannot recall what the posting said, or gives a reason that
would fit any employer in town.
2. Walk me through what you think this job involves day to day.
Why ask it: it tests whether they read the posting and hold a realistic picture
of the work. Most first-month quits happen because the job was not what the
person pictured, and this question surfaces that gap before you train them.
A strong answer: describes the actual tasks in plain language and asks a
clarifying question or two about the parts they are unsure of.
A weak answer: a generic description that could fit any job, or duties that
were never in the posting.
3. Tell me about a time you had to learn something new quickly.
Why ask it: for the first month, learning is the job. This is the closest thing
to a performance predictor you get from someone with no employment record.
A strong answer: names the specific thing, how they went about learning it, how
long it took, and how they knew they had it.
A weak answer: no example at all, or a story where somebody else did the
learning and the candidate watched.
4. What is the most responsibility you have been given, anywhere?
Why ask it: it deliberately opens the evidence up beyond paid work, so a
candidate with no resume can still show you something real. School, sports, a
family business, and caregiving all count.
A strong answer: a specific responsibility with a real consequence attached,
held over a stretch of time, described without inflation.
A weak answer: a title with no duties behind it, or an example the candidate
cannot describe once you ask a follow-up.
5. How do you handle being told you did something wrong?
Why ask it: you will correct this person often in the first ninety days.
Coachability decides whether that goes well or turns into a standoff.
A strong answer: a real example of feedback they received, what specifically
changed afterward, and no defensiveness in the retelling.
A weak answer: claims they have never been corrected, or the story is really
about how the other person was unfair.
6. What kind of work do you not enjoy?
Why ask it: every entry level job has a repetitive or unglamorous part, and it
is cheaper to hear about the mismatch now than in week three.
A strong answer: honest and specific, paired with a clear statement that they
can still do it when it is part of the job.
A weak answer: "nothing," which is a rehearsed non-answer, or a dislike that
happens to be the main duty of the role.
7. What questions do you have about the job?
Why ask it: preparation and real interest show up here more than anywhere else.
A candidate with no questions has usually not thought about the work.
A strong answer: practical questions about training, the schedule, who they
report to, and what a good first month looks like.
A weak answer: none at all, or only questions about time off before they have
asked anything about the work itself.
8. When could you start, and what does your availability look like?
Why ask it: schedule fit sinks more entry level hires than skill ever does, and
this surfaces school terms, second jobs, and travel time early.
A strong answer: specific dates and hours, offered without hedging.
A weak answer: vague availability that shifts when you ask a second time.
NOTES
[Capture exact phrases the candidate used, plus anything to verify later.]
Set 2: Motivation, Reliability, and Schedule Fit
The attendance set. Commute plan, what time they would leave home, commitments kept when it was inconvenient, what they do when they are going to be late, and the informal work most candidates never think to mention.
Motivation, Reliability, and Schedule Fit Questions
ENTRY LEVEL INTERVIEW: MOTIVATION, RELIABILITY, AND SCHEDULE FIT
Candidate: __
Interviewer: __
Date: __
Attendance, not ability, is the most common reason an entry level hire does not
work out. These questions test whether the person can actually be here.
1. How will you get here, and how long does the trip take?
Why ask it: getting to work is the single most common practical reason a first
job ends early. Keep the question about the commute itself, ask it of every
candidate, and do not treat it as a proxy for anything else.
A strong answer: a specific route and travel time, with a backup plan if the
usual one falls through.
A weak answer: has not thought about it, or the plan depends on someone else
who has not agreed to it.
2. What time would you need to leave home to be here at the start of a shift?
Why ask it: it forces the abstract answer into an actual number. People who
have done this arithmetic tend to arrive on time.
A strong answer: an immediate, concrete time, usually with a margin built in.
A weak answer: a guess that does not match the travel time they just gave you.
3. Tell me about a commitment you kept when it was inconvenient.
Why ask it: it is the reliability question that does not require a job history.
Practices, rehearsals, a shift covering for a friend, and family obligations
all work as evidence.
A strong answer: a specific commitment held over time, with the inconvenient
part described honestly.
A weak answer: a one-off favor, or a general claim to be reliable with nothing
behind it.
4. Have you ever had to be in the same place at the same time every day?
Why ask it: for many entry level candidates, school or a team is the only
structure they have kept, and it tells you what a fixed schedule feels like to
them.
A strong answer: describes the routine and what they did to keep it.
A weak answer: has never held a fixed commitment and does not seem to see why
the question matters.
5. Something goes wrong and you are going to be late. What do you do?
Why ask it: you are not testing whether they will ever be late. You are testing
whether they will tell you as early as possible, which is the difference
between an inconvenience and a hole in the schedule.
A strong answer: calls or messages a named person as soon as they know, gives
a realistic new arrival time, and offers to make it up.
A weak answer: says it would never happen, or plans to explain after arriving.
6. Are there any days or hours you are not available to work?
Why ask it: schedule conflicts are better found now. Ask this of every
candidate in the same words, take the answer at face value, and do not probe
into the reason behind it.
A strong answer: clear, specific limits stated up front.
A weak answer: full availability that quietly narrows once an offer is made.
7. What would you like to be doing a year from now?
Why ask it: training an entry level hire costs real weeks, so you want someone
whose plan is compatible with staying long enough to repay that.
A strong answer: honest about direction, and consistent with the role lasting
more than a season.
A weak answer: a plan that clearly ends in six weeks, or an answer engineered
to be what they think you want.
8. Have you worked anywhere before, even informally?
Why ask it: babysitting, yard work, a family shop, tutoring, and helping at a
market are all real work, and many candidates leave them off an application
because they assume they do not count.
A strong answer: volunteers the informal work and can describe what they
actually did and who relied on them.
A weak answer: nothing surfaces even after you name examples.
NOTES
[Note availability and start date exactly as stated.]
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
How fast they pick things up and how they take correction: teach me something you know, the first attempt that went wrong, what they do when stuck and nobody is free, and how they would judge their own first month.
Coachability, Learning, and Feedback Questions
ENTRY LEVEL INTERVIEW: COACHABILITY, LEARNING, AND FEEDBACK
Candidate: __
Interviewer: __
Date: __
For a first job, how fast someone learns and how they take correction matter
more than anything on the application.
1. Teach me something you know how to do.
Why ask it: it is the most useful question in this whole set. Explaining a
process reveals comprehension, sequencing, and patience all at once, and the
candidate cannot rehearse it.
A strong answer: picks something real, starts at the beginning, checks whether
you are following, and does not skip the boring steps.
A weak answer: rushes, assumes knowledge you do not have, or cannot break the
task into steps at all.
2. Tell me about a time someone showed you how to do something and you got it wrong the first time.
Why ask it: the first-attempt failure is guaranteed in a first job. You want to
know what happens next.
A strong answer: owns the mistake plainly, describes asking again or practicing
until it stuck.
A weak answer: cannot recall ever getting anything wrong, or the story ends
with the instructions being bad.
3. How do you learn best: watching, reading, or doing?
Why ask it: it is a practical planning question, not a personality test. The
answer tells you how to build their first week of training.
A strong answer: a clear preference with an example of it working, plus
willingness to learn the way your business actually trains.
A weak answer: no idea, and no curiosity about how training will work.
4. You are stuck and the person who could help is busy. What do you do?
Why ask it: this is the judgment question. Guessing on something that matters
and asking about something trivial are both expensive.
A strong answer: tries a reasonable amount on their own, then asks rather than
guessing when the cost of being wrong is real, and says how they would decide
which situation they are in.
A weak answer: always guesses, always interrupts, or freezes and waits.
5. What was the hardest subject or class you took, and how did you get through it?
Why ask it: it substitutes for the work-difficulty question when there is no
work history, and persistence transfers directly to a first job.
A strong answer: names a specific method they used and what changed as a
result, including if the grade stayed mediocre.
A weak answer: dropped it, or the story has no action in it.
6. Have you ever had to follow a written procedure exactly?
Why ask it: most entry level work has steps that cannot be improvised: closing
checklists, food safety, cash handling, safety gear. Some people find that easy
and some find it insulting.
A strong answer: gives an example and treats following the procedure as
obviously correct rather than a constraint.
A weak answer: describes improving on the procedure without telling anyone.
7. At the end of your first month here, how would you know you were doing well?
Why ask it: it tests whether they think in terms of results rather than effort,
and it tells you what they will optimize for.
A strong answer: names observable things: fewer questions on the same task,
finishing on time, being trusted with something unsupervised.
A weak answer: "if nobody complains," or a purely emotional measure.
8. What have you gotten noticeably better at recently?
Why ask it: it looks for a track record of improvement in any domain, which is
the closest proxy you have for how they will grow in the role.
A strong answer: a concrete before and after, with the practice in between.
A weak answer: nothing comes to mind after a long pause.
NOTES
[Record how the candidate explained the teach-me answer, in their words.]
Set 4: No Work History Set
For an application with nothing on it but school. Situational questions plus evidence from teams, volunteering, and caregiving, with a note on how to score a hypothetical answer without being won over by a pleasant one.
No Work History Set: School, Team, Volunteer, and Situational Questions
ENTRY LEVEL INTERVIEW: NO WORK HISTORY SET
Candidate: __
Interviewer: __
Date: __
Use this set when there is no employment history to ask about. Behavioral
questions need a comparable past experience, so lean on situational questions
and on evidence from school, teams, volunteering, and family responsibility.
How to score a situational answer: a good one names an action and a person to
tell. A weak one is a value statement such as "I would stay positive."
1. Two people show you the same task differently. What do you do?
Why ask it: it happens in the first week of every job with more than three
employees, and the answer shows whether they resolve or quietly pick a side.
A strong answer: does the task the way they were shown, then asks which method
is the standard, rather than guessing or complaining sideways.
A weak answer: follows whoever seems more senior and never raises it.
2. A customer or a coworker asks you something you do not know. What do you say?
Why ask it: not knowing is the default state of a new hire. What they do with
it decides whether customers get bad information.
A strong answer: says plainly that they will find out, then asks someone and
comes back with the answer.
A weak answer: makes something up, or leaves the person waiting with no
explanation.
3. You finish everything you were assigned and your manager is busy. What next?
Why ask it: initiative is easy to claim and hard to fake in a specific
scenario, and idle time is where entry level hires either grow or drift.
A strong answer: names something visibly useful they could start, and confirms
it with the manager at the first opening.
A weak answer: waits to be told, or invents a task that would need approval.
4. Tell me about a group project or team you were part of. What was your part?
Why ask it: it is the teamwork evidence available to nearly every candidate,
including one who has never been paid for anything.
A strong answer: describes their own contribution specifically and credits
others accurately.
A weak answer: describes what the group did with no trace of what they
personally did.
5. Describe something you had to keep at before you were any good at it.
Why ask it: the first two weeks of a new job feel exactly like this, and
tolerance for being bad at something new is a real predictor of getting through
training.
A strong answer: a specific skill, the awkward early stage described honestly,
and what kept them going.
A weak answer: only lists things that came naturally.
6. Have you been responsible for another person? What did that involve?
Why ask it: caregiving for a sibling, coaching younger kids, or running a
practice is genuine responsibility that never appears on a resume.
A strong answer: concrete duties, real consequences, sustained over time.
A weak answer: cannot describe what the responsibility actually required.
7. At the end of the day you realize you made a mistake and nobody noticed. What do you do?
Why ask it: this is the integrity question in the form of an ordinary work
scenario, and it is far more revealing than asking whether they are honest.
A strong answer: tells someone, without much deliberation, and explains why
catching it early is cheaper.
A weak answer: weighs whether it will be discovered, or fixes it quietly in a
way nobody could check.
8. What do you do outside school or work that takes real effort?
Why ask it: sustained effort somewhere is the pattern you are hiring for, and
this is the friendliest way to find it.
A strong answer: something with regular hours behind it and visible progress.
A weak answer: nothing, and no interest in the question.
NOTES
[Situational answers: write down the action they named, not your impression.]
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
For retail, food service, front desk, and warehouse hires: the upset customer, saying no, the busiest hour, the coworker not pulling their weight, and an honest question about repetitive work. Pair it with the core set.
Customer-Facing and Teamwork Set for Frontline Roles
ENTRY LEVEL INTERVIEW: CUSTOMER-FACING AND TEAMWORK SET
Candidate: __
Interviewer: __
Date: __
Use this set for retail, food service, front desk, warehouse, and any first job
where the new hire is in front of customers or working a shift alongside
others. Pair it with the core set.
1. A customer is already upset before you have said a word. What do you do?
Why ask it: it is the most common hard moment in a frontline entry level job,
and the instinct shows immediately.
A strong answer: listens first, does not argue, fixes what they can, and gets a
manager for what they cannot, without making the customer repeat themselves.
A weak answer: explains the policy first, or takes the anger personally.
2. How would you tell a customer no?
Why ask it: saying no politely is a learned skill, and a new hire who cannot do
it either breaks your rules or upsets people.
A strong answer: says no clearly, explains what they can do instead, and knows
when to escalate rather than inventing an exception.
A weak answer: avoids saying no, promises something they cannot deliver, or is
blunt to the point of rude.
3. Tell me about working with someone you did not get along with.
Why ask it: shifts are close quarters. You need to know whether friction turns
into a functioning working relationship or into your problem.
A strong answer: keeps the criticism proportionate, describes what they did to
keep the work moving, and does not need to win.
A weak answer: a long grievance, or a claim to get along with absolutely
everyone.
4. It is the busiest hour and three things need doing at once. How do you choose?
Why ask it: prioritization under pressure is the skill that separates a good
frontline hire from an overwhelmed one.
A strong answer: uses a rule that makes sense: the customer in front of them,
anything about safety, anything that gets worse if it waits, and asks when the
call is genuinely unclear.
A weak answer: does whatever is nearest, or freezes and does the easiest thing.
5. What does good service look like to you, as a customer?
Why ask it: everyone has been a customer, so this gives a candidate with no
service experience a fair way to show judgment.
A strong answer: specific behaviors they have noticed and valued, not slogans.
A weak answer: "being friendly," with nothing underneath it.
6. A coworker is not doing their share. What do you do?
Why ask it: how a new hire handles this predicts whether small resentments
reach you as information or as a resignation.
A strong answer: talks to the coworker directly and normally first, and raises
it with a supervisor if it keeps affecting the work.
A weak answer: covers silently and stews, or goes straight over their head on
the first occurrence.
7. Much of this job is repetitive. How do you feel about that?
Why ask it: it invites an honest answer to a question most candidates expect to
have to lie about, and it prevents a week-three surprise.
A strong answer: honest about the boredom and specific about how they keep
quality up anyway.
A weak answer: claims to love repetition, which is rarely true and tells you
nothing.
8. You are asked to do something that seems against the rules. What do you do?
Why ask it: new hires are the most likely to be told "we always do it this
way" by a coworker, and you need to know if they will check.
A strong answer: asks the person, and asks a manager if the answer does not
sit right, without accusing anyone.
A weak answer: goes along with it because someone senior said so.
NOTES
[Note tone and manner, since this is the job in a customer-facing role.]
Set 6: Entry Level Scorecard and Red Flags
Six scoring areas with written anchors for what a 5 looks like at this level, an eight-item red flag checklist, and a decision box that asks for the minimum bar you set before the first interview.
Entry Level Interview Scorecard and Red Flags
ENTRY LEVEL INTERVIEW SCORECARD
Candidate: __
Interviewer: __
Date: __
Role: __
Score each area from 1 (poor) to 5 (excellent) immediately after the interview,
while the answers are fresh. Write the evidence in the candidate’s own words,
not your impression of them. Decide your minimum total before you meet the
first candidate.
SCORING AREAS
Motivation and interest in this job Score: [ 1 2 3 4 5 ]
Evidence: __
Reliability and schedule fit Score: [ 1 2 3 4 5 ]
Evidence: __
Coachability and response to feedback Score: [ 1 2 3 4 5 ]
Motivation: knows what this job is and wants this one, not any job
Reliability: a concrete commute plan and a history of keeping commitments
Coachability: a real example of correction and what changed afterward
Learning: explained something clearly and taught it in order
Communication: plain, direct, comfortable saying "I do not know yet"
Responsibility: a duty with real consequences, held over time
RED FLAGS
[ ] Cannot say anything about your business or the role
[ ] No plan for getting to work, or the plan depends on an unconfirmed favor
[ ] Availability changes between the interview and the offer
[ ] Has never been corrected by anyone, ever
[ ] Blames a teacher, coach, or former manager for everything
[ ] Speaks about customers or coworkers with contempt
[ ] Wants the mistake in the scenario question to stay hidden
[ ] Asks no questions about the work at any point
DECISION
Total score: ______ / 30
Minimum bar set before interviews: ______
Overall: [ ] Strong yes [ ] Yes [ ] No [ ] Strong no
Strengths: __
Concerns: __
Training this person would need first: __
Interviewer signature: __
Note: if more than one person interviews, everyone scores independently before
the group talks, so the loudest opinion does not set the tone.
What a Good Answer Sounds Like
A good entry level answer is specific, has an action in it, and does not need to be impressive. You are listening for concrete detail and honest self-report, not polish. Polish at this level usually means somebody rehearsed with a relative, which tells you very little.
Teach me something you know how to do.
Why ask it: Explaining a process reveals comprehension, sequencing, and patience at once, and it is the one question in the set nobody can rehearse.
Strong answer: Picks something real, starts at the beginning, keeps the steps in order, checks whether you are following, and does not skip the dull parts. The content does not matter. The structure of the explanation does.
Weak answer: Rushes, assumes knowledge you do not have, or cannot break a familiar task into steps at all. That is usually how their training will go too.
You are stuck and the person who could help is busy. What do you do?
Why ask it: Guessing on something expensive and interrupting over something trivial are both costly, and this is the judgment call a new hire faces daily.
Strong answer: Tries a reasonable amount alone, then asks rather than guessing when the cost of being wrong is real, and can say how they would tell the two situations apart.
Weak answer: Always guesses to avoid looking slow, always interrupts to avoid being wrong, or waits with nothing happening until someone notices.
At the end of the day you realize you made a mistake and nobody noticed. What do you do?
Why ask it: It is the integrity question dressed as an ordinary work scenario, which makes it far harder to answer with a rehearsed line about honesty.
Strong answer: Tells someone without much deliberation, and can explain why catching it early costs the business less than finding it a week later.
Weak answer: Weighs whether it will be discovered, or fixes it quietly in a way that leaves no trace anyone could check.
The most useful follow-up across all of these is simply what happened next. Candidates who lived through the story keep going without effort. Candidates who assembled it for the interview run out of detail almost immediately, and that gap is more reliable than anything in the first answer.
Signals to Probe For and Red Flags
Weigh a handful of signals heavily and ignore most of the rest. Nervousness, a weak handshake, and a rehearsed opening tell you nothing about a nineteen year old at their first interview. A missing plan for getting to work tells you a great deal.
Reliability signals
A commute plan with an actual time in it
A commitment kept when it was inconvenient
Tells someone early when something goes wrong
Coachability signals
A real example of being corrected
Owns the first attempt that went wrong
Asks instead of guessing when it matters
Communication signals
Explains a process in order, without skipping
Comfortable saying they do not know yet
Asks practical questions about the work
Red flags
Nothing specific about your business or the role
Has never been corrected by anyone
Availability shifts after the offer is made
Two Red Flags That Are Worth More Than the Rest
First, a candidate who has never been corrected by anyone. Nobody gets to a first interview without having been told they got something wrong, so the claim usually means they did not register it or will not admit it, and both are expensive when the entire first month is correction. Second, availability that changes between the interview and the offer. It rarely narrows once and stops, and the schedule you agreed to is the one you built the shift plan around.
How to Run the Interview
Run it in thirty minutes with prepared questions, in the same order, for every candidate. One round is usually right at this level. The evidence available from a candidate without a work history is limited, and a second round mostly re-collects it while making the candidate travel twice.
Step
What to do
Time
1. Set up
Explain the job in plain terms and what the interview will cover
3 min
2. Core questions
Ask all eight in order, taking notes as you go
12 min
3. Second set
Add reliability, coachability, or the customer-facing set
8 min
4. Their questions
Answer theirs, and note whether they had any about the work
4 min
5. Show the space
Walk them through where they would actually work
3 min
6. Score
Fill the scorecard before the next candidate arrives
3 min
Showing the space is not a courtesy, it is part of the assessment. A candidate who watches the work happening and asks a practical question about it has just given you better information than four more prepared answers would have. A candidate visibly put off by what they see has saved you a hire.
Ask the Practical Questions Out Loud, Early
Commute, availability, and start date belong near the front of the interview, not tacked on at the end. If someone cannot make the schedule work, both of you would rather find out in minute four than after a warm twenty-five minute conversation. Asking these in the same words for every candidate also keeps the comparison clean, and it is the part interviewers most often skip when the rapport is good.
Scoring for Potential, Not Polish
Score six areas from 1 to 5 immediately after each interview, in the candidate's own words rather than your impression of them. At entry level this matters more than for senior roles, because with no work history to anchor the decision, an unstructured interview drifts toward whoever was easiest to talk to.
Scoring area
What a 5 looks like at entry level
Motivation for this job
Knows what this job is and wants this one, not any job
Reliability and schedule fit
A concrete commute plan and commitments kept before
Coachability
A real example of correction and what changed after it
Learning speed
Explained something clearly, in order, checking you followed
Communication and manner
Plain and direct, comfortable saying they do not know yet
Responsibility anywhere
A duty with real consequences, held over a stretch of time
Set the minimum total before you meet the first candidate, and write it down. Deciding the bar after you have met a likeable applicant is how the bar moves. If more than one person interviews, everyone scores alone before the discussion, then you compare written evidence rather than memories.
What the interview relies on
Experienced hire
Entry level hire
Past job performance and results
Situational and hypothetical questions
Evidence from school, teams, or caregiving
Skills tested directly in the interview
Reliability and schedule fit weighted heavily
A scorecard filled in the same day
The pattern is straightforward: an experienced hire is assessed on what they have already produced, and an entry level hire on the raw inputs that produce it. Mixing the two is how interviews for a first job end up testing whether someone has already had one.
Fair, Legal, and Structured Interviewing
Keep every question tied to the job, ask the same ones of everyone, and check the rules that apply when a candidate is under 18. These three cover most of what goes wrong in entry level hiring, and the first two also happen to produce better hires. Read the specifics on questions you cannot ask before you interview.
Ask about the job, not the person
Federal anti-discrimination law, enforced by the EEOC, prohibits basing a hiring decision on protected characteristics, and questions that probe them create risk even when they are asked as small talk. Entry level interviews are where this slips most, because the conversation feels casual and the candidate is often young. Do not ask how old someone is, whether they still live at home, whether they have children or plan to, where they or their parents are from, what they do on Sundays, or anything about a health condition. You may ask whether they can perform the essential functions of the job and whether they are legally authorized to work. This is general information, not legal advice.
Use the same questions for every candidate
A structured interview asks every candidate the same questions in the same order and scores them against the same standard. It is fairer, and it also predicts on-the-job performance better than a conversation that wanders wherever rapport takes it. That matters more at entry level than anywhere else, because with no work history to anchor on, an unstructured interview drifts toward whoever the interviewer happens to click with, which is not a hiring criterion. Write the questions before the first interview, ask them all, and score them the same way. The sets on this page are built to be used exactly like that.
If the candidate is under 18, check the rules first
Entry level often means a first job, and a first job often means a minor. Federal child labor rules under the Fair Labor Standards Act set the floor: 14 is the general minimum age for non-agricultural work, 14 and 15 year olds may not work during school hours and face daily and weekly hour caps plus time-of-day limits, and hazardous occupations are off limits until 18. States frequently set stricter limits and many require a work permit or age certificate, so check your state agency too. Confirm the rules before you make the offer, not after. This is general information, not legal advice.
Expect first-job paperwork to take longer
A first-time worker often has no driver license and no passport, which is where I-9 completion stalls in small businesses. USCIS allows a combination of documents, and for a minor there are specific alternatives when List B identity documents are unavailable, so read the acceptable documents list before the first day rather than improvising at the counter. Tell the candidate at the offer stage exactly what to bring. The same applies to the W-4 and any state forms: a first-time employee has usually never filled one in, so plan a few extra minutes and a person who can answer questions.
Structured Interviews Beat Conversations, Especially Here
A structured interview asks every candidate the same predetermined questions and rates the answers against the same standard, which the federal government treats as a core selection method precisely because it is more reliable than an open conversation. Asking the same job-related questions of everyone also keeps you inside the EEOC rules on protected characteristics. At entry level the effect is larger, because there is no work history for an unstructured interview to fall back on.
If the candidate is under 18, the federal child labor rules set hour caps, time-of-day limits, and prohibited occupations, and many states add stricter requirements and a work permit. Confirm all of it before the offer. This is general information, not legal advice.
What to Say About Pay
Put the pay in the posting and repeat it in the interview, because an entry level candidate is the least likely to negotiate and the most likely to walk away over a surprise. Several states and cities now require a pay range in the job posting, so check what your state demands before you publish anything.
Entry level is not an occupation in federal wage data, so there is no single benchmark to quote. Look up the actual job title you are hiring for in the Bureau of Labor Statistics wage survey, take the lower percentiles for a role with no experience required, and adjust to your local market and your state or city minimum wage, whichever is higher than the federal floor.
Say the Number Twice
Give the hourly rate in the posting and again in the first few minutes of the interview, along with the expected schedule and how many hours a week the role actually runs. First-time workers frequently do not know to ask, and a candidate who accepts an offer without understanding the hours is a candidate who quits in week two. Applicant tracking is coming soon to FirstHR. Pay transparency in the posting is the part you control today.
Hiring Entry Level Without HR
A large employer runs entry level hiring through a recruiter, a phone screen, and a prepared panel. A small business runs it through the owner, in the back office, between everything else, and often decides the same day. That reality is exactly why the prepared question set earns its keep here.
You are interviewing between everything else you do that day
A large employer screens entry level candidates through a recruiter, a phone screen, and a panel with prepared questions. A small business owner interviews in the back office between shifts, often minutes after meeting the person. That is exactly why a fixed question set helps more here than anywhere: you do not have to invent questions on the spot, you cannot forget the reliability ones, and every candidate gets the same interview whether they came in at 9 a.m. or at closing. Print one set, ask it in order, and score it before the next person walks in.
The resume tells you almost nothing, so the interview has to do all the work
With an experienced hire, the work history carries a lot of the evaluation. At entry level there is often nothing on the page except school and an address, which means the interview is your entire assessment. The response is not to interview longer, it is to interview for different evidence: responsibility held anywhere, a commitment kept when it was inconvenient, a time they were corrected and changed, and how clearly they can explain something they already know. All four are available to a candidate who has never been paid for anything.
The cost of an entry level hire is the training, not the wage
An entry level role is cheap to pay and expensive to fill twice, because the real investment is the two to four weeks somebody experienced spends teaching. That is the number to protect, and it is why reliability and coachability outrank everything else on the scorecard. Once you choose someone, FirstHR covers the part after the decision: send the offer for e-signature, run the new hire paperwork and the onboarding workflow, assign training modules so the person teaching is not starting from scratch, and keep the signed documents on the employee profile. Applicant tracking is coming soon to FirstHR.
The other thing worth borrowing from larger employers is the reference call. For an entry level candidate the reference is a teacher, a coach, or a family they babysat for, and those calls are unusually candid. A single reference check is often worth more than a second interview round at this level.
From Interview to First Week
The interview decides who you hire. The first week decides whether the hire works. For a first-time employee, that means a clear offer letter stating pay, schedule, and start date, an explicit list of what to bring for the I-9, and a named person responsible for training them.
Pick the sets before you post
Choose the core set plus one other that matches the role, and decide the minimum score you will accept before you meet anyone you like.
Score right after each interview
Fill the scorecard while the answers are fresh, in the candidate’s own words, and keep the completed forms with your hiring records.
Send a clear offer
Confirm pay, schedule, start date, and exactly which documents to bring on day one, since a first-time worker has never done this before.
Train deliberately in week one
Name who trains them, what they should be able to do unsupervised by Friday, and when you will check in. This is where the hire is actually made.
Expect the new hire paperwork to take longer than usual: a first-time worker has never completed a W-4, and often has neither a driver license nor a passport, so read the acceptable documents list before day one rather than working it out at the counter.
FirstHR handles the part that starts once you have chosen someone: the offer sent for e-signature, the new hire paperwork collected and stored on the employee profile, an onboarding workflow so nothing gets forgotten in a busy week, and training modules so the person doing the teaching is not inventing it each time. Applicant tracking is coming soon to FirstHR. For now, pair it with whatever you use to collect applications. More hiring documents live in the hiring templates library.
If the role you are filling does not have a posting yet, the same structure applies to writing it. Our job description templates for customer service representatives and warehouse associates cover two of the most common entry level hires, and both pair with the question sets above.
Key Takeaways
Assess motivation, reliability, coachability, learning speed, and responsibility shown anywhere, not skills you can teach in a week.
Reliability comes first: attendance rather than ability is what usually ends a first job, so ask about the commute and availability early.
Use situational questions where there is no work history, and score them by the action named, not by how positive the answer sounds.
Ask the candidate to teach you something they know; it reveals comprehension and sequencing that no resume would show.
Score six areas from 1 to 5 right after each interview and set your minimum total before you meet the first candidate.
Check federal and state child labor rules before making an offer to anyone under 18, since hours and duties are restricted.
Frequently Asked Questions
What questions should I ask an entry level candidate?
Ask questions that produce evidence a person without a job history can actually give you. The strongest six are: what made you apply for this job specifically, walk me through what you think the job involves day to day, tell me about a time you had to learn something new quickly, what is the most responsibility you have been given anywhere, how do you handle being told you did something wrong, and teach me something you know how to do. Each one is answerable from school, sports, volunteering, or family responsibility, so a candidate with an empty resume is not disqualified by the format of your questions. Add the practical ones about commute, availability, and start date, because schedule fit ends more entry level hires than skill does. Ask the same set of every candidate and score it.
How do you interview someone with no work experience?
Change the evidence you ask for rather than lowering the bar. Behavioral questions that start with tell me about a time at work do not work when there is no work, so lean on situational questions and on experience from school, teams, volunteering, and caregiving. Ask what happens when two people show them the same task differently, what they do when they finish everything and the manager is busy, and what they would do about a mistake nobody noticed. Score a situational answer by whether it names a concrete action and a person to tell, not by how positive it sounds. Then test learning directly by asking the candidate to teach you something they already know, which reveals comprehension and sequencing that no resume would have shown you anyway.
What should I look for in an entry level hire?
Reliability, coachability, learning speed, communication, and evidence of responsibility somewhere. Reliability comes first because attendance, not ability, is the most common reason a first job ends: ask how they will get to work, what time they would leave home, and what they do when they are going to be late. Coachability is second because you will correct this person constantly in the first ninety days, so ask for a real example of feedback and what changed afterward. Learning speed matters because for the first month, learning is the job. Skills you can teach in a week are not a selection criterion, so do not weight them. Score all five areas separately on a rubric so one confident answer does not carry a candidate who is weak everywhere else.
Are behavioral or situational questions better for entry level candidates?
Situational questions carry more weight at entry level, with behavioral questions used wherever the candidate has any comparable experience to draw on. A behavioral question asks about a real past event, which is the stronger predictor in general, but it only works if the candidate has lived through something comparable. A situational question poses a scenario and asks what they would do, which is available to everyone. The practical approach is to ask behavioral questions about school, teams, volunteering, and family responsibility, where most candidates do have material, and to use situational questions for anything specific to the workplace. When scoring a situational answer, look for a named action and a named person to escalate to. An answer built out of attitude words is not an answer.
What questions are illegal to ask in an entry level interview?
Do not ask about characteristics protected under federal law, which the EEOC enforces: race, color, religion, sex including pregnancy, national origin, age, disability, or genetic information. Entry level interviews are where these slip in most easily, because the tone is casual and the candidate is often young: avoid asking how old someone is, whether they live with their parents, whether they have or plan to have children, where their family is from, what they do on Sunday mornings, or about any health condition. You may ask whether they can perform the essential functions of the job, whether they are legally authorized to work, and what their availability is, as long as you ask every candidate the same way and do not probe the reason behind a stated limit. This is general information, not legal advice.
Can I hire someone under 18 for an entry level job?
Yes, within limits, and the limits are worth checking before you make the offer. Under the federal Fair Labor Standards Act, 14 is the general minimum age for non-agricultural work, and 14 and 15 year olds may not work during school hours, are capped on daily and weekly hours, and face restrictions on how early and how late they may work. Hazardous occupations are prohibited until 18, which rules out many warehouse, machinery, and driving tasks. States often impose stricter rules and many require a work permit or age certificate issued through the school, so check your state labor agency alongside the federal rules. None of this changes your interview questions. It changes the schedule and the duties you can offer. This is general information, not legal advice.
How long should an entry level interview be?
Thirty minutes is usually enough, and one round is often the right number. That is time for eight to ten prepared questions with follow-ups, plus the candidate’s own questions and a walk through the space where they would work. Longer interviews at this level rarely produce better information, because the evidence available from a candidate with no work history is limited and you exhaust it fairly quickly. Spend the time you save on scoring properly and on checking one reference, such as a teacher, coach, or a person they babysat for, which tends to be more informative than a fourth round of questions. If two people will interview, do it in one session rather than two visits, since a candidate with no transportation of their own may struggle to come back twice.
Should I use a scorecard for entry level hiring?
Yes, and it matters more here than for senior roles. With no work history to anchor the decision, an unstructured entry level interview drifts toward whoever the interviewer found easiest to talk to, which is a preference rather than a hiring criterion. A scorecard fixes what you are rating in advance: motivation, reliability, coachability, learning speed, communication, and responsibility shown anywhere, each from 1 to 5 with written evidence rather than an impression. Set your minimum total before you meet the first candidate, and if more than one person interviews, have everyone score independently before the group discusses. It takes about three minutes per candidate and it is the difference between comparing evidence and comparing memories a week later.
