Coworkism Shop
How to 5 min read

How to Build a Portfolio That Gets You Remote Work

A remote hiring manager can't watch you work, so your portfolio has to do it for you. Here is what to include, where to host it and how to get it found.

By Published Updated
How to Build a Portfolio That Gets You Remote Work
In this article
  1. Why does a remote worker need a portfolio?
  2. What should go into it?
  3. Where should I host it?
  4. How do I make it easy to find?
  5. How do I get it in front of people?
  6. What mistakes should I avoid?
  7. Is a PDF portfolio enough?
  8. Will my setup affect how I'm judged?
  9. The short version

Coworkism earns from purchases made through the MaviGadget links in this post.

A remote portfolio should show a small set of your best projects, explain what you did and what came of it, and make it simple to get in touch. Clients and hiring managers who never meet you in person use it to judge whether you can do the work, so clarity matters more than volume.

Why does a remote worker need a portfolio?

In an office, people see how you work. When you freelance or join a distributed team, that evidence has to travel with you. A portfolio gives a stranger something concrete to check before they trust you with a project, and it lets you answer the same questions once instead of in every email.

It also gives you a place to point people to. A link in an application, a proposal or an email signature does more than a list of skills in a CV.

What should go into it?

Choose fewer, better pieces. Three to six projects that match the work you want are enough for most people.

  • Projects: writers can link published articles, designers can show finished layouts, developers can link live sites or repositories.
  • A short case study for each: what the problem was, what you did, what changed.
  • Testimonials: a sentence or two from a client or colleague who agreed to be quoted, with their name and role if they allow it.
  • A short bio: who you are, what you do, what kind of work you want, and a photo if you like.
  • Contact details: an email address and the one or two profiles you actually keep up.

How do I write a useful case study?

Keep it to four short parts: the situation, your role, the steps you took, and the outcome. Be exact about what was yours and what was the team's. If you have a real figure, such as a measured change in traffic or turnaround time, include it and say where it came from. If you don't, describe the outcome plainly. An honest sentence beats an impressive number you can't back up.

Where should I host it?

It depends on your field and how much control you want.

OptionGood forTrade-off
Your own websiteAnyone who wants full control of layout and messageYou pay for a domain and hosting and maintain it
Behance or DribbbleDesigners and visual creatorsLess control over the design, and clients see other work beside yours
GitHubDevelopersNeeds a tidy profile to read well to non-technical people
LinkedInAnyone applying for employed rolesNot built as a portfolio, so best as a pointer to your main page

If you use GitHub, pinning your best repositories to your profile puts the work you want seen at the top.

How do I make it easy to find?

Write for people first, then check the basics for search. Give each page a clear title, describe each project in plain words, and use the terms a client would type, such as "freelance web developer" or "B2B copywriter", where they are true. Google's SEO starter guide covers the fundamentals, including descriptive titles and helpful content.

How do I get it in front of people?

  • Link it in your email signature, proposals and profile bios.
  • Send a short, personal note to a company you would like to work with, with one relevant project linked rather than everything.
  • Share new case studies on the networks where your clients are.
  • Mention it when you meet people at events. Coworking spaces are a practical place for this, and our piece on hosting workshops in coworking spaces shows one way to meet potential clients.

What mistakes should I avoid?

  • No portfolio at all. Even one page with two projects is better than nothing.
  • Irrelevant work. If a piece doesn't relate to the jobs you want, leave it out.
  • Cluttered design. Use clear headings, short descriptions and a layout that works on a phone.
  • Typos. Read it aloud and ask someone else to read it too.
  • Stale content. Old projects and dead links suggest you've stopped working. Review it after each major project.
  • Hidden contact details. Put them on every page or one click away.

Is a PDF portfolio enough?

A PDF is handy as a backup, for example when a client asks for a file or you present without a connection. But it is harder to update and share, and search engines read it less easily than a web page. Keep a web version as your main portfolio.

Will my setup affect how I'm judged?

Portfolios are often followed by a video call, so a stable connection and a tidy workspace help you come across well. Our guides to reliable internet for remote work and a portable home office kit cover that side. If you travel a lot, our digital nomad guide has more on working from different places, and Mavigadget's Digital Nomad Collection lists gear for it.

The short version

Pick your best few projects, explain each one honestly, host the portfolio somewhere you can keep it current, and make contacting you easy. Then use it everywhere you introduce yourself. A small, clear portfolio that you maintain will serve you better than a large one that nobody has the time to read.

Frequently asked questions

How many projects should a remote portfolio have?
Three to six strong, relevant projects usually work better than a long list. Each should show a result or a clear outcome, and the work should match the jobs you want.
Do I need my own website?
Not strictly. A personal site gives you the most control, but GitHub, Behance, Dribbble or a well-built LinkedIn profile can work if they suit your field. Many people use one main home and link to the rest.
Should I put numbers in my case studies?
Only numbers that are true and that you can explain. If you don't have exact results, describe the outcome in words and say what your part was.
Is a PDF portfolio enough?
A PDF is fine as a backup for sending to a client or presenting offline, but a web page is easier to update, share and have found by search engines.
How often should I update it?
Review it whenever you finish a significant project, and at least check that links, contact details and your bio are still right before you apply for anything.

Sources and further reading

  1. pinning your best repositories to your profile docs.github.com
  2. SEO starter guide developers.google.com