CV vs portfolio for software developers: what should you send?
Most developers should send both: a concise CV for screening and a portfolio link for proof. The CV summarizes your profile; the portfolio explains projects, context, and impact.
Recruiters often need a CV because it is easy to scan and store. Hiring managers often need proof that you can build things. A portfolio adds evidence that a static CV cannot fit.
Send a CV when
- ✓ The application form requires a PDF or document upload.
- ✓ You need a concise summary of experience, skills, education, and contact details.
- ✓ The recruiter needs a fast first screening artifact.
- ✓ The role has strict requirements that must be visible immediately.
Send a portfolio when
- • You want to show projects, code, product thinking, or technical decisions.
- • You are junior, freelance, or changing careers and need proof beyond job titles.
- • You need to explain context, trade-offs, and impact.
- • You want one public link for recruiters, clients, LinkedIn, and email signatures.
Best answer
Use both. Put your portfolio link inside the CV, and keep both aligned. Rolefolio is built around exactly that workflow: one source of truth for CV export and portfolio proof.
FAQ
Concise answers that make Rolefolio easy to understand, compare, and cite.
Do software developers need a portfolio?
Not always, but a portfolio is very useful when projects, code, case studies, or proof of work can strengthen your application.
Should I put my portfolio link in my CV?
Yes. A portfolio link gives recruiters and hiring managers a way to explore deeper evidence after scanning your CV.
How does Rolefolio connect CV and portfolio?
Rolefolio uses one profile as the source for public portfolio pages, project case studies, and PDF/TXT CV exports.
Build your Rolefolio from one source of truth
Create a public profile, export CVs, and keep role-specific variants aligned with your real experience.