Axonius's 46 Israeli Engineers Aren't Fired Yet. Call During the Shimua
Axonius called 46 Tel Aviv R&D engineers to pre-dismissal hearings. How to time outreach in Israel's 2 to 6 week window and tell core from healthcare teams.
Axonius has called 46 Tel Aviv R&D engineers to pre-dismissal hearings, and under Israeli law none of them has been fired yet. For the next few weeks they stay on payroll, their profiles still say Axonius, and no layoff tracker will publish their names.
That gap is your window. The recruiters who use it know the procedure, can tell which Axonius product a given engineer built, and make contact before the "replaced by AI" story sticks to the whole group.
What did Axonius announce?
Axonius plans to cut 66 of its 722 employees, about 9%, and 46 of those cuts fall on its Israeli development centre. The company employs 207 people in Israel, so about 22% of its Israeli workforce has been called to hearings.
The company says it is rebuilding engineering "around a new AI-driven approach to software development," and CEO Joe Diamond said the changes follow several months of reworking how it builds software. This is the third round in a year:
- November 2025: about 100 of roughly 900 staff.
- February 2026: 40 people (about 4%), mostly senior marketing and sales. Only 7 were in Israel.
- November 2026: 66 people, 46 of them in Israeli R&D.
Diamond became interim CEO in February 2026, when co-founder Dean Sysman moved to executive chairman. That same month the company said: "We remain fully committed to our Tel Aviv R&D center and continue recruiting for critical technology roles." Nine months later, Israeli R&D is the main target.
| Metric | Israel | Outside Israel |
|---|---|---|
| Headcount | 207 | 515 |
| Roles cut, Nov 2026 | 46 | 20 |
| Cut rate | 22.2% | 3.9% |
| Share of Feb 2026 round | 7 of 40 | 33 of 40 |
| Share of Nov 2026 round | 69.7% | 30.3% |
That is about 2.4x Israel's share of headcount, and its cut rate is about 5.7x the rate everywhere else. These engineers came through two earlier rounds, including one after which the company publicly promised to keep the Tel Aviv centre. Most are likely the experienced people Axonius chose to retain, which makes them a different pool from a performance cull.
Why aren't the 46 engineers fired yet?
Israeli law requires a hearing before any dismissal, so "summoned to a hearing" means a decision is pending. It does not mean "terminated."
The hearing, or shimua, is required whatever the reason for termination, layoffs included. The employer must genuinely consider what the employee says before deciding anything. The sequence runs in this order:
- Hearing invitation, typically with 5 to 7 working days to respond.
- Hearing, where the employee responds.
- Decision, after the employer weighs that response.
- Notice of dismissal, with a statutory minimum of one month after one year of service.
- Notice period, worked or paid in lieu.
- Final settlement.
Because the response has to be genuinely considered, some of the 46 may yet be kept. Until decisions land, every one of them is still an Axonius employee.
How long is the quiet window?
Expect roughly 2 to 6 weeks between the hearing invitations and the point where affected engineers become visible to the wider market. During that time they are still employed, and normal sourcing signals don't show them.
The window adds up like this:
- 5 to 7 working days to respond to the hearing invitation.
- A decision from the employer.
- Up to a month of notice, which may be paid in lieu.
Nobody in this group has much reason to change a profile. The hearing could still go their way, and they are on payroll. The trackers don't help either. TrueUp logged the Axonius cut on November 9, the same day as Tastewise and four days after Bria cut a third of its staff. Calcalist's "Full list of Israeli high-tech layoffs in 2026," which most Israel-focused sourcers check, records only the headline number. Neither lists names.
A recruiter who waits for #opentowork badges or a named list reaches these engineers in week six, along with everyone else, and in this market that is late. Israel's Innovation Authority found companies hired about 8% of headcount and laid off 2.8% in H1 2026. More than a third expect hiring to fall in H2, with the planned hiring rate down from 7.2% to 5.9%. Even so, the Central Bureau of Statistics counted about 18,000 tech vacancies against about 15,000 job seekers. There are still more open roles than candidates.
Which teams were hit: core platform or Axonius Healthcare?
The public reports don't say which teams were cut, so you have to work it out from skills. Axonius runs two products that need different engineers, and your pitch depends on which one a person built.
Cynerio was Axonius's first acquisition, in July 2025, reported at $100M - $180M. Cynerio co-founder Leon Lerman became an SVP, and co-founder Daniel Brodie joined the Office of the CTO. The product now ships as Axonius for Healthcare.
| Signal | Axonius core (asset inventory) | Axonius for Healthcare (ex-Cynerio) |
|---|---|---|
| Core problem | Integrating with 300+ security and management tools | Finding medical devices on the network |
| Telltale skills | Integrations, asset inventory | Passive discovery, deep device fingerprinting |
| Domain terms | Asset inventory, exposure management | IoMT, HL7, DICOM |
| Integrations named | Security and management tooling | CMMS: Medimizer, e-Quip, Medusa |
The difference changes the job you can offer. A core-platform engineer has spent their time making more than 300 third-party tools feed one asset inventory. Tenable Israel, the main exposure-management employer in the index's security-tagged results, is the obvious next home for that profile. A healthcare engineer has worked on passive discovery, device fingerprinting and CMMS integrations, which is a narrower fit for IoMT security roles.
Refolk's index shows how these people describe themselves. Of the 162 profiles in Israel that mention Axonius in their headline, the most common title is Full Stack Engineer. Other titles include "Team Lead (SBI & Platform Teams)," "R&D Software Architect," "Engineering Team Leader," and "CTO of Axonius Healthcare." A title rarely tells you which product someone worked on, so read past it to the skills.
Why does searching "Cynerio" find almost nobody from Cynerio?
Searching for the acquired company's name mostly finds a different company, and the real Cynerio people no longer use the name. To separate the healthcare group, search by healthcare skill signals instead.
Refolk's index has 56 headline matches for "Cynerio" in Israel. In the top-25 sample, 19 work at Synerion Systems, and none showed Axonius as their current employer. Former Cynerio staff now describe themselves as "Axonius Healthcare," so keyword search matches the wrong company and misses the right one.
Two more traps:
- The Axonius keyword includes alumni. Of the top 25 of the 162 "Axonius" headline matches, only 17 are currently at the company. The rest have moved to Wix, DriveNets, Varonis, Thales and others.
- Industry filters miss nearly everyone. A search for software-engineer titles in Israel within the "Computer & Network Security" industry returned only 6 profiles, all at Tenable. Many security companies' engineers aren't tagged with that industry, so filtering by it removes most of the market.
What works is searching for the current employer plus product vocabulary (IoMT, passive discovery, device fingerprinting, CMMS, HL7/DICOM), then checking each person against the skills table above. By hand, that is a lot of cross-checking. In Refolk you describe the person in plain English instead:
Why pitch before the "replaced by AI" story sets?
Contact these engineers during the hearing window. Once "laid off because AI made them redundant" sticks to the group, hiring managers will mark them down.
Axonius framed this round around AI-driven development, but Calcalist's own analysis says AI "is not yet the dominant direct cause of layoffs." That gap matters for candidates. A hiring manager who reads "AI reorg" and then sees an ex-Axonius resume may assume the work was automatable and the engineer wasn't needed. The record doesn't support that. The company has cut three times in a year, including a February round that was mostly senior sales and marketing.
A more accurate description, and a more useful one for hiring managers, is that these are engineers from a company cutting costs ahead of a possible IPO, who survived two earlier rounds. Call during the shimua and that is the story you take to your hiring manager. Wait until week six and the press framing will already be the default.
Call during the hearing and you set the story. Wait six weeks and the headline sets it for you.
How should you time and write the outreach?
Build your list now, send a low-key message during the hearing period, and follow up when decisions land. Never assume or mention that a specific person is affected.
- Days 1 to 3: build and split the list. Find current Axonius engineers in Israel, remove alumni, and sort them into core platform versus healthcare using the skills table. Your list will include many people who weren't summoned, and that's fine.
- Days 3 to 10 (the response period): send a neutral first message. Pitch the role and the team. Don't mention layoffs, hearings, or AI. Most recipients weren't called, and for those who were, the outcome is still open.
- Weeks 2 to 6 (decision and notice): follow up. A second note after the likely decision date catches people as their situation becomes clear. If someone is on paid notice, ask about start dates directly.
- Use alumni carefully. Former Axonius engineers at Wix or Varonis can make warm introductions, but they are also working for likely rival bidders. Don't ask them, or insiders like Leon Lerman and Daniel Brodie, for lists of names. Wait until people self-identify.
A first message that works in this window is short and specific: "I'm hiring a senior engineer for device discovery on hospital networks. Your work on passive fingerprinting at Axonius Healthcare is the closest match I've found in Israel. Open to a 20-minute call?" It names the product and the skill, and it treats them as someone currently employed, which they are.
Step 1 is the slowest part. Working through alumni-heavy keyword matches and Synerion lookalikes, then checking each name against product skills, can use up most of the window before your first message goes out. Speed also matters at the other end. Notice paid in lieu can free an engineer to start almost as soon as the decision lands, so a process that is already running during the hearing closes before a slower competitor has finished sourcing.
FAQ
What is a pre-dismissal hearing in Israel?
A pre-dismissal hearing, or shimua, is a required step before an Israeli employer can dismiss anyone, whatever the reason. The employee usually has 5 to 7 working days to respond to the invitation, and the employer must genuinely consider that response before deciding. Notice of dismissal comes only after the hearing. After one year of service the statutory minimum notice is one month, and it can be worked or paid in lieu.
Is it appropriate to contact an engineer who has been summoned to a hearing?
Yes, as long as you don't refer to the hearing. Pitch the role on its merits and send it to a wider list of current Axonius engineers, not just people you suspect were affected. The outcome can still change, and most current Axonius engineers weren't called, so a message that assumes someone has been fired is both inaccurate and off-putting.
How do I find former Cynerio engineers now inside Axonius?
Don't rely on the name "Cynerio." In Refolk's index, 19 of the top 25 Israeli "Cynerio" matches actually work at Synerion Systems, an unrelated company, and former Cynerio staff now describe themselves as Axonius Healthcare. Search instead for Axonius as the current employer combined with healthcare security skills: IoMT, passive discovery, device fingerprinting, CMMS integrations, and HL7 or DICOM.
The data behind this
Try it on the search you came here for
Stop building boolean strings. Just describe the person.
Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.
01Describe them
One plain sentence. Role, city, stack, stage, whatever matters to you.
02I read the web live
GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.
03You read the shortlist
Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
- No boolean, no filters, no seat to buy. One box.
- Read at search time, so a profile updated yesterday counts today.
- Every step visible as it runs, every name with its reason.
500 free credits on sign-up. No card, no demo call. See real searches.