Wix's May 29 Cut Puts 920 Velo and React Engineers in Tel Aviv in Play
Wix's May 29, 2026 layoff of ~1,000 opens a 60-90 day window on senior frontend and Velo engineers in Tel Aviv. Here is the sourcing plan.
On Thursday, May 28, 2026, Wix CEO Avishai Abrahami told staff and the public on X that the company would cut as many as 1,000 employees, roughly 20% of its global workforce. Israeli reports peg about 920 of those in Israel, the vast majority sitting in or around Tel Aviv. If you hire senior frontend, React Native, or Node-backed serverless engineers, this is the cleanest cohort you will see this quarter, and the window closes faster than you think.
What actually got cut, and where
Wix ended Q1 2026 with 5,277 employees, more than 60% of them in Israel. That implies a pre-cut Israel headcount north of 3,200. A ~920-person Israeli cut is therefore close to a third of the local org, not a trim. Abrahami framed it two ways at once: the shekel has traded as high as NIS 2.8 to the dollar, the highest rate since 1993, which makes Israeli payroll punishingly expensive in USD terms; and Wix is restructuring around what he calls AI-native software work.
Both framings matter for sourcing. The currency story tells you why ex-Wix engineers will entertain a USD-denominated remote offer that would have been a downgrade 18 months ago. The AI story tells you exactly how not to pitch them.
The same week, Amdocs confirmed about 3,000 layoffs including hundreds in Israel, Rapyd entered an overhaul expected to cut hundreds, and SentinelOne began preparing hundreds of cuts including dozens in Israel. AI21 Labs cut ~110, roughly 60% of staff. So the late-May Israeli signal is noisy. By mid-July, the Wix cohort becomes clearly identifiable again, and that is when the work gets interesting.
Why "ex-Wix frontend" is not what most recruiters think it is
The reflex when a website-builder company lays people off is to file them under "low-code." That reflex is wrong, and acting on it is how you lose this hire to Meta Tel Aviv or Lightricks.
Wix's own job descriptions tell you the actual stack: Git, Node.js, React, Redux, MobX, ES6+, with expertise expected across React/Angular/Vue and Babel/Webpack/Rollup/Parcel plus TypeScript. The frontend org has an internal name, "Wix's Frontend Engineering Guild," that builds scalable, resilient products and complex micro-frontends. The Velo platform, the part outsiders most often misread, is a full-stack serverless platform with a Node.js server-side runtime hosted on Wix's cloud that supports hundreds of millions of websites at a sub-100ms p50 response time.
That is not a WYSIWYG hobbyist profile. That is a JavaScript-at-extreme-scale profile, the kind of engineer who has shipped a Node service that cannot afford a bad GC pause.
A Velo engineer is not a low-code person. They are a Node engineer who has been on call for hundreds of millions of sites.
Two open-source projects that originated at Wix are useful filters here: Detox (gray-box end-to-end testing for React Native) and React Native Navigation. Contributors to either of those, especially ones with @wix.com commit history, are top-of-funnel for any team that needs senior React Native or mobile test infrastructure work.
The 5-day RTO wedge that nobody is using yet
A few months before this cut, Wix cancelled hybrid work and required Israeli staff back to the office five days a week. Their current careers language is explicit: "Our work model is fully in person, with 5 days a week from our office."
That mandate landed badly with a chunk of the senior bench, and many of the ~920 affected people were already actively unhappy about it before they got the news on May 29. If you are a remote-first or hybrid employer paying in USD, you have a rare double wedge: lifestyle and currency, in the same conversation. You do not need to negotiate against an in-office incumbent. The incumbent already lost that fight internally.
This is the framing that tends to convert in first-touch outreach to this cohort. Lead with the work model, not the comp number.
The Boolean is not "Velo"
Here is the non-obvious move. If you search LinkedIn or your ATS for "Velo," you will under-index senior internal Wix engineers. Velo shows up on developer-relations and partner-engineer profiles more than on core platform profiles. The terms senior Wix engineers actually put on their profiles are:
- "Frontend Engineering Guild"
- "xEngineer" (Wix's internal title for end-to-end product owners)
- "Wix Studio Editor"
- "Repluggable" (an internal micro-frontend framework)
- "micro-frontends" plus "Wix"
- "KickstartX" (the Wix Campus program in Glilot, Tel Aviv)
Combine any of those with "React," "TypeScript," and a Tel Aviv District location filter and you immediately separate the platform engineers from the partner ecosystem. This is exactly the kind of multi-term Boolean that decays on LinkedIn the moment a competing recruiter publishes a similar string, which is why we built Refolk: you describe the person in plain English ("senior frontend engineer, ex-Wix, worked on Studio Editor or Repluggable, based in Tel Aviv, strong React and TypeScript") and get a ranked shortlist pulled across GitHub, LinkedIn, and the open web.
Refolk's own index gives a useful size check: a search for Frontend / Senior Frontend Engineer titles in Israel with React and JavaScript skills returns about 1,329 matching profiles, and Tel Aviv District dominates the regions. The top current employers in that sample include Wix.com, Meta, eBay, Guardio, Cyera, and Jifiti. In other words, the senior frontend pool in Tel Aviv is finite and well mapped. You are not competing against an infinite supply.
A 60 to 90 day plan that respects the noise
Here is how to time this. The same-week cluster (Wix + Amdocs + Rapyd + SentinelOne + AI21) is going to produce a flood of "Open to Work" green frames in early June. You cannot triage that volume by hand without picking up a lot of false positives from the Amdocs BSS bench, which is a completely different sourcing problem (and worth its own plan in Ra'anana).
Weeks 1 to 2 (early to mid June): build the watchlist, do not send
Use this window to build a clean list. The signals that matter:
- Current or last employer Wix, last role contains "Frontend," "Full Stack," "Software Engineer," or "xEngineer"
- Tenure at Wix of 2+ years (filters out the very newest joiners and gets you institutional knowledge)
- Tel Aviv District or remote-from-Israel location
- Either a GitHub profile with commits to Detox, React Native Navigation, or wix/* repos, OR a Medium presence on the wix-engineering publication, OR a conference talk at ReactNext
Do not send outreach yet. The cohort is being carpet-bombed by everyone with a recruiting seat. Your inbox win is a function of timing, not volume.
Weeks 3 to 6 (mid June to mid July): first touch, AI-aware framing
Now send. Abrahami publicly attributed the cut to AI restructuring, which means a sizable share of this cohort is privately worried they are being "automated away." Generic frontend pitches that talk about "scaling our React codebase" will underperform. Pitches that explicitly position the role as building AI-leveraged tooling, owning evaluator infrastructure, or shipping agent-facing UI will outperform, because they reframe the person as the one wielding the AI rather than the one displaced by it.
If your team also hires React Native, name Detox and React Native Navigation by project name. That single line of specificity collapses the distance between "cold recruiter" and "someone who actually knows what I built."
Weeks 7 to 12 (mid July to late August): the cleanup pass
By mid-July the noise clears and the cleanest available signal becomes: "Open to Work + ex-Wix + Tel Aviv + 4+ years React." This is when Lightricks, Monday.com, Riskified, and the Meta Tel Aviv office start absorbing the bench at speed. If you have not closed by late August, you are competing for the tail, not the head.
For hiring ex-Wix engineers specifically, this is also when you should do a second pass on people who did not respond in June. Many will have taken offers from local scale-ups that turn out to look a lot like the job they just left, in-office and shekel-denominated. A USD remote offer in August reads very differently than the same offer in June.
Adjacent pools worth running in parallel
Three other talent flows are open at the same time and serve different roles:
- Amdocs (BSS, telecom platforms, Ra'anana-heavy): different stack, different geography inside Israel, do not mix into the Wix list.
- Rapyd (fintech backend, payments): useful if you hire Node backend or payments, not for frontend.
- SentinelOne (security, endpoint, detection): different cohort entirely, but a parallel Israeli tech talent sourcing track if you also hire security engineers.
The mistake is collapsing all four into one "Israeli layoff list." They cluster on the calendar but not on the role. Senior frontend engineer Israel searches should be Wix-led; payments and BSS searches should not.
What to budget for, in plain numbers
Q1 Wix revenue grew 14% YoY to $541M but the company posted a $57.5M net loss, and shares fell 27% on May 13 after the earnings miss. Adjusted EPS came in at $0.68 against a $1.22 consensus. That gap is what drove the cut, and it is also why severance and notice periods will be on the shorter end of what Israeli law allows. Translation: this cohort hits the market with less runway than the 2022 to 2024 Big Tech cuts gave their alumni. They will move faster. Your offer cycle needs to match.
If you can get from first message to verbal in under three weeks, you will win hires you would otherwise lose to a same-city competitor with a faster loop. If your loop is six weeks, you are sourcing for someone else's pipeline.
FAQ
Are Velo engineers really comparable to "real" Node engineers?
Yes, with one caveat. The Velo runtime is Node.js hosted on Wix's cloud, serving hundreds of millions of sites at sub-100ms p50. Engineers who worked on the platform itself (not just on customer Velo apps) have shipped distributed JS at a scale very few companies match. The caveat: filter for Wix internal platform tenure, not just "Velo" on the profile, because the keyword over-indexes partner and DevRel roles.
How do I tell a Wix Studio Editor engineer apart from a generic frontend hire?
Look for "Repluggable," "micro-frontends," "Studio Editor," or "xEngineer" on the profile, plus contributions to wix/* GitHub repos or talks at ReactNext. The Frontend Engineering Guild is the umbrella term inside Wix, so that phrase showing up verbatim is also a strong signal of someone who self-identifies with the platform org rather than a product team.
Should I lead outreach with the layoff?
No. Lead with the role, the work model (especially if you are remote or hybrid), and a specific reference to something they actually built. The five-day RTO mandate at Wix is a better wedge than severance sympathy, and the AI-restructuring framing in Abrahami's announcement means a sympathetic "we know you got hit" opener can read as condescending. Be useful, not sorry.
When does this window actually close?
Practically, late August 2026. Lightricks, Monday.com, Riskified, eBay Israel, and Meta Tel Aviv are the most active local absorbers of senior frontend talent, and they will move on this cohort within 60 to 90 days. After August, you are sourcing the tail, paying more, and competing against people who already met your candidates in June.