10 Questions to Ask Any Freelancer Before You Hire Them

A strong portfolio tells you what someone has already finished. It does not tell you how they handle a rushed deadline, a scope change, or a client who needs three rounds of feedback instead of one. That gap is where most freelance hires go wrong. Before you agree to a rate or a start date, ask about the parts of the job a portfolio cannot show: process, availability, ownership of the work, and what happens when the brief changes. The ten questions below cover what to get in writing before you sign anything.

1. Have you worked on a project like this one

A general portfolio proves skill. It does not prove someone has solved your specific problem before. Ask for one or two examples that match your project type, your industry, or your platform, and ask what made those projects hard. A specialist who has hit the same snag you are about to hit will describe the problem in specific terms, not general ones.

For visual and creative roles, a structured, role-specific set of interview questions gives you a consistent way to score every candidate against the same criteria. Twine’s interview questions for freelance graphic designers is a useful template even if the role you are hiring for is different.

2. How do you structure pricing, and what does it include

A day rate and a project rate answer different questions. Ask which one applies, what triggers an extra charge, and whether revisions, source files, and a short onboarding call are included or billed separately. A specialist who answers this clearly, with a number and a scope, is easier to budget against than one who answers with a range.

3. What is your realistic turnaround time

Ask for a specific date, not a general estimate like “a couple of weeks.” Then ask what could push that date back: other clients, revision rounds, or dependencies on your side, like late feedback or missing brand assets. A freelancer who names the risks upfront is telling you they have shipped enough projects to know where delays usually come from.

4. How do you handle revisions and scope changes

Find out how many rounds of feedback are included and what happens if you want to change direction partway through. Some freelancers rebuild a quote from scratch at the first sign of scope creep. Others absorb small changes and flag anything that will affect the timeline or the price. Neither answer is wrong, but you need to know which one you are working with before the first draft lands.

5. Who owns the files and the work when the project ends

Confirm who holds the rights to the final files, the source files, and any drafts along the way, and get it in writing before work starts. This matters more than it sounds: a logo without its source file, or code without its repository access, can leave you unable to make even small changes later without going back to the same person.

Fraudulent or unverified profiles are a real risk in remote hiring, not just a theoretical one. Twine’s guide to vetting and onboarding remote creative specialists covers how to spot the warning signs before you commit budget to someone you have never worked with.

6. What does your process look like from brief to delivery

Ask a specialist to walk you through their last project, step by step: what they needed from the client, what they delivered at each stage, and where check-ins happened. A clear, repeatable process is a strong signal. Vague answers about “it depends on the project” usually mean there is no process at all, just improvisation each time.

7. How and how often will we communicate

Set expectations on channel, response time, and update frequency before the project starts, not after you have sent three unanswered messages. Ask whether they prefer async updates, a weekly call, or something in between, and whether that changes if the project runs into a rough patch.

8. Can I see work beyond the polished portfolio

A portfolio shows the best five projects out of fifty. Ask to see a brief they worked from, a piece of client feedback they responded to, or a project that did not go perfectly and how they handled it. How someone talks about a hard project tells you more than how they present an easy one.

9. What tools do you use, and can you hand off cleanly

Ask what software, platforms, or frameworks they work in, and whether your team can open and edit the final files without needing them. A specialist who works in an obscure tool with no clean export path can leave you dependent on them for every future edit, even small ones.

10. What happens if the project needs to pause, scale, or extend

Plans change: budgets get cut, launches get delayed, or a project that started small suddenly needs a second person. Ask how they handle a pause, whether they can bring in help for a larger scope, and what notice they need either way. The answer tells you whether this is a one-off transaction or the start of a working relationship you can return to.

Putting the answers to work

None of these questions are complicated, but asking all ten before you agree to anything catches most of the problems that surface later: missed deadlines, disputed ownership, and scope that quietly grows without a matching invoice. Treat the answers as part of the brief itself, not a formality before it.

If you would rather start from a shortlist of specialists who have already been vetted on exactly these points, Twine matches growing teams with experts across design, video, development, and marketing, with no agency markup on top.

Ready to assemble your next project team. Start with Twine.

Raksha

When Raksha's not out hiking or experimenting in the kitchen, she's busy driving Twine’s marketing efforts. With experience from IBM and AI startup Writesonic, she’s passionate about connecting clients with the right freelancers and growing Twine’s global community.