How to Present Personal Projects on a Remote Job Application

For remote roles, how you present a project matters even more. A recruiter in Berlin or Austin will never meet you before the first call. Your CV, your links and your written explanations are the whole first impression. This guide covers how to choose which projects to include and where each one goes, including CV, application form, cover letter, LinkedIn and interview. It also covers how to word them honestly, and the Nigeria-specific problems that trip people up: links that won't open, NYSC and school projects, and work you did for clients that you can't fully show.

Quick answer

Pick two to four projects that match the job ad. List them in a "Projects" section under your summary if you're early-career, or below work experience if you're experienced. For each one, give the title, dates, your role, tools, what you did and a measurable or checkable result, plus a public link. Use the same project in your form answers, cover letter and LinkedIn, and be ready to walk through it on a call.

What counts as a personal project

A personal project is work you chose to do, planned and finished without a job title attached. It counts on a CV when it shows a skill the employer is hiring for and someone else can check it.

Things that count:

• A dashboard you built from public data, such as an analysis of Lagos rental listings or CBN exchange-rate history
• An app, website, browser extension or automation script you built and published
• A help-centre knowledge base you wrote for a small business, a church or a student association
• A content series, newsletter or YouTube channel you ran on a schedule
• A final-year project, NYSC community development project or hackathon entry, if it uses job-relevant skills
• Unpaid or token-paid work for a local business, presented honestly

Things that usually don't count on their own:

• Course certificates (put those under certifications)
• Tutorial clones that look exactly like the course demo
• Ideas or plans that never shipped

Paid freelance work for clients is a different category. It normally belongs under experience, which our guide to highlighting freelance experience on a remote job CV covers in detail.

Why personal projects matter more in remote hiring

Remote hiring leans heavily on written, checkable evidence. Many distributed companies screen through written applications, skills tests and trial tasks before any video call. Automattic, which says on its careers page that its staff work from wherever they choose across many countries, describes an application followed by a skills assessment, often a text-based Slack interview, then a code test or a trial of up to 20 hours of real work (as of October 2026). The same page advises applicants to showcase relevant projects and contributions in their cover letter.

That process has two practical consequences for you:

• Your project is the closest thing to a work sample before the trial. A hiring manager reading 200 applications for a role open across Europe, the Middle East and Africa (EMEA) can open your link and see how you work in minutes.
• The way you write about the project is itself evidence. Remote teams communicate mostly in writing, so a clear project description demonstrates the async communication they need.

Projects don't replace experience for senior roles, and some jobs (licensed accounting, regulated healthcare work) still need formal credentials. For entry-level and career-change applications, though, a well-presented project is often what gets you shortlisted. Our guide to remote jobs for Nigerians with no experience explains which roles are realistic starting points.

How to choose which projects to include

Two to four projects is the useful range on a CV. One looks thin. Six reads as a list nobody will open.

Before you add a project, run it through this test. Each "yes" earns a point. Include projects that score four or five, and drop anything under three.

Tailor the selection for each application. A data analyst applying to a fintech company should lead with the transactions analysis, not the football stats dashboard, even if the football one took longer.

Where personal projects go on your CV

Early-career or career change: projects near the top

If projects are your strongest evidence, place a section called "Projects" or "Selected projects" straight after your professional summary and before education. The UK government's National Careers Service advises that people applying for a first job can focus on skills learned through projects, work experience or volunteering, which supports giving projects real space rather than hiding them.

Experienced: projects below work experience

If you already have relevant jobs, keep work history first and add a short projects section afterwards. Use it to fill a specific gap. A support agent moving into data analysis might list two analysis projects that the current job doesn't show.

Don't disguise projects as jobs

Never list a personal project as if it were employment with a company. Don't invent a company name or give yourself a title like "CEO, AnalyticsHub" for a solo weekend project. Background checks and reference calls expose it, and remote employers who hire through an employer of record (EOR) often verify employment history. If a project grew into something with real users or revenue, say so plainly inside the project entry.

