Skip to content
SuperGig Early access

How to Vet a Freelancer: Screening Steps, Questions and Red Flags

SuperGig Editorial Updated July 2026 9 min read

To vet a freelancer, run five steps in order: write a brief specific enough to filter out generalists, read the portfolio for evidence they personally owned the work rather than sat near it, run a 20 minute screening call on one past project in detail, pay for a small scoped test task, and call one real reference. Only then agree a written scope and payment schedule. Fund the work in milestones held in escrow so a bad hire costs you one milestone instead of the whole budget.

See how vetting works

Step 1

Write a brief that filters people out

Most bad hires are decided before anyone is interviewed. A vague brief ("need a website, WordPress, budget flexible") pulls in fifty applicants, forty of whom are copy-pasting the same pitch, and you end up screening on charm because you have nothing else to screen on. A good brief does the first round of vetting for you.

Name the outcome, the constraint and the deadline. "Migrate a 400 page Shopify store to a new theme without losing existing URLs, live before Black Friday" is a filter. Anyone who replies without mentioning redirects has disqualified themselves in one line. Include your budget range too. Hiding it doesn't get you a better price, it just wastes two weeks discovering that the people you like cost triple what you can pay. If you don't know the range yet, our guide to what it costs to hire a freelancer gives current US bands by discipline.

Step 2

How to check a freelancer's portfolio

A portfolio proves that work exists. It does not prove who did it. That gap is where most hiring mistakes hide, and it is the single most useful thing to interrogate. Agency alumni show client logos from projects where they wrote two components. Designers show shots of screens that a lead redlined for them. None of that is dishonest exactly, but it isn't the claim you need.

So ask, per piece: what was your specific role, who else was on it, what would have been different if you weren't there? Then push one level deeper on a detail only the person who did the work would know. Why this framework and not the obvious alternative? What broke after launch? How long did the part everyone underestimates actually take? Someone who owned the work answers instantly and usually volunteers a complaint about it. Someone who was adjacent to it gets abstract fast.

  • Prefer live links over screenshots. Screenshots can be anyone's.
  • Look for two or three projects in your exact category, not twenty across every category.
  • Check the most recent work is recent. A portfolio that stops in 2023 is a question.
  • For developers, ask for a repo or a code sample you can actually read.

Step 3

What questions should I ask before hiring a freelancer?

Twenty minutes is enough. You are not testing knowledge, you are testing whether their account of their own work holds up under two follow-up questions, and whether working with them will be pleasant when something goes wrong. Skip the hypotheticals. "How would you approach a redesign?" gets you a rehearsed answer. "Tell me about the last redesign you shipped and what you'd do differently" gets you the truth.

Ask this A good answer sounds like A weak answer sounds like
What did you build vs what did the team build? Names their exact scope, credits others "I led the whole project" with no detail
What went wrong on your last project? A real failure plus what they changed "The client was difficult"
How many clients are you serving right now? A number, and what they'd drop for you Dodges, or claims unlimited capacity
What do you need from me to hit the deadline? A concrete list: assets, access, decisions "Nothing, I'll handle everything"
How do you handle scope changes mid-project? A written change process and rate "We'll figure it out as we go"

The last one matters more than people expect. Scope creep, not incompetence, kills most freelance projects. Someone who has a boring answer ready has been through it.

One practical note: this call scales badly. Doing it once is fine. If you are screening a dozen candidates a week, it is worth automating that first-round screening interview so you only spend live time on the shortlist that survives it.

Step 4

Should I pay a freelancer for a test project?

Yes, and this is the step most buyers get backwards. Unpaid test projects feel like a free way to reduce risk. What they actually do is filter your pipeline by who has spare unbilled hours, which is a polite way of saying they filter for the people with the least demand. The freelancers you most want are booked. They will decline a free four hour task and you will never know they existed.

Pay for anything longer than about 30 minutes. Two to four hours at their normal rate is cheap next to a failed hire. Make the test a genuine slice of the real job: one page of the site, one section of the report, one endpoint, one email sequence. Give the same brief to two or three finalists at once and compare like for like.

Then grade the process, not just the artifact. Did they ask a clarifying question before starting, or assume? Did the work land when they said it would? Did they flag the ambiguity in your brief that you knew was there? That behavior is what you are buying for the next three months. The deliverable is almost secondary.

Step 5

What are red flags when hiring a freelancer?

Most freelance disasters were visible in the first week and got rationalized away. The reliable signals are structural rather than about talent: how someone prices, how fast they reply before they have your money, whether they will put anything in writing. Here is the comparison I use across the six dimensions that actually predict outcomes.

Dimension Green flag Red flag
Portfolio Live links, named role, deep detail on request Screenshots only, no role, stock-looking work
Communication Asks questions before quoting, replies in a day Slow or vague while still selling you
Pricing Itemized, in market range, tied to scope One number, no breakdown, far below market
References Offers two contactable past clients Refuses, stalls, or sends only testimonials
Contract and scope Written deliverables, revisions, IP transfer Verbal agreement, "we'll keep it flexible"
Payment terms Milestones, escrow, deposit under 50% Full payment upfront, off-platform, crypto or wire only

The bottom row is where actual fraud lives. Nearly every "I got scammed hiring a freelancer" story ends the same way: the buyer was talked off the platform and into a direct transfer, usually with a small discount as the sweetener. Once the money has left, there is no dispute process and no recourse. A discount for paying outside escrow is not a discount, it is the price of your protection.

Step 6

Reference checks that actually tell you something

Written testimonials are worthless for vetting. Anyone can write those, and the happiest clients are the ones asked for them. What you want is one 10 minute call with a past client who hired this person for something similar in size and scope.

Two questions do most of the work. First: "Did the project land on the original timeline, and if not, what happened?" Second, and this is the one that gets honest answers: "Would you hire them again for the same thing, or for something different?" The pause before that answer is often more informative than the answer. A reference who says "for design, absolutely, but I'd project-manage it myself next time" has just told you exactly what you're signing up for.

If a freelancer can't produce a single contactable client, that is a genuine problem for anyone with a few years of history. Early-career freelancers are a fair exception, and you compensate by making the paid test bigger and the first milestone smaller.

Step 7

Lock the scope and the payment terms before day one

Vetting gets you a good candidate. Structure is what keeps a good candidate from turning into a bad project. Before any work starts, write down the deliverables in specific nouns, the number of revision rounds included, the hourly rate for anything out of scope, who owns the IP on delivery, and what "done" means for each milestone. Two paragraphs is enough. The point is that a disagreement in week six has a document to resolve it.

Then break the money into milestones and fund them one at a time. Milestone payments held in escrow cap your downside at a single stage: the freelancer can see the money is real and committed, you don't release it until you have approved the work, and neither side is trusting the other on faith. If you want the mechanics, we walk through the full flow in how freelance escrow works. Worth also confirming the engagement is genuinely contractor-shaped, which our 1099 vs W2 guide covers for US buyers.

Step 8

Or let the vetting happen before you see anyone

Everything above takes real time. Running it properly across eight applicants is most of a working week, which is why so many buyers skip to the interview and hope. Open marketplaces make this worse by design: on a platform like Upwork the filtering is entirely your job, and volume is the product.

SuperGig moves the screening upstream. Every freelancer clears a 4-stage vet covering portfolio review, a skills assessment, a live paid simulation and reference checks before they can be matched, so the shortlist you get within 48 hours is people who already passed steps 2 through 6. You still run the call and the paid test, because fit is yours to judge, but you're judging fit rather than authenticity. Work is milestone-funded, freelancers keep 100% of their rate, and if the match is wrong you get a free rematch within 48 hours. See how the 10% project fee works, or browse vetted web developers and designers to see the bar we screen to.

FAQ

Vetting freelancers: quick answers

How do you vet a freelancer?

Vet a freelancer in five steps: write a brief specific enough to filter out generalists, read their portfolio for proof they personally owned the work, run a 20 minute screening call about one past project in detail, pay for a small scoped test task, and call one real reference. Then protect the engagement with a written scope and milestone payments held in escrow.

What questions should I ask before hiring a freelancer?

Ask what exactly they built versus what their team built, what went wrong on their last project and how they handled it, how many clients they are serving right now, what they need from you to hit the deadline, and how they handle a change of scope mid-project. Specific, slightly unflattering answers are the good ones.

What are red flags when hiring a freelancer?

The clearest red flags are a portfolio with no named role, a quote given before any questions are asked, a price far below market, pressure to pay in full upfront or move payment off-platform, refusal to give references, and slow or vague replies during the sales stage. Communication rarely improves after the invoice.

Should I pay a freelancer for a test project?

Yes. Pay for any test task longer than about 30 minutes. Unpaid tests select for the freelancers with the least demand for their time, which is the opposite of what you want. Keep the paid test small (two to four hours), make it a real slice of the job, and treat the process as part of the evaluation.

Skip the Screening. Get a Vetted Shortlist.

Brief your project, review hand-picked top-1% freelancers within 48 hours, and pay only for milestones you approve.

See pricing