The Portfolio Is the Interview
I used to think a portfolio's job was to get you an interview. You put your work in, it looks good enough, someone emails you, the interview happens, you get the job.
The interview is the portfolio. By the time someone schedules a call with you, they have already decided.
What actually happens
A hiring manager at a company worth working for looks at dozens of portfolios a week. They are not reading — they are scanning. They spend under thirty seconds making a first decision: keep or close tab.
If they keep reading, they're looking for confirmation of the initial impression. They might spend another two minutes. If they're genuinely interested, they'll look at a project in detail and maybe the about page.
By the time they send you an email, they have a fairly complete picture of whether they want to hire you. The call is to confirm the picture, handle logistics, talk about the team. It is not where the evaluation happens.
The evaluation happened on the portfolio.
What this means for what you build
If the portfolio is the interview, every decision on it is an interview answer.
The typography choice answers: does this person have taste? The performance of the site answers: does this person care about the experience? The copy answers: can this person communicate? The interactions answer: does this person sweat the details?
Nothing is decoration. Everything signals something.
A portfolio that loads slowly signals you don't think about performance. A portfolio with inconsistent spacing signals you don't notice inconsistency. A portfolio with boilerplate copy signals you didn't think about your own positioning.
These are not minor issues. They are the interview answers. You gave them whether you meant to or not.
The thing that most portfolios get wrong
Most portfolios are about the designer. Here are my projects. Here is my process. Here is my bio.
A portfolio that converts is about the reader. It answers the question the hiring manager is actually asking: will working with this person make my product better?
The answer to that question is demonstrated, not stated. You cannot write "I care about craft" and have it land the same way as showing something that makes the reader feel the craft. The work has to do it.
This is why the portfolio site itself is often more persuasive than what's in it. A custom cursor with macOS-accurate physics, a footer built with GSAP Flip, keyboard shortcuts that actually work — these tell a story about the kind of engineer who built them. They answer the question before it's asked.
What I keep coming back to
The test I use for anything on the portfolio: would a designer I respect pause on this? Would it make them want to look at the next thing, or would it make them slightly less interested?
Everything that passes that test stays. Everything that fails gets removed or rebuilt. There's no middle ground — average quality actively undermines the work around it.
The portfolio is the interview. Make it answer the questions you want to be asked.