How to Build a Portfolio That Helps You Get Remote Jobs
Build a portfolio that gets you remote jobs from Nigeria: what to show for your role, how to write up each piece, free hosting, and a four-week plan.
By Tolu Adebanjo, Job search writer
Updated 14 min read

A portfolio that gets you remote jobs is a small, easy-to-open collection of three to five pieces of work. Each piece shows the problem you solved, how you solved it and what came out of it. You don't need paid clients to start: self-initiated projects and volunteer work count if you label them honestly.
This matters more from Nigeria than almost anywhere else. A hiring manager in London or Austin can't easily call your former boss in Ibadan, has never heard of your university and will never meet you before the offer. Your portfolio is the one piece of evidence they can check themselves in ten minutes.
This guide covers what a portfolio looks like for your type of role (including support and admin roles, where most people assume they don't need one), how to structure each piece, where to host it free, how to put it into applications, and a four-week plan to build one before you apply.
Quick answer
To build a portfolio for remote jobs, choose three to five pieces of work that match the jobs you want. Write each one up as a short case study covering the problem, your actions, the tools you used and the result. Host the pieces on a free page that loads quickly on a phone (GitHub Pages, Notion or a shared PDF). Put the link in your CV header, LinkedIn and every application form. Self-initiated work is fine if you say it was self-initiated.
Why a portfolio carries extra weight in remote hiring
Remote employers hire on evidence they can check from a distance. In an office hire, the interview day does a lot of the work. In remote hiring, written answers, work samples and trial tasks do it instead.
Two real hiring processes show this (both checked in October 2026):
- Canonical (the company behind Ubuntu) advertised a Visual Designer role on its Greenhouse job board as "Home based - EMEA". The form asks applicants to "attach a PDF portfolio if you have one available", requires written answers such as "Describe your most complex web design project", and states that plagiarism or AI-generated content will disqualify an application.
- Automattic (WordPress.com, Tumblr) says on its work with us page that applicants should showcase relevant projects and contributions. Most roles start with a text-based Slack interview, followed by a paid trial of up to 20 hours of real work.
Neither company is guaranteed to have a role open to you today. Eligibility changes by role, so always read the location line on the live ad. The pattern is the useful part: remote employers want to see work and writing, and a portfolio gives them both before they spend time on a call.
For Nigerian applicants there's a second reason. Many good candidates get filtered out because the employer can't verify a Nigerian employer, a Nigerian degree or a reference. A portfolio sidesteps that problem because the employer judges your work directly.
What counts as a portfolio for your type of role
Most people picture a designer's gallery. In practice, nearly every remote role can be backed by some kind of evidence. The table below gives a starting point for each role family. The detailed guides for each role go further.
| Role family | What to show | Good format |
|---|---|---|
| Software, QA, DevOps | 2 to 3 working projects with READMEs, tests and a live demo | GitHub plus GitHub Pages |
| Data and analytics | Cleaned dataset, analysis notebook, dashboard, one-page findings | GitHub, Tableau Public or a PDF |
| Design and video | 3 to 5 case studies showing process, not just final images | Website or PDF |
| Writing and editing | 3 to 5 published or self-published pieces in your niche | Website, Notion or Google Docs |
| Customer support | Sample replies to tricky tickets, a help-centre article, a macro set | Notion page or PDF |
| Virtual assistant and admin | SOPs, a cleaned-up spreadsheet, a calendar or inbox system, a travel itinerary | Notion page or PDF |
| Marketing and social media | Campaign plan, sample ads, content calendar, results with screenshots | Notion page or PDF |
| Finance and bookkeeping | Anonymised reconciliation, month-end checklist, model or report | PDF with redacted figures |
| Sales and SDR | Cold email sequence, call script, CRM pipeline you set up | Notion page or PDF |
If your field isn't listed, ask yourself: "What file or link would prove to a stranger that I can do the first month of this job?" That file is your portfolio piece.
For deeper guidance on specific roles, see the software portfolio guide, the design portfolio guide for remote employers, the writing portfolio guide and the virtual assistant portfolio guide. The role guides on WorkRemote's careers pages list the tools and skills each role expects, which tells you what your samples need to show.
Build a small portfolio before you apply
A lot of people wait for their portfolio to feel "complete" and never apply. Don't. A small, sharp portfolio beats a large, messy one, and you can keep adding to it while you job hunt.
The minimum we'd want to see before you send applications:
- Three pieces aimed at one job title. Three customer support samples get you further for a support role than one support sample, one logo and one blog post.
- One landing page with your name, the role you're targeting, your time zone and working hours, and links to the three pieces.
- A short write-up for each piece (the case-study structure is below).
- A way to contact you: a professional email address and your LinkedIn.
That's enough to start applying. Each week, replace your weakest piece with a better one instead of piling on more.
Pick one target role first
Your portfolio should match the job ads you're answering. Open five live ads for the role you want and note the tools and tasks that keep coming up. If four of the five mention Zendesk and refund handling, your support samples should involve Zendesk-style macros and a refund conversation. Your samples then line up with what the screener is scanning for.
How to structure each portfolio piece
Screenshots alone don't get people hired. Hiring managers want to see how you think, because remote work means you'll often make decisions without anyone to ask. Use this structure for every piece and keep each write-up to roughly 150 to 300 words:
- Context: who the work was for and whether it was a client, an employer, a volunteer project or self-initiated.
- The problem: what wasn't working, in one or two sentences.
- What you did: the steps you took and the decisions you made, including at least one trade-off.
- Tools: name them (Figma, Excel, Zendesk, HubSpot, Python, Canva, QuickBooks).
- Result: a number if you have a real one, otherwise a concrete outcome ("cut the onboarding email from 900 to 350 words"). Never invent metrics.
- What you'd do next: one line. It shows judgement.
- Time spent: this helps an employer picture your speed.
Example (hypothetical): a customer support portfolio piece
Example (hypothetical): Chiamaka wants a remote SaaS support role but has only worked in a Lagos bank branch. She picks a project management app she uses and writes three tickets a frustrated customer might send: a billing double charge, a lost project after a sync error, and a feature request written as a complaint.
For each ticket she writes her reply, a short internal note explaining her tone choices, and the macro she'd save for similar tickets. She adds a 400-word help-centre article on "How to recover a deleted project" and a one-paragraph summary of what she learnt.
Her write-up opens with "Self-initiated sample, not written for this company", which keeps it honest. In total that's one Notion page, about 1,500 words, built over a weekend, and it shows written English, empathy, product thinking and familiarity with how support teams work.
Creating work samples when nobody has paid you yet
Paid client work is the strongest evidence, but you don't need it to start. Here are honest ways to build pieces in order of how much weight employers tend to give them:
- Real work for real people, even unpaid. Redo the price list for your cousin's food business, set up bookkeeping for your church's welfare committee, or manage social media for a student association. Ask permission to show the work, and ask for a one-line written comment you can quote by name.
- Open contributions. Developers can fix documentation or small bugs in open-source projects on GitHub. Writers can contribute to community knowledge bases. Accepted contributions are public and dated, which makes them easy to verify.
- Self-initiated briefs based on real products. Redesign a confusing page, write the onboarding emails you wish a fintech app sent, or analyse a public dataset. Call it a "self-initiated concept" or "unsolicited redesign", never client work.
- Recreations of common tasks. Build the spreadsheet, SOP or ticket reply that the job ad describes. This is the fastest route for admin and support roles.
If you're starting from zero work history, our guide to remote jobs that hire beginners explains which roles are realistic first targets. The guide on presenting personal projects in an application covers how to describe these pieces on forms.
Show remote-work habits, not only skills
Remote managers worry about two things beyond skill: whether you communicate clearly in writing, and whether you'll be reachable and reliable from another time zone. Your portfolio can answer both questions before anyone asks.
- Write your case studies well. The write-up is itself a writing sample. Keep sentences short, put the conclusion first and use plain headings.
- Add a two- to three-minute video walkthrough (Loom or a screen recording) for one piece. It shows your spoken English and how you explain work, which is close to what a recorded async update looks like.
- Include documentation. A README, an SOP or a handover note shows you can leave work in a state others can pick up, which matters when your teammates are asleep.
- State your working hours in their time. For example: "Based in Lagos (WAT, UTC+1). Available 9am to 5pm UK time, which is 10am to 6pm in Lagos in winter and the same hours in summer." For US East Coast roles, say which overlap you can offer, since New York is 6 hours behind Lagos from 1 November and 5 hours behind in summer.
- Mention your setup in one line, such as "Inverter backup and two internet providers". Many employers quietly wonder about power and connectivity in Nigeria, and one calm sentence settles it.
Where to host your portfolio for free
You don't need a paid website. You need something that opens quickly on a phone, works on a slow connection, and won't disappear when a free trial ends. Here are the options we'd consider, with the facts checked against each provider's own documentation as of October 2026:
| Option | Best for | Points to know |
|---|---|---|
| GitHub Pages | Developers, data people, anyone comfortable with simple code | Free site at username.github.io; 1 GB site limit and a soft 100 GB a month bandwidth limit |
| GitHub profile README | Developers | A public repo named exactly after your username shows a README on your profile |
| Notion (published page) | Support, VA, admin, marketing, writers | Free notion.site address; search indexing is a toggle; custom domains need a paid add-on |
| PDF on Google Drive | Everyone, especially for upload fields | Set sharing to "Anyone with the link"; also keep a copy to attach |
| Design platforms (Behance, Dribbble) | Designers | Common in design hiring; check each platform's current terms yourself |
A few details from the official documentation:
- GitHub says a user site must live in a repository named after your username followed by .github.io (for example, yourname.github.io), and you get one user site per account (GitHub Docs: What is GitHub Pages). Published sites can be no larger than 1 GB and have a soft bandwidth limit of 100 GB a month (GitHub Pages limits), which is far more than a portfolio needs.
- A GitHub profile README only appears if the repository is public, named exactly after your username, and has a README.md at the root (GitHub Docs: Managing your profile README).
- Notion lets you publish a page to a notion.site address and turn on search indexing. Notion notes that search results can take up to four weeks to appear, and custom domains need a paid add-on (Notion Help: Notion Sites).
Make it load on a weak connection
Many recruiters open portfolios on their phones between meetings, and you may update yours on mobile data. Keep it light:
- Compress images before uploading (export JPGs at web quality instead of full-resolution PNGs).
- Embed videos as links instead of auto-playing them on the landing page.
- Keep a PDF version to a few megabytes so it uploads through application forms without failing.
- Open your link on your own phone using mobile data, not Wi-Fi, before you send it anywhere.
Putting your portfolio into your applications
A portfolio nobody clicks doesn't help you. Put it where screeners look:
- CV header. Add a short, readable link next to your email and LinkedIn, such as "Portfolio: yourname.github.io". Spell it out in full, because some applicant tracking systems strip hyperlinks. The guide on writing a CV for international remote jobs covers the rest of the layout.
- LinkedIn. Add the link to the Featured section and your contact info, and mention one piece in your headline or About section.
- Application forms. Paste the link into "Website" or "Portfolio" fields even when they're optional. If the form accepts uploads, attach the PDF version too. Canonical's form above takes a PDF portfolio, for example.
- Cover letters and messages. Link the single most relevant piece, not the homepage: "Here's a sample refund reply sequence I wrote for a SaaS product: [link]."
- Test every link while logged out. Google Drive files default to restricted access, and a "Request access" screen often ends the application on the spot. Open each link in a private browser window first.
Should you tailor the portfolio for each job?
Don't rebuild the whole portfolio each time. Reorder it instead. Keep one master page and, for an important application, send a link or PDF that leads with the two pieces closest to that job. Ten minutes of reordering is usually worth more than an hour of new work.
Mistakes that make hiring managers close the tab
- Showing confidential work. Never publish a former employer's customer data, internal dashboards or bank statements. Redact names and figures, or recreate the work with dummy data, and say you did so. If you signed a non-disclosure agreement, respect it.
- Calling self-initiated work "client work". It's easy to check, and when it's caught, everything else you've shown loses credibility.
- Presenting AI-generated work as your own. Using AI tools for research or editing is common, but submitting generated work as your own can disqualify you outright, as Canonical's application form states. If AI was part of your process, say how.
- Too many weak pieces. Fifteen average items bury the three good ones. Cut hard.
- No dates. Undated work looks stale. Add the month and year to each piece.
- Broken links and dead demos. Free hosting tiers on some app platforms put projects to sleep or delete them. Check your demos monthly.
- Doing large unpaid "test tasks" for unknown companies. Legitimate employers sometimes set short assessments, and some pay for longer trials, as Automattic does. A stranger asking for a full week of free work, or asking you to pay for "portfolio verification", is a warning sign. Our guide to spotting remote job scams in Nigeria lists the patterns.
A four-week plan to build your portfolio
Treat this as a schedule for someone with about an hour or two a day. Stretch it if you have less time.
| Week | Focus | Output |
|---|---|---|
| 1 | Pick one target role; study 5 live ads; draft piece 1 | Notes on tools and tasks; first sample |
| 2 | Build pieces 2 and 3; write case studies | Three written-up pieces |
| 3 | Set up hosting; add landing page, hours and contact; record one walkthrough | Live portfolio link and PDF version |
| 4 | Test links on mobile data; update CV and LinkedIn; start applying | Applications sent with portfolio |
After week four, keep a weekly habit: replace your weakest piece, or add a real result once you have one. Skill assessments in the hiring process are their own topic. See the guides on completing a remote writing assessment and remote technical assessments.
Frequently asked questions
Do I need a portfolio for remote customer service or admin jobs?
It isn't always required, but it helps. Most support and admin applicants send only a CV, so three sample ticket replies or a well-built SOP on a Notion page gives a screener something concrete to judge. It's especially useful if your experience is with Nigerian employers the screener can't easily verify.
How many pieces should a portfolio for remote jobs have?
Three to five pieces is enough for most roles. Three strong, relevant pieces aimed at one job title work better than ten mixed ones. Add or replace pieces as you improve instead of waiting until you have a large collection.
Can I build a portfolio before I've had any job?
Yes. Self-initiated projects, volunteer work for local businesses, churches or student groups, and open-source contributions all count. Label each piece accurately, for example as a "self-initiated concept", and never present practice work as paid client work.
Is a free portfolio site good enough, or do I need my own domain?
A free site is good enough. Employers judge the work, not the address, so a username.github.io or notion.site link is fine. A custom domain looks a bit more polished but costs money every year, and you can add one later.
Can I include work I did for my current or former employer in Nigeria?
Only if it isn't confidential, or if you have permission. The safest approach is to describe the problem and your approach, then recreate the output with dummy data. Remove customer names, account numbers and internal figures.
Should I attach my portfolio as a PDF or send a link?
Do both when the form allows it. A link is easier to update and can include video. A PDF still works if your site goes down, and some application forms, such as Canonical's, ask for a PDF upload. Keep the PDF small enough to upload on a mobile connection.
Is it okay to use AI tools when building my portfolio?
You can use them for research, outlining or proofreading, but the work you present must be yours, and you should be open about how you used AI. Some employers state that AI-generated content will disqualify an application, so read each job ad carefully.
Key takeaways
- A remote job portfolio is three to five relevant pieces, each written up with the problem, your actions, the tools and the result.
- Nearly every role can have a portfolio, including customer support, admin, finance and sales, not just design and development.
- Build a small portfolio aimed at one target role before you apply, then improve it while you job hunt.
- Self-initiated and volunteer work counts if you label it honestly. Fake clients and passed-off AI work can sink an application.
- Free hosting (GitHub Pages, Notion, a shared PDF) is enough. Test every link while logged out and on mobile data.
- State your time zone and working hours in the employer's time, and mention your power and internet backup in one line.
Next steps
Pick your target role today and open its guide on the WorkRemote careers pages to see which tools and tasks your samples should cover. Once your first three pieces are live, search the remote job listings on WorkRemote for that role. Each listing shows where applicants may live, so you can skip ads you're not eligible for. Applying is always free, and after a search you can turn on a free email alert for new matching jobs. If you'd like a person on our team to rewrite your CV and LinkedIn so your portfolio links sit where screeners look, see what the CV and LinkedIn review covers, which is part of Premium.
Sources
- Visual Designer, Canonical (Greenhouse job board)
- Work With Us, Automattic
- What is GitHub Pages?, GitHub Docs
- GitHub Pages limits, GitHub Docs
- Managing your profile README, GitHub Docs
- Notion Sites / public pages and web publishing, Notion Help Centre


