A working interview is a hiring format in which the candidate performs actual job duties — typically for a half-day or full-day — instead of (or in addition to) answering interview questions. The employer watches you do the work. You see the team, the environment, and the daily reality of the role. Both sides walk away with real signal rather than rehearsed impressions.

The format has been standard in restaurants and hospitality for decades. What's changed in 2025-2026 is its spread into other industries: small tech startups using "contract days" to evaluate engineers, creative agencies running paid trial briefs, retail managers scheduling trial shifts before extending offers, and freelance contractors running short paid pilots before long engagements. If you're job-hunting outside of large corporate hiring funnels, you're more likely than ever to be asked to do one.

This article explains what a working interview actually involves, how the format differs from a regular interview, the legal rules around payment, the industries where it shows up, and how to prepare so the day works in your favor.

What a working interview actually looks like

The shape of the day depends heavily on the industry, but the structure is consistent: arrive, get oriented, do some version of the real work, debrief.

Restaurant trial shift. You arrive 30-60 minutes before service. A senior cook or sous chef walks you through the kitchen, your station, and the menu. You prep your station alongside the team. When service starts, you work a real shift — usually one service period, lunch or dinner — under direct observation. At the end, the chef pulls you aside for a 10-15 minute debrief about pace, cleanliness, technique, and team fit.

Tech startup contract day. You arrive in the morning. The hiring manager introduces you to the team and walks you through the codebase or product. You shadow standup and a few meetings. After lunch, you pair-program on a real (but scoped) ticket with one or two engineers. Late afternoon, you submit a small PR, the team reviews it together, and you have a final conversation about engineering culture and the road ahead.

Creative agency trial brief. You're given a 4-6 hour creative challenge — a real-shaped problem like a campaign concept, a landing page mock, or a brand refresh moodboard. You work in their office, with access to the team for questions. At the end, you present what you made to two or three people and discuss your thinking.

Retail trial. A 3-4 hour shift on the floor with a supervisor shadowing. You greet customers, work the register, restock shelves, and handle a real transaction or two. The supervisor evaluates customer interaction, work ethic, and reliability.

How is a working interview different from a regular interview?

The simplest distinction: in a regular interview, you describe your work. In a working interview, you do the work.

A regular interview is a structured conversation. You answer behavioral and technical questions, possibly solve a problem on a whiteboard or in a coding environment, and the employer infers from your answers whether you can do the job. The signal is indirect. Strong candidates can interview poorly. Weak candidates can interview well.

A working interview removes that gap. The employer sees the actual work product, the pace, the collaboration style, the questions you ask, and how you handle real friction. Candidates also get more honest signal: how the team actually communicates, whether the office is what was described, whether managers are present and engaged.

The trade-offs are real on both sides. Pros: much faster mutual signal, less time spent on rounds of phone screens, fewer surprises in the first week of the actual job. Cons: large time commitment, scheduling friction (especially for employed candidates), and the persistent risk that unpaid versions of the format slip into exploitation.

Larger companies tend to stick with traditional interview loops because legal, scheduling, and compliance overhead make working interviews hard to scale. Smaller employers — restaurants, agencies, early-stage startups, contractors — favor working interviews because they can't afford a bad hire and the format gives them the clearest read.

The legal status of working interviews

In the United States, the Fair Labor Standards Act (FLSA) generally requires that employees be paid for hours worked — and the U.S. Department of Labor has consistently treated working interviews as compensable work when the candidate performs productive duties that benefit the employer.

The practical rule: if you are doing work that the company would otherwise pay an employee to do, you should be paid. That includes prepping food during a shift, writing code that lands in the repo, taking customer payments, or producing creative work the agency might use. Payment can be at the role's normal hourly rate, a flat trial-day fee, or the federal/state minimum wage — but it has to be paid.

The narrow exception is a skills demonstration: a brief, controlled exercise (typically under 30 minutes) that primarily benefits the candidate by showing their capabilities, with no real work output for the employer. A short knife-skills demo, a 20-minute coding screen, or a quick sketch is usually fine. A full shift, a full day of pair-programming, or a 6-hour creative brief is not.

