Proving Experience from a Startup That No Longer Exists

A senior engineer joined a startup as employee number four. He built the core platform across three years, watched the company close two funding rounds, and then watched it shut down when the third round didn't come together. Two years later he's applying for a new role. The hiring team asks for a reference. The startup's domain is parked. The founder is at three new companies and reachable in none of them. The engineer's LinkedIn says he worked there, but anyone who could confirm the work is scattered, and nothing about the startup exists in a place a recruiter can call.

The work he did was real. The proof of it is gone — unless he captured it before the door closed.

Here's how to assemble that proof, whether the startup folded yesterday or three years ago.

TL;DR

• Find the founders and your closest colleagues now. Contact info goes cold fast after a shutdown.
• Get a written reference from at least one founder or executive, while you can still reach them.
• Collect surviving public artifacts — Wayback Machine, press, your own commits, any public traces of the company's existence.
• Save the work you authored — code, decks, write-ups — within whatever post-shutdown IP policy applied.
• Make every piece verifiable: a signed reference, an attested project, an artifact tied to a date.

The situation

Your former employer no longer exists. The company shut down, got acquired and absorbed, or quietly faded out. The website is parked, the office is gone, the email aliases bounce. You worked there for one to five years and did real, substantive work. Now you're job-hunting and the standard verification path — "can you provide a reference from your manager at [Company]?" — has nowhere to land. The five moves below build the verification layer the company itself can no longer provide.

1. Track down the founders and your closest colleagues now

Action. Write down every name you can remember — founders, executives, your manager, your closest peers, key engineers or designers or salespeople you worked with daily. Find each one on LinkedIn. Send a short message asking for their personal email or to connect outside the platform. Do this in the next week, not the next year.

Why it works. After a shutdown, contact information goes cold quickly. People move once, twice, three times in the years after a company closes. The LinkedIn URL is stable; the email address attached to it is not. Founders specifically are the most valuable references because they can speak to the company's existence and your role in it — and they're often the hardest to track because they've started new companies, joined VC firms, or moved on entirely.

Done right. A list of 5–10 people from the company with current LinkedIn URLs, personal emails where possible, and a note about what they could attest to about your work. Founders, executives, your direct manager, and at least two peers who saw your day-to-day.

Common mistake. Waiting until you need the reference to look. By then the founder is at a stealth-mode company and isn't checking LinkedIn messages. The window is now, while the shutdown is recent enough that people are still actively reachable.

2. Get a written reference from at least one founder or executive

Action. Reach the highest-ranking person you worked closely with — a founder, the CTO, the head of your function. Ask for a written paragraph confirming the company existed, when you worked there, and what you did. Attach a draft they can edit.

Why it works. A reference from a founder carries asymmetric weight in the defunct-startup case. The founder can attest to the company's existence itself — something a former peer cannot do credibly — and their statement transfers to a future hiring team as legitimate verification of an entity that doesn't otherwise exist on paper. Without this, every reference call about your time at the startup runs into "and the company is...?" — a question only a founder can answer.

Done right. A short email like: "Hey [Founder], before [Startup Name]'s records fully scatter, would you write a short paragraph I can keep on file? Three or four sentences: [Startup Name] operated from [start] to [shutdown], I joined as [role] in [date] and left in [date], and during my time I led [specific project] and owned [specific area]. If you want to edit or expand, please do — but having something signed off by you would mean a lot for future job searches."

Common mistake. Asking only your direct manager. If your manager has also left and works at a different company now, their reference is one person's recollection. The founder's reference establishes the company, which is the harder thing to establish.

3. Collect surviving public artifacts of the company's existence

Action. Pull whatever public traces of the company still exist into a folder you control. Wayback Machine snapshots of the homepage. Press coverage from Crunchbase, TechCrunch, or industry publications. Funding-announcement archives. Any LinkedIn employee count screenshots. Patent filings or SEC documents if relevant.

