Careers & Jobs
Building a Digital Portfolio for an Entry-Level Job
Build an entry-level digital portfolio with relevant projects, clear case studies, honest credits and reliable access for employers.
At a glance
Select work relevant to the vacancy.
Explain your own contribution and limitations.
Check permissions, privacy and access before sharing.
A digital portfolio gives someone a way to inspect your work and understand how you approached it. For an entry-level applicant, that work might come from a course, a personal project or an authorised voluntary task. You do not need to invent clients or paid experience to make it useful.
The aim is a small, clear selection that supports the role you want. A portfolio is particularly familiar in creative and technical recruitment, but it is not required for every vacancy. Follow the application instructions first and use work samples where they help demonstrate relevant ability.
Choose the audience before the platform
Start with a role description. What would the employer need to see to understand your contribution? A design role may need visual decisions and iterations; an administration role might benefit from a fictional spreadsheet or a well-structured procedure. The sample should relate to the work, not simply show that you can upload files.
The National Careers Service graphic designer profile identifies portfolios as a way to show creative ideas and skills to employers. That is a useful example of a role where work samples matter. It does not mean that every applicant needs a complex website or the same type of portfolio.
Use the job advert’s requirements to choose what belongs. If an employer requests a PDF with a size limit, make that version. If it asks for a link, check that the destination opens reliably and that the first screen tells a reader what they are looking at.
Select a few projects with clear evidence
Begin with three strong samples as a manageable editorial choice, not an industry rule. Look for different evidence across them: research, execution, problem solving or revision after feedback. Five nearly identical pieces may explain less than two carefully chosen projects with different demands.
Label the context honestly. “Personal practice project using fictional data” is a useful description. “College group project; I created the page layout and tested the navigation” makes your contribution understandable. Avoid presenting a template, tutorial result or team output as entirely your own original work.
If your work is limited, create one focused practice brief. For example, design an information sheet for a fictional community event, build a small booking-data summary with invented records or write a concise help article for a familiar everyday process. Define what success means before starting so you can assess the result.
| Sample | Evidence to show | Context to disclose |
|---|---|---|
| Design project | Brief, drafts and final layout | Personal, course or authorised client work |
| Spreadsheet | Inputs, checks and readable summary | Fictional data and assumptions |
| Writing sample | Audience, structure and edited version | Sources, permissions and your role |
| Coding project | Working example and clear explanation | Dependencies, limitations and contributions |
| Group project | Your individual tasks and decisions | Credit for collaborators and shared work |
Write a short case study for each sample
Give every project a title that explains what it is. Then cover the brief, your role, the approach, the result and what you would improve. A reader should not have to infer all of this from a screenshot. Keep the explanation concrete enough that you could discuss it in an interview.
For a fictional spreadsheet project, you might explain that the goal was to summarise weekly enquiries, that you checked for duplicate records and that you added a separate assumptions note. Show how you verified a total. Do not invent a claim that the sheet saved a company ten hours when no company used it.
A result can be modest and still informative: the layout became easier to scan after a peer review, the calculation matched a manual check or the prototype completed the intended task. If evidence is informal, say so. The STAR structure can help organise an explanation, but a portfolio case study should also let readers inspect the work itself.
Show how to understand or use the work
Include a short orientation beside a download, demonstration or repository. Tell the reader what to open first, what the sample does and any important limitation. Avoid requiring a recruiter to install unfamiliar software simply to understand the basic idea.
For coding work, GitHub’s README guidance explains how a project introduction can describe its purpose and how to get started. You can apply the same communication principle to other formats: provide enough context to make the evidence usable.
If a live demonstration is unreliable, include a clearly labelled recording or screenshots alongside the explanation. State what is functional and what is a mock-up. A prototype can be valid entry-level evidence when its scope is clear; presenting it as a deployed service would mislead the reader.
Check permission, privacy and attribution
Use material you created or have permission to share. GOV.UK explains that copyright protection can arise automatically. Finding a photograph, design or document online does not by itself give you permission to republish it in your portfolio. Keep a record of licences and attribution requirements for third-party assets.
Before sharing workplace or voluntary work, ask the appropriate person what can be shown. Remove personal information, confidential figures, access credentials and private correspondence. Replacing a company name is not enough if the remaining detail still identifies people or reveals sensitive business information.
Where permission is unavailable, create a separate fictional example that demonstrates the skill without reproducing the restricted material. If you used AI assistance, describe its relevant role and your own checking honestly, particularly when the employer asks about tools or authorship. You should be able to explain the decisions behind the final result.
Make the portfolio easy to review
Use readable type, clear headings and descriptive link names. Test the page or document on a phone as well as a larger screen. Check contrast, image descriptions and whether the content still makes sense without an animation or video playing automatically.
Ask a trusted person to review the access path without using your account. Can they open the link, identify your role and find a relevant sample? A file visible only to its owner will not help an application. Choose access settings deliberately and share only the material intended for that audience.
Keep contact details proportionate: a professional email address or the contact route requested by the employer is usually more useful than a public home address. Match the portfolio’s project names and dates with your CV so that the two tell a consistent story.
Choose evidence relevant to the vacancy.
State the brief and your contribution.
Review permissions, accuracy and access.
Send the format the employer requests.
Common questions
Do I need paid client work?
No. Clearly labelled personal, course or voluntary projects can show relevant skills. The important point is to describe the context and your contribution truthfully.
How many projects should I include?
Choose enough to demonstrate the relevant skills without repetition. Three is a useful starting exercise, but the employer’s requirements and the quality of your evidence matter more than a fixed number.
Must I pay for a website?
Not necessarily. A suitable document or existing platform may meet the request. Decide the format from the application instructions, access needs and type of work before spending money.
Can I include a group project?
Yes, where sharing is permitted. Identify the team context, credit others and explain exactly which decisions and outputs were yours. Do not claim sole ownership of shared work.
What if my project is unfinished?
You can show a work in progress if it provides useful evidence and you label its status clearly. Explain what works, what remains and what you would do next.
Should I include every exercise from a course?
Usually a selection is easier to review. Choose examples that support the vacancy and explain what they demonstrate. Keep less relevant practice material in your own archive.
Can I show a project that used AI?
Follow the employer’s rules and be transparent about meaningful assistance. Explain what you contributed and how you checked the output. Do not claim generated work as evidence of skills you cannot demonstrate.
How often should I update it?
Review it when applying for a different role or completing stronger work. Check links and access before every application, even when the content has not changed.
Sources and further reading
- National Careers Service: graphic designer
- GitHub Docs: repository READMEs
- GOV.UK: copyright protection
Sources checked 21 October 2026. Project-selection and presentation examples are editorial suggestions, not universal employer requirements.
