Ollie Shuts Nov 6, Conductor Nov 20. Snapshot Their Team Pages First

If you want to hire engineers from a shut down startup like Ollie, no layoff list will hand them to you. The Khosla-backed AI assistant shuts down on November 6 with no named buyer, no WARN notice, and no published roster. All that's left is a team page, a GitHub org, and a founder's reply thread, and each of those has a deletion date.

CEO Bill Lennon announced the shutdown on X on Oct 30, about two months after Ollie announced a $7.5M seed. The clock started then.

Why no layoff list will show you Ollie's engineers

No layoff list will show them because WARN only applies at 100 employees under federal law and 75 under California's Cal-WARN, and courts usually require those 75 to be at a single site. A seed-stage team is nowhere near either number.

Lennon described Ollie as "a small team." Nobody has published an exact headcount. (One caution: the "76" on Ollie's Dealroom page has no label and is probably a platform score, not a headcount.) Layoff trackers don't list companies this small. A seed shutdown produces one founder post and then silence.

This isn't a one-off gap. The whole market for early-stage engineers is built so that WARN can't see it:

• In Refolk's index sample of US Founding Engineers, no employer shows up more than once. The top of the list reads Orbit, Navier AI, Erebor, Sazabi, Bounti.ai, and so on.
• That means the talent is spread across thousands of tiny companies, and none of them will ever cross a WARN threshold.
• So any process that waits for filings, layoff spreadsheets, or public announcements about the Ollie team will never see a seed-stage shutdown.

In startup shutdown talent sourcing, the founder's shutdown post is the starting gun. Everything after it is a race against the date the servers go off.

The deal type tells you how much of the team is actually free

When a startup shuts down with no buyer, the whole team is free. When it's bought outright, the buyer keeps most of the team. When it's a reverse acquihire, only the people the buyer didn't pick are free. This autumn produced all three.

A reverse acquihire is a deal where a big company hires some or all of a startup's team and licenses its technology without buying the company itself. An acquihire is a purchase made mainly to get the team, with the product usually wound down.

Each deal type changes who's worth calling.

• Ollie has no acquirer to hold anyone on retention. Every engineer is in play on Nov 6, and Lennon's own explanation ("With Muse, Instinct, and others entering the space, it became harder to stand out, grow, and raise the capital we needed") suggests the engineering wasn't what failed.
• Conductor joins Meta Superintelligence Labs. The changelog says local Conductor keeps getting new models and critical bug fixes until early 2027, so someone has to ship that work. Assume those engineers are tied up.
• Huxe handed over "certain employees." The filing doesn't say who got offers or whether they accepted. Your leads are the people who weren't picked, and the filing doesn't name them.

4,519 founding engineers, and two of them say they're looking

Refolk's index shows 4,519 people in the US whose current title is "Founding Engineer," against 701 in the UK. Only 2 of the US group have "open to work" in their headline.

A founding engineer is one of a startup's first technical hires, usually working across the whole stack before there's a real org chart. These are exactly the people a seed shutdown like Ollie's frees up.

0.04%

The reason is simple. Engineers at a startup that's winding down usually find their next job through investors and former colleagues before they touch their profile. Their headline often keeps showing the dead company for weeks. So a keyword filter for "open to work" or "seeking" returns almost nobody, and the people it does find aren't the ones from last week's shutdown. Search on history instead: the repos someone committed to and the companies on their timeline, not what their headline claims today.

The location split is the one that changes your search. In the UK sample, founding engineers cluster in London. In the US, only about a quarter of the sample sits in San Francisco. Ollie was a San Diego company. If you filter to SF, you'll lose most of the team you're trying to reach.

Snapshot schedule: what to archive before each deadline

Archive the team page, careers page, trust page, and GitHub org in the Internet Archive's Wayback Machine before the service ends. For Ollie, that means before Nov 6. For Conductor, it means before Cloud goes read-only on Nov 13.

Once a company is dead, its domain lapses, its org gets deleted or made private, and the team page turns into a 404. Here's the schedule:

1. Today, for Ollie: Save the homepage, about/team page, careers page, and trust page in the Wayback Machine. Ollie was one of the first mainstream apps to achieve SOC 2, so its trust page is worth saving before the domain lapses.
2. Today, for Ollie: List every public repo in the GitHub org and export the commit authors while the org is still public.
3. Before Nov 6: Save Lennon's shutdown thread and its replies. Screenshot the replies as well, because reply threads are where teammates show up.
4. Before Nov 13: Snapshot Conductor's changelog (the "Conductor is joining Meta" entry), docs, and any team or careers pages while Cloud is still fully live.
5. Before Nov 20: Conductor Cloud shuts down. Anything you haven't captured by then is gone.

Do the archiving first and the outreach second. You can send a message any week. You can't save a page after it's been deleted.

Rebuild the roster from what the company left behind

When the company is gone, its roster survives in four places: commit authors, the trust page, the founders' X replies, and archived team and careers pages. Each one catches people the others miss.

• Commit authors. Pull the author names and emails from the commit history of every public repo. These are the people who actually shipped, whether or not they appeared on the team page.
• Trust page. Ollie's SOC 2 work means someone owned security and compliance. The archived trust page is your first clue to who.
• Founders' X replies. Under @blennon_'s shutdown post, look for former teammates writing "proud of what we built" and investors tagging people. Khosla Ventures and AI House backed the seed, so their partners' replies matter too.
• Archived team and careers pages. Old team pages give you names. Old job ads show which roles the company filled, what stack it used, and roughly when each hire joined.

Cross-referencing all of this by hand is the slow part. One commit email leads to a personal GitHub, which leads to a LinkedIn that still says "Ollie," which leads to a portfolio site. Refolk closes exactly that gap: you describe the person in plain English and get a ranked shortlist across GitHub, LinkedIn, and the open web, with the cross-referencing already done.

Once you have names, sort them by what they owned. Someone who built the core assistant is a different hire from someone who ran the SOC 2 program, even though both may have "Founding Engineer" on their profile.

Work out who the acquirer probably didn't take

In an acquisition or reverse acquihire, your leads are the people outside the deal: those the buyer didn't need for the product it's keeping and those it didn't make offers to. Finding the acquihire leftover employees is a process of elimination.

Conductor. CEO Charlie Holtz and CTO Jackson de Campos are going to Meta Superintelligence Labs. The company raised a $22 million Series A in March from Spark Capital and Matrix. The engineers keeping local Conductor alive until early 2027 are probably covered by retention. Look at the edges instead: people whose work was tied to Cloud, which shuts Nov 20, and anyone who decides they don't want to move into a big-company lab.

Huxe. Apple took "certain employees" from the team founded by Raiza Martin, Jason Spielman, and Stephen Hughes (all ex-NotebookLM). Refolk has already mapped that group in the Huxe and NotebookLM alumni piece, so I won't repeat it here. The lesson to take from Huxe is about timing.

~4 months

Regulatory filings show up late. Once a DMA filing goes public, the people it covers have usually landed somewhere already. If you're tracking reverse acquihire team members through filings, you're reading history, not leads.

The next teams to run this play on are already public. OpenAI said it plans to acquire Pierre Computer, another developer tools startup, on the same day Meta announced Conductor, and Ona is another acquired team where the same approach applies. For each one, ask the same question: which product is the buyer keeping, and who doesn't work on it?

The hard part is that Meta, OpenAI, and the startups' own investors are all fishing in the same small pool, and they move faster than an outside recruiter rebuilding rosters one shutdown at a time. If you have a founding-engineer seat open right now, waiting for the next dead company and then guessing who its acquirer passed over is a slow and unreliable way to fill it.

How to approach engineers from a shut-down startup

Reach out during the shutdown window, mention specific work you saw, and don't ask whether they're "open to work." With only 0.04% of US founding engineers saying so in their headline, that question shows you didn't do the research.

What works:

• Lead with the artifact. Name the repo, the feature, or the SOC 2 effort. It proves you know who they are and weren't just scraping a list.
• Acknowledge the shutdown plainly. Lennon's own framing was that the team "learned a ton." Meet them there, not with sympathy.
• Don't filter by city. Ollie was in San Diego, and only 24% of the US founding-engineer sample sits in San Francisco.
• Offer a conversation, not a job description. Founding engineers pick teams and problems, and they want to know who else is in the room.
• Beat the investor network. Shutdown-stage engineers usually line up their next job through investors and former colleagues, and Ollie's are Khosla Ventures and AI House. Your message needs to arrive the week of Nov 6, not in December.

If you miss the window, profiles will catch up eventually. Headlines change, the dead company drops to "previous," and the engineer moves on. Re-running the same search a few weeks later shows you where each person ended up, which is often your next warm lead.

FAQ

Do startups that shut down have to file a WARN notice?

Usually not. The federal WARN Act applies at 100 employees, and California's Cal-WARN at 75, with courts typically requiring those employees to be at a single facility. A seed-stage company like Ollie, which called itself "a small team," falls well below both. That's why no layoff list or tracker will show its engineers.

How do I find employees of a defunct startup once the website is gone?

Start with the Wayback Machine for the team, careers, and trust pages, then pull commit authors from any public repos you exported before the org went dark. Add the replies under the founder's shutdown post on X. Cross-reference names across GitHub and LinkedIn, and expect many profiles to still list the dead company for weeks.

Who is left over after a reverse acquihire?

Everyone the acquirer didn't make an offer to, and anyone who turned one down. Filings like Apple's Huxe disclosure don't say who got offers, so work it out from the product: the buyer keeps the people it needs for the technology it licensed. Engineers working on parts being shut down are your strongest leads.

When should I contact engineers from a startup that just shut down?

In the week of the shutdown date, after you've archived everything. For Ollie, that's around Nov 6. For Conductor, it's before Cloud shuts down on Nov 20. Investors and former colleagues place these engineers quickly, and regulatory filings can lag by months (about four in Huxe's case), so the founder's announcement is your real deadline.