Last month a founder I know hired a "senior" React developer off a popular marketplace. The portfolio was clean. The proposal was sharp. Six five-star reviews, a 98% job success score, and a cover letter that answered every question in the brief.
Two weeks in, the kickoff call was a disaster. The freelancer couldn't explain the architecture choices in his own portfolio projects. His screen share froze every time someone asked him to walk through code. The "previous work" turned out to be a template he'd cloned. My friend paid him a kill fee and started over.
The question isn't how to find a freelancer. Upwork, Fiverr, Toptal, and LinkedIn have that covered. The question is how to check if a freelancer is good before you wire them money and hand over a deadline.
Why the usual freelancer signals lie
A portfolio shows finished work. It doesn't show who did the work, how many revisions it took, or whether the freelancer was the designer or the project manager's nephew who uploaded the files. I've seen the same Figma case study in three different freelancers' portfolios on the same marketplace. None of them built it.
Proposals have the same problem. A freelancer with a $20 ChatGPT subscription can generate a tailored, keyword-perfect response to your brief in thirty seconds. The proposal reads like they understand your project. They might not have read past the title.
Reviews aren't much better. A 4.9 rating after six projects means six clients clicked five stars to close out a milestone. It doesn't tell you whether the deliverable actually worked, or whether the client had the expertise to judge it.
What platform vetting gives you (and where it stops)
If you're sourcing from Upwork, Fiverr, Toptal, or LinkedIn, you get some vetting for free. Upwork shows a Job Success Score and earnings history. Fiverr Pro runs a manual review before badging sellers. Toptal claims to accept only 3% of applicants through a multi-stage screen.
These are helpful signals. But they measure the freelancer's history across all clients and all project types.
A developer who's great at WordPress landing pages will carry the same Job Success Score into a React migration and bomb it. A Fiverr Pro badge means the seller passed Fiverr's review process. It doesn't mean they're the right person for your specific brief.
Platform vetting answers "has this person completed work before." You need to answer "can this person do my work." That requires your own screening step.
How to vet a freelancer in six steps
Here's how I recommend vetting freelancers.
Step 1: Screen the portfolio for specific red flags
Start with the cheapest filter. Look at three to five portfolio pieces and check for:
- Inconsistent style across projects. A designer whose portfolio jumps between wildly different aesthetics probably assembled it from multiple sources.
- No process explanation. Good freelancers describe the problem, their approach, and the outcome. Bad ones just post screenshots.
- Template work passed off as custom. Google a distinctive visual element. If it shows up on ThemeForest or a UI kit, move on.
- Zero failed or messy projects. Nobody's portfolio should be 100% polished wins. If it looks too clean, something's been hidden.
Don't try to make the hire decision from the portfolio. You're just deciding who gets to the next step.
Step 2: Send a short video interview with job-specific prompts
Ask the freelancer to record answers to four or five prompts on video, on their own time. No scheduling, no time zones. Tools like one-way video interview platforms handle this, or you can use a simple Loom request.
The prompts matter more than the tool. Write questions that force specifics:
- "Walk me through a recent project where the brief changed halfway through. What did you do."
- "Here's a short description of our project. What's the first question you'd ask before starting."
- "Tell me about work you delivered that didn't go well. What happened."
These prompts can't be faked with a canned answer. You hear the person think, watch them organize their response, and notice whether they give concrete details or vague generalities.
Fifteen to twenty minutes of their time. Two to three minutes of yours per candidate if you watch at 1.5x or just review the highlights.
Step 3: Run a paid test project for anything over $2,000
For a quick logo or a blog post, the video interview is probably enough. For a six-month contract rebuilding someone's billing system, you ideally want more.
Give the freelancer a real task scoped to two to four hours of work. Pay them for it. $100 to $300 is typical depending on the skill level. The test should mirror the actual project, not a generic whiteboard exercise.
What to watch for:
- Do they ask clarifying questions before starting, or just deliver something. The ones who ask questions are the ones who'll save you revision cycles later.
- How do they handle an intentionally vague brief. Leave one thing ambiguous on purpose. See if they flag it or guess.
- Is the deliverable organized. Clean file naming, a short README, inline comments. These are signals of how they'll work on day 30, not just day 1.
Step 4: Check references for contracts over $5,000
Most people skip this. That's a mistake for anything high-stakes.
Ask the freelancer for two or three past client contacts. Then call those clients and ask specific questions:
- "What went wrong during the project, and how did [name] handle it."
- "Would you hire them again for the same scope."
- "How was their communication when things got stressful."
Don't ask "were they good." Everyone says yes. Ask about problems. The answer tells you whether the freelancer manages difficulty or disappears from it.
If the freelancer can't produce a single reference, that's information too.
Step 5: Score against a rubric, not your gut
Sit down with your shortlist and score every freelanc against the same criteria. Same weights. Same scale. Write the scores down before you discuss with anyone, because the first person who says "I liked her vibe" will anchor the whole conversation.
A simple five-point rubric works:
- Communication clarity (1-5): did they explain their thinking in concrete terms.
- Technical fit (1-5): does their test project or portfolio match the technical demands.
- Process signals (1-5): did they ask questions, organize their deliverable, respond on time.
- Reference quality (1-5): what did past clients say about working under pressure.
- Responsiveness (1-5): how quickly and clearly did they reply throughout the vetting process.
The highest total score gets the offer. If two candidates are within a point of each other, go with the one who responded faster. Communication speed during the sales cycle predicts communication speed during the project.
Step 6: Protect yourself with the right contract
Vetting doesn't end when you pick someone. You need a contract that covers what happens when things go sideways.
At minimum, a freelance contract should include:
- Scope of work. Describe the deliverables, not the activities. "A functioning checkout page" is a deliverable. "Front-end development work" is not.
- Payment structure. Milestone-based payments tied to deliverables. Never pay 100% upfront. A common split: 25% at kickoff, 50% at first deliverable, 25% at final approval.
- Intellectual property. A work-for-hire clause that assigns IP to you on payment. Without this, the freelancer may own what they build.
- Confidentiality. An NDA if the project involves proprietary data, customer information, or trade secrets.
- Termination terms. What happens if you need to end the contract early. A kill fee or a two-week notice period.
Use escrow (Upwork and most platforms offer this) for contracts with new freelancers. It protects both sides.
Red flags that should kill the hire
Some warning signs are loud enough to override a strong portfolio or a good test project.
- Unresponsive during vetting. If they take four days to reply to your AI video interview, they'll take a week to reply when you need a revision on a deadline.
- No questions about the brief. A freelancer who says "got it, I'll start Monday" to a vague brief either didn't read it or doesn't care about getting it right.
- Overpromising on timeline. "I can do that in two days" on a project that should take two weeks is a red flag and not a selling point.
- Refusing a paid test. Good freelancers understand why you're asking. The ones who refuse are usually the ones who can't do the work.
- Copied or template portfolio work. If you reverse-image-searched a portfolio piece and found it somewhere else, the conversation is over.
- Aggressive negotiation on IP or NDA terms. Pushing back on a standard work-for-hire clause suggests they plan to reuse your deliverables.
- No references and no repeat clients. Repeat business is the strongest signal in freelancing. If nobody hires them twice, ask why.
The vetting is the relationship
Every freelancer engagement is a bet. You're betting that a stranger will care about your project as much as you do, at least for the duration of the contract. No screening process eliminates that bet entirely.
But there's a difference between a bet and a guess. A guess is hiring someone because their proposal was well-written. A bet is hiring someone because you watched them explain a failed project on camera, scored their talent assessment or deliverable against a rubric, called a past client who described how they handled a scope change, and signed a contract that protects both sides.
The freelancers who make it through a real vetting process tend to appreciate it. They've been burned by clients who didn't know what they wanted, too. A clear process signals that you're organized, that you'll give real feedback, and that the project is worth their time.
Frequently asked questions about vetting freelancers
How long should a freelancer vetting process take?
Twenty to thirty minutes of your time per hire, spread across two to three days of the candidate's time. The video interview is the step that makes this possible, because nobody's trading calendar invites. If you're spending more than an hour per candidate, you're over-interviewing or missing a filter earlier.
Can I skip the video interview if the portfolio is strong?
No. A strong portfolio tells you the person was on a project that shipped. It doesn't tell you what they did on the project, how they'd handle yours, or whether they can communicate clearly under a deadline. A five-minute one-way video interview is the cheapest insurance in the hiring process.
Do I need a background check for freelancers?
For most projects, no. Your test project, reference checks, and contract terms provide enough protection. For freelancers who'll access sensitive customer data, financial systems, or confidential IP, run a basic identity verification and background check. Services like Checkr or GoodHire handle this for about $30 to $50 per check.
Should I use Upwork's escrow or handle payment directly?
Use escrow for your first project with any new freelancer. It protects both sides: you don't pay until the milestone is approved, and they know the money exists. After you've completed two or three projects together and built trust, direct payment is fine.
What if I'm hiring one freelancer, not fifty?
The process is the same. The time savings are smaller, but the decision quality is identical. Even for a single hire, a recorded video interview beats a live call for the first round because you can rewatch it, forward it to a co-founder, and compare it side by side with the next candidate. Tools like Truffle can speed up the review with 30-second highlight clips and AI-generated summaries, but the process works with any video tool.
