How to list a bankrupt startup on your resume

Why does a bankruptcy like Character.AI's change how you write your resume?

Character.AI filed for Chapter 11 bankruptcy protection in Delaware on 12 October 2026, about five years after launch, and named Disney as lead bidder for certain intellectual property at $20 million — an offer other bidders can still beat. Court filings put both assets and liabilities in the $50–100 million range, and the sale is expected to wrap up by late November or early December 2026. For the people who worked there, the fallout lands in a very specific place: the employer line on their CV now points at a company that may have no website, no HR contact and no working email domain by the time a recruiter reads the application.

That's a documentation problem, not a credibility problem — but you have to solve it on the page, because nobody will solve it for you. A recruiter skimming 200 applications doesn't know whether your two years at a shuttered AI startup were brilliant or wasted. They know the name doesn't resolve to anything they can click. Ambiguity on a CV never resolves in your favour; it resolves into the next candidate. The fix is cheap and it's structural: give the reader enough context in one line that they stop wondering and start reading your results.

This isn't a niche problem anymore either. Between AI startups running out of runway, acqui-hires that leave the original entity hollowed out, and a steady drip of layoffs across the sector, a large share of mid-career technologists now carry at least one employer that no longer trades. Some of those companies were genuinely good places to work that simply lost a funding race. Your job is to make sure the CV says that plainly, in professional language, without sounding defensive — and then to spend the rest of the page proving what you actually built.

Should you still list a company that no longer exists?

Yes — always, and under its real name. Deleting a dead employer creates an unexplained gap, and an unexplained gap is read far more harshly than a bankruptcy ever will be. Hiring managers have seen plenty of startups fold; they've also seen plenty of candidates quietly hide eighteen months. One of those is normal and the other triggers a background check conversation you don't want. Keep the company name exactly as it appeared on your contract and your payslips, because that's the name a verification vendor will search, and a mismatch between your CV and your employment records is the sort of small discrepancy that stalls an offer.

Where it gets fiddly is the acquisition tail. If parts of the business were sold off, don't write the buyer's name in your employer field — you never worked for the buyer. Keep your employer line as the original entity, and if the sale matters for recognition, mention it in the context line instead: "assets acquired by [buyer] in 2026" is accurate and does the name-recognition work without overstating your position. Same logic applies if you were one of the people hired across in a transition deal: that's a separate, later role with its own dates, not a retroactive upgrade to the first one.

A word on dates, since this is where most people get careless. Use the month you actually stopped being paid, not the month the company formally dissolved or the month the news broke. If you were kept on through a wind-down to support customers, say so in the context line — "retained through wind-down" is a compliment to you, not a footnote. The same discipline that helps when you're explaining a step down in title applies here: precise dates, one clean entry, no editorialising in the employer field itself.

How do you write the one-line context tag for a dead employer?

Put it directly under the company name, in plain text, in under fifteen words: what the company did, its funding stage or headcount, and its outcome. Something like "Series B AI companion platform, ~60 staff; ceased operations 2026" tells a recruiter everything they need in one glance. The three ingredients matter in that order. Sector tells them whether your experience is relevant. Stage tells them what your job probably involved — a 20-person seed company and a 400-person Series D are different professions with the same job titles. Outcome stops them searching the name and finding a bankruptcy docket with no warning from you.

Here's the contrarian bit: I'd put that context line on every startup role, not just the ones that died. Nobody outside your niche knows what your old employer sold, and "Senior Engineer, Northwind" is a wasted line if the reader can't place Northwind. Three concrete versions worth stealing: "Seed-stage fintech, 12 staff; wound down 2025 after funding round fell through." "B2B analytics SaaS, $14M raised, 70 staff; assets acquired 2026." "Pre-launch AI tooling startup; team dissolved 2026, product never shipped publicly." Each is one line, each is verifiable, and each pre-empts the obvious question.

Now the things to leave out. Don't write "(defunct)" or "(no longer in business)" as a bare tag — it reads like a death notice and gives the reader nothing useful. Don't blame anyone: no "after investors pulled out," no "due to leadership decisions," no lawsuits, no regulatory drama, even when that's genuinely what happened. Don't move the explanation into your professional summary, where it becomes the first thing anyone learns about you. And skip the resilience language entirely — "thrived through uncertainty" is the kind of phrase that makes an experienced recruiter assume you have nothing concrete to report.

Which achievements survive when the company doesn't?

The results that survive are the ones tied to your own work rather than the company's fate: scale you handled, systems you owned, people you led, cycle times you cut, revenue you personally influenced. A company can go bankrupt and it remains true that you took deployment frequency from monthly to daily, cut inference costs 40%, or ran support for 300,000 monthly active users. Those numbers describe your competence. What dies with the company is anything that was really a claim about the business — valuation, total funding, growth curves, "fastest-growing" anything. If the reader's natural follow-up is "and yet it folded?", cut the bullet.

Pre-launch work is the hardest case, and it's worth handling deliberately rather than deleting. Work that never shipped still demonstrates judgement if you write the problem, the decision and the measured signal instead of the outcome: beta cohort sizes, retention in a pilot, load-test results, the architecture call you made and why. The same approach that works for writing up a product that got killed before launch works for a whole company that got killed before profitability — lead with what you decided, back it with pre-launch numbers you can defend, and don't apologise for the ending.

One practical safeguard: write every number so you could defend it in an interview without access to a dashboard you no longer have. Round honestly, use ranges where you're unsure, and attach the unit. "Reduced p95 latency from ~900ms to ~310ms across the chat API" survives scrutiny; "improved performance by 300%" invites a question you can't answer. Keep a private file of your own screenshots, performance reviews and launch notes while you still can — once the email domain lapses, your memory is the only record, and vague memory produces vague bullets that read as inflation.

How do you answer "what happened there?" and check the rewrite still parses?

Answer it in two sentences, offer it before you're asked, and don't flinch. Something like: "We ran out of runway during the Series C process and the board chose a sale; I stayed through the wind-down to migrate customers off the platform." Then stop talking and pivot to what you built. That's it. The recruiter's real question isn't "why did it fail" — it's "are you going to be weird about this for twenty minutes?" A calm, specific, blame-free sentence settles it instantly. Rambling, or hinting at internal politics you can't discuss, turns a non-issue into the memorable part of your interview.

Make the story consistent everywhere a hiring team will look. Your CV's context line, your LinkedIn headline and your cover letter should all describe the same ending in the same neutral language. If you're applying to a company in the same sector, a sentence in the cover letter naming what you learned about pricing, safety or unit economics is far stronger than anything you can fit on the CV — specific lessons from a failure are genuinely attractive to people who are still burning investor money on the same problems. Just keep it to two or three lines and keep the tone matter-of-fact.

Then check the mechanics, because a context line is exactly the kind of addition that breaks CV parsing. Bracketed text crammed beside a job title, italics inside the employer field, or a tag shoved into a header or text box can all end up detached from the role an ATS builds. Keep it as a normal paragraph line beneath the company name on its own row. If you're reworking the whole experience section anyway, it's faster to rebuild the CV in a clean, ATS-friendly template than to patch a five-year-old file, then run the finished PDF through a free CV analysis to see your score out of 100, your ATS-compatibility rating and a layout read of what actually got extracted.

Frequently asked questions