A Portfolio That Works When Nobody Knows Your Employers
When someone hires from another continent, they cannot call your previous manager, do not know whether your former employer was a market leader or a three-person shop, and have no shared contacts to ask. Everything that vouches for you locally stops working.
A portfolio is what fills that gap. Not a gallery, and not a personal website with a hero image: a small set of worked examples that let a stranger evaluate your judgement.
Why reputation does not cross borders
Because reputation is a network property, and networks are local. A recruiter in another country cannot verify your employer's standing, cannot reach anyone who worked with you, and cannot calibrate your job titles against theirs. Evidence is the only thing that transfers intact.
This also explains a common frustration: strong candidates with excellent local track records getting no traction internationally. Nothing is wrong with the track record. It simply is not legible to someone outside the market.
| Signal | Works locally | Works internationally |
|---|---|---|
| Previous employer's name | Strong | Usually meaningless |
| Job title | Understood | Calibrates differently by market |
| Mutual contacts | Decisive | Rarely available |
| Worked examples with outcomes | Useful | Decisive |
In shortEvidence is the only credential that survives crossing a border intact.
What a credible case study contains
Four things: the problem with its constraints, what you specifically decided, what you rejected and why, and the measurable outcome. The rejected options matter most, because they are what distinguishes someone who exercised judgement from someone who executed instructions.
- 01The situation and the constraint
Two or three sentences. What was broken, and what made it hard: budget, timeline, legacy system, team size.
- 02Your specific role
«The team migrated the platform» tells a reader nothing about you. Say what you owned.
- 03The decision and the alternatives
What you chose, what you rejected and the reason. This is the part that demonstrates thinking.
- 04The outcome, measured
A number, a timeframe, a before and after. If the outcome was mixed, say so: it reads as more credible, not less.
Include one case that did not go well, with what you would do differently. It is disproportionately persuasive, because almost nobody does it and everybody knows projects fail.
In shortProblem, constraint, your decision, what you rejected, measured outcome. In that order.
Showing work you are not allowed to share
Most professional work is confidential, and that is not an obstacle. You can describe the shape of a problem, your reasoning and the scale of the outcome without naming the client, showing the interface or disclosing figures that identify anyone.
- Anonymise the client and describe them by sector and size: «a logistics company of around 200 people».
- Use relative figures instead of absolute ones: «reduced processing time by 40%» rather than revenue numbers.
- Recreate the artefact rather than publishing the original: a redrawn diagram, a sanitised template.
- If in doubt, ask. Many former employers agree to a described case study when the alternative is nothing.
What you must not do is publish material you signed away, or reconstruct it closely enough that the client is identifiable. A portfolio that breaches confidentiality tells a hiring manager exactly how you will treat their information.
In shortDescribe the reasoning, not the artefact. Confidentiality is a constraint, not a blocker.
Where to put it and how much
Three cases, on a page you control, linked from the top of your CV. More than five reduces the chance any of them is read carefully. The venue matters less than permanence: it must still exist in two years and not depend on a platform's algorithm.
- A simple page on your own domain: permanent, controllable, loads fast.
- Three to five cases, each readable in two minutes.
- A one-line summary at the top of each so a skimmer gets the point.
- Plain text and diagrams over screenshots that need explaining.
- A gallery of twenty links with no context.
- A slide deck that must be downloaded to be read.
- Content only on a social platform, subject to its reach and its rules.
- A site so designed that the loading time exceeds the recruiter's patience.
In shortThree cases, two minutes each, on something you own. Volume works against you here.
If your work is not visual
Most work is not, and portfolios are not only for designers. An operations manager, an accountant or a project lead can all show reasoning: a process redesigned, a decision framework, a template that others adopted, a written analysis of a problem in their field.
- Write up a decision you made and the reasoning behind it, as if explaining it to a peer.
- Publish a template or checklist you built, with the thinking behind each item.
- Analyse a public problem in your domain and show how you would approach it.
- Record a five-minute walkthrough of how you would tackle a typical brief.
Nobody is evaluating your visuals. They are evaluating whether you would make good decisions without supervision.
In shortJudgement is the thing being assessed, and judgement can be written down in any field.
Frequently asked questions
Do I need a portfolio if I am not a designer?
Yes, though not a visual one. Any role can demonstrate judgement: a process you redesigned, a decision framework, a written analysis. What is being assessed is how you think, not what you can draw.
How many cases should a portfolio have?
Three to five. Beyond that the chance of any single one being read carefully drops sharply. Depth in a few beats breadth across many.
How do I show work covered by confidentiality?
Describe the problem shape, your reasoning and relative outcomes without naming the client or publishing protected material. Sector and company size are usually enough context.
Where should a portfolio live?
On a page you control, ideally your own domain. What matters is that it still exists in two years and does not depend on a platform's reach or policies.
What makes a case study credible?
The rejected alternatives. Stating what you considered and why you ruled it out is what separates someone exercising judgement from someone following instructions.
Should I include projects that failed?
One, yes, with what you would do differently. It is disproportionately persuasive because almost nobody does it and every experienced person knows projects fail.
Is a personal website necessary?
A simple page is enough. An elaborate site with slow loading and no cases performs worse than plain text with three well-explained examples.
Can I use side projects instead of professional work?
Yes, especially early in a career. What matters is that the reasoning is real and the constraints are described honestly, not whether someone paid for it.
Should the portfolio be in English?
If you are applying internationally, yes. Keep a version in your own language if you also apply locally, but the international one should be in the market's language.
How do I link it from my CV?
Near the top, in the header, as a plain URL that is readable when the CV is printed. Buried at the bottom it will not be clicked.