Building a Portfolio Before You Have a Résumé

For most of the twentieth century, the résumé occupied a nearly sacred position in American hiring. A single-page document — job titles, dates, degrees, and a handful of bulleted accomplishments — decided who received an interview and who did not. In many industries, that logic still holds. Yet in fields shaped by the internet, from software engineering to journalism to design, a quieter document has begun to displace the résumé at the top of the review pile: the portfolio.

A portfolio is, at its simplest, a curated collection of work a candidate has actually completed. It differs from a résumé in a critical way. A résumé asserts; a portfolio demonstrates. When a hiring manager reviews a résumé, she must trust that the applicant did what she claims. When she reviews a portfolio, she can read, click, or run the artifact herself. The line between candidate and colleague thins immediately, because the manager is no longer evaluating a claim — she is evaluating work.

This shift has practical consequences for high school and college students. Waiting until a first job to accumulate portfolio-worthy artifacts is a strategic mistake, because the artifacts most useful for entry-level hiring are often the ones a student can create for free during school: a working web app, a data analysis of a public dataset, a short film, a redesigned poster for a local nonprofit, a well-documented open-source contribution. Each of these can be started before graduation and refined over years.

It would be an overstatement to declare the résumé obsolete. Many industries — medicine, law, most of the public sector — still hire primarily from credentials, and portfolios in those fields carry a different weight. But even there, the underlying principle is spreading: employers increasingly ask candidates to show what they can do, not merely list what they have done. Preparing that evidence early is now one of the highest-leverage habits a student can build.