Groupon's COO Walked With No Severance. Project Foundry's 400 Cuts Start Today.
Groupon's COO exit today opens Project Foundry's 12-week engineering layoff window. Here's how to source the 400-role cut through Q3 2026.
Groupon's COO walked out the door today with no severance, on the exact date the board approved Project Foundry two months ago. That's not an executive shuffle. That's the starting gun on a 12-week rolling window where up to 400 people, including engineers from a 350-person org, hit the market on a schedule you can actually plan against.
Most sourcers will read the headline, tag "Groupon" in LinkedIn Recruiter, and move on. That's a mistake. Project Foundry is one of the cleanest, most predictable talent-supply events of the year, and it runs through October in the US and well into Q4 everywhere else. Here's how to work it.
The dates that matter
Jiri Ponrt notified Groupon of his resignation on May 21, 2026. Effective date: today, July 10. The 8-K says voluntary, no disagreement, and importantly, no severance. On the same May 21, the board approved Project Foundry, which eliminates up to 400 roles globally, roughly 24% of the workforce, across HR, customer service, and engineering. Aditya Rajkumar (ex-7-Eleven Skipcart, marketplace/last-mile background) starts as COO on August 3.
Read the sequencing. Plan approved, COO out with no payout on the effective date the plan starts biting, successor from a marketplace-automation background arriving three weeks later. Groupon's CEO Dusan Senkypl (Pale Fire Capital, ~22% shareholder) has committed publicly to rebuilding the company as an AI-native operator. This is a locked roadmap, not a rumor mill.
For sourcers, the operational implication is simple: you have fixed dates to work backward from.
The engineering org is 350 people, and most of them aren't in Chicago
If you're chasing "Groupon Chicago engineering talent," you're indexing on the wrong city. Chicago is HQ. It is not the biggest engineering hub.
CTO Ales Drabek joined in May 2025 and runs the org from Munich. Internal profile signals across the open web put the largest concentrations of Groupon engineers in Bengaluru and Hyderabad, then Prague (Pale Fire's home turf), Seattle, and Chicago. Ireland (Sligo) is in the mix too. If your Boolean starts with ("Groupon") AND ("Chicago" OR "Illinois"), you're seeing maybe a third of the pool.
This is where plain-English search beats keyword gymnastics. Instead of stacking location filters and title synonyms, you can ask Refolk something like "senior backend engineers who left Groupon in the last 90 days, ranked by Kafka and Scala depth, anywhere in EMEA or India" and get a ranked shortlist that doesn't collapse to whatever LinkedIn's location field happens to say this week.
The legacy stack is a sourcing asset
Groupon's historical stack, still visible on plenty of current engineer profiles, includes Ruby on Rails, Node.js, Ember.js, Python, Scala, Clojure, Java, Hadoop, Hive, Spark, and Kafka. Two of those (Scala and Clojure) are unusual enough to double as high-signal search terms. Ember is nearly a fingerprint. If you want to identify long-tenured Groupon engineers without leaning on the company name at all, pivot on the stack.
Why "Project Foundry engineering cuts" is a different pitch
Read Groupon's own language carefully. Project Foundry doesn't just cut engineers. It cuts them because AI-generated code and automated QA are absorbing the work. Groupon is deploying AI voice agents to replace human merchant outreach and shipping product features without traditional engineering teams. The company is literally telling its own engineers, in an SEC filing, that agents replaced them.
That reframes your outreach. Every recruiter this month is sending some variant of "sorry to hear about the layoffs, we're hiring." The engineers you want are getting fifty of those. The wedge here is different: the AI-native restructuring narrative gives them a bruise that generic outreach can't reach.
If you're hiring for a company where engineers build AI systems rather than get replaced by them, say that out loud in the first line. "You shipped code that got called overhead. Come ship code that gets called leverage." Not literally that, but that idea. The Project Foundry cohort will read it differently than any other layoff cohort this year.
Groupon told its own engineers, in an SEC filing, that agents replaced them. That is not a bruise generic outreach can reach.
The 12-week rolling window (and why it's actually longer)
Here's the pacing most people will get wrong.
Groupon's fiscal Q3 runs July 1 through September 30. The 8-K says "most reductions expected by the end of Q3 2026." Read casually, that sounds like a hard October cutoff. It isn't.
The same filing notes that pace depends on "local legal rules and consultation processes in different countries." In practice, that means:
- US cuts (Chicago, Seattle): fastest. Expect the bulk to close between now and mid-September. WARN triggers in Illinois add some structure to timing.
- India cuts (Bengaluru, Hyderabad): staggered through Q3, with notice-period tails that push actual last-days into October and November.
- EMEA cuts (Prague, Munich, Sligo): works councils, statutory consultation periods, and individual notice terms push these into Q4 2026 and, for senior roles, potentially into early 2027.
The 8-K also explicitly leaves room for additional actions through 2027. So the "12 weeks" framing is the US-fast version. The realistic sourcing window for the full pool is closer to nine months.
If you're pacing outreach cadence, treat Chicago and Seattle as July-August work, India as August-October, and Prague/Munich/Sligo as September-January. Trying to hit all of it in one August sprint is how you burn the pool.
The "talent density" cohort is the hidden shortlist
Buried in the 8-K is a line worth reading twice: up to 50% of the $20-25M in annualized payroll savings gets "reinvested in 2026 in marketing, AI infrastructure, and talent density."
Translation: while Groupon is cutting 400 people, it is also hiring. Selectively. For AI-native roles.
That creates a specific, identifiable cohort: engineers who were on the eligible list, weren't retained for the new AI teams, and are now on the market. These are people who cleared Groupon's bar recently enough to survive multiple prior reductions but weren't picked for the AI reset. That is not a bad signal. In most cases it means they were strong on the legacy stack (Rails, Ember, Scala, Hadoop) rather than weak overall.
For engineering leaders hiring senior ICs who can pick up an AI-adjacent codebase without being AI-native from day one, this cohort is undervalued for the next two quarters. Sourcing laid-off engineers from this specific slice, rather than the whole Foundry pool, is where the compounding returns are.
The comparables tell you this isn't isolated
Project Foundry lands inside a pattern. Cisco cut around 4,000 roles in May 2026. Wix released 1,000+ in the same window, heavily concentrated in Israeli engineering. Nike put roughly 1,400 tech-heavy roles on the market in Beaverton. Oracle's 10-K named AI as the reason for 21,000 cuts. Microsoft's July 6 action freed 3,200 sellers on the commercial side.
Two implications. First, the engineers you're pulling from Groupon are being courted by everyone working the Cisco and Wix pools too. Speed matters. Second, if you're targeting a specific stack or geography (say, Prague engineers who know Scala and Kafka), you can cross-reference Groupon leavers against Wix leavers against smaller Prague-based layoffs and build a stack-native shortlist that isn't dependent on any single company.
That kind of cross-company, stack-first sourcing is exactly where natural-language queries pull ahead of Boolean. You describe the person once ("Scala-heavy backend engineer in Prague or Munich, laid off in the last six months, has shipped streaming systems at scale"), and Refolk pulls the answer across companies rather than making you rerun the same search seven times.
An operational playbook for the next 12 weeks
If you're a technical recruiter or engineering leader working Groupon layoffs 2026 as a supply pool, here's a concrete cadence.
Week 1 to 2 (now)
Build the initial list. Focus on US-based engineers whose LinkedIn "Open to Work" flipped in the last 30 days, plus anyone with Groupon in their current title and a recent public commit history on GitHub. Cross-reference with the stack (Ember, Rails, Scala) to catch profiles that don't say "Groupon" anywhere current. The COO gap between July 10 and August 3 is when internal decisions accelerate; people find out this week.
Week 3 to 6 (late July through mid-August)
Rajkumar starts. Second wave of role clarifications hits internally. This is when "retained but reassigned" engineers realize the new role isn't what they signed up for. Start on India (Bengaluru, Hyderabad). Notice periods there mean profiles get accurate around now.
Week 7 to 12 (late August through end of September)
Prague and Munich open up. Consultation processes complete. This is your Scala/Kafka/Clojure window, which is worth waiting for.
Q4 (October through December)
The "additional actions through 2027" language kicks in. Sligo and any second-round EMEA reductions land. If you missed the summer pool, this is your second bite.
Across all of it, the trap is treating Project Foundry as one event on one date. It's a supply chain with a schedule.
FAQ
How many Groupon engineers are actually on the market from Project Foundry?
Groupon has approximately 1,734 employees and Project Foundry cuts up to 400 (about 23-24%). Engineering is one of three named target functions, out of a CTO org of roughly 350 people. Exact engineering headcount inside the 400 hasn't been disclosed, but a proportional cut would put engineering losses in the 80-100 range, with the balance from HR, customer service, and sales. The rolling nature of the cuts means only a fraction of that pool is on the market at any given week.
Where are the Groupon engineers actually based?
Chicago is HQ, but engineering is not Chicago-centric. CTO Ales Drabek runs the org from Munich. The largest engineering concentrations sit in Bengaluru and Hyderabad, followed by Prague (Pale Fire Capital's home city), Seattle, Chicago, and Sligo, Ireland. Sourcers who filter on Chicago alone miss the majority of the pool.
What's the best angle for outreach to Project Foundry engineers?
The AI-native restructuring narrative is a specific bruise. Groupon told these engineers, in filings and press coverage, that their work is being absorbed by AI agents and automated QA. Outreach that acknowledges that (and offers a role where they build AI systems rather than get replaced by them) reads differently than the fiftieth "sorry about the layoff" message in their inbox this week.
When does the sourcing window actually close?
The headline says end of Q3 2026 (September 30). The reality is longer. US cuts land fastest, India through October and November, and EMEA (Prague, Munich, Sligo) stretches into Q4 2026 and early 2027 due to works councils and consultation periods. The 8-K also explicitly leaves room for additional actions through 2027, so treat this as a nine-month sourcing window, not a twelve-week one.