The format of a project entry

Each entry needs six parts, kept to three or four lines:

1. Project name and link on one line
2. Dates (month and year)
3. One-line purpose: what problem it solves and for whom
4. Your role, especially if others were involved
5. Tools used, named exactly as the job ad names them
6. One or two result lines that someone can check

Keep it plain text. Many applicant tracking systems (ATS), the software companies use to collect and filter CVs, read text more reliably than text boxes, icons or two-column templates. Write the link out in short form (github.com/yourname/project) so it survives if the CV is printed or the hyperlink is stripped.

Writing project descriptions that show results

Use this pattern for each bullet: what you did, how you did it, and what changed as a result. Start with a strong verb, name the tool, then give the result.

Weak: "Built a dashboard using Power BI."

Stronger: "Built a Power BI dashboard tracking 18 months of naira and dollar prices for 40 food items from public NBS data, cutting a weekly manual price report from three hours to 15 minutes for a Lagos food vendor."

Honest numbers only. If you don't know the result, use a result you can check instead:

• Users or downloads (from your analytics or app store console)
• Time saved (measured before and after)
• Response rate, open rate or completion rate (from the tool's own reports)
• Size of the data, codebase or content set
• Feedback from a real person you can name as a reference

If the project had no measurable outcome, describe the scope and the hardest problem you solved. "Handled offline sync so field staff could log entries without data and upload later" is specific and believable. A made-up "increased efficiency by 47%" is neither.

Example (hypothetical): three project entries for different roles

The three entries below are invented to show the format. They aren't real people or projects.

Data analyst

Lagos Rent Tracker | github.com/adaeze-o/lagos-rent | Jan to Mar 2026 Solo project analysing 6,000 scraped rental listings to compare rent by area and property type. Tools: Python (pandas), SQL, Power BI - Cleaned listings with inconsistent naira formats and duplicate posts, documenting each step in the README - Published an interactive dashboard; shared in two data communities, where 3 analysts suggested fixes I merged

Customer support specialist

Help Centre for a Kano Fashion Store | link to public Notion page | Aug 2025 Volunteer project writing a self-service help centre for an online store receiving repeated WhatsApp questions. Tools: Notion, Google Forms, Canva - Wrote 22 articles covering delivery, sizing and returns, in plain English with screenshots - Store owner reported fewer repeat questions on delivery times in the following month (reference available)

Content writer

Remote Work Explained newsletter | link to archive | Jun 2025 to present Weekly newsletter explaining remote work terms for Nigerian graduates. Tools: Substack, Google Docs, Grammarly - Published 30 consecutive weekly issues without a missed deadline - Grew to 410 subscribers through LinkedIn posts, with open-rate screenshots available on request

Each entry uses a different kind of evidence: public code, a reference, a publishing record. That variety is what makes them believable.

Making your project links work for a recruiter abroad

A broken link loses the shortlist place. Before sending any application, open every link in a private browser window while signed out. Then open it again on a phone using mobile data.

Permission and access problems

• Google Drive and Docs: set sharing to "Anyone with the link can view". A recruiter won't request access, they'll move on.
• Notion: publish the page to the web, then check it signed out.
• GitHub: make the repository public, and pin the projects you want seen. GitHub lets you pin up to six repositories or gists to your profile, so pin only the ones that match your target roles.
• Hosted demos on free tiers: many free hosting plans put an app to sleep when nobody visits, so the first load can take a long time. Add a screenshot or a short screen recording to the README so the reviewer sees it working even if the demo is slow.

A GitHub profile README for developers and data people

A profile README is the page someone sees at the top of github.com/yourname. According to GitHub's documentation, it only appears when the repository has exactly the same name as your username, is public, and contains a README.md file with content in its root. Use it for three or four lines: what you do, the roles you're targeting, and links to your best two projects.

Inside each project repository, the README does the explaining a CV can't:

• What the project does, in two sentences
• A screenshot or GIF
• How to run it
• Decisions you made and trade-offs you accepted
• What you'd improve next

Developers who need more than this should read our guide on building a software portfolio that attracts remote employers.

Non-code projects

Designers, writers, marketers and support specialists usually do better with a one-page case study (PDF or web page) than with a raw folder of files. Cover the problem, your approach, two or three visuals, the result and what you learned. Keep the PDF small so it opens quickly on a weak connection. Our guides on design portfolios for remote employers and professional writing portfolios go into role-specific detail.

Presenting projects in forms, cover letters and LinkedIn

A remote application rarely stops at the CV. Use the same project, told the same way, everywhere it appears. Inconsistencies (different dates, different numbers) make reviewers suspicious.

Application form fields

Greenhouse, Lever, Ashby and Workable forms often include fields such as "Portfolio URL", "GitHub" or "Website", plus free-text questions like "Tell us about something you built". Practical rules:

• Put your single strongest link in the portfolio field, not a link to a page of links, unless the role is design or writing, where a portfolio home page is expected.
• Answer the free-text question with one project, in about 100 to 200 words: the problem, what you did, the result, and what you'd do differently.
• Write the answer in a document first. Forms can time out, and a power cut halfway through a long answer means starting again.

Cover letters

Pick the one project that best matches the job ad and give it a short paragraph. Name the tool, the result and the link. Don't summarise your whole CV. Our guide on writing a remote job cover letter covers the rest of the letter.

LinkedIn Projects and Featured

LinkedIn's profile help page lists a Projects section for showing projects you've worked on along with team members. Use it for the same two to four projects on your CV.

The Featured section is more visible because it sits near the top of your profile. LinkedIn's help page on Featured work samples says you can add external links such as a portfolio, uploaded documents, images and videos, and your own posts and articles (as of October 2026). A good Featured row has a case-study PDF, the live project link and a short post you wrote about what you learned. More on profiles in our guide to writing a LinkedIn profile for remote job opportunities.

Talking about your projects in interviews and assessments

Expect a remote interviewer to say "Walk me through this project" or to share their screen and open your repository. Prepare a two-minute version for each project:

1. The problem and who it was for
2. What you built and the main tools
3. The hardest decision and why you chose that way
4. The result
5. What you'd change now

Practise the walkthrough with your screen shared. Rehearse it once with your camera on, during your usual power and internet setup, so you know your inverter or hotspot holds for the length of a call.

If you used AI tools such as ChatGPT, Copilot or Claude to build or write parts of the project, say so and explain what you checked and changed yourself. Interviewers increasingly ask, and an honest answer goes down better than being caught out. For more interview practice, see our guide on explaining your remote work experience in an interview.

Nigeria-specific points to get right

NYSC, university and SIWES projects

Final-year projects, Students Industrial Work Experience Scheme (SIWES) placements and NYSC community development projects can all go in a projects section, but rewrite them for a foreign reader. "CDS project, Ikorodu LGA" means nothing abroad. "Organised a free digital-skills workshop for 60 secondary-school students, managing registrations in Google Forms and a volunteer schedule in Google Sheets" does. Our guide for Nigerian students and fresh graduates covers other ways to use those years.

Small paid or unpaid local work

Many Nigerians have built a website for an uncle's shop or run Instagram for a friend's business for a token fee. Present it as a project if it was informal and you had no contract. If it was ongoing and paid, it's freelance experience. Whichever you choose, describe the business accurately ("a family-owned pharmacy in Enugu") and don't inflate it into "a leading retail chain".

Client data and confidentiality

Don't publish real customer names, phone numbers, BVNs, account details or internal documents in a project, even if a business owner gave you access. Recreate the work with dummy data, blur screenshots, or describe the project without the files. Ask permission before naming a business. A remote employer will read a careless data leak in your portfolio as a warning about how you'd handle their customers.

Time zones as part of the story

If a project involved people abroad, such as an open-source contribution reviewed by maintainers in the US, or a hackathon team split between Lagos and London, say so. A line like "Coordinated asynchronously with a maintainer in New York, six hours behind Lagos in winter" shows exactly the working pattern remote employers worry about. US Eastern time moves to six hours behind Lagos from 1 November 2026.

Keep an offline copy

Keep a PDF of each case study and a short screen recording of each app on your laptop and phone. If your hosting goes down or the internet fails just before a call, you can still share your screen and walk through the work.

Common mistakes that weaken personal projects

• Listing tutorials as original work. Reviewers recognise popular course projects. If you started from a tutorial, say so and describe what you added.
• No link, or a link that needs permission. Treat every unchecked link as broken.
• Tool lists with no outcome. "React, Node, MongoDB" tells the reader nothing about what you can do.
• Too many projects. Six weak entries hide the one strong one.
• Inflated titles or invented companies. These fall apart at the reference or background check stage.
• Doing large unpaid "test projects" for strangers. A short skills test is normal. A request to produce days of real deliverables for free, often from a recruiter you can't verify, can be a way to get free work. Read our guide to spotting remote job scams in Nigeria.
• Different details in different places. Match dates and numbers across your CV, LinkedIn and form answers.

Frequently asked questions

Should personal projects go under work experience on a CV?

No, unless the project became genuine paid work with clients. Put personal projects in a separate "Projects" section. Presenting a solo project as a job misleads the employer and usually comes out during reference checks.

How many personal projects should I put on my CV?

Two to four is usually right. Choose the ones that use skills named in the job ad and that a reviewer can open and check. Rotate them for different applications instead of listing everything you've built.

Can I include a project I did with a team or at a hackathon?

Yes, but state your role clearly. Write what you personally did, for example "built the payment screen and wrote the API tests", and mention the team size. Interviewers will ask about your part, and vague answers suggest you did little.

Do personal projects count if they never made money?

Yes. Employers care about the skills shown and whether the work was finished and well explained, not whether it earned income. A result such as users, time saved or a working feature you can demonstrate is enough.

What if my best project used a client's confidential data?

Describe it without exposing the data. Rebuild a version with dummy data, blur sensitive screenshots, or write a case study that explains the problem and your approach. Get the owner's permission before naming the business.

Is it okay to say I used AI tools on a project?

Yes. Say which tools you used and what you checked, tested or rewrote yourself. Hiding it is risky if the interviewer asks, and many remote teams use AI tools daily, so honest, careful use reads well.

Where do I put project links if a job application form only accepts a CV upload?

Put the links in the CV itself. Write short, readable URLs next to each project title, and add your portfolio or GitHub link to the contact line at the top. If there's a cover letter field, mention your strongest project link there too.

Key takeaways

• Put two to four relevant projects in a dedicated "Projects" section, near the top if you're early-career or changing careers.
• Each entry needs a name, dates, role, tools, a checkable result and a link that opens without permission requests.
• Write results honestly: users, time saved, scope or a named reference, never invented percentages.
• Tell the same project the same way across your CV, application form, cover letter and LinkedIn Projects or Featured section.
• Rewrite NYSC, SIWES and school projects for a foreign reader, and never publish client or customer data.
• Prepare a two-minute screen-shared walkthrough for each project, and keep offline copies in case your connection fails.

Next steps

Pick your strongest project today and rewrite its entry using the six-part format above. Then check every link signed out and on mobile data. Next, find roles where that project is relevant on the WorkRemote job listings, where each listing shows where applicants may live. After a search, use "Get email updates" to get new matching jobs in a daily email. If you want someone to rework how your projects read, the CV and LinkedIn review is part of WorkRemote Premium. For the skills and tools each role expects, browse the remote career guides by role.

Sources

• Work With Us, Automattic
• CV sections, National Careers Service (UK government)
• Managing your profile README, GitHub Docs
• Pinning items to your profile, GitHub Docs
• Your LinkedIn profile, LinkedIn Help
• Manage featured samples of your work on your LinkedIn profile, LinkedIn Help