Applications and interviews · 5 min read
Build a work portfolio for South African job applications
Select small, verifiable examples that show your own decisions, process and result.
A portfolio does not need expensive design or a long website. Its purpose is to help an employer understand how you work. A student, tradesperson, administrator or developer can use carefully chosen samples, provided they are honest and safe to share. Start with the duties in real vacancies, then build a small collection of evidence that answers those duties rather than displaying every project you have ever touched.
Choose a format that suits the occupation
A software applicant might show a repository and a short explanation of how to run it. An administrator can show a fictionalised tracker or a process note. A designer may show a few annotated images. A tradesperson could describe a practical assessment, with photographs only where permitted. A researcher can share a public report or an anonymised method summary. No employer should have to open a complex site just to learn what you did. A tidy PDF or small set of links can work well.
Read two or three real adverts and list the skills they ask for. Select one sample per important skill, not one per year of your life. Include a brief context, the problem, your own actions and the outcome. If the result was mixed, explain what you learned and changed. A clear explanation of a small real task often provides stronger evidence than a polished image without process. If the employer asks for a format or file limit, follow that instruction rather than insisting on your preferred platform.
Make your contribution and level clear
Group projects often look impressive, but recruiters may not know which part you owned. State who else worked on it and what you did personally. If you used a tutorial, say what you changed, tested or extended. Do not claim expert skill because you completed one course. An entry-level portfolio should make learning visible: a first version, the problem found, the feedback received and the improved version. It is reasonable to show supervised work as long as supervision is stated.
Use plain labels. For each sample, include tools, constraints and the decision you made. A candidate for customer support could explain how they categorised enquiries and escalated a difficult case. A finance applicant could show a fictional ledger check with formulas visible, not a real employer's accounts. A graduate may turn a course project into a short case study. Link the sample to the vacancy in one sentence in the cover letter or application field. This makes the portfolio useful rather than decorative.
Protect people and organisations in every sample
Before publishing a document, remove names, contact details, customer data, internal prices, source code you do not own and site security details. Ask permission from an employer, client or supervisor when ownership is unclear. Anonymising is more than deleting a name: combinations of dates, locations and events can identify a person. If you cannot safely share the real work, recreate the method with invented data and label it as a demonstration. Do not suggest that a fictional example is a live client project.
Keep your own identity information minimal too. A public portfolio may need a professional name and contact method, but it does not need an identity number, home address, bank details or full certificate scans. If an employer wants formal qualification proof, use its verified application process. SAQA explains the official verification route for South African qualifications; a portfolio is not a substitute for that process. Respect any confidentiality agreement from prior work. Employers may see careful handling of information as evidence of judgment.
Test whether a recruiter can use it quickly
Open the portfolio on a phone and a slow connection. Check that files load, links work and headings explain each sample. Put the most relevant work first and remove outdated or broken items. Ask a person outside your field to tell you what they think you did after reading one page. If they cannot tell, simplify the explanation. Use accessible text around images and avoid a slideshow that hides the main point. A hiring manager may spend little time on an optional link.
Keep a private master folder with original work and a separate public version. Give public files sensible names and dates. If you use a code repository, include setup instructions and avoid secrets or personal credentials. If you show a calculation, write the assumptions. If you show a design, describe the user problem and any testing. A portfolio should complement a CV, not force the reader to infer your qualification and employment history from scattered files.
Use samples in interviews and keep them current
Choose two examples you can explain without reading notes. Practise describing the task, your contribution, a challenge and the result in a few minutes. Be ready to discuss what you would change now. If an interviewer asks about something you cannot disclose, say why and offer a safe alternative example. Do not let an assessment request become unpaid production work without clarifying how it will be used. The right portfolio creates a conversation, not a claim that you can do everything.
Review samples when you learn a new skill or seek a different role. Remove an old item if it no longer represents your best work. Keep links stable in applications already sent. If a platform closes, retain a local copy you can share through an approved channel. No one needs to pay Work.net.za for a portfolio review or application. Use the employer's stated instructions and share only the samples that help answer the specific vacancy.
Sources and further reading
Explore this topic
Frequently asked questions
Do I need a website for my portfolio?
No. A clear PDF or a few accessible links can be enough. Choose the format that suits the work and the employer's instructions.
Can I use a university group project?
Yes, if you identify your own contribution and do not share classmates' or participants' private information without permission.
Should I include every certificate?
No. Keep a concise education section and provide formal documents through a verified employer channel when requested.