Robinhood's June 16 Cut Lands Mid-World Cup. The Integration Layer Is the Prize.
Robinhood cut ~290 staff into record event-contract volume. Here's how to source the Predictions Hub integration engineers before July 7.
Robinhood filed an 8-K on June 16, 2026 cutting roughly 10% of full-time staff (about 290 people) the same month its prediction-market volumes hit records and Bernstein modeled the line nearly quadrupling to $586M for the year. If you recruit for Kalshi, Polymarket, Coinbase, IBKR, Webull, DraftKings, FanDuel, CME, or Rothera, the actionable window is roughly three weeks. The first fully released candidates land on the market around July 7, and the people you actually want are not the ones you'd guess from the org chart.
The setup: a RIF announced from "business strength"
The 8-K, signed by CFO Shiv Verma, frames the cut as happening "from a position of business strength, including June month-to-date average daily trading volumes at record levels across equities, options, and prediction markets." Robinhood will accrue ~$20M in cash severance and ~$8M in share-based comp in Q2 2026. Q2 closes June 30.
CEO Vlad Tenev's internal memo talked about raising "an absolute elite performance bar" and flattening layers. He conspicuously did not cite AI. That matters, because tech-sector employers announced 123,653 job cuts through the first five months of 2026, a 66% jump over the same period in 2025, with AI cited as the leading reason for three consecutive months. Brian Armstrong leaned on the "AI era" framing when Coinbase cut ~700 roles. Tenev did not. Read that as a signal about which seats actually got hit.
Why this RIF is mispriced
Look at the volume curve before you build your target list. In 2025 Robinhood's platform recorded over 12 billion event contracts traded. By May 2026 that number had reached approximately 16 billion. Q1 2026 alone produced 8.8 billion event-contract trades and drove "other trading revenue" up 320% YoY to $147 million. Daily prediction-market turnover across the industry climbed from $2.2 billion on June 11 to $4.8 billion on June 12 as the FIFA World Cup spun up, already past the $1.4 billion that traded around last season's Super Bowl.
No rational CEO guts the team driving 17% of transaction-based revenue in the middle of that. Predictions Hub core is almost certainly intact. The cut hit elsewhere, and the engineers you want are sitting in two specific places adjacent to it.
Where the cut probably landed
Tenev said "flatten layers." Translate that:
- Middle managers between IC leads and VPs, especially in non-Predictions product lines (cash card, retirement, crypto wallet, international expansion).
- Adjacent product teams whose work is being deprecated or absorbed. The most important one: the integration layer that connected Robinhood to Kalshi and Interactive Brokers' ForecastEx before Robinhood took a stake in Rothera and started routing World Cup contracts there.
That integration team is the mispriced asset. Their internal work is being quietly replaced by Rothera plumbing. Their external value is the highest in the market right now.
The Kalshi/ForecastEx integration engineers are the rare prize
Think about what these people actually built. They reverse-engineered the order entry, market data, and settlement APIs of a CFTC-licensed exchange (Kalshi) and a separate clearinghouse-affiliated venue (ForecastEx) under a regulated US broker. They shipped it into a retail product (Predictions Hub) at a scale that handled 8.8 billion contracts in a single quarter. They scaled it through a World Cup that pushed industry daily turnover above $4.8B.
Kalshi is publicly hiring for exactly this skill stack: order matching engines, trade execution algorithms, market data feeds, trading APIs, and clearing systems including margining, collateral management, and banking integrations. Kalshi's monthly trading volume hit $17.9 billion in May 2026 with about 57% market share. Polymarket dropped to ~$7.1 billion and needs regulated US distribution. Coinbase's clearing entity needs people who have shipped CFTC-adjacent infra at retail scale. IBKR's ForecastEx team has the exchange but not the consumer integration muscle.
Event-contracts engineering did not exist as a discipline before 2021. The entire global pool is a few hundred people.
The supply-side math is what makes this RIF actually matter. Monthly prediction-market volume was under $100M as recently as early 2024 and crossed $13B by the end of 2025. Anyone with 18+ months of production event-contracts experience is, generously, a few hundred people worldwide. A Robinhood cut that touches even 15 to 25 of them is a real supply shock.
The structural conflict nobody's pricing in
There's a wrinkle that should change how Kalshi recruiters approach this list. Robinhood is simultaneously a Kalshi distribution partner and, via its Rothera stake, a direct competitor. Rothera launched May 28 and traded approximately 200 million contracts in its first 18 days, with World Cup and MLB contracts driving nearly 100% of volumes. The "scale Rothera gradually over time" language in Robinhood's filings is corporate for "we want this revenue ourselves."
Engineers who built the Kalshi integration layer at Robinhood know how Kalshi's API behaves under load from a major broker counterparty. That institutional knowledge is gold for Kalshi product and infra teams. It is also legally fraught: NDA exposure, potential trade-secret claims, and the optics of hiring directly from your largest distribution partner during a quiet pivot. Polymarket, Coinbase, IBKR, and the sportsbook predictions teams (DraftKings Predictions, FanDuel Predicts) have none of that friction. Rothera itself, via its existing Robinhood relationship, is the ironic but clean landing spot.
If you're at Kalshi, you'd better move fast and you'd better not move clumsily. If you're anywhere else on that list, you have the easier pitch and the cleaner conflict picture.
The pool you're actually working with
Refolk's index shows ~403 current and former Robinhood software engineers identifiable as alumni or current staff. The dominant title clusters are Software Engineer, Senior Software Engineer, and Staff Software Engineer, concentrated in NYC, Seattle/Bellevue, and the Bay Area. Those are the same metros where Kalshi (NYC), Polymarket (NYC), and Coinbase's clearing entity recruit hardest.
Out of that 403, the Predictions-relevant subset is small. You're looking for signal across three layers:
- Order routing and execution to external venues (Kalshi, ForecastEx).
- Market data ingestion and normalization across two different exchange feeds with different contract specs.
- Risk, margin, and post-trade plumbing that ties the broker's internal ledger to external clearing.
Standard LinkedIn boolean strings will not get you there. "Robinhood" AND "event contracts" returns marketing managers and compliance analysts alongside the engineers. "Predictions Hub" is mostly absent from public profiles because the internal product name leaked late. Most of the people you want describe their work as "trading infrastructure" or "broker connectivity," which collides with the equities and options teams.
This is the exact friction we built Refolk for: you describe the person in plain English (the engineer who shipped the Kalshi integration into Predictions Hub, NYC, IC4 to IC6, not a manager) and get a ranked shortlist across GitHub, LinkedIn, and the open web. Conference talks at FIA Boca, CFTC comment letters, internal Robinhood blog posts archived on web.archive.org, and GitHub activity on order-book libraries all become searchable signal instead of a half-day of tab juggling.
The garden-leave clock and your July 7 deadline
The $20M cash severance and $8M SBC accrue in Q2, which closes June 30. IC notice and garden-leave periods at Robinhood commonly run about three weeks. That puts the first wave of fully released, free-to-sign candidates on the market the week of July 7. Recruiters who wait for LinkedIn "Open to Work" badges will be a week late, and the badges themselves are a noisy signal in a cohort where most people will take a call before they update their profile.
Reach out in the first 10 days after the filing while people are still numb and still attached to the work. The pitch that lands is not "we're hiring," it's "the system you built is about to get deprecated internally, and we want to ship the next version of it at scale."
Where each acquirer should focus
- Kalshi: integration-layer ICs who touched the Kalshi API directly, but route through outside counsel to manage the partnership conflict. Backend, infra, and clearing roles map cleanly to the public Kalshi reqs.
- Polymarket: anyone who shipped retail-grade onboarding and KYC under broker-dealer rules. Polymarket's gap is regulated US distribution, not matching engines.
- Coinbase / The Clearing Company: staff-level engineers who built risk and margin under CFTC oversight. Bernstein names Coinbase as the other key distribution player in the $10.8B-by-2030 thesis.
- IBKR (ForecastEx) and Webull: traditional broker DNA plus event-contracts experience is the rarest combo. These shops can pay flat cash and skip the equity story.
- CME, DraftKings Predictions, FanDuel Predicts: people who scaled World Cup volume. Sports liquidity expertise is the differentiator.
- Rothera: the cleanest legal path for the laid-off Robinhood engineers themselves, and the fastest ramp because the systems are familiar.
Bernstein estimates industry prediction-market revenues expand from roughly $400M in 2025 to $2.5B in 2026 and reach about $10.8B by 2030 at current take rates. Every venue on that list is going to be hiring this exact profile through year-end. The Robinhood cohort is the first concentrated supply they'll see.
What to do this week
If you're sourcing the Robinhood Predictions team, the work is concrete:
- Build a list of the ~25 to 40 most plausible Predictions-adjacent ICs from the 403 known Robinhood engineers, weighted toward NYC and Seattle.
- Layer in GitHub signal: order-book libraries, FIX/QuickFIX commits, anything touching contract specs or CFTC reporting formats.
- Cross-reference public conference talks, podcast appearances, and any FIA, Futures Industry Association, or CFTC comment letters.
- Reach out before July 7 with a specific pitch tied to the work, not a generic "exciting opportunity" template.
Refolk handles steps one through three in a single plain-English query, which is the only way this timeline is realistic for a small recruiting team. Step four is still on you, and the engineers who shipped event-contracts infrastructure at Robinhood will know within two sentences whether you've actually read their work.
FAQ
How many of the ~290 Robinhood layoffs are actually engineers worth chasing for event-contracts roles?
Probably 15 to 40. The Predictions Hub core team is almost certainly intact given Bernstein's $586M revenue forecast and the World Cup mid-tournament. The mispriced cohort is the integration-layer engineers who connected Robinhood to Kalshi and ForecastEx before the Rothera pivot, plus middle managers and adjacent ICs in deprecated product lines. Out of Refolk's index of ~403 current and former Robinhood engineers, the Predictions-relevant subset is small but very high signal.
Why is the July 7 window so important for sourcing Robinhood Predictions team alumni?
The 8-K accrues $20M in cash severance and $8M in SBC in Q2, which closes June 30. Typical IC notice and garden-leave periods at Robinhood run about three weeks from the June 16 announcement. That puts the first fully released candidates on the market around July 7. The supply of event-contracts engineers globally is in the low hundreds, and competitors at Kalshi, Polymarket, Coinbase, IBKR, Webull, CME, DraftKings Predictions, and FanDuel Predicts are all hiring from the same pool right now.
Can Kalshi actually hire the engineers who built Robinhood's Kalshi integration?
Legally yes, practically it's complicated. Robinhood is still a Kalshi distribution partner, so hiring the engineers who built that integration creates NDA exposure and a delicate optics problem during a period when Robinhood is quietly shifting volume to Rothera. Kalshi can hire them, but should route through outside counsel and likely target ICs who touched adjacent infrastructure (market data, clearing) rather than the direct Kalshi API integration. Polymarket, Coinbase, and IBKR have none of that conflict.
What plain-English query would I run in Refolk to find this cohort?
Something like: "Software engineers who left Robinhood in June or July 2026 and worked on Predictions Hub, the Kalshi or ForecastEx integration, or event-contract clearing, based in NYC, Seattle, or the Bay Area, IC4 to IC6, not managers." Refolk pulls signal from GitHub, LinkedIn, and the open web to rank candidates by actual relevance to event-contracts engineering rather than keyword overlap, which is the bottleneck on a three-week sourcing window like this one.