Amdocs' 4th Cut in 4 Years: The BSS Talent Is in Ra'anana, Not LinkedIn
Amdocs is cutting up to 3,000 jobs on May 28, 2026. Here is how to source the BSS, OSS, and 5G charging engineers LinkedIn under-indexes.
On May 28, 2026, Globes and Ynet reported that Amdocs is preparing to dismiss between 2,700 and 3,000 employees, roughly 7 to 10 percent of its 29,000-person workforce, including hundreds in Israel. New CEO Shimie Hortig, in seat since the end of March, is framing the cut as a reorganization "for the AI era" and centralizing AI into a new GenAI and data division. If you run sourcing at Netcracker, CSG, Oracle Communications, Optiva, Matrixx, or any AI-for-telco startup, this is the most concentrated pool of convergent billing, 5G charging, and order orchestration talent that will hit the market in 2026. The catch: most of them are not findable by title.
What actually happened on May 28
Amdocs has not officially confirmed the figure. CTech and Ynet reported the 2,700 to 3,000 range, and the company said the processes are "still under review." The framing, per Globes, is "a broad move designed to make Amdocs a flexible, efficient and less hierarchical company, while adapting work processes to the AI era." Crunchbase added the company to its layoff tracker on June 10 as the largest entry of the week.
This is the fourth consecutive year of cuts. In 2023, Amdocs cut roughly 2,700 jobs in two waves (700 then 2,000, with about 300 of those in Israel). In 2024, more than 1,500 followed. In 2025, several hundred more. If 2026 hits the high end of guidance, the cumulative toll since 2023 reaches roughly 7,200 positions.
The financial backdrop matters for how you pitch these candidates. Amdocs reported Q2 fiscal 2026 revenue of $1.17 billion, up 3.9 percent year-over-year, with full-year guidance trimmed. This is not a death spiral. It is a deliberate margin and narrative reset under a new CEO, which is a harder story to sell to a skeptical senior engineer than "the ship is sinking." More on that below.
Why "Amdocs engineer" is not a searchable title
If you run a Boolean string on LinkedIn for ("BSS Engineer" OR "Billing Engineer") AND Amdocs AND Israel, you will get something close to zero useful hits. We checked. The literal title strings barely exist inside Israel, and globally only a handful of profiles even self-identify with an "Amdocs" skill tag despite the 29,000 headcount.
The reason is structural. Amdocs engineers carry generic titles ("Software Engineer," "Solution Architect," "Technical Lead," "Delivery Manager") with the actual specialization buried in project history. The signal is in the product names, not the job title:
- CES / CES26: the flagship customer experience suite. CES26 launched March 2, 2026 as an agent-driven BSS-OSS-Network suite powered by the aOS Cognitive Core.
- amAIz / aOS: the agentic AI platform for telco operations.
- Openet: acquired in 2020. Alumni are your 5G charging and policy control specialists.
- MYCOM OSI: acquired in 2022. Alumni are your network assurance people.
- Vindicia: subscription billing.
- Brite:Bill: bill presentment.
- Ensemble: catalog-driven order management.
If you are not searching by these strings, by TM Forum certifications (Open APIs, ODA), and by named carrier program tags (etisalat by e&, AT&T, Telefónica Germany, Telia Finland, Globe, Optimum), you are not sourcing this population. You are sourcing the ten percent of it that happens to be public-facing.
This is the exact friction that drove us to build Refolk: you describe the engineer in plain English ("ex-Amdocs convergent charging engineer who shipped on the Telefónica Germany rollout, based in Israel"), and Refolk pulls the ranked shortlist across GitHub, LinkedIn, and the open web without forcing you to guess the right Boolean. Title-based sourcing is broken for telecom billing engineer sourcing. Description-based sourcing is not.
The Israeli cohort LinkedIn under-indexes
About 5,000 of Amdocs' 29,000 employees sit at the Ra'anana campus and the regional Israeli hubs (Sderot, Pa'amei Tashaz, and others). "Hundreds" of those are reportedly in scope for this round.
This subset is the hardest to reach on standard platforms for three reasons. First, many are reservists with intentionally minimal English-language LinkedIn presence. Second, the regional hubs were built specifically to employ engineers in the periphery who often optimize for stability over visibility. Third, the meaningful career artifacts (Hebrew-language CVs on niche job boards, GitHub commits to internal-mirror repos, Stack Overflow answers tagged with Diameter, 3GPP, or TMF specs) live outside the platforms most recruiters default to.
The best Amdocs engineers were already half out the door before May 28. The pink slip is a lagging indicator.
If you want the Israel tech talent sourcing edge here, you need GitHub signal weighted as heavily as LinkedIn signal, Hebrew-name normalization, and the ability to triangulate "worked on the Pelephone billing migration in 2019" without that string ever appearing on a profile.
The contrarian read: the best ones already left
Three consecutive layoff rounds before this one have already done their work on voluntary attrition. Senior engineers with deep BSS and OSS domain expertise and any outside options have been quietly leaving since 2024. The May 28 announcement is a forcing function for the people who stayed through the first three rounds, not a fresh signal that "the talent is now available."
What this means tactically: if you are only starting your Amdocs alumni hiring motion now, you are two years late on the top decile. The 2023, 2024, and 2025 alumni are already at Netcracker, CSG, Totogi, and the systems integrator BSS/OSS practices at Accenture, Wipro, Infosys, TCS, and Tech Mahindra. Some are at Nexus, where Orange deployed their first agent in four hours generating $6M+ in yearly revenue, which is the kind of pitch that lands hard with a bitter ex-Amdocs charging engineer.
The right move is to source the 2023 to 2025 alumni in parallel with the May 28 cohort, then introduce them to each other. Amdocs people hire Amdocs people. The internal referral graph from those earlier rounds is your real distribution mechanism.
Who is hiring into the gap
Five competitor categories will be moving on this cohort, and they will move at different speeds.
Direct vendor competitors
Netcracker, CSG International, Oracle Communications, Optiva, Matrixx Software, Comarch, and Nokia (CloudBand and Digital Operations) all compete head-to-head on the same RFPs Amdocs is currently mid-implementation on. They have the easiest pitch: "same work, less restructuring risk." Expect them to move within 30 days.
AI-for-telco startups
Totogi (cloud BSS), TupleStream, Aarki, and agentic-telco entrants like Nexus are the natural home for the engineers who actually believe the AI narrative and resent being on the wrong side of it. Pitch: "you build the agentic charging engine, not the demo."
Carrier in-house teams
Telefónica Germany, AT&T, Telia Finland, Globe, and Optimum are all mid-implementation on Amdocs platforms. Their internal teams need the exact same skills and can offer better stability than any vendor. This is the channel most recruiters underestimate, and it will tighten the supply faster than expected.
Systems integrators
Accenture, Wipro, Infosys, TCS, and Tech Mahindra all have BSS/OSS practices that can pitch AI-augmented migration to carriers nervous about Amdocs execution capacity during restructuring. Their pitch to candidates is travel and variety. Their pitch to clients is hedge.
Adjacent verticals
Vindicia alumni and Brite:Bill alumni map cleanly to subscription billing companies well outside telco (Recurly, Zuora, Stripe Billing). If you are recruiting for any of those, this is a free expansion of your top-of-funnel.
What to send, and when
Stated CEO rationale from Hortig is making Amdocs "a flexible, efficient and less hierarchical company, while adapting work processes to the AI era." The function-level breakdown of the 3,000 has not been disclosed. We do not know whether the cut is engineering-heavy or back-office-heavy. We do not know whether the figure is net or gross, because Amdocs is reportedly hiring AI and ML roles simultaneously into the new GenAI and data division.
What we do know is that the people most worth reaching, the convergent billing, 5G charging, and order orchestration specialists, are at maximum receptivity to two specific framings right now:
- "You are not a legacy engineer." The AI-era framing has implicitly labeled the BSS/OSS core as non-AI. That is wrong on the technical merits (CES26 itself is agent-driven), and the engineers know it. A first message that acknowledges this lands harder than any generic "exciting opportunity" pitch.
- "You will ship, not migrate." Three years of restructuring fatigue is real. Candidates want to write code that goes to production, not slide decks for a reorg.
Refolk users running BSS OSS engineer recruiting motions typically build the shortlist from product-name and program-name queries (CES, amAIz, Openet, MYCOM OSI, etisalat by e&, Telia Finland) rather than titles, then layer the AI-narrative messaging on top. The shortlist is the unlock. The message is the conversion.
The 60-day window
Anthony Goonetilleke, Group President of Technology and Head of Strategy, is the executive face of the CES26 and aOS agentic strategy that determines which teams Amdocs internally codes as "core" versus "exposed." Watch his org for retention bonuses and re-leveling announcements. Those are the leading indicator of which specific product lines are losing people first.
For practical purposes, your window is roughly the next 60 days. The 2023 alumni teach us that the top decile is gone within 45 days of any public announcement, the middle decile within 90, and the bottom decile within six months. If you want the top of that distribution, you need a shortlist this week.
FAQ
How many Amdocs engineers are actually being cut on May 28, 2026?
The reported figure is 2,700 to 3,000 total positions, roughly 7 to 10 percent of a 29,000-person workforce, with hundreds in Israel. Amdocs has not officially confirmed the number, and the function-level breakdown (engineering vs. implementation services vs. back-office vs. support) is not disclosed. Treat 3,000 as a ceiling estimate, not a hard count of engineers.
Why is title-based LinkedIn sourcing so weak for Amdocs alumni?
Amdocs engineers carry generic titles like "Software Engineer" or "Solution Architect," with the actual BSS/OSS specialization buried in project history. The literal title "BSS Engineer" barely exists inside Israel, and only a tiny fraction of the 29,000-person base self-identifies with the "Amdocs" skill tag. Sourcing has to be driven by product names (CES, amAIz, Openet, MYCOM OSI, Vindicia), TM Forum certifications, and carrier-program tags.
Who are the most active competitors hiring into this gap?
Direct vendor competitors (Netcracker, CSG, Oracle Communications, Optiva, Matrixx, Comarch, Nokia) move fastest. AI-for-telco startups (Totogi, Nexus, TupleStream) compete on mission and equity. Carrier in-house teams at Telefónica Germany, AT&T, Telia Finland, and Optimum may quietly absorb the largest share because they already use the platforms. Systems integrators (Accenture, Wipro, Infosys, TCS, Tech Mahindra) take the implementation-heavy profiles.
Is the Israeli cohort really harder to reach than other Amdocs geographies?
Yes, materially. The Ra'anana campus and regional Israeli hubs employ roughly 5,000 engineers, many of them reservists with limited English-language LinkedIn presence. Hebrew-language sourcing, GitHub activity, and Stack Overflow signal (Diameter, 3GPP, TMF specs) carry more weight than profile titles. This is the segment where description-based search across multiple sources outperforms platform-native Boolean by the widest margin.