A job search portfolio is a small collection of evidence that shows how you work. It can help a recruiter understand a skill that is difficult to assess from a job title alone. An operations applicant might show a simplified handover checklist; a teacher might share a sample lesson plan; a junior analyst might explain a decision made from a public dataset. The purpose is to give the reader a useful example and enough context to interpret it. You do not need a personal website, expensive design tools, or material from a former employer.
Job search portfolio: start with a hiring question
Choose a role and list the questions a recruiter might reasonably ask after reading your CV. Can you explain a complicated process in plain language? Can you check a spreadsheet before it is used to make a decision? Can you document a change so that the next person understands it? One portfolio item can answer one clear question. When a sample tries to prove every skill, the important part can be difficult to find.
Write a short purpose statement for each sample before choosing its format. “Show how I found and explained two inconsistencies in a dataset” is concrete. “Demonstrate my business expertise” is too broad to guide the work. A one-page explanation or a small annotated screenshot often communicates more than a complete set of files. Keep full supporting materials available when appropriate, but make the first version easy to skim.
Sample one: show how you solve a problem
Choose a problem with a clear beginning and end. An example could be a small inventory exercise using made-up figures. You notice that the closing count differs from the recorded quantity, trace the difference to a duplicated receipt, and explain which entry needs to be reviewed. Use a small table to show the starting state and the corrected outcome. Explain why you preserved the original records and how you separated assumptions from verified facts.
A useful caption tells the reader what you want them to notice. For example: “The exception column separates mismatched entries from items that have not yet been checked.” The caption should say more than “Spreadsheet sample.” If the exercise is fictional, label it as a demonstration. A transparent example can show good reasoning without suggesting that a real company commissioned the work.
Sample two: make a complicated instruction easier to use
Pick a procedure you can describe without exposing private information. Examples include setting up a practice meeting, organizing an equipment sign-out sheet, or explaining how to submit a support request in a demo system. Write a first version, then ask someone unfamiliar with the process to follow it. Note where they hesitate or misunderstand what to do next. Revise the instruction using what you observed.
Show a short before-and-after comparison. If the first version used the heading “Complete onboarding,” the revised version might specify who confirms access, where to record completion, and which step comes next. Explain why you made those changes. This shows the reader that you can test whether communication works, instead of simply choosing a more attractive template or adding decorative detail.
Sample three: document a decision and its tradeoff
Employers often want to understand why you chose an approach. Create a brief decision note with a goal, two plausible options, and a reason for your choice. For example, a community group needs a way to collect event bookings. A shared spreadsheet is familiar but may create editing conflicts; a form collects consistent information but someone must check responses regularly. State which constraint matters most for the scenario.
Include one thing that might change your recommendation. Perhaps the spreadsheet is suitable for ten organizers but less suitable for many independent contributors. The goal is to show that you can make decisions with imperfect information and revisit them when conditions change. Avoid presenting the example as universal advice. Show the context that made your recommendation reasonable.
Sample four: explain your contribution to a team project
A team project can be a strong sample when the reader can tell what you did. Describe the shared objective in one sentence and your contribution in another. Identify any part that belongs to someone else. If you helped organize feedback on a student project, explain which responses you summarized, what pattern you identified, and how the group used the findings. Do not publish teammates’ names or work without permission.
If the original material is private, build a simplified exercise that illustrates the same skill. Use synthetic names and values, and label the result as a reconstruction. Check screenshots for browser tabs, account identifiers, emails, document paths, and other details that can remain visible even after obvious information is removed. When in doubt, create the sample from scratch using public or invented data.
Sample five: show revision after feedback
Select a work sample you genuinely improved. Write down the initial goal, the feedback, what you changed, and the effect of the change. For instance, you created a report summary that readers found difficult to scan. After feedback, you moved the decision to the opening paragraph and placed the background in an appendix. A short side-by-side explanation can show why the second version is more useful.
Do not include feedback that identifies a customer or colleague. Summarize the substance in your own words. If the change was not tested, say what you expect it to improve and how you would check that expectation. A clear distinction between observed results and expected benefits makes a sample more credible.
Put the samples into a readable package
Use a simple index with a title, skill, and short description for each item. Keep an offline copy you can open during an interview. If you use a shared link, check it in a signed-out browser to make sure it opens without exposing folders you did not intend to share. Use readable file names and accessible text rather than putting every explanation inside an image.
For each application, choose the two or three samples most relevant to the vacancy. Point to a particular item when you discuss a skill, and be ready to explain how you produced it. Review the portfolio periodically and retire examples that no longer represent your best work. A few examples with clear context, honest authorship, and a practical explanation can do more for a reader than a large archive of unrelated files.
For more ideas about formats and sharing, see CareerOneStop’s guide to portfolios.
Frequently asked questions
Does a job search portfolio need its own website?
A job search portfolio can be a short PDF or a shared folder. Test the link in a private window and name each sample so a reviewer can find it without opening every file.
What if my best job search portfolio sample is confidential?
Build a new sample from scratch with fictional data and label it as a demonstration. A job search portfolio should show what you can do without revealing a former employer’s records.
Related career guides
Read how to tailor a CV for international jobs · cover letter guide · video interview preparation guide.