When a portfolio does more for you than a résumé

A résumé is a record and a portfolio is an argument. Which one helps you depends on whether the reader needs to check a fact or form an opinion.

ConxfolioPublished 2026-09-12

— one is filed. The other is looked at.

The two documents are often discussed as alternatives, which is the wrong frame. They answer different questions from different readers at different moments, and an application that has both is answering both.

What a résumé is good at

Being filed. A résumé is a record in a fixed shape: dates, employers, titles, education, skills. A recruiter can scan it in ten seconds, check a fact, forward it, and store it in a system that expects a document of that kind. It is dull by design and the design is correct.

It is also the document that has to survive a text extractor, which is a constraint a web page does not have. The format page covers what that costs and how to check it.

What a portfolio is good at

Making an argument. A page has room for a sentence about what changed, for a case study, for an image, for the reasoning behind a decision. It is ordered by importance rather than by time, which means the first thing a reader meets is the thing you chose rather than the thing that happened most recently.

It is also the only one of the two that a person visits voluntarily. Nobody browses a résumé.

The four situations where the page wins

• The work is visual or built. A description of a thing is weaker than the thing, and always will be.
• Your titles undersell you. Where the job title at your employer means less than what you actually did, a page is where the difference gets explained.
• You are changing field. A record ordered by time makes a change look like a break. A page ordered by argument makes it look like a decision.
• Somebody asked what you do. An address is a better answer to that question than an attachment, and people do ask it in ordinary conversation.

Where the résumé still wins

Any formal process. Application portals require a file. Agencies forward documents. Internal panels compare like with like. And a great many readers simply prefer the record, because they are checking rather than exploring. A page cannot be filed and is not meant to be.

The reasonable arrangement is therefore always the same: the record goes in the application, and its header carries the address of the page.

They should be made of the same material

The commonest failure is two documents that disagree, usually because they were written months apart. A title differs, a date differs, an employer is named two ways. A reader who notices stops trusting both.

The portfolio builder avoids this by construction: the details sheet arrives filled from the résumé already in this browser, and it states that nothing in it is invented. You correct entries and switch off what does not belong, which keeps the page a view of the record rather than a second version of it.

The naming question underneath

People sometimes mean a CV when they say résumé, and the two words land differently in different countries. That is a separate question with a real answer, and the résumé and CV page has it. It matters here only because the document you attach should be the one the posting asked for by name.

What a page cannot do

It cannot make thin work look substantial, and a reader can tell the difference between four pieces with outcomes and nine without. It does not affect any employer's screening software. And nothing here predicts an outcome; what a page does is give somebody a reason to have a conversation, which is a smaller claim than most sites make and a true one.

If you have the record and not the page, the three-step walkthrough covers the distance between them, which is shorter than it looks.

What to do when a posting asks for neither

Some approaches happen in a message rather than a process: a founder asking what you do, a conversation at an event, an introduction from somebody you both know. In those, attaching a document is heavier than the exchange warrants and an address is exactly the right weight.

That is the case where the page is doing work the résumé cannot do at all, and it is more common than the formal processes people design their documents around. Having the link ready costs one evening once, and the situations where you want it tend to arrive without notice.

It is also the version that survives a conversation. An address somebody can type from memory is an address they can revisit a week later, which an attachment buried in a message thread is not.

Keep them in step

Whichever you update, update the other within the week. Two documents drifting apart is the failure mode of having both, and it is avoided by treating the résumé as the record and the page as a view of it rather than as two separate writing projects.