“Please send samples of your work.” For a graduate seeking a first job, that request can feel like a closed door. How do you show past work when nobody has employed you yet?
A portfolio provides part of the answer. It is a small, organised collection of evidence showing how you approach a problem and what you can produce. It may contain designs, spreadsheets, reports, lesson plans, presentations, code, writing samples, process documents or before-and-after demonstrations. It does not need to be a costly personal website.
The goal is not to make your work look bigger than it is. The goal is to show employers a few relevant examples that are clear, accurate and genuinely yours. This guide explains how to build such a collection using accessible tools and projects you can create without a previous formal job.
Understand the difference between a portfolio and a certificate
A certificate may show that you attended or completed a course. A portfolio demonstrates what you made or did with the knowledge. A recruiter who sees “Excel” on a CV may wonder whether you can work beyond basic data entry. A portfolio containing a labelled workbook with formulas, error checks and a short explanation provides a stronger basis for assessment.
The two can complement each other. A candidate for a regulated role may need specified qualifications regardless of portfolio quality. For other roles, relevant projects can help employers evaluate practical ability.
Keep the portfolio focused on one job family. A collection with three strong administrative projects is often more useful for an operations role than a colourful website containing unrelated songs, drawings and opinion pieces.
Step 1: choose the role and identify its real tasks
Start with five to ten current vacancies for the job you want. Read the duties, not only the job title. Group recurring responsibilities under verbs: prepare, analyse, communicate, design, organise, test, teach, record or coordinate.
Suppose you want to become a junior monitoring and evaluation assistant. You might find duties involving survey forms, data cleaning, summaries and reporting. A relevant portfolio should therefore contain a short questionnaire, a properly structured sample dataset, an analysis table and a clear report. A gallery of unrelated motivational graphics will not demonstrate those tasks.
For an administrative role, look for document control, schedules, spreadsheets and correspondence. For social-media work, look for audience understanding, content planning, writing and performance evaluation. For entry-level teaching roles, look for curriculum planning, assessments and learner feedback.
Step 2: build three projects that show different strengths
A useful beginner's portfolio can consist of three pieces:
A technical or functional project showing that you can perform a core task.
A communication project showing that you can explain findings or decisions clearly.
A problem-solving project showing how you think, test options and improve an output.
The projects should be small enough to complete well. Employers are more likely to understand a tidy five-page case study than a half-finished application with 30 broken pages.
Here are concrete project combinations for different career paths:
Target roleProject 1Project 2Project 3 Administrative assistantSample inventory registerMeeting agenda and minutesCustomer enquiry log Entry-level accountantFictional cashbookBank reconciliation exerciseMonthly expense summary Communications assistantFour-week content calendarPress-style announcementAudience engagement report Customer supportEnquiry response templatesComplaint escalation flowFAQ improvement proposal Data analystClean public datasetDashboard with stated assumptionsTwo-page findings memo TeacherLesson plan and worksheetAssessment rubricLearner-support activity plan Software developerSmall working applicationDocumented code repositoryBug-fix case study All fictitious business transactions should be explicitly marked as invented. Where public datasets are used, cite their origins and check licences or usage terms.
Step 3: use a simple case-study format for every project
A portfolio is not just a pile of files. Each project needs context so a reviewer can understand what it proves. Use six headings:
Problem: What situation were you trying to address?
Your role: Did you work alone? If others contributed, what part was yours?
Tools and method: Which tools, research steps or procedures did you use?
Output: What did you produce? Link or display it.
Result or evaluation: What did you verify? For a demonstration project, explain what worked in testing rather than claiming actual commercial impact.
Reflection: What would you improve if you repeated the work?
This framework helps an employer assess both practical skill and judgement. A junior designer might show two drafts, explain a readability problem and describe how they improved hierarchy. A junior analyst might present incorrect data entries they detected and explain how they validated the final figures.
A worked example: an inventory project for an operations role
Imagine that you are applying for an operations assistant vacancy in Abuja. You decide to create a sample stock tracker for a fictional neighbourhood shop. Do not use a real shop's records unless the owner has authorised that use.
Create a spreadsheet containing 40 invented products, stock units, unit costs, receipts, issues and closing balances. Add a rule to flag products that fall below a chosen stock threshold. Produce a one-page summary of stock movements and items requiring review.
Then write a 250-word note:
“This demonstration project illustrates how a small shop could record stock movements and identify items running low. I created fictional transactions, built a closing-balance formula and checked five sample rows manually. The file is not based on any real retailer's business records. If implemented, the next step would be to agree on stock-count procedures and reconcile records with physical inventory.”
That explanation shows technical work, transparency and operational thinking. The project is not a claim that you improved a real company's profits.
Step 4: make evidence easy to inspect
Each project should have a descriptive title, a short overview, readable files and a clear indication of what the reviewer should look at. Do not require someone to download ten folders to understand one accomplishment.
You may host simple project links in a shared folder with carefully managed viewing permissions, create a small PDF portfolio or use a personal website. For many entry-level roles, a well-ordered PDF with links is enough.
Professional platforms can help too. LinkedIn's official guidance explains that work samples such as documents, articles and external links can be displayed in the Featured section of a profile. Its profile section guidance also lists projects and volunteer experience. Features may change, so follow the current platform instructions.
For coding projects, a source repository can show how you structure work and document decisions. For visual design, an image gallery may be appropriate. For research, provide a short report and clear data sources. Choose the platform the intended reader can access easily, including on a mobile phone with limited data.
Step 5: write descriptions that explain the value
Weak portfolio caption: “This is my amazing Excel dashboard.”
Stronger caption: “A sample monthly expense dashboard built from fictitious transactions. It separates categories, calculates totals and highlights differences between budgeted and actual expenditure.”
Weak caption: “Social media design for a popular brand.”
Stronger caption: “Unofficial design exercise for a fictional food-delivery brand. The brief was to create four mobile-friendly offer posts while keeping text legible.”
If you create a personal redesign of an existing company's website, state that it is an unsolicited concept and not commissioned or endorsed by the company. Avoid using protected logos, private data or other people's copyrighted work without permission.
Step 6: use Nigerian realities as meaningful project constraints
A local-context portfolio can demonstrate thoughtful problem-solving. A logistics candidate might design an order-tracking process accounting for failed deliveries and customer address confirmation. A school administration candidate might build an attendance template suited to classes that use paper registers before transferring information to a computer. A community health communications candidate might design a plain-language information sheet with clear sourcing and referral to qualified professionals.
These are project ideas, not claims that every Nigerian employer faces the same constraints. Explain your assumptions, test them with reasonable evidence and avoid stereotyping users or regions.
For technology-focused graduates, the official 3 Million Technical Talent programme includes skills such as data analysis, quality assurance, software development and user-experience design. Its placement information discusses trained talent moving into internships, jobs and freelance micro-work. This is a verified example of the connection between applied skills and career opportunities, not proof that participation guarantees placement.
Step 7: present your own contribution clearly
A final-year group project may be useful, but “we built an app” does not explain what you personally contributed. Write: “I designed the form validation and tested the registration flow while other team members handled database and visual design.” If you led research interviews or the presentation, state that precisely.
Use authorised work only. Never publish another person's bank statement, student records, customer list, medical information, employee file or login credentials to demonstrate your skills. Anonymisation can be helpful, but it must be effective and lawful; if in doubt, use a fictional dataset.
Do not buy fake testimonials, publish altered certificates or ask someone to pretend that you worked for their company. Integrity is an asset in the hiring process.
Step 8: complete the portfolio in 14 days
You do not need to become an expert in two weeks. The objective is to produce a credible first version.
Days 1–2: Pick one target job family, review vacancies and select three useful tasks.
Days 3–5: Complete your first project, including notes about assumptions and checks.
Days 6–8: Create a second project that demonstrates communication or documentation.
Days 9–11: Finish a third project demonstrating problem-solving or improvement.
Day 12: Edit project descriptions for accuracy, clarity and relevance.
Day 13: Assemble a readable PDF or portfolio page, test links and check mobile readability.
Day 14: Ask someone familiar with the field to review it. Remove weak material and correct errors.
The timeline is illustrative. A technical project may take longer; a short writing or administration portfolio may take less time. Quality is more important than meeting a calendar at all costs.
Step 9: link your portfolio to your CV and applications
Do not simply include a generic portfolio URL and hope the recruiter explores it. In your CV, reference the most relevant project beside the relevant skill. In a cover note, write one sentence connecting a project to the advertised work:
“I have attached a sample stock-control spreadsheet showing how I record transactions, check balances and flag low-stock items, which relates to the inventory support duties in your advert.”
When interviewed, be ready to explain how you created the project, what went wrong and which parts you would change. An employer may learn more from your reasoning than from the appearance of the final file.
Frequently asked questions
Can a portfolio replace work experience?
It can help demonstrate skills when paid experience is limited, but it cannot automatically replace licences, professional requirements or specific experience that an employer genuinely needs. Think of it as evidence that supports your application.
Do I need to pay for a website?
No. A readable PDF and appropriately shared links can be enough. A website can help if the role involves web work, writing, visual design or a public body of work, but it is not a compulsory first step.
Can I use school assignments?
Yes, if they are your work and you have the right to share them. Remove private information and credit collaborators. Explain the assignment's purpose and your contribution rather than submitting it without context.
Should I publish unfinished projects?
You can describe ongoing work when it is genuinely relevant, but your main portfolio should prioritise complete, reviewable examples. A half-built prototype may be useful for certain technical discussions if you explain its limits honestly.
How many projects should a fresh graduate include?
Three carefully selected examples are a practical starting point. Add more only when they contribute distinct, relevant evidence. A portfolio is a curated argument, not an archive of everything you have ever done.
Build evidence before you are asked for it
Select one common task from your target role today. Create a small project, explain your method and make it easy to inspect. When someone asks what you can do, you will have something more convincing than a list of adjectives: a piece of work that can be assessed.













Reader conversation
0 approved comments