Link the two or three pieces of work that best prove you can do the job you are applying for, and remove everything else. For engineers that usually means one strong GitHub repository or a live project, not a profile full of forks and tutorials. For designers, a focused case study site, not a Dribbble feed of unrelated shots. When applications go out in volume, every recruiter who clicks your link should land on something relevant within ten seconds.
Why fewer links work better
Recruiters screening applications spend very little time on each one. If your resume lists a GitHub, a personal site, a Behance, a Medium blog, a Kaggle profile, and a LeetCode link, they will click one at most, and probably the first. If that first link shows a half-finished to-do app from 2021, that becomes their impression of your work.
A portfolio is evidence. One clear piece of evidence beats six scattered ones.
What to link, by role
Software engineers
- A GitHub profile with two to four pinned repositories that relate to your target role. A backend engineer might pin an API service with tests and a README that explains the design.
- A live deployed project, if you have one, with a link in the README.
- Open source contributions, linked as specific merged pull requests rather than the project home page.
Data analysts and data scientists
- One or two projects with a clear question, the data used, and the conclusion. A public Power BI or Tableau dashboard works well.
- A notebook that reads like a short report, not raw cells with no explanation.
- Kaggle only if you have meaningful competition results or well-documented notebooks.
Designers
- A portfolio site with three case studies: problem, your role, process, outcome. More detail on this is in portfolio and ATS tips for designers.
- A Figma prototype link for one project if it adds something the case study cannot show.
Product managers
- A short write-up of one product decision you drove, with the context and result. A one-page Notion or Google Doc is fine.
- A public product teardown, if you have no shipped product yet.
Writers, marketers, and content roles
- Three to five published pieces in the format the job needs. Blog posts for content roles, campaign results for performance marketing.
What to remove
- Tutorial clones. Netflix clones, weather apps, calculator apps. They show you followed a course, not that you solved a problem. Keep one only if you added something real.
- Unfinished projects with no README, broken builds, or "coming soon" pages.
- Unrelated work. If you are applying for backend roles, your college Arduino project does not need to be pinned.
- Dead links. Expired Heroku apps, old free-tier hosting, domains you stopped paying for. A broken link is worse than no link.
- Confidential work. Screenshots or code from your employer that you do not have permission to share. This can raise real concerns with a careful recruiter.
- Profile counters and badges as the main content. LeetCode counts or streak graphs are fine as a secondary link for SDE roles, but they are not a portfolio.
Make each link pass the ten-second test
Open your link in a private window on your phone and ask: within ten seconds, can a stranger tell what this is and why it matters?
- GitHub READMEs should start with one line on what the project does, a screenshot or demo link, and the stack.
- Case studies should open with the outcome, not three paragraphs of background.
- Personal sites should load quickly and look fine on mobile. Many recruiters screen on their phones.
Where to put the links
On your resume: one line near your contact details with at most two links. Use short, readable URLs, for example github.com/yourname and yourname.dev. Make sure they are clickable in the PDF.
On LinkedIn: use the Featured section for your best project and add the portfolio URL to your contact info. The Featured section shows up when a recruiter opens your profile from an application.
In application forms: many Easy Apply forms include a "website" or "portfolio" field. Save the right link once in your profile and screening answers so it is filled consistently. If you are using LinkedIn auto apply, check that the saved portfolio link points to the version that fits the roles you are targeting.
One portfolio, several roles
If you apply to two role types, such as frontend and full stack, you do not need two websites. Pin projects that serve both, or create two short landing pages on the same site and use the matching link on each resume version. Do not send a full stack recruiter to a page that only shows CSS animations.
Getting found as well as clicked
A portfolio can also bring inbound interest if it shows up when people search your name. Using your real name in the site title, adding a short bio, and linking it from LinkedIn and GitHub all help. The guide on getting your portfolio website found on Google goes through the basics.
A quick audit checklist
- List every link currently on your resume and LinkedIn.
- Click each one. Delete any that are broken, outdated, or irrelevant to your target role.
- For the two or three that remain, update the README or intro so the first lines explain the project.
- Check each on mobile.
- Update your saved portfolio answer in your job tools so every application uses the cleaned-up link.
Next step
Spend 30 minutes today on the audit above. Unpin or archive at least one repository or project that does not support the role you want, and rewrite the opening of your best project so a recruiter understands it in ten seconds.
