The one rule for every field
Whatever your discipline, the rule is the same: a few deep, well-explained pieces beat a pile of shallow ones. Three strong projects with the thinking shown — what problem, what you did, what changed — outperform ten thumbnail entries every time. Recruiters skim; they are looking for evidence you can do the work AND explain your decisions. Depth, context and outcome are what convert a portfolio from a gallery into an offer.
What a portfolio proves, by field
The case-study format (works for every field)
1 · The problem / brief
What were you actually solving, and why did it matter? Set the context in a sentence or two — a project with no stated problem reads as an exercise, not work.
2 · Your specific role and constraints
What did YOU do (vs the team), on what timeline, with what limits? Interviewers probe individual contribution — claim only what you can defend, and name the constraints you worked within.
3 · The approach and key decisions
The choices you made and why — the tradeoffs, the things you tried that failed. This is the substance recruiters read for; it shows judgment, not just output.
4 · The outcome — what changed
The part students skip: what measurably resulted? Accuracy, performance, users, engagement, a shipped product. "It works" is not an outcome; "it handles 4,000 requests/second" or "cut the task from 2 hours to 5 minutes" is.
5 · Honest limitations
A short, straight-faced "what it does not do / what I would improve" is the strongest credibility signal in a student portfolio. It says you understand your own work.