Digging Through the Digital Attic: How Forgotten Accounts Become Proof of Work
Somewhere between your second job and your current one, you stopped updating things. The GitHub account with three half-documented repositories. The Dribbble profile from the year you briefly considered a design pivot. The Medium draft titled "Thoughts on Product Ops" that hasn't been touched since 2019. None of it is embarrassing. All of it is invisible. And together, it represents the portfolio you didn't know you had.
For American professionals navigating a job market where hiring managers routinely check five or six platforms before a first interview, dormant accounts are either an untapped asset or a quiet liability. The difference comes down to whether anyone — including you — has looked at them lately.
Start With an Inventory, Not a Redesign
The instinct is to immediately polish. Resist it. Before you touch a single profile, you need a complete picture of what exists. Open a spreadsheet and work through the usual suspects: code repositories, design communities, writing platforms, presentation decks uploaded to SlideShare years ago, conference talks that live only on a defunct event site, that portfolio you built on a platform that has since pivoted three times.
Search your own email archives for the phrase "welcome to" or "confirm your account." Registration emails are the most reliable archaeological record of your online life. Most people find five to ten accounts they genuinely forgot about, and at least one that makes them wince.
For each item, note three things: the platform, the last activity date, and whether the content still reflects the work you want to be hired for. That third column is where the strategy lives.
Decide What Earns Its Keep
A dormant profile falls into one of three buckets. It either supports the professional identity you're building, contradicts it, or sits neutrally outside it.
Supporting content gets activated. That ten-year-old GitHub repo where you built a data pipeline for a nonprofit? If you're positioning as an engineer, it deserves a current README, a screenshot, and a line in your bio. Old work doesn't need to look new — it needs to be legible. Explain what the project was, what you did, and what the outcome was, the same way you'd frame it in an interview.
Contradicting content gets retired or privatized. The half-finished blog under a persona you abandoned, the niche community account tied to a former career direction — these don't need to be deleted, but they shouldn't be the first thing a recruiter finds. Most platforms offer archiving or privacy settings that let you keep the history without broadcasting it.
Neutral content is a judgment call. A personal photography account probably doesn't hurt an accountant. It might hurt a candidate for a role that demands an intensely curated brand. There's no universal rule — only the identity you've decided you want people to find.
Consolidate Before You Amplify
Here's where most professionals go wrong: they share the resurrected portfolio everywhere at once, then burn out maintaining six platforms. The better sequence is consolidation first.
Pick one hub — a personal site, a LinkedIn Featured section, a single well-maintained portfolio page — and route everything through it. Your GitHub gets linked from the hub, not the other way around. The old Behance account gets a current bio that points back to the same place. The goal is that no matter which dormant corner a stranger stumbles into, the exit path leads to the identity you've built.
This is also where stale links get fixed. A 2018 portfolio that 404s is worse than no portfolio, because it signals abandonment. Redirects, updated URLs, and current contact information are unglamorous work that pays disproportionate dividends.
Put the Maintenance on a Schedule
An attic only stays clean if you visit it. Once your accounts are activated and consolidated, add a recurring calendar reminder — quarterly is plenty — to spend ninety minutes reviewing what's live, what's outdated, and what new work deserves to be added.
The professionals who benefit most from this exercise aren't career-changers or designers with obvious visual work. They're the quiet specialists — the analyst, the operations manager, the staff engineer — whose best work is scattered across tools that were never designed as portfolios. A documented side project, a well-written postmortem, a talk from a local meetup: these are proof of work, and proof of work compounds.
You already did the hard part. The projects exist. The work was real. All that's left is deciding that the record of it should be as intentional as the work itself.