Why it works. A future hiring manager checking your background may try to verify the company itself before verifying your role. "Does this company exist?" is the first question a background check runs into, and a Wayback Machine link plus two press articles answers it before the recruiter has to ask. The references you collected in steps 1 and 2 then verify your role within the (now-substantiated) company.

Done right. A document with: 2–3 Wayback Machine URLs of the company's homepage across different years, the funding-round announcements from Crunchbase or equivalent, 1–2 press mentions if any exist, and any official filings (Delaware incorporation records are public). Saved to personal cloud, not work account.

Common mistake. Assuming a Crunchbase profile is enough on its own. Crunchbase is helpful but it doesn't establish that you worked at the company. The public artifacts establish the company; the references establish you. Both are needed.

4. Save the work you authored, within whatever policy applied

Action. Identify the work you authored at the startup — code, decks, write-ups, design files, decision memos. Save copies of what you can legitimately keep under the company's IP policy (or what's recoverable from public sources like your own GitHub commits to public repos).

Why it works. A concrete artifact you can show is the strongest possible evidence for defunct-company work. "I led the migration to microservices" with a link to the architecture document you authored, with your name on it, is far more compelling than the same bullet with no artifact behind it.

Done right. Save PDFs or screenshots of: documents you authored where your name appears as the owner, public repository commits if your work was open-source, slides from presentations you delivered, public-facing blog posts or talks from your time there. Redact customer or proprietary information where the IP policy required.

Common mistake. Two equally bad ones. The first: assuming everything you wrote is yours to take. Most companies' IP policy survives the shutdown; saving proprietary internal documents may still be a breach. The second: throwing away artifacts that legitimately belong to you (your own GitHub commits to open-source projects, public blog posts, talks you gave externally). The line is what was made public, what you personally authored, and what the company's policy allowed you to retain.

5. Make every piece verifiable

Action. For each captured piece — the references, the public artifacts, the saved work — establish a clear attestation: who signed the reference, when the artifact was published, what the source of the claim is. Then store them in a record that lets a future hiring manager check each piece without needing you to make introductions.

Why it works. The defunct-startup case is the textbook scenario where verification matters most, because the company itself can't vouch for you. Each piece of evidence — the founder's written reference, the Wayback link to the company's homepage, the GitHub commit history, the press mention — is checkable by anyone with a browser. Aggregated, they substitute for the HR department that no longer exists.

Done right. A verifiable career record holds each piece as a signed, sourced entry: the founder's reference attached to the dates of your tenure, the public artifacts dated and linked, the work you authored tied to the project it came from. When a future hiring manager asks "can you verify your time at [Defunct Startup]?", the answer points at a record they can read in two minutes without needing to track down someone who's no longer reachable.

Common mistake. Treating the captured pieces as a folder on your laptop that you'll eventually organize. The captures only become verification when they're presentable — signed, dated, sourced, accessible to a third party. A folder of unlabeled PDFs is not yet evidence.

How verification rebuilds what the company no longer can

When a startup folds, the verification infrastructure of "call HR, confirm employment" disappears with it. The five moves above rebuild that infrastructure from the components that survived: people, public records, your own authored work, and signed attestations from the founders and colleagues who were there. Each one alone is partial. Together they substitute for the company itself.

A verifiable career record is where these components live as a unit. The founder's signed reference, the Wayback Machine link, the surviving artifacts — all attached to the same set of dates, all checkable independently, all collected before the people involved scattered too far to reach. The startup is gone. The work, and the proof of it, doesn't have to be.

---

Continue reading

• What to save from every job before you leave — the prevention version of this recipe, applied at the moment you leave
• What is a verifiable career record (and why your resume isn't one) — the thesis behind why this kind of capture matters
• Employment Verification: What It Is, How It Works, and Why It Matters for Your Next Job — what hiring teams actually check, and why defunct-employer cases are uniquely hard