30 interview questions to ask freelancers (and what good answers sound like)

A freelance interview is short, so every question has to earn its place. You need to learn three things quickly: can this person do the work, will they communicate well remotely, and are they a good fit for this specific project?

Here are 30 questions, grouped by what they reveal, with notes on what strong answers sound like.

Experience and skills

1. Walk me through the project you are most proud of. What was your role? Listen for precise ownership: "I designed and built the payment integration" rather than "we did a lot of things".
2. What was the hardest problem on that project, and how did you solve it? Strong answers explain the reasoning, not just the solution.
3. What would you do differently if you started that project again? Good freelancers reflect honestly. "Nothing" is a weak answer.
4. Which part of our brief is closest to work you have done before? Tests whether they read the brief and can connect it to real experience.
5. Which part is newest to you, and how would you approach it? Honesty about gaps is a strength.
6. Which tools do you use daily, and why those? Reveals depth and opinions grounded in experience.

Problem-solving

1. Here is a real problem from our product. How would you approach it? Watch how they ask clarifying questions before proposing answers.
2. How do you decide when something is good enough to ship? Look for a balance between quality and pragmatism.
3. Tell me about a time you had to make a decision with incomplete information.
4. How do you approach a codebase, design system or account you have never seen before?
5. What would you look at first in your first week with us?

Remote communication

1. How do you usually report progress to clients? Strong candidates describe a concrete routine: daily notes, weekly demos, written summaries.
2. Show me an example of a status update you have written. One of the most revealing requests you can make.
3. How do you handle being blocked when the team is offline? Look for proposing defaults and moving to other work rather than waiting.
4. How many hours of overlap can you offer with our time zone, and when?
5. How do you prefer to receive feedback?
6. Tell me about a misunderstanding with a client. How did you resolve it?

Reliability and ownership

1. How do you estimate work? What happens when an estimate turns out wrong? Good answers mention breaking work down, adding buffers and flagging slips early.
2. Tell me about a deadline you missed. What happened? Everyone has one. Listen for ownership, not excuses.
3. How do you manage several clients at once?
4. What does a typical working week look like for you?
5. How do you make sure your work is maintainable after you leave? Look for documentation, clean handovers and tests.

Working with the team

1. How do you work with designers / developers / product managers? (pick the relevant ones)
2. Tell me about a disagreement with a teammate or client about an approach. Strong answers show respect, evidence and willingness to commit to a decision.
3. What kind of client or team do you work best with?
4. What frustrates you most in client projects? Reveals values, and possible red flags.

Practical fit

1. When could you start, and what is your availability?
2. What is your rate for this engagement?
3. How long would you ideally like this engagement to last?
4. What questions do you have for us? Thoughtful questions about goals, users and risks are a very good sign.

How to run the interview

• Use the same core questions for every candidate so comparisons are fair.
• Take notes during the call and score immediately afterward, before memories blur.
• Talk less than 30 percent of the time. You are there to listen.
• Follow up on vague answers: "Can you give me a specific example?"
• Leave ten minutes for their questions.

Red flags to listen for

• Vague answers about their own contribution
• Blaming every past client for problems
• Claiming expertise in everything
• No questions about your product or users
• Reluctance to discuss rate, availability or process

Combine interviews with real work

Interviews are only one signal. Pair them with a review of past work and a short practical test or paid trial. See how to vet freelancers and paid trial projects.

Skip the first rounds

HireCurated interviews every freelancer before they join the network. Request a shortlist and spend your interview time only on final candidates.