Wix Cut 1,000 on May 28. The Velo Multi-Tenant Team Is the Real Prize.
Wix's largest-ever layoff frees a niche Tel Aviv talent pool that Lovable, Bolt, v0, and Replit need. Here is how to sequence outreach before Base44 absorbs them.
On May 28, 2026, Avishai Abrahami announced the largest layoff in Wix's history: roughly 1,000 people, about 19% of a 5,277-person company where more than 60% of headcount sits in Israel. If you run sourcing for an AI-native app builder, a developer tools company, or any multi-tenant SaaS, the next 14 days are the entire window. The valuable profile is not what most recruiters will chase.
Most inbound lists will target "Wix frontend engineer." The wrong target. The hire that moves your roadmap is the Velo platform IC who has actually shipped multi-tenant rendering at the scale of a million sites per Mongo cluster. There are not many of those people on Earth, and Wix just put a meaningful fraction of them on the market.
What actually got cut, and where the pain lands
Wix's Q1 2026 print is the context. Revenue was up 14% to $541.2M, but the company swung from a $33.8M profit a year earlier to a $57.5M GAAP net loss. Non-GAAP operating margin compressed from 21% to 5%. EPS came in at $0.68 against a $1.22 consensus, a 44% miss. The stock fell roughly 26% on the day and is down close to 50% YTD. Market cap is now around $2B, off a peak near $20B.
The capital structure made the cut inevitable. Wix completed a $1.6B Dutch tender at $92/share, buying back about 30% of its equity and leaving roughly $900M in cash. With a near-empty war chest, a strong shekel adding about $64M of FY26 opex headwind, and the CEO publicly tagging "fast evolution of AI capabilities" as the reason, R&D was always going to take the hit. Customer care already absorbed a 40%+ reduction via AI in prior rounds. This is the first cut to deeply touch product and engineering.
Internal reporting via Globes and Calcalist used unusually direct language: "As AI tools take on more development and design work, several roles are simply becoming redundant." That framing, plus the geography, tells you exactly where to look. Tel Aviv. Frontend platform. Editor and Studio. The AI website-builder teams whose function has been functionally replaced by Base44, the Maor Shlomo acquisition that hit $150M ARR in mid-May and triggered a $38M earnout.
The profile that matters: editor internals and multi-tenant runtime
"Tel Aviv frontend engineers hiring" is the obvious search. It is also the wrong filter. The Wix engineering blog has been quietly publishing a roadmap of what their best ICs actually do, and almost none of it is generic React.
The Velo team, formerly Wix Code, ships a low-code runtime that hosts roughly 1 million sites per MongoDB cluster, with a custom tenant-allocation layer that keeps individual collections under 50GB. Wix Studio serves 4.5B+ daily requests across AWS, GCP, and proprietary data centers, with 200+ CDN nodes and 99.98% uptime. The Studio editor itself is a real-time collaborative canvas with on-canvas commenting, role-based permissions, live multiplayer cursors, custom breakpoints, and a VS Code-based IDE shipped to end users.
Read that list and ask: who else has shipped that stack? Webflow. Figma. Framer. A handful of others. That is the entire global pool. A 1,000-person Wix cut probably 2x to 3x the available supply of this niche overnight.
This is the profile Lovable, Bolt.new, v0, Replit, Cursor, Windsurf, Emergent, and Magic Patterns are about to need badly. Lovable's full-stack React/TS generation, Bolt's WebContainer-based browser IDE, v0's Next.js component synthesis with Design Mode, and Replit Agent 3/4's 200-minute autonomous builds all hit the same wall: multi-tenant rendering at scale, drag-and-drop editor internals, and low-code runtimes that do not collapse when a million agent-generated apps come online. Wix solved those problems five years ago.
A 1,000-person cut at Wix probably doubles or triples the global supply of canvas-WYSIWYG engineers in a single afternoon. </pre>
Correction on format. The pull block:
A 1,000-person cut at Wix probably doubles or triples the global supply of canvas-WYSIWYG engineers in a single afternoon.
Why the standard sourcing playbook will miss them
Three reasons the usual layoff cycle does not apply here.
The February RTO already started the timer
In February 2026, Wix forced a five-day return-to-office that triggered visible backlash inside the company and across the Israeli tech scene. The strongest Editor and Studio engineers started passive interviewing in March. By the time the May 28 announcement hit X, the best of them were already in late-stage loops at Melio, Pentera, Duda, Teads, and the US AI builders. If your outreach goes out in week three, you are negotiating against a verbal offer.
Base44 is hiring from the same building
Wix is reallocating ICs toward Base44 even while cutting elsewhere. The acquired AI vibe-coding platform went from $100M ARR in March to $150M in mid-May. Maor Shlomo is being handed budget. Internal transfer offers are going out this week to the exact Velo and Studio ICs you want. If you are competing for "Wix Editor engineers," you are not just competing with Lovable and Bolt. You are competing with Wix's own Tel Aviv AI org, which has the incumbency advantage and no relocation friction.
The shekel is doing half the work for you
Abrahami specifically cited shekel strength as a layoff driver. That cuts both ways. USD-paying foreign acquirers have a structural comp advantage over Israeli employers right now. A US AI startup paying in dollars can outbid Melio and Pentera without breaking a band. If you are a US engineering leader and you have been told Tel Aviv comp is "competitive with the Bay," the FX math just shifted in your favor for at least the next two quarters.
How to actually find them
The LinkedIn search "Wix" plus "React" returns thousands of profiles. Most of them are marketing site builders, customer support engineers who learned to deploy, or junior frontend ICs. The signal you want is buried under noise.
What works is filtering on the artifacts. GitHub commits to wix-private, wix-incubator, or stylable orgs. Blog posts on wix.engineering. Conference talks at React Israel, Reversim, or InfoQ. Co-authorship on the multi-tenant Mongo post. Velo SDK contributions. These are not LinkedIn-searchable fields.
This is the exact friction we built Refolk for. You describe the person in plain English, "Tel Aviv engineer who shipped multi-tenant rendering or canvas editor internals at Wix, Webflow, Figma, or Framer, with public artifacts," and you get a ranked shortlist across GitHub, LinkedIn, and the open web instead of a 4,000-row CSV you still have to filter. For sourcing Israeli engineers in a 14-day window, that compression is the difference between a hire and a near-miss.
A sequencing plan for the next 14 days
Treat this as a time-boxed campaign, not an evergreen pipeline.
Days 1 to 3: identify the platform ICs, not the generalists
Build three lists. One for Velo / Wix Data multi-tenant SaaS engineers. One for Studio Editor canvas and collaboration ICs. One for the AI website-builder team being absorbed into Base44. Do not merge them. The pitch is different for each.
Days 4 to 7: first-touch with specificity
Generic "saw the news, would love to chat" notes will get archived. The Velo IC wants to hear that you have a multi-tenant scaling problem they would actually find interesting. The Studio canvas engineer wants to hear about your editor surface, not your Series B. Reference a specific post, talk, or commit. The reply rates on specific notes versus generic ones in this segment are not close.
Days 8 to 14: close the loop before internal transfers do
Base44's internal recruiting team has the home-field advantage. Your only structural advantage is speed, USD comp, and the fact that the strongest ICs were already unhappy after the February RTO. If you are still on first contact by day 12, you have lost.
If you are running parallel searches across the AI-builder cohort, Lovable, Bolt, v0, Replit, Cursor, this is also where a tool like Refolk earns its keep. You can re-ask the same question with different role shapes ("now show me the same profile but with SSR and crawler-readability experience") without rebuilding your Boolean string from scratch.
Correcting that. Real block:
The contrarian read
Most write-ups will frame this as "AI ate Wix." That is the company's own framing and it is half wrong. AI is replacing the AI website-builder team, yes. But the Velo multi-tenant runtime and the Studio canvas editor are not "AI redundant." They are the substrate that every AI builder needs and has not built yet. Wix is cutting the layer that wraps the platform, and a portion of the platform team is going out the door with it because the company has $900M in cash and no margin for a soft restructure.
For the engineering leader at Lovable or Bolt who has been told "we cannot find canvas editor engineers, they do not exist," the answer for the next 14 days is: they do, they are in Tel Aviv, and they were just freed. Move now.
FAQ
Are Wix engineers actually open to leaving Israel, or is this a Tel Aviv-only opportunity?
Historically Wix engineers have been sticky to Israel, but two things shifted. The February 2026 RTO mandate pushed a meaningful chunk of senior ICs into active job search before the layoff. And shekel strength means USD-denominated offers from US AI startups now carry a real premium even without relocation. Expect roughly a third of strong candidates to consider remote-from-Israel arrangements with US companies, and a smaller but non-trivial share to consider relocation to NYC, London, or Stockholm if the comp and equity story is sharp.
How do I tell a Velo platform IC apart from a generic Wix frontend engineer on LinkedIn?
Title alone will not do it. Look for public artifacts: contributions to wix-incubator or stylable on GitHub, posts on wix.engineering with their byline, talks at Reversim or React Israel, or named involvement in the multi-tenant Mongo architecture writeup. The Velo and Studio platform teams publish more than most internal infra orgs, which is a gift to sourcers willing to do the artifact work. If their LinkedIn just says "Senior Software Engineer at Wix" with no detail, assume generalist until proven otherwise.
Is Base44 really competing for the same people, or is that overstated?
It is real and it is the single biggest threat to your timeline. Base44 went from $100M to $150M ARR in two months and just triggered a $38M founder earnout, which means internal headcount is being reallocated toward it aggressively. The same Tel Aviv ICs you are targeting are getting internal transfer offers this week. You are not just competing with Lovable and Bolt. You are competing with Wix paying its own people to stay in a different building.
What is the right outreach window before this pool is gone?
Fourteen days from the May 28 announcement for the strongest 20% of the cut. Thirty days for the next tier. After that, the top platform ICs are in final loops or have accepted, and you are sourcing the middle of the distribution. The February RTO compressed this timeline by roughly 60 days versus a typical layoff cycle. Treat the calendar as your binding constraint.