How to put freelance work on your resume

The mistake: pasting your profile

Freelancers usually get this wrong in one of two directions: hiding the freelance years entirely (leaving a gap that reads worse than the truth), or pasting their platform profile — Job Success score, hourly rate, badges — into a resume. Recruiters don't hire profiles. A 98% Job Success score means nothing to an ATS keyword search and little to a screener; the client problems you solved mean everything.

The fix is translation, not decoration: your gigs are real experience that needs to be written in the language of the field you're applying to. Our scanner detects platform-profile exports for exactly this reason — scoring one as a resume understates the person behind it.

The structure decision: one role or a projects section?

This is the choice that shapes everything else, and it follows rules, not taste. If your freelancing is continuous (roughly a year or more) with a coherent focus, consolidate it into ONE role entry: 'Independent Marketing Consultant — 2021–present', with your best project outcomes as bullets underneath. It reads like a job because it was one.

If your projects are scattered across fields, part-time alongside a job, or shorter-term, use a 'Selected Projects' section instead — each project gets a client-type label ('retail e-commerce client', never confidential names without permission) and one to three bullets. Alongside employment, this section sits below your work history; as your main activity, it sits on top.

Never list ten gigs as ten separate 'jobs' — that reads as instability to a six-second skim, which is the exact opposite of what the work proves.

The bullet formula

Every freelance bullet should carry four parts: a target-field action verb, the deliverable in the TARGET field's vocabulary, the scope (clients, budget, volume, timeline), and an outcome. 'Made websites for small businesses' becomes 'Designed and shipped 9 responsive Shopify storefronts for retail clients over 14 months.'

The vocabulary translation matters as much as the structure: you're proving you already speak the field's language. A recruiter reading 'built booking plugin' files you under hobbyist; reading 'developed and deployed a custom scheduling integration for a 12-location dental group' files you under engineer.

No metrics? Use the rescue ladder — never invent one

Most gig work never measured revenue impact, and inventing numbers is both wrong and detectable in interviews. When a project has no headline metric, step down this ladder and take the first rung you honestly have: a client business result (time saved, leads generated) → a scope figure (pages, users, records, budget) → speed ('delivered in 3 weeks') → repeat business ('retained for 3 follow-on engagements') → a concrete qualitative change ('replacing a manual spreadsheet process').

A bullet with no number at all is still fine. An honest bullet beats a fabricated one, always — and every claim in your resume should survive the question 'tell me more about that.'

Dates, overlaps, and the 'gap' that isn't

Freelancing alongside employment overlaps honestly: keep both entries with their real dates. Freelancing between jobs is not a gap — it's the consolidated role above, dated like any other. What kills applications isn't the freelance chapter; it's the unlabeled hole where recruiters are left to imagine something worse.

One more honesty rule that doubles as self-protection: client names appear only with permission; otherwise use industry-plus-size framing ('a national bakery chain'), which recruiters fully accept.

Common questions