By bzc ∙ Published Sat Jan 10 2026 ∙ 1 min read
Last year I wrote a blog on what not to include and mentioned that you should avoid dead links or GitHub profiles.
I realized I may not have been as clear as I could have and wanted to have a dedicated blog expanding on this topic.
When I first started my career as a software engineer I had all the links,
I thought it set me apart. I thought it made me look great.
Now after many years of experience and being a hiring manager it's something I don't care for. If I saw it on your resume I'd click. At best I'd move on, but often be disappointed.
The core problem with portfolio style links is unless you're applying for a creative role they rarely tell me anything about yourself.
If you have a fancy website, I know you can make something pretty but I don't think I'm hiring a designer. If you can show me past work, clients, projects - Is this representative of the work you output on a day to day?
What I'm trying to say is, people might have acquired a wealth of skills in their personal projects but tangible impact is difficult to quantify in pet projects. What's more helpful is distilling the key impactful contributions in the resume itself as "Projects" or "Notable Works".
Treat resumes as the modern day business card. Make them short, concise, tell me in a flash why I should care. And why I shouldn't toss it in the bin.
Contributions, skills, impact is all that matters.
Anything that needs a hiring manager to do additional research or make their own interpretation is a chance to be passed on a better presented candidate.
More related to Kipnu than your resume, in general we do our best efforts to keep you anonymous unless you choose to share your contact information. If you link profiles from external sites, that tends to defeat the purpose of our efforts.