State laws frequently go further. California, New York, Massachusetts, and several other states have explicitly ruled against unpaid working interviews in labor board decisions, and have ordered back-pay in cases where candidates worked unpaid trial days.

Red flags that suggest the format is being abused:

• More than one unpaid day requested
• No discussion of payment upfront
• Work produced during the trial being shipped to clients, customers, or users
• Multiple candidates being run through the same "trial" repeatedly
• Vague or shifting definitions of what the trial covers

Internationally, the rules vary widely. The UK's National Minimum Wage Act has been used to challenge unpaid trial shifts. Canada's provincial labor codes generally require payment. EU member states differ but lean toward payment requirements. The high-level message is the same: if you're doing real work, you should be paid for it.

Industries where working interviews are common

The format clusters in specific industries. Knowing where it shows up helps you anticipate it during your job search.

• Restaurants and hospitality. The original home of the working interview. Trial shifts are nearly universal at independent restaurants and common at chains for chef, line cook, server, and bartender roles.
• Retail. Trial shifts on the sales floor are common at independent stores, boutiques, and some specialty chains. Less common at big-box retailers.
• Tech startups. Contract days and paid trial weeks have become standard at Series A and earlier startups, where a single bad engineering hire can sink the company. Less common at Series B+ where structured interview loops have been built.
• Creative agencies. Paid trial briefs are common for designers, copywriters, art directors, and strategists at small-to-mid-size agencies.
• Technical contracting and freelance. Short paid pilots (a few days to a week) are standard before long contracts, especially for backend, infrastructure, and ML work.
• Healthcare. Less common, but trial shifts appear in dental practices, veterinary clinics, and small medical offices for clinical and admin roles.
• Government and non-profit. Very rare. Hiring rules at most public-sector employers preclude the format.

If you're interviewing in any of the first five categories, expect the working interview question to come up and plan for it.

How to prepare for a working interview

The best preparation treats the trial day as both an interview and your first day at the job.

1. Research the actual daily workflow. Job descriptions describe the role abstractly. Working interviews test the role concretely. Find out what someone in this role actually does hour by hour. Read team blog posts, look at LinkedIn for current and former employees, ask the recruiter for a realistic agenda.
2. Dress for the work environment, not the interview. A chef trial means kitchen whites and proper shoes. A startup contract day means whatever the engineering team wears day-to-day (usually casual). A construction trial means work boots and a hard hat. Showing up in a suit when the team is in t-shirts signals you didn't do the homework.
3. Bring the tools you'd bring on day one. Your own knives, your own laptop with your preferred editor, your portfolio, your references, your notebook. Not having your tools wastes the first hour of the trial.
4. Prepare intelligent questions about the role's daily reality. Not "what's the company culture like" — you'll see that yourself. Better: "How does the team handle conflicting priorities between two senior stakeholders?" or "What's the typical Friday afternoon like?"
5. Plan a short introduction. Two or three sentences. Who you are, what you've done that's relevant, what you're hoping to learn from the day. Practice once out loud.
6. Bring water, snacks, and anything you'd need for a real work day. Trial days are physically and mentally more demanding than regular interviews. Low blood sugar at hour five will sink you.
7. Get a full night's sleep. A working interview is closer to a marathon than a sprint. Going in tired turns a strong candidate into a mediocre one.

For prep tasks that involve research, question generation, or rehearsing the introduction conversation, the AI interview preparation tool is genuinely useful — it helps you simulate the pre-trial conversations and pressure-test the questions you plan to ask.

What to do during the working interview

Behavior during the day shapes the employer's read more than skill alone.

• Arrive on time, dressed correctly. Ten minutes early. Not thirty — that creates awkwardness.
• Ask clarifying questions before tasks. Misunderstanding a task and silently doing the wrong thing is the most common trial-day failure. A 30-second clarifying question is always worth it.
• Show your work. Narrate when appropriate. In a coding trial, talk through your thinking. In a kitchen trial, explain your prep order if asked. The employer is trying to evaluate not just the output but your reasoning.
• Take initiative without overstepping. If you finish a task, ask what's next. If you see something obvious to do (clearing plates, refilling something, picking up an obvious follow-up ticket), do it.
• Be friendly with the team but professional. You're not yet a teammate. Don't gossip, don't complain, don't volunteer opinions about how things should change.
• Take notes if appropriate for the role. Engineering, design, and analytical roles benefit from visible notebook use. Service roles often don't.
• Don't pretend to know things you don't. Faking familiarity with a tool, ingredient, or process is the easiest way to disqualify yourself. Ask.
• Treat it as your first day, not an interview. This single mental shift changes how candidates carry themselves and almost always improves the outcome.

How to evaluate the working interview from your side

The working interview's biggest advantage to candidates is honest signal — and it's the part candidates most often skip. You should walk in with your own evaluation checklist.

• How does the team actually communicate? Are conversations direct, respectful, frequent? Or terse, sarcastic, or absent?
• Is the work environment what was described? The job description said "collaborative team." Are people actually collaborating, or wearing headphones in isolation all day?
• Do people seem to like working there? Watch the room. Energy is hard to fake for a full day.
• Did the role's daily reality match the job description? Senior IC role that turned out to be 60% project management? Server role that turned out to be 80% bussing? These mismatches are the most common cause of three-month turnover.
• Was the trial paid as expected? If the payment terms shift during or after the day, that's data about how the employer handles money in general.
• Was the time commitment honored? If "4 hours" became 8, that's a preview of how they'll treat your time as an employee.

A working interview that you walk out of feeling uncertain is usually a working interview you should decline. Trust the signal.

Red flags during working interviews

Watch for these. Any one is a yellow flag; two or more is a reason to walk.

• Being asked for more than a single day of unpaid work
• No clear plan or agenda for the trial day
• Being left alone without a proper introduction to the team
• Work being shipped to real clients or users during your trial
• The hiring manager unavailable or absent during the day
• No debrief at the end
• Vague or shifting answers about next steps or timeline
• Pressure to commit before you've had time to think
• Comments from existing employees that contradict what the manager has told you
• A trial that suddenly extends to a second unpaid day mid-trial

After the working interview

The day isn't over when you leave. The next 24 hours matter.

• Send a thank-you note. Brief, specific, sent the same day or the next morning. Reference one concrete thing from the day. Two short paragraphs is enough.
• Self-debrief. Write down what went well, what didn't, what surprised you, what concerned you. Do this before anything fades.
• Confirm comp and timeline. If salary or hourly rate hasn't been discussed, raise it now. If a decision deadline wasn't set, ask.
• Compare against other opportunities. If you have other offers or interviews in progress, line them up. The working interview gave you more real signal than any other format — use it.
• Decide whether to accept. If the trial day was a strong yes for both sides, the offer often arrives within 48-72 hours.

When AI assistance fits and when it doesn't

The honest answer: AI tools are far less useful during a working interview than during a traditional interview. You're doing the actual work — coding, cooking, serving, designing — not answering questions an AI could help you frame.

Where AI does help:

• Pre-day research. Summarizing what's been written about the company, the team, and the role.
• Question generation. Drafting and stress-testing the questions you plan to ask.
• Introduction rehearsal. Practicing the short "who I am and why I'm here" intro.
• Post-day debrief. Talking through what happened, evaluating whether to accept, and drafting a thank-you note.
• Salary negotiation. Working out a target number and walk-away point before the offer call.

For the interactive-prep parts of that list, the AI interview preparation tool is the right surface. For real-time question-answering interview formats (phone screens, behavioral rounds, technical rounds), Interview Copilot is the relevant product. For pricing on either, see the pricing page.

A working interview is one of the few interview formats where the candidate genuinely has equal information leverage. Prepare for it like a first day, evaluate it like a job, and treat the signal it gives you — in both directions — as more reliable than anything a traditional interview produces.