Portfolio vs CV for Devs and Designers: What Wins

Short answer: the recruiter looks at your CV first. Almost always. Even if you have a portfolio that would make Dribbble envious and GitHub feel inadequate. The CV opens first because it lives in the ATS, in the email attachment, in the database. The portfolio requires a separate click. A recruiter going through 80 candidates a day doesn't always make it to the second tab. So the real question isn't "portfolio or CV" - it's "how do you make someone actually want to open your portfolio after reading the CV".

Why this confusion exists at all

There's a popular belief in the IT community: "developers don't need a CV if they have GitHub", or "designers don't need a CV if they have Behance". That belief is comforting but wrong. It was born in an era when startups hired people purely on community reputation. Today, even small product teams have HR and an ATS. And those require something structured.

The confusion also comes from the fact that each document plays a different role depending on the role. A frontend developer and a UX designer live in different realities: for a designer, the portfolio answers 60-70% of questions about work quality, while for a developer, GitHub mainly just proves they write code at all. Let's start with who shows what.

Developers: when GitHub actually helps and when it doesn't

GitHub isn't a portfolio in the classic sense. It's more like a draft folder. A recruiter without a technical background won't go there because they don't know what to look at. A technical interviewer or CTO will go there, but only after the CV has already passed the first filter. Genuinely useful GitHub looks like this: a few repositories with READMEs that explain the problem and the solution, or a meaningful contribution to an open-source project where real pull requests are visible. The green activity calendar barely matters, because everyone knows it can be gamed.

• Helps: 2-3 projects with a problem description and technical decisions explained in the README
• Helps: real open-source contributions with visible discussion in PRs
• Doesn't help: 40 forks of other people's repositories without a single line of your own code
• Doesn't help: tutorial projects like "todo app" or "landing page"
• Doesn't help: private repositories the recruiter has no access to

For backend developers the situation is even more interesting. Their work often lives inside closed systems: microservices, business logic, payment integrations. Showing that publicly is impossible. So the CV carries more weight for a backend developer than for a frontend or full-stack developer with public projects. And that weight has to come in numbers: "reduced API response time from 800ms to 120ms", not "developed RESTful APIs".

Designers: portfolio matters more, but CV still opens first

For UX and product designers, the portfolio decides far more than it does for developers. The recruiter or hiring manager wants to see real case studies: what problem was being solved, what solutions were considered, why this one was chosen. Pretty Figma screenshots alone prove nothing. Design without context reads as a collection of pictures.

But even in this case, the CV opens first. Why? Because the portfolio link has to be found somewhere in the CV. If the CV looks weak or confusing, the recruiter may never even get to the link. So a good designer doesn't just drop a Behance or Notion-case link at the bottom of the document. They make the CV feel like a teaser already: specific metrics, project names, a short context about the company.

One story, two formats

This is where most candidates drop the ball: the CV and portfolio tell different stories. The CV says "built an analytics dashboard for a fintech startup" but the portfolio contains a case study about some e-commerce project that's not even mentioned in the CV. Or the CV lists one company name but the portfolio shows completely different branding. The recruiter genuinely isn't sure they're looking at the same person.

The rule is simple: every project in the portfolio should tie to a specific line in the CV. And vice versa: every significant achievement in the CV should either appear in the portfolio or have a clear reason why it doesn't (NDA, closed product, etc.). It's not a perfect scenario, but it's honest communication. Recruiters get that.

• Company and project names should match or have an obvious connection
• Dates in the CV and portfolio case studies should not contradict each other
• Success metrics in the CV and in the case study should show the same numbers
• If the portfolio contains projects absent from the CV, explain it in the About section

What a recruiter actually looks at and in what order

Here's the real sequence. First, the CV lands in the ATS and goes through automatic screening for keywords and formatting. This part never reaches a human. Then the recruiter opens the CV and spends an average of 6-10 seconds on the first scan: header, most recent position, tech stack. If something catches their eye, they read deeper. If not, they close it. Only if the CV passes that filter do they go look at the portfolio or GitHub.

A hiring manager or tech lead looks at things differently. They might open the portfolio or GitHub straight away because they're more interested in seeing decisions than reading a list of technologies. But they'll still come back to the CV to understand context: where did this person work, for how long, what team scale. So the CV and portfolio are read by different people at different stages of the funnel.

How to check whether your CV and portfolio tell the same story

There's a simple test. Give your CV and portfolio to someone who doesn't know you. Have them read the CV, then open the portfolio. Ask: "is this the same person described in the CV?" If they hesitate or say "well, kind of", there's a problem. The CV and portfolio should reinforce each other, not exist in parallel universes.

It's also worth checking how your CV looks after ATS processing. Formatting can break apart, columns merge, and portfolio links can become unreadable. Trackr's AI CV Analyzer shows how an ATS actually reads your document and whether it even sees the portfolio link. Better to know this before the document reaches a recruiter, not after.

1. 1Check that all portfolio projects are mentioned (even briefly) in the CV
2. 2Compare metrics across both documents. The numbers should match
3. 3Check that the portfolio link is in the CV header and is clickable
4. 4Download the CV as PDF and make sure the link didn't convert to plain text
5. 5Give the CV to a third person for a 10-second scan: what do they remember after closing it?

When the portfolio genuinely outweighs the CV

There are a few scenarios where the portfolio genuinely matters more. First, if you're a junior or mid-level developer without many commercial projects. A CV with two job entries doesn't give enough signal. A well-crafted portfolio case study can do more than one more freelance project line. Second, if you're changing stacks or directions. For example, moving from web design into UX. The CV will show your old experience, but the portfolio can demonstrate that you already think in a new way.

Third scenario: you're applying to a company where the hiring manager is also a practicing specialist who writes code or designs interfaces themselves. Those people often skip the "pretty" CV and go straight to looking at the work. If your stack or approach resonates with what they do themselves, the interview decision can come very fast. Trackr's AI Coach helps you prepare for the conversation once you've already passed that first filter.

• Junior and mid-level without extensive commercial experience: portfolio compensates for a short CV
• Changing direction or stack: portfolio proves the new identity better than rewriting the CV
• Roles with a creative component (design, content, video): there, a CV without a portfolio isn't taken seriously at all

And honestly: if you have a strong CV with specific numbers and a solid GitHub or portfolio that tells the same story, the question of "which matters more" just disappears. It only comes up when one document is significantly weaker than the other. That's when candidates start compensating for one's weakness with the other's strength. Better to just make both decent.