A lot of frontend candidates treat their resume and portfolio as the same pitch, repeated twice. They’re actually solving different problems.
What a resume is for
A recruiter or ATS scans it in seconds, mostly looking for keyword matches (React, TypeScript, years of experience) and basic pattern-matching against the job description. Its job is narrow: don’t get filtered out.
What a portfolio is for
Once you’re past the screen, whoever reviews your portfolio has more time and a different question: not “do you have the right keywords” but “can this person make good decisions.” This is where architecture choices, tradeoffs you explain, and real projects (not tutorial clones) actually matter.
The mistake
Cramming project explanations into your resume (bullet after bullet of “built X using Y”) wastes the resume’s narrow window on detail it can’t actually communicate well. And a portfolio that’s just a reworded resume wastes the deeper attention it’s been given.
The takeaway
Keep your resume sharp, keyword-matched, and skimmable. Save the why — your reasoning, your tradeoffs, what you’d do differently — for the portfolio, where someone is actually willing to read it.