A hiring manager abroad opens your application and has about two minutes. If your CV says "hardworking graduate" and nothing else, you lose to the person who attached three small pieces of real work. You don't need a job history to have those pieces. You need to make them on purpose.
This guide shows what a portfolio is, which samples to build for common remote roles, how to present them, and how to avoid the mistakes that make beginner portfolios look weak.
What a portfolio does for someone with no experience
Employers hire on evidence that you can do the task. Experience is only the most common form of evidence. A portfolio is another form: proof you can produce work at the standard they need, without them having to guess.
It also answers the quiet worry about hiring from Africa: "Will this person deliver without supervision?" A clear, finished sample with a short explanation of your process speaks to that worry better than a claim in a cover letter.
Pick one role first
The biggest beginner mistake is a portfolio that tries to cover writing, design, data entry and virtual assistance at once. Pick one target role and build everything for it. You can widen later.
Choose based on a skill you already have or can practise cheaply. If power cuts and data costs limit you, favour roles where you can draft offline (writing, spreadsheets, customer support scripts) and upload later.
What to build, by role
| Target role | Samples to build (3 is enough) | Where to host |
|---|---|---|
| Content writer | One how-to article, one product comparison, one email newsletter on a topic you know | Google Docs links, a free blog, or a simple site |
| Virtual assistant | A sample travel itinerary, an organised inbox plan, a cleaned-up spreadsheet of messy contacts | Shared Google Drive folder |
| Customer support | Five written replies to realistic complaints, a short help-centre article, a tone guide | Google Docs, PDF |
| Data analyst (entry) | One public dataset cleaned and summarised in a spreadsheet, one dashboard, a one-page findings note | Google Sheets, GitHub or a PDF |
| Designer | A social media set, a logo for a made-up brand, a one-page flyer redesign | Behance, Canva shared link, PDF |
| Developer | Two small working projects with a clear README | GitHub |
Where the work comes from when nobody has hired you
1. Fix a real problem for a real small business
Offer a local shop, church, school or salon one small free deliverable: rewrite its product descriptions, set up its order tracking sheet, redesign its price list. Get permission to show it. Real context beats invented context, and you can often add a one-line comment from the owner.
2. Redo something that already exists
Take a confusing app help page, a weak product description or a messy public spreadsheet and improve it. Label it clearly as a "redesign exercise" or "rewrite sample" so nobody thinks you were hired. Never use a company's logo as if you worked for it.
3. Make a brief for yourself
Write a client brief first: audience, goal, deadline. Then produce the work against it. Showing the brief makes you look like someone who thinks like a professional.
4. Volunteer for a nonprofit or community project
Newsletters, social posts, simple websites and data entry are often needed by small groups. Ask for a written confirmation of what you did, even a short email.
How to present each sample
Each piece should take under a minute to understand. Use this four-line format under every sample:
- The problem: who the work was for and what they needed.
- What you did: the steps and tools, in two or three sentences.
- The result or intended result: something concrete. "Cut the price list from three pages to one" is better than "made it look better".
- A link to the file or page, set to viewable by anyone with the link.
Be honest about what is practice work. Employers forgive "this was a self-set project". They don't forgive discovering it was passed off as paid work.
A worked example (hypothetical)
Say Amaka, a recent graduate in Enugu, wants customer support roles with overseas software companies. She has no job history. Over two weekends she does this:
- Writes five replies to invented but realistic complaints: a late delivery, a double charge, a login failure, an angry customer, a feature request. Each is under 120 words, polite and clear on next steps.
- Writes a one-page help article explaining how to reset a password, with numbered steps.
- Records a two-minute voice note summarising how she would handle a refund request, so employers can hear her spoken English.
She puts all three in one Google Drive folder, adds a one-page PDF cover sheet with the four-line format, and links it from her CV and LinkedIn. Total cost: a few hours and some data. She now has something to attach to every application, which most beginners don't.
Where to put it so people see it
- Top of your CV: one line, "Portfolio: [link]". Our guide to writing a CV for international remote roles covers the rest of the page.
- LinkedIn Featured section: pin your best two samples.
- Application emails: link the single most relevant sample for that job, not the whole folder.
Use a short, sensible link. Test it in a private browser window to check it opens without a login. Also check it loads on a slow connection, because reviewers may be travelling or on mobile.
Common mistakes
- Too many samples. Three strong ones beat twelve average ones.
- Locked links. "Request access" screens kill applications. Reviewers rarely wait.
- Stolen or templated work. Copying other people's work or passing off AI output you haven't checked is easy to spot and ends the application. If you use AI tools, edit heavily, and be ready to explain your process in an interview.
- Spelling and formatting slips. For a beginner, polish is the main signal. Read samples aloud before publishing.
- No target. A portfolio that doesn't match the job advert's tasks feels irrelevant.
- Publishing private data. Don't show real customers' names, phone numbers, BVN or NIN details in samples. Blur or invent them.
Match the portfolio to the job advert
Read the advert and list its three most repeated tasks. If it says "manage inbox, schedule meetings, prepare reports", lead with samples showing those. Rename your files to match: "Inbox-management-sample" is clearer than "Document 3".
Use the advert's wording where it's true for you. Then check the employer is genuine before sending anything personal; see how to spot a fake remote job offer. A real employer never needs payment from you to review your portfolio.
Keep improving it
After each application, note which sample got comments. Replace the weakest piece every month. Once you have a real client, even one small paid job, add a one-line testimonial and move your self-set projects lower. If you're still searching for roles, our list of places to find remote jobs that hire from Africa will help you filter.
Frequently asked questions
Do I need a personal website?
No. A well-organised Google Drive folder, Notion page or GitHub profile is fine to start. A website helps later, but only if you keep it tidy.
Can I include school projects?
Yes, if they relate to the role and you can show the output. Describe what you did yourself, especially if it was a group project.
Should I work for free to build samples?
Do small, limited favours for people you know, with a clear end. Be cautious of strangers asking for long unpaid "tests". A short, specific test is normal; weeks of real work for nothing is not.
How many samples do I need?
Three relevant ones is a good start. Quality and relevance matter more than quantity.
Your next step this weekend
Choose one target role, build the first sample using the four-line format, and put it in a link-shareable folder. Once it opens correctly in a private window, attach it to your next application.
Always apply through the employer's official website or verified channels. Genuine employers never ask applicants to pay for a job, training, or an interview.