Portfolio, GitHub and Website Links on a Resume

Which links are worth the line

Almost everybody should have one. Very few people need three. Each extra link splits the reader's attention and increases the chance that the weakest one is the one they open.

What does not belong: personal social accounts, a link to a general job board profile, and anything requiring the reader to request access. A link that produces a permission-request screen is worse than no link, because the reader now knows you did not check.

Formatting so it survives everything

A resume gets read as a PDF on a laptop, as parsed text in a tracking system, and occasionally on paper. The link has to work in all three, and the way to achieve that is unglamorous.

1. Write the URL out. "github.com/yourname" is readable on paper, in a parsed text field and on screen. Hyperlinked words such as "Portfolio" are invisible the moment the document becomes plain text.
2. Drop the protocol and the www. Cleaner, shorter, and still recognisable as a link to every reader and every parser.
3. Strip tracking parameters. LinkedIn URLs in particular arrive with a long tail of parameters. Set a vanity URL and use that.
4. Never use a shortener. The reader cannot see where they are going, corporate mail filters distrust them, and the redirect will outlive your interest in maintaining it.
5. Also make it clickable. A hyperlink under the visible text costs nothing and helps the majority of readers who are on a screen.
6. Keep it in the body of the document, not in a header or footer field, which some parsers ignore entirely.

You can check what a parser actually extracts from your file — including whether your links survived — by running it through the ATS checker before you send it anywhere.

What a recruiter will actually find

The uncomfortable part of this section is that the link is judged in about twenty seconds and the judgement is unfiltered. It is worth being specific about what that twenty seconds involves for each destination.

A GitHub profile

They see your pinned repositories, the date of your last activity and whether the top repository has a README. Most will read one README and nothing else. If your best work is a private company repo, pin something public you can actually stand behind and describe it properly.

A portfolio site

They see whichever three pieces are at the top, and they judge the whole body of work on those. Order matters more than quantity, and the strongest piece goes first even if it is old.

A personal site

They notice when it was last updated and whether it says what you do. A landing page with a name and no explanation converts a link into a shrug.

A LinkedIn profile

They check whether the dates and titles match your resume. Discrepancies here are noticed more often than people expect and are the main reason to update both at once.

Making the destination worth the click

Three or four strong pieces beat twenty mediocre ones, and this is the single most common thing people get wrong. A portfolio is judged on its average, not its maximum, because the reader is sampling. Removing your weakest four projects raises the average immediately and costs you nothing.

For each piece, the reader wants the same four things they want from a resume bullet: what the problem was, what you did, what you decided and what happened. A gallery of finished images with no context looks good and argues nothing. Two paragraphs under each piece turns a portfolio into evidence of how you think, which is the thing that actually separates candidates at interview stage.

For repositories specifically

• Pin three repositories and make sure the first one is your best. The default ordering by recent activity will otherwise put a throwaway experiment at the top.
• Write a real README on each: what it does, why it exists, how to run it, and what you would change. This is often the only file anybody opens.
• Commit history is visible and a single "initial commit" containing a whole project tells a reader something about how you work. It is not disqualifying, and it is noticed.
• Archive or hide the abandoned experiments. A profile of thirty half-finished forks reads as noise; five deliberate projects read as a portfolio.
• Do not link a repository containing credentials, keys or client data. This gets checked in security-adjacent hiring and it is a fast rejection.

For a sense of how heavily the link is weighted by field, compare the software engineer example, where a repository is close to expected, with the UX designer example, where the portfolio outranks the resume, and the accountant example, where no link beyond LinkedIn is needed at all.

A short pre-send check

• Every link opens in a private browser window, with no login and no access request.
• The URLs are readable as text and free of tracking parameters.
• The destination has been updated more recently than your last application.
• The first thing visible at each destination is your strongest work.
• Nothing published is confidential, client-owned or under an NDA.
• LinkedIn dates and job titles match the resume exactly.
• Nothing on any linked profile contradicts what the resume says.

Then leave it alone. A link that is current, clean and points at three good things is finished, and the time you would spend polishing it further is better spent on the experience section, which is where the decision is actually made. If you want a second opinion on how the whole page reads together, the resume review covers the links along with everything else.