Questions to Ask a Freelancer Before Hiring: 18 That Work

Most first calls with freelancers follow the same script. The client talks about the project for ten minutes, the freelancer talks about themselves for ten minutes, then price and start date. Both sides hang up liking each other. Neither knows whether the work will go well.

The problem is the questions. “Do you have experience with React?” gets a yes from everyone. What works are questions about specific past behaviour, or about your project in particular. Those are hard to answer from a script.

Structure the call before you ask anything

Plan 45 minutes and keep the same order for every candidate. Otherwise you will not be able to compare them afterwards.

1. 5 min: the project in briefGoal, current state, deadline. No solution details yet.
2. 10 min: their questionsEarly on purpose. This is where you see how they think.
3. 15 min: track recordOne past project in depth rather than five at a glance.
4. 10 min: working style and capacityCommunication, workload, holidays, cover.
5. 5 min: contract and next stepsBilling, ownership, test task, timeline.

The second block matters most. Give them room to ask and just listen. Someone who asks about your users, your existing stack and who signs off on decisions has actually read your freelance job post and is already thinking about the work.

Questions about your project

These show whether someone understands what you need or is about to sell you a standard package.

1. What would you want to clarify before starting?
2. What is missing from our brief?
3. Where do you see the biggest risk to the deadline?
4. What would you cut if the budget dropped by a third?

Question 4 is the revealing one. Strong freelancers prioritise on the spot and explain why. Weaker ones say it cannot be done, or promise everything anyway.

Questions about their track record

You are not interested in the length of their CV. You want evidence.

5. Show me a project similar to ours. Which part was yours?
6. What went wrong on your last project, and what do you do differently now?
7. Which client relationship did not work out, and why?
8. Which two past clients can I phone?

With 6 and 7, listen to where the blame lands. People who only ever find fault with former clients will describe you the same way one day. Someone who names a mistake of their own and what changed afterwards tends to be the safer bet.

Questions about working style and capacity

Many freelance projects fail for organisational reasons rather than technical ones. These questions surface the risks early.

9. How many clients are you working with right now?
10. How often will I see progress, and in what form?
11. How quickly do you usually reply, and on which channel?
12. How do you track time, and can I see the entries?
13. What happens if you are ill or on holiday?
14. Do you use subcontractors?

There is no correct number for question 9. Three clients at once can work well if each has fixed days. The evasive answer is the problem. Question 14 may feel suspicious, but it is not: you are entitled to know who works on your project and who gets access to your data.

Extra questions by role

The list above fits almost any project. Depending on the role, one or two more questions help, because only someone with real practice can answer them cleanly.

Ask developers how they hand over code: with tests, documentation, access to the repository from day one? And who applies security updates once the project ends. No answer there can leave you with a system nobody wants to maintain.

With designers, ask about revision rounds. How many are included, and what counts as a revision rather than a new concept? It sounds petty. It prevents the most common argument.

For marketing freelancers, ask about the baseline behind any success figure. Doubling clicks means little if the budget tripled at the same time.

Questions about contract, ownership and data

These tend to get skipped in the first call and become expensive later. Settle them before you ask for a quote.

On question 16, US and UK law both leave copyright with a contractor unless there is a written assignment. Our guide on who owns the copyright when you hire a freelancer explains why. On question 17, if GDPR or UK GDPR applies and a contractor processes personal data for you, Article 28 GDPR requires a written processing contract.

Questions you should not ask

Two kinds of question do not belong in the conversation.

The first is anything personal and irrelevant to the job: age, family plans, religion, nationality. Apart from being none of your business, it can create legal exposure. Discrimination law covers many contractors in the UK, and in the US the rules vary by state.

The second kind can blur employment status. “Can you be in the office nine to five every day?” or “Would you join our team meetings like everyone else?” describe an employee. In the US, the IRS looks at behavioural and financial control when it classifies workers. Medium and large UK clients must assess contractors under the off-payroll rules (IR35). German law has its own test, covered in our guide to false self-employment in Germany. Ask about outcomes and deadlines instead. When and where someone works should stay their call.

What to do with the answers

Straight after the call, write a keyword and a score from 1 to 5 next to each question. Not tonight, not tomorrow. By the third call the candidates blur together. Feed the scores into the scorecard from our guide on how to vet a freelancer, and give your top two a paid test project.

If the conversations show your project needs several roles at once, say backend, frontend and hosting, one freelancer may be the wrong shape. Then it is worth comparing with a team such as the one OnlineBuilders puts on software builds.

Your next step: paste the 18 questions into a document with an empty column for notes. Delete the ones that do not fit your project and use the same list in every call.

Questions people ask

How long should a first call with a freelancer last?

Thirty to forty-five minutes is enough. Calls that run longer usually drift into solving your problem, which is work you should be paying for.

Should I send the questions in advance?

Sharing a rough agenda is fair and saves time. Keep the questions about mistakes and about their exact role on past projects for the live call, where unrehearsed answers are more telling.

Is it fine to ask a freelancer about their age or family plans?

No. It is irrelevant to the work and can expose you to discrimination claims in some jurisdictions. In the UK, for instance, the Equality Act 2010 can apply to people engaged on a contract to personally do work.

What if the freelancer barely asks any questions?

Treat it as a warning. Nobody can estimate a project properly without information, so silence usually means a standard package is about to be sold to you.