# Polymarket's Nov 4 Contractor Cuts: Find the Engineers in Commit History

_Polymarket's Nov 4 contractor cuts came with no headcount, and few profiles name the client. How to find its CLOB and Solidity engineers via commit history._

- Canonical URL: https://www.refolk.ai/blog/polymarket-layoffs-contractors-find-engineers-github
- Published: 2026-11-15
- Reading time: 9 min
- Keywords: Polymarket layoffs, hire prediction market engineers, source smart contract engineers GitHub, Polymarket engineers commit history, Kalshi Polymarket engineers

If you want to hire the engineers Polymarket released on November 4, 2026, there is no list to start from. The company disclosed no headcount, the contractors got a private email, and few of them name the client on their profiles, so the usual post-layoff search comes back empty. If you want to hire prediction market engineers who have shipped a production order book, look at Polymarket's public commits. Profile headlines won't get you there.

## What did Polymarket actually cut on Nov 4?

Polymarket ended contractor agreements and let some people go across marketing, customer experience and engineering, effective November 4, 2026. It has disclosed no headcount and called the viral 30% figure inaccurate.

Here's what the reporting confirms:

- **The email.** Affected contractors were told: "As part of a company-wide reduction in force, we've made the decision to end your contractor agreement with Polymarket effective November 4, 2026."
- **The mix.** According to a person familiar with the matter, more than half of those affected were contractors.
- **The silence.** Polymarket declined to say how many employees or contractors it works with.
- **The statement.** The company said its reorganization "has meant a lot of new hires, changes in personnel and letting some people go."

A private email and no headcount leave nothing public to work from. That's the gap this article is about.

The leadership changes around the cuts matter too. CMO Matthew Modabber was fired in October. Travis VanderZanden now runs marketing as chief growth officer. Warren Jenson, formerly CFO at Amazon, became CFO in September under founder Shayne Coplan.

## Is Polymarket in trouble, or just professionalizing?

The numbers point to professionalizing. Annualized revenue topped $1.8 billion, up from a run rate of more than $1 billion in June (roughly 80% growth), and Polymarket is reportedly in early talks with prospective investors to raise about $1 billion.

That changes how you should read the engineers who were released. A company in distress cuts the people it can't afford. A company professionalizing cuts the arrangements that don't fit its new structure, and Polymarket's own statement puts "a lot of new hires" in the same sentence as "letting some people go." Cutting contractors while bringing in a former Amazon CFO and a new chief growth officer fits that pattern.

So assume the contract engineers who left are strong on CLOB and Solidity work rather than weak performers. Some of them likely worked on the trading infrastructure behind a company that went from a $1 billion run rate to $1.8 billion since June.

## Why does searching "Polymarket" surface marketers instead of engineers?

The people who put Polymarket in their headline are mostly in go-to-market roles. Contract engineers tend not to name their clients. In Refolk's index of professional profiles, 911 headlines mention Polymarket, and only 3 in a 25-profile sample hold engineering titles.

