How to interview a freelancer
On this page
- What's actually different about this interview
- Verify what they actually did on portfolio work
- Scoping and pricing: how they think about a project before it starts
- Availability and competing clients
- A freelancer engagement scorecard
- A worked example
- References, for freelancers specifically
- Worker classification: a brief note, not legal advice
- A checklist before you engage a freelancer
- Questions people ask
Interview a freelancer by testing what a full-time interview usually skips: exactly what they personally did versus a team on their portfolio work, how they scope and price a project before starting, their real availability across other clients, and how they communicate async without a daily check-in to catch problems early. Skill questions matter too, but the engagement usually fails or succeeds on these operational specifics, not on raw ability.
What's actually different about this interview
A freelancer interview looks similar to a regular one on the surface, same portfolio review, same skill questions, but the things that predict whether the engagement goes well are different. You're not managing this person day to day the way you would an employee, so you can't course-correct with a quick hallway conversation. Scope, communication style and availability have to be right from the start, because you have much less room to fix a mismatch mid-project than you would with someone on your own team.
Verify what they actually did on portfolio work
A portfolio shows the output, not who produced which part of it. This is the single most common gap in freelancer interviews: hiring managers admire a piece of work without confirming the freelancer's actual role in producing it.
| Question | Strong answer | Red flag |
|---|---|---|
| Walk me through this piece specifically. What did you personally do versus anyone else involved? | A clear breakdown: what was theirs, what was a collaborator's or client's, told without hedging | Vague ownership, or the answer changes when you ask a follow-up about a specific detail |
| What was the brief for this, and where did you push back on it or change it? | Specific example of professional judgment applied to the client's original ask | No real answer, suggesting they executed literally without judgment, or take full credit for a brief someone else wrote |
| What would you have done differently if you were doing it again? | A specific, honest critique of their own work | Nothing, or an answer that blames the client entirely for anything imperfect |
Scoping and pricing: how they think about a project before it starts
How a freelancer scopes work tells you more about the engagement than their day rate does.
- "Walk me through how you'd scope this project, step by step." A strong answer breaks the work into phases, names what's included and excluded, and flags where the scope is likely to expand. A weak answer jumps straight to a number with no visible reasoning.
- "What's happened on a past project when the client asked for more than the original scope?" Listen for a described process (a change order, a conversation, a revised quote) rather than either "I just do it" (a scope-creep risk to you later) or "I refuse anything extra" (rigid in a way that may not fit real collaborative work).
- "How do you price: hourly, project rate, or a retainer, and why that model for work like this?" A considered answer connects the pricing model to the type of work and the risk of scope changing. Someone who hasn't thought about which model fits which situation is more likely to produce billing disputes later.
Availability and competing clients
Freelancers, by the nature of the work, have other clients, and that's normal, not a red flag on its own. What matters is whether they're specific and honest about it.
| Question | Strong answer | Red flag |
|---|---|---|
| What does your client load look like right now, and how much time can you realistically give this? | A specific number of hours or days per week, with an honest note about how firm that is | Vague reassurance ("I'll make time") with no real number |
| What happens on your end if two clients need you urgently at the same time? | A described prioritization approach, even if imperfect, showing they've thought about the conflict | "That won't happen" or no real answer, which predicts you'll be the one finding out the hard way |
| How do you communicate when you're going to miss a deadline? | A specific example of flagging early, with enough notice to adjust | No example, or a story where the client found out only when the deadline had already passed |
A freelancer engagement scorecard
| Dimension | 1 — Weak | 2 | 3 | 4 — Strong |
|---|---|---|---|---|
| Ownership of portfolio work | Can't clearly separate their contribution from a team's | Some clarity, but vague on specifics when pressed | Clear, specific breakdown of their role | Same, plus a candid critique of their own work |
| Scoping and pricing process | No visible process, jumps to a number | Some structure but thin on scope-change handling | Clear phased scoping with a defined change process | Same, plus pricing model matched deliberately to the work's risk profile |
| Availability honesty | Vague reassurance, no real numbers | Some specifics but no plan for conflicts | Specific availability and a described conflict-handling approach | Same, plus proactive about flagging capacity issues before they become problems |
| Async communication | No evidence of proactive updates; problems surface late | Communicates but reactively, only when asked | Proactive updates at a reasonable cadence | Same, plus flags risk and deadline slippage early, with options rather than just bad news |
A worked example
Invented, to show the scoping question doing real work. A hiring manager is interviewing a freelance copywriter for a project brief that's fairly loosely defined: "refresh our website copy."
Q: Walk me through how you'd scope this project.
"Before I'd quote anything, I'd want a short call to nail down which pages, roughly how many words per page, and whether this includes new photography direction or just copy. I'd split it into two phases: a discovery and outline phase, priced separately and short, then the actual writing phase priced per page once the outline's approved. That way if 'refresh the website' turns out to mean twelve pages instead of the four I was picturing, we catch that at the outline stage instead of after I've written everything."
Score: 4 on scoping and pricing process. The candidate identified the exact ambiguity in the brief unprompted, proposed a phased approach that protects both sides from scope creep, and explained the reasoning rather than just quoting a number. Compare this to a candidate who simply asks "what's your budget?" with no scoping process at all, a weaker answer even if the eventual number is similar.
References, for freelancers specifically
Ask for references from projects similar in scope to what you need, and ask a more specific question than you would for an employee reference: "tell me about a moment on this project that didn't go smoothly, and how they handled it." A freelancer's day-to-day working relationship with a client is the thing you're actually trying to predict, and a generic "would you hire them again" rarely surfaces it. If a freelancer has done substantial paid work but can't produce a single client willing to talk, ask directly why, rather than letting it pass unaddressed.
Worker classification: a brief note, not legal advice
This is general information, not legal advice. Whether someone can be engaged as an independent contractor rather than an employee depends on facts specific to the engagement and on the rules where you and the worker are located, and those rules vary and change. Confirm your specific situation with your own counsel or tax advisor before finalizing an engagement.
How you interview and then manage a freelancer can affect this. Commonly cited factors include how much control you exercise over how and when the work gets done, whether the work is central to your ongoing business versus a discrete project, and whether the person works for multiple clients using their own tools and schedule. The IRS explains the general framework for distinguishing an independent contractor from an employee on its own site; see the IRS page on independent contractor versus employee (as of September 2026) as a starting point, not a final answer for your situation.
In practice, this means the questions above are worth asking for classification reasons as well as quality ones: a freelancer who sets their own schedule, uses their own tools, and works for multiple clients looks more like a genuine independent engagement than one you direct hour by hour the way you would an employee.
A checklist before you engage a freelancer
- You've confirmed what they personally did on the portfolio work you're evaluating, not just admired the output.
- You've heard a real scoping and pricing process, not just a quoted number.
- You have a specific availability commitment and a plan for how conflicts with other clients get handled.
- You've checked at least one reference with a specific, not generic, question.
- You've thought about how the engagement is structured (control, schedule, tools) with classification risk in mind, and confirmed your approach with your own advisor where it matters.
- A written agreement covers scope, deliverables, payment terms and IP ownership before work starts.
If you run freelance engagements alongside full-time hiring, keeping the interview structured the same way helps: Interview Signal builds a live question guide from the project brief and produces a scorecard with the freelancer's own answers checked against the transcript, so the scoping and availability commitments above are on record, not just remembered.
Questions people ask
How is interviewing a freelancer different from interviewing an employee?
The core skill questions are similar, but a freelancer interview needs to cover things an employee interview doesn't: exactly what they own versus a team, availability across other clients, how they scope and price work, and how you'll actually control the engagement without controlling their schedule and methods, which affects worker classification.
Should I ask a freelancer for references?
Yes, ideally from clients on work similar in scope to what you need, and ask the reference a specific question about a project that didn't go smoothly, not just whether they were happy overall. A freelancer with no client willing to talk is worth a direct question about why.
What's the biggest interview mistake hiring managers make with freelancers?
Evaluating portfolio work without confirming what the freelancer actually did on it versus a team or another contractor. A polished piece in a portfolio can represent a small part of someone's actual contribution.
Do I need a written contract for a short freelance engagement?
Yes, even for something brief. Scope, deliverables, payment terms and IP ownership in writing protect both sides and matter more, not less, on short engagements where there's less time to sort out a misunderstanding as you go. This isn't legal advice; have your contract reviewed for your situation.