# Interview Questions for Hourly Jobs

> Most hourly interviews ask questions that cannot be answered wrongly. A question is only worth asking if a weak candidate would answer it differently from a strong one.

Author: Kariaa Research
Published: 2026-08-15
Category: Guides
Reading time: 9 min read
Canonical URL: https://www.kariaa.com/reports/interview-questions-for-hourly-jobs

---

import { CompareColumns, RankedList, FlowSteps, Takeaways, FAQ } from "@/lib/report-charts";

Ask a candidate whether they work well under pressure and they will say yes. Ask
whether they are reliable and they will say yes. Ask about their greatest weakness and
they will produce something rehearsed, and you will have learned that they prepared.

**A question is only worth the minute it costs if a weak candidate would answer it
differently from a strong one.** Most hourly interview questions fail that test, which is
why interviews so often end with a general feeling rather than a decision.

## The one rule that fixes most interviews

Ask about what happened, not about what someone would do.

A hypothetical invites the answer the candidate believes you want, and everybody knows
what you want. A specific past event has to be remembered, and remembering produces
detail: names, times, what went wrong, what they actually did next. Detail is very hard to
manufacture on the spot and easy to hear when it is missing.

<CompareColumns
  left={{
    title: "Questions that cannot fail",
    items: [
      { label: "Are you reliable?" },
      { label: "How do you handle pressure?" },
      { label: "What would you do if a shift ran over?" },
      { label: "Are you a team player?" },
      { label: "Why do you want this job?" },
    ],
  }}
  right={{
    title: "Questions that separate",
    items: [
      { label: "Walk me through your last shift" },
      { label: "Tell me about the busiest day you worked" },
      { label: "When did a shift actually run over?" },
      { label: "Who covered for you last time you were sick?" },
      { label: "What did your last supervisor rely on you for?" },
    ],
  }}
  caption="The left column is answered identically by every candidate"
/>

## Questions worth asking, and what each one is for

<RankedList
  items={[
    {
      label: "Walk me through your last shift, start to finish",
      note: "The single most useful question in hourly hiring. Someone who has done the work describes it in sequence with specifics. Someone who has not describes it in adjectives. It also surfaces pace, tools and responsibilities without a single leading question.",
    },
    {
      label: "What time did you leave the house for that shift?",
      note: "A commute question disguised as a logistics question. It reveals the real travel time, the mode of transport, and whether the schedule you are offering is survivable, which is the most common cause of an early exit.",
    },
    {
      label: "Tell me about a time the work did not go to plan",
      note: "Everyone has one. A candidate with no example is either very new or is managing you. Listen for whether they describe what they did rather than what someone else failed to do.",
    },
    {
      label: "Who covered for you the last time you could not make a shift?",
      note: "Asks about reliability sideways. It establishes that absences happen, which makes an honest answer easier, and the answer tells you how they handle one.",
    },
    {
      label: "What did your last supervisor come to you for?",
      note: "Better than asking about strengths, because it requires a real relationship to answer. Vague answers here are informative in themselves.",
    },
    {
      label: "What would make you leave a job like this in the first month?",
      note: "Blunt, and candidates answer it honestly far more often than you would expect. It surfaces the deal-breaker you were going to discover in week three anyway.",
    },
  ]}
  caption="Six questions, each doing a job that the generic version does not"
/>

## Ask the disqualifying facts first

Interview time is expensive and finite. Spending it on someone who cannot work the shift
the role exists to cover is the most common way an hourly interview is wasted.

**Confirm the deciding facts in the first two minutes: the actual schedule, the start
date, the pay expectation, and anything the role legally requires.** None of them need an
interview to establish, and any one of them can end the process. That ordering is the
same principle set out in [How to Screen Job
Applicants](/reports/how-to-screen-job-applicants).

<FlowSteps
  steps={[
    { label: "Confirm the facts", sub: "Shift, start, pay, license" },
    { label: "Walk through a real shift", sub: "Sequence and detail" },
    { label: "Probe one thing that went wrong", sub: "What they did" },
    { label: "Their questions", sub: "Often the best signal" },
    { label: "Say what happens next", sub: "And by when" },
  ]}
  note="Roughly twenty minutes. A longer hourly interview rarely produces a better decision."
  caption="An interview that fits the role it is for"
/>

## What the candidate asks you is evidence too

The questions a candidate asks are unrehearsed in a way their answers are not.

Someone asking who they report to, how the schedule is published, what happens when
somebody calls out, and whether overtime is voluntary has done this work before and is
checking the things that actually determine whether a job is liveable. Someone with no
questions at all has either been told not to ask or is not seriously considering the role.

**Treat the absence of questions as information rather than as politeness.** It is one of
the few unguarded moments in an interview.

## Questions to leave out

Some standard questions are worse than useless because they invite an answer that cannot
be checked and then feel like evidence.

Anything about someone's personal circumstances is both legally risky and beside the
point. Questions about family, childcare, health, age, citizenship beyond confirming
authorization to work, or living arrangements should not be asked. If schedule
availability matters, ask about availability directly, which is the thing you actually
need to know and is entirely legitimate to establish.

**Where a question touches employment law, the safe version asks about the requirement
rather than the person.** Ask whether someone can work the required shift, not why they
might not be able to. This is general practice rather than legal advice, and anything
touching protected characteristics is worth confirming with counsel in your jurisdiction.

## Score against the criteria, not against each other

The last failure is comparative. Interviewing six people in a day produces a ranking of
those six, which is not the same as knowing whether any of them can do the job.

Write down what a pass looks like before the first interview and mark each candidate
against it independently. That is what makes a decision defensible a week later when the
memory of the room has faded, and it is what stops the strongest interviewer from beating
the strongest worker.

For employers running continuous hourly hiring, the load is rarely the interview itself.
It is getting to a shortlist worth interviewing and replying fast enough that people still
attend. Applications through Kariaa arrive already checked against the requirements you
set, each requirement marked passed or failed on its own with the evidence and a
confidence level attached, and moving someone forward is one of four next steps: a video
interview, a set of questions, a booking, or a message. Candidates reply in WhatsApp or
Telegram.

<Takeaways
  items={[
    "A question is only worth asking if a weak candidate would answer it differently from a strong one. Most standard questions fail that test.",
    "Ask what happened, not what someone would do. Remembering produces detail; hypotheticals produce the answer they think you want.",
    "Confirm shift, start date, pay expectation and any legal requirement in the first two minutes, before spending interview time.",
    "Walk me through your last shift is the highest-yield question in hourly hiring, because doing the work and describing the work are hard to fake apart.",
    "The questions a candidate asks are unrehearsed. No questions at all is information, not politeness.",
    "Score each candidate against written criteria rather than against each other, or you rank the day's interviews instead of the applicants.",
  ]}
/>

<FAQ
  items={[
    {
      question: "What questions should I ask in an interview for an hourly job?",
      answer: "Ask about specific past events rather than hypotheticals. Walk me through your last shift start to finish is the highest-yield question, because someone who has done the work describes it in sequence with detail while someone who has not describes it in adjectives. Follow with a time the work did not go to plan, who covered their last absence, and what their previous supervisor relied on them for.",
    },
    {
      question: "How long should an interview for an hourly role be?",
      answer: "Around twenty minutes is usually enough. Confirm the deciding facts in the first two minutes, spend the middle on one real shift walkthrough and one thing that went wrong, leave room for their questions, and close by saying what happens next and by when. Longer hourly interviews rarely produce better decisions.",
    },
    {
      question: "What interview questions should I avoid?",
      answer: "Anything about family, childcare, health, age, living arrangements, or citizenship beyond confirming authorization to work. These carry legal risk and do not tell you whether someone can do the job. Where availability matters, ask about availability directly rather than about the circumstances behind it. Confirm specifics with counsel in your jurisdiction.",
    },
    {
      question: "Are behavioral interview questions better than hypothetical ones?",
      answer: "Yes, for a mechanical reason. A hypothetical invites the answer the candidate believes you want, and the wanted answer is usually obvious. A past event has to be recalled, and recall produces detail such as names, times and what went wrong. Detail is difficult to invent under time pressure and its absence is easy to hear.",
    },
    {
      question: "How should I compare candidates after interviewing several?",
      answer: "Score each one independently against criteria written down before the first interview, rather than ranking them against each other. Comparative scoring tells you who interviewed best on that day, which is not the same as who can do the job, and it leaves the decision hard to justify a week later once the impression has faded.",
    },
  ]}
/>

---

*Written by the team at **Kariaa**. Learn more at [www.kariaa.com](https://www.kariaa.com).*