| Query (Refolk's index, Nov 2026) | Total matches | What a 25-profile sample shows |
|---|---|---|
| Headline mentions "Polymarket" | 911 | 20/25 (80%) currently at Polymarket |
| Polymarket sample, engineering titles | n/a | 3/25 (12%): Engineer, VP Product Engineering, Director of Engineering (Data Platform) |
| Headline mentions "Kalshi" | 14,179 | 8/25 (32%) actually at Kalshi; the rest are collisions like "Kashi" |
| US smart-contract/Solidity titles (4 variants) | 54 | 14/25 hold exact Smart Contract Engineer/Developer titles; neither Polymarket nor Kalshi appears |

The samples are small, so treat the percentages as directional. The pattern is still clear. The Polymarket sample is mostly product, growth, talent, social and affiliates, including a "Growth Lead, Tennis." For a growth person, a hot brand in the headline helps their career. Contract engineers often stay quiet about their clients, so a keyword search mostly hands you the marketing team, which is the opposite of what an engineering hirer wants.

The Kalshi row shows the second problem. A keyword search on a company name matches strings, not companies. 14,179 hits sounds like a deep pool until you find that about two-thirds of the sample work somewhere else. Without matching the name to the right company, most of your results are noise. Commit history doesn't have this problem, because the repo owner identifies the company.

> **54** US profiles with a smart-contract or Solidity title in Refolk's index
>
> The top employers are Ethereum, Polygon Labs, Consensys and Api3. Neither Polymarket nor Kalshi appears.

That last row is the real constraint for anyone trying to source smart contract engineers. If the US pool of people carrying the title is 54, and the top employers are protocol and infrastructure companies, a title search for a Solidity or matching-engine hire runs dry in days. After that, the req can stay open for months while you work through the same short list everyone else is messaging, or pay an agency to work through it for you.

## Where is the real trail? Polymarket's public GitHub

The trail runs through commit history on github.com/Polymarket, which has 104 repositories. The repo owner tells you the company, so there are no name collisions, and the commits show what each person actually built.

Two terms first. CLOB is Polymarket's central limit order book, and the CLOB clients are the client libraries for it. CTF is Polymarket's on-chain conditional-token exchange.

The repos worth reading:

- **clob-client-v2**, last updated Nov 10, 2026
- **ctf-exchange-v2**, last updated Oct 28, 2026
- **py-clob-client-v2**, last updated Oct 27, 2026
- **rs-clob-client-v2**
- **uma-ctf-adapter**
- **clob-client** (v1), archived May 25, 2026, whose package.json still lists named contributors with linked GitHub handles
- **rs-clob-client** (v1), archived May 11, 2026

Here is the workflow, in order:

1. **Pull contributors from the v2 repos.** Use the Contributors view or the GitHub API. Note commit counts and the last commit date for each person.
2. **Pull the v1 contributors.** Start with the package.json in clob-client, then the archived history. These people built the first generation and may have left long before November.
3. **Separate builders from integrators.** Not everyone who contributes to a public client library works for Polymarket. Some may be outside developers wiring it into their own systems. They're a separate pool worth tracking, but they weren't Polymarket contractors.
4. **Weight by depth.** Changes to order signing, matching logic or Solidity contracts count for more than README fixes.
5. **Resolve each handle to a person.** Check the GitHub bio, linked site, commit email domain and social handles.
6. **Cross-check against profiles that never mention Polymarket.** Look for "independent," "smart contract engineer," "trading systems" or a consultancy name with dates that line up with the commits.

Steps 5 and 6 are where a sourcer's afternoon goes, because you're joining a GitHub handle to a profile that deliberately leaves the client out. Refolk does that join for you: ask for the people who committed to these repos and you get back ranked people, with their GitHub, LinkedIn and open-web presence tied together.

> **Example search:** "Engineers who committed to Polymarket's ctf-exchange-v2 or clob-client-v2 repos in 2026 whose LinkedIn does not mention Polymarket" - [run it on Refolk](https://www.refolk.ai/start?q=Engineers%20who%20committed%20to%20Polymarket's%20ctf-exchange-v2%20or%20clob-client-v2%20repos%20in%202026%20whose%20LinkedIn%20does%20not%20mention%20Polymarket)
>
> A ranked list of contributors matched to their professional profiles, with commit depth and current stated role side by side.

## How should you read the v1-to-v2 timeline?

Treat it as a lead list, not a layoff list. Someone who committed to the v2 repos in October and has nothing public after November 4 is worth a private message. That still doesn't prove they were cut.

The v1 repos were archived in May 2026, and the v2 repos were active until somewhere between Oct 27 and Nov 10. That gives you a rough clock. But commits stop for plenty of reasons that have nothing to do with a contractor email:

- **Release cadence.** ctf-exchange-v2 was last updated Oct 28, so every contributor to it "stopped" on the same day.
- **Private work.** The public repos are only part of the codebase. An engineer can move to a private repo and vanish from public history.
- **Employees, not contractors.** Some contributors are on payroll and unaffected.
- **Finished scope.** A contractor brought in for the v2 migration may have wrapped up cleanly.
- **Ordinary life.** Vacations, parental leave, a side project.

The useful signal is the combination: deep commits to order or contract logic, a profile that names no client, and public activity that stops near Nov 4. One of those alone means very little.

The ethics follow from this. Contributor names in a public package.json are public. Whether any of those people were affected hasn't been verified by anyone. Never name an individual as laid off, in a message, a Slack channel or a client update.

## Kalshi vs Polymarket: which volume number belongs in your pitch?

Name the measure every time. Kalshi traded 2.8 times both Polymarket exchanges combined in October 2026 when you count dollars, about three times on DefiLlama's 30-day figure, and 6.6 times on DeFi Rate's notional numbers against Polymarket US alone.

| Source | Measure | Kalshi vs Polymarket |
|---|---|---|
| Totalis | Dollars traded, October 2026, vs both Polymarket exchanges | 2.8x ($16.9B for Kalshi) |
| DefiLlama | 30-day volume | About 3x |
| DeFi Rate | Notional, October, vs Polymarket US only | 6.6x ($98.2B vs $14.8B) |

The spread comes from two choices: what each tracker counts, and whether the comparison includes both Polymarket exchanges or only the US one. The engineers you're contacting built these books. If your outreach says "Kalshi does 6x" without saying what you measured, they'll see right away that you don't know the market.

Kalshi is the likeliest competing employer. It was valued at $40 billion after a $1 billion Series G in October 2026, and it has both the volume and the funding to absorb Polymarket's matching-engine and settlement talent. If you aren't Kalshi, don't pitch scale. Pitch ownership: the chance to design a book or a settlement layer rather than maintain one.

> **Blockchain engineering roles open now** - [see the open roles](https://www.refolk.ai/jobs/search?q=blockchain&family=engineering)

For founders hiring Kalshi and Polymarket engineers at the same time, keep the two pools apart. Kalshi's people are at a company that raised $1 billion in October. They're passive and expensive. Polymarket's released contractors may be available now and open to contract-to-hire.

## How do you message someone who may or may not have been cut?

Write to them privately, about their code, and don't assume they were let go. The work they did is public. Their employment status isn't.

What works:

- **Open with a specific commit or PR.** "Your change to order signing in clob-client-v2" shows you read the code.
- **Don't mention the layoffs as theirs.** You can say Polymarket is restructuring, since that's public news. Don't say it happened to them.
- **Name the arrangement.** Say up front whether the role is contract, contract-to-hire or full-time. Contractors who just lost a client want to know that first.
- **Make "not me" easy.** One line that says "if you're happily heads-down, ignore this" keeps the door open.
- **Get the market right.** If you cite Kalshi's lead, say which measure you're using.

A short version: "I read your work on ctf-exchange-v2's settlement path. I'm hiring someone to own matching and settlement on [product], contract or full-time, your call. Worth 20 minutes? If the timing's wrong, no reply needed."

## FAQ

### How many people did Polymarket lay off?

Polymarket hasn't said. It declined to disclose its employee or contractor counts and called the viral 30% figure inaccurate. A person familiar with the matter said more than half of those affected were contractors, mainly in marketing, customer experience and engineering, with contractor agreements ending November 4, 2026.

### Can I tell from GitHub who was affected by the Polymarket layoffs?

No. Commit history shows who built what and when their public activity stopped, but commits stop for many reasons: release cadence, private repos, finished scope or time off. Use contributors to ctf-exchange-v2 and clob-client-v2 as a lead list for private, no-assumption outreach, and never name anyone publicly as laid off.

### How do you find contractors after a layoff when the company publishes no list?

Start from the work instead of the employer. For engineering contractors, that means contributor history on the company's public repos, cross-checked against profiles that never name the client. Keyword search on the company name mostly returns go-to-market staff. In Refolk's index, only 3 of 25 sampled "Polymarket" headlines were engineering titles.

### Where else should I source smart contract engineers on GitHub?

Look in protocol and infrastructure repos. In Refolk's index, the top employers of the 54 US profiles with smart-contract or Solidity titles are Ethereum, Polygon Labs, Consensys and Api3. Commit history in those organizations, plus Polymarket's CTF exchange and UMA adapter repos, finds people whose titles never say "Solidity" at all.

---

_From the Refolk blog. More posts: https://www.refolk.ai/blog/index.md_
