Hire a Graphic Designer

September 18, 2026

Most bad graphic designer hires aren't a talent problem, they're a process problem. A portfolio that looks great in a five-minute scroll can still fail on your actual brief, and a designer who interviews well can still miss deadlines under real client pressure. This guide covers how to review a portfolio for the signal that actually predicts fit, structure a paid test that tells you something real, and set up rates and file ownership before you need them.

How to Review a Portfolio (For Signal, Not Polish)

A polished portfolio tells you a designer can produce polished work when they control every variable, timeline, brief, and client. It doesn't tell you how they perform under your actual constraints. Look past the hero pieces for:

  • Range within a style, not just range across styles. A portfolio full of wildly different aesthetics can mean genuine versatility, or it can mean the designer is still finding their voice. Ask what they'd change if they redid an older piece today, the answer tells you how they think about their own growth.
  • Systems thinking, not just single pieces. Look for evidence they've worked within a brand system, consistent type, color, and spacing applied across multiple assets, not just one-off pretty graphics. This is the skill that matters for ongoing work.
  • Process, if they show it. A designer who can show a rough concept next to the polished final tells you more about how they think than the final piece alone.
  • Relevance to your actual need. A beautiful print portfolio doesn't predict skill at digital ad creative, and vice versa. Match the portfolio's medium to the work you're hiring for.

The Paid Test Project

A portfolio review narrows the field. A paid test project is what actually predicts fit. Structure it like this:

  • Use a real brief, not a hypothetical one. Give the same brief you'd give an employee, real constraints, real brand guidelines, a real deadline.
  • Pay for it. A paid test signals you respect the work and attracts candidates who respect the process, unpaid "spec work" tests filter out the designers you most want.
  • Keep it small. One social graphic, one landing page hero, or one email template, not a full campaign. You're testing process and communication, not extracting free production work.
  • Give one round of revision. How a designer handles feedback tells you more than the first draft does. Watch whether they ask clarifying questions or just guess.
  • Score it against your actual brief, not against how much you personally like the aesthetic. Did they follow the brand guidelines? Hit the deadline? Ask good questions?

Writing a Brief That Gets Usable Work

The single biggest predictor of a good outcome isn't the designer, it's the brief. A strong brief includes:

  • The specific goal (what should someone do after seeing this?)
  • Brand guidelines or examples of work you like and don't like, with reasons
  • Exact dimensions, platform, and file format needed
  • Required text, logos, or assets, provided upfront, not mid-project
  • A real deadline and how many revision rounds are included

"Make it pop" and "something modern" are not briefs. If you can't articulate what success looks like, the designer can't either.

File and Source-Asset Ownership

Settle this before work starts, not after a dispute:

  • Who owns the final files? For work-for-hire arrangements, you typically own the final deliverables once paid in full, state this explicitly in the agreement.
  • Do you get source files? Editable source files (Figma, Illustrator, Photoshop) matter if you'll need to update the work later without going back to the same designer. Decide upfront whether you need them, they're often worth negotiating for even at a modest premium.
  • What about stock assets and fonts? Licensed stock photos and commercial fonts often can't be transferred outright, confirm what's actually yours to keep using versus what was licensed for the original project only.

Revision Structures

Set the number of revision rounds and what counts as a revision (versus a new request) before work starts. A common structure: two rounds of revisions included in the quoted price or rate, anything beyond that billed separately. This protects both sides, the designer isn't stuck in unlimited scope creep, and you know exactly what you're paying for.

What It Costs

Rates vary widely by specialty and experience level. As a general benchmark for ongoing or dedicated design work: Philippines-based designers typically run $5–$10/hour, Latin America-based designers typically run $10–$20/hour depending on specialty (brand/identity work commands more than production graphics), and U.S.-based freelance or agency designers typically run $35–$75+/hour. For project-based work like a logo or a single campaign, per-project pricing is common instead of hourly.

How to Hire and Onboard

  1. Write the brief before you post the role, not after. A vague brief attracts vague applicants.
  2. Screen portfolios for relevance and systems thinking, not just polish.
  3. Run a paid test project against a real brief, with one revision round.
  4. Settle file ownership and revision structure in writing before ongoing work begins.
  5. Start with a defined trial period, 30 to 60 days, before committing to a longer engagement.

Building a broader creative team? See our companion guide to hiring a video editor, the full list of roles you can hire nearshore, or our general guide to hiring a virtual assistant.

FAQ

Should I pay for a test project, or is a portfolio review enough?
Pay for it if the role is ongoing. A portfolio review tells you about past work; a paid test tells you how the designer handles your actual brief, your feedback, and your deadlines.

Do I own the rights to work I paid for?
Generally yes, for work-for-hire arrangements, once paid in full, but confirm this explicitly in your agreement rather than assuming it. Licensed elements like stock photography or commercial fonts may carry separate restrictions.

How many revision rounds are normal?
Two rounds is a common default for project-based work. Set the number upfront, and define what counts as a revision versus a new request, to avoid scope creep on either side.

Related Guides