Talvio
Beta
Talvio
Beta

How to List Freelance and Contract Work on Your Resume

How to format freelance and contract experience so recruiters and ATS read it as real work: umbrella entries, long contracts, unnamed clients, overlap, and tailoring.

Published Updated

Freelance and contract work is real experience. The problem is that it often looks messy on a resume: a dozen short engagements, clients you can't name, overlapping dates, and a title you invented yourself. Recruiters skim, ATS parsers expect a familiar structure, and a scattered list of gigs can make solid work look like instability.

The fix isn't to hide it. It's to give it a structure that reads like a job, because in most of the ways that matter, it was one.

Decide: one umbrella entry or separate roles

This is the first and biggest choice.

Use one umbrella entry when you did many short projects for different clients under your own name or business. You list yourself as the employer and put the client work underneath.

Use separate entries when you had a small number of long contracts, usually several months or more each, that functioned like full roles. A nine-month contract embedded in one company's team reads better as its own entry than buried in a list.

Mix the two if you had one or two big contracts plus a lot of smaller work. The big ones get their own entries, the rest go under the umbrella.

A rough test: if you'd describe it in an interview as "I worked at X," give it its own entry. If you'd describe it as "I did a project for X," it belongs under the umbrella.

How to format an umbrella freelance entry

Treat your freelance practice like an employer. That gives ATS systems and recruiters the fields they expect: a title, an organization, dates, and bullets.

Freelance Product Designer | Self-employed (or your business name) Jan 2022 to Present

  • Designed and shipped onboarding and billing flows for 8 SaaS clients, from early-stage startups to a 200-person fintech
  • Led a checkout redesign for an e-commerce client, working with their two-person dev team from research through launch
  • Built and maintained a reusable component library adopted by three long-term clients

A few details that make this work:

  • Pick a real title. Use the role a hiring manager would search for, like "Freelance Software Engineer" or "Contract Marketing Manager." Avoid "Founder" or "CEO" of a one-person practice unless you're applying for roles where that framing helps. It can make recruiters wonder whether you actually want a job.
  • Keep the dates continuous. One date range for the whole umbrella avoids a dozen tiny gaps. If there were quiet months in between, that's normal for freelancing and doesn't need explaining on the page.
  • Lead with your strongest, most relevant work. You don't need to list every client. Pick the three to five engagements that best match the role you're applying for.

How to format a long contract as its own role

For substantial contracts, list the client company as the employer and make the contract nature clear without making it the headline:

Senior Data Engineer (Contract) | Northwind Logistics Mar 2023 to Nov 2023

  • Migrated nightly batch pipelines to a streaming setup, cutting report delays from next-day to under an hour
  • Worked inside the platform team, owning two of their core ingestion services for the length of the contract

If you were placed through an agency, you can show both: "Senior Data Engineer (Contract via Agency Name) | Client Name." Use the client name if you're allowed to share it, since that's the company the recruiter will recognize.

Marking it as a contract matters. It explains the short tenure up front, so nobody reads a nine-month stint as a role that didn't work out.

What to do when you can't name the client

NDAs and confidentiality are common in freelance work. You can still show the work by describing the client instead of naming it:

  • "a Series B healthtech company"
  • "a top-10 UK retailer" (only if that's accurate)
  • "an early-stage B2B SaaS startup"
  • "a regional logistics provider with around 300 staff"

A good description tells the reader the industry, size, or stage, which is usually what they wanted to know anyway. Be careful not to accidentally identify the client through a description that only fits one company.

Writing bullets that show impact

Freelance bullets tend to drift into lists of tasks: "built websites," "wrote copy," "managed social media." That's what you did, but not why it mattered. The same principles that apply to any strong resume bullet apply here:

  • Start with what changed. What was different for the client after you finished?
  • Show scope. How big was the project, team, or audience?
  • Name the tools or methods that match the job description, where they're relevant.
  • Use real numbers only. If you don't know the result, describe the scope or outcome without inventing a metric.

Compare:

  • Weak: "Built websites for small business clients."
  • Stronger: "Built and launched marketing sites for 12 local service businesses, handling design, copy, and hosting setup, and trained each owner to update their own content."

Freelancing also gives you skills that in-house roles don't always show: scoping work, handling client relationships, managing your own pipeline, and delivering without a manager checking in. If the job you're applying for values ownership, a bullet or two on that is worth including.

Handling overlap with a full-time job

Plenty of people freelance on the side. If your freelance work overlapped with a full-time role, you have two options:

  1. List both with overlapping dates. This is fine and common. Make sure the freelance entry clearly reads as part-time or side work, for example "Freelance Web Developer (part-time)."
  2. Move the freelance work to a Projects section. If it was occasional or less relevant to the role, a projects section keeps your main work history clean.

Choose based on relevance. If the side work is closer to the job you want than your day job, it deserves a proper entry.

Making it ATS-friendly

Freelance entries trip up parsers mostly when they break the expected pattern. Keep it simple:

  • Put title, organization, and dates on consistent lines, in the same order as your other roles
  • Use a standard section heading like "Experience" or "Work Experience," not "My Journey" or "Gigs"
  • Avoid tables or text boxes for the client list
  • Spell out the role title in words a recruiter would search for

Tailor which clients you show

The big advantage of freelance experience is that you usually have more projects than you can fit, which means you can pick the ones that fit each role. Applying to a fintech? Lead with your fintech client. Applying for a role that's heavy on research? Lead with the project where you ran user interviews.

This is where keeping a few resume variants pays off. Instead of one master list of every client, keep a fuller record of your work somewhere and pull the most relevant engagements into each version. If you use Talvio, you can keep your experience in your profile, put together a resume for each kind of role you're targeting, and download it as a PDF when you apply.

Quick checklist

  • Many short projects go under one umbrella entry, long contracts get their own
  • Title is a real, searchable role, not "Founder" of a one-person practice
  • Contract roles are clearly marked as contracts
  • Unnamed clients are described by industry, size, or stage
  • Bullets show what changed, with real numbers only
  • Formatting matches your other roles so parsers read it correctly
  • The clients you feature match the job you're applying for

Freelance and contract work doesn't need an apology on your resume. Give it the same structure as any other job, show what you delivered, and it reads as what it usually is: proof that you can do the work without anyone holding your hand.

Start your first resume

Free forever, no card needed. Talvio is in beta, and more features are on the way.