A job title asks the reader to imagine the work behind it.
A small piece of work gives them something they can actually examine: a decision explained clearly, a process made understandable, a problem broken into useful parts. That is one reason I like the idea of a work sample. It can move a conversation from “trust my description” to “let’s look at this together.”
Imagine someone explaining that they are good at organizing complicated tasks. They could list the responsibilities they have held. They could also show a simple plan made for an invented situation: a community event with a venue, deliveries, volunteers, and several decisions still open.
The plan would not prove they can run every real event. It would reveal some choices. Did they notice that one task depends on another? Did they distinguish a confirmed arrangement from an assumption? Can another person understand where to begin?
For me, that is the useful promise of a sample. It makes part of someone’s judgment visible. It gives the other person a better question to ask next.
There is a related idea in the U.S. Office of Personnel Management’s guidance on work samples: a formal work sample asks applicants to perform tasks resembling the job. The guidance recommends it for skills applicants are expected to have on entry, rather than skills the employer intends to teach afterward. The fit between the example and the actual work matters.
A self-chosen portfolio piece is not the same as a structured assessment. We choose what to show, and usually choose something that presents us well. That makes the explanation around the piece important. What was the purpose? Which part did we do? What help or tools were involved? What would we change if the constraints were different?
The explanation belongs with the work
A polished document can hide a weak decision. A rough page can contain careful thinking. I would rather see the reasoning behind a tradeoff than be left to infer competence from the neatness of the layout. Presentation helps someone enter the work; it should not have to carry the whole claim.
In the imagined event plan, the interesting conversation might begin with an omission. Why is there no detailed volunteer schedule? Perhaps the person has identified that the venue must be confirmed before the roles can be assigned. Perhaps they simply forgot. The page alone cannot tell us which. Their explanation can.
A sample also has boundaries. Some work is confidential. Some good work happens through conversations, judgment under pressure, or contributions that belong to a team. A person should not have to expose a former employer’s material to make experience believable. A fictional example can be useful when it is clearly labeled and does not borrow private facts.
That matters especially when someone is making experience understandable in a new country or setting. The familiar labels may not travel well. A concrete example can create a starting point, while the wider history still deserves to be heard.
There is a responsibility on the receiving side too. If we ask to see work, the request should be proportionate to what we need to understand. Asking for a small relevant example is different from expecting a candidate to complete a substantial real project for free. Curiosity about ability should not become a way to acquire unpaid work.
For someone looking for feedback, one piece can make asking for useful advice easier. Instead of asking whether they seem ready for a whole profession, they can ask whether this explanation is clear, what assumption seems weakest, or which decision deserves another look.
I would not ask one piece of work to tell the whole story of a person. It cannot show every condition they have faced, every quiet contribution, or what they will be able to learn next.
It can give two people something specific to discuss. Used with that modest expectation, a sample does not close the question of someone’s ability. It opens a better conversation about it.
