HPE Layoffs 2026: What the Juniper Integration Means for Networking Talent

HPE is cutting 2,500 jobs, roughly 5% of its workforce, while absorbing Juniper Networks into a combined networking division that doubles HPE’s networking business but creates significant product overlap with Aruba in switching, wireless, and SD-WAN. The displaced pool is heavy on network engineers, infrastructure architects, and product overlaps between Aruba and Juniper lines that will not both survive the integration.

Last updated: May 10, 2026

Two product lines. Same customer. Same market. That is the entire story of this layoff if you strip away the earnings call language about “strategic alignment” and “cost synergies.” HPE bought Juniper for $14 billion and now has two enterprise networking portfolios competing with each other inside the same org chart. Aruba on one side. Juniper on the other. The engineers who built and supported the losing line are entering a market that needs exactly what they know.

Tom Kenaley, KORE1. I run searches across our IT staffing services practice, and networking infrastructure has been one of the noisier inbound segments since late 2025, when the first integration-related departures started showing up. We earn a placement fee when companies hire through us. The observation below is that the HPE-Juniper overlap is producing a specific, identifiable talent pool that most hiring teams are not screening for because they are still thinking about this as a general tech layoff, which means they are running Cisco-centric keyword searches and ignoring candidates whose resumes say Junos and ArubaOS instead. It is an acquisition integration, and those produce different candidates with different timelines and different motivations than a standard cost-cutting layoff.

What HPE Actually Cut

The 2,500 number came out in March 2025. HPE framed it as a cost-reduction program targeting $350 million in gross savings by fiscal 2027, spread over 18 months. About $70 million of that landed in fiscal 2025. The remaining $280 million is executing across 2026 and 2027. NetworkWorld confirmed the 2,500 figure and connected it to both the Juniper integration timeline and the tariff pressures hitting HPE’s server business.

Then there is the Juniper side. October 31, 2025 was Juniper’s last day as an independent company name on anyone’s badge. The integration-driven reductions that followed did not get a separate press release. They showed up on TheLayoff.com and Blind as rolling cuts across global functions, AMER sales, and engineering teams where Juniper products overlapped directly with Aruba equivalents. No official count. The pattern is familiar to anyone who watched the Broadcom-VMware integration or any other enterprise tech acquisition in the past three years where the acquirer quietly trims headcount in batches small enough to stay under the WARN Act threshold while still eliminating entire product teams over the course of two or three quarters.

HPE’s headcount hit roughly 67,000 at the end of fiscal 2025, a jump from about 61,000 the prior year because of the Juniper acquisition folding in around 10,000 people. Trim 2,500 from 67,000 and you get a 3.7% reduction on the combined entity. The real question is where inside the org those cuts land.

The Juniper Integration Overlap

HPE’s networking division was already its most profitable business before Juniper. Fifteen percent of total revenue. Forty-one percent of total earnings. A 24% operating margin, per HPE’s own filings. That profitability came from Aruba, which owns campus wireless, wired switching, and SD-WAN in the mid-market and enterprise segments.

Juniper brought its own wireless (Mist AI), its own switching (EX Series), its own SD-WAN, and a data center and service provider routing business (MX, QFX, PTX) that Aruba never competed in, which means the combined company now has two complete enterprise networking stacks that share the same total addressable market and compete for the same campus and branch office deals. The routing and service provider piece is additive. No overlap. That side is safe and probably growing.

The campus and enterprise side is where the collision happens.

The DOJ required HPE to divest its Instant On wireless business and license the Mist AI source code to a competitor as conditions for approving the deal. That tells you the government saw the same overlap the engineers inside both companies had been talking about for a year. When the regulator forces a divestiture because it sees anticompetitive overlap in the wireless market, the internal rationalization that follows across the switching, SD-WAN, and management plane teams that share the same structural problem is not going to be gentle, even if those product categories were not the ones specifically cited in the consent decree.

HPE announced dual branding: “HPE Aruba Networking” and “HPE Juniper Networking.” Rami Rahim, Juniper’s former CEO, runs the combined division. Dual branding sounds diplomatic. In practice, it usually means both product lines coexist for 12 to 24 months while the combined company figures out which architecture wins in each segment, then the losing line goes to sustaining-mode support and the engineering team behind it gets absorbed or shown the door.

I have watched that happen at Broadcom-VMware, at Cisco-Meraki in the early years, at HPE-Aruba the first time around when HPE bought Aruba Networks in 2015. The window between “dual brand” and “single roadmap” is where the engineering talent exits. We are inside that window right now.

Which Roles Are Most Exposed

Not all HPE networking roles carry the same risk. The profiles below are ordered by how exposed they are to integration-driven redundancy, based on where we see the overlap landing and what we are hearing from candidates who have already left or been told their role is “under review.”

Campus wireless engineers on the Aruba side. Mist AI won the industry narrative on AI-driven wireless operations. Juniper’s Mist platform has been winning enterprise RFPs against Aruba Central for the past three years. If HPE consolidates to Mist as the go-forward cloud management plane, the Aruba Central engineering and support teams are the ones absorbing the impact, which is a bitter outcome for people who built one of the two or three best enterprise wireless management platforms in the industry over the past decade and now find themselves on the wrong side of an acquisition they had nothing to do with. Some of these engineers have deep 802.11ax/be RF design skills that transfer directly to any enterprise wireless deployment.

SD-WAN engineers are a second bucket. Aruba EdgeConnect came from the Silver Peak acquisition. Juniper’s Session Smart Router is a competing product. There is no scenario where HPE funds two SD-WAN roadmaps indefinitely. One goes to maintenance mode. The people behind it start updating their LinkedIn profiles around the same time.

Pre-sales and solutions architects who sold against the other side. An Aruba SE who spent five years positioning against Juniper EX switches in competitive deals, memorizing the weaknesses in Junos routing policy configuration and the throughput limitations of the EX4400, now works for the same company as the people who built those switches and spent five years positioning against Aruba. Awkward, and usually temporary. The field teams get merged, territories get redrawn, and the SE count contracts because you no longer need two technical sellers covering the same account when one of them knows the product you are keeping and the other knows the product you are sunsetting, and the customer is going to figure that out during the next QBR anyway.

QA and test engineers on overlapping product lines. Not glamorous. Not headline material. But every duplicate switching platform, every duplicate wireless controller, every duplicate SD-WAN appliance had a test team behind it. Those teams are running at 2x the headcount the combined company needs for a single product roadmap, and the math on that is easy enough for anyone in middle management to do on a whiteboard, which means the people on those teams have done the math too and the best ones are already interviewing.

Network operations and TAC support staff are a fifth group. HPE does not need two TAC organizations fielding tickets on two sets of campus switches that serve the same market segment. The consolidation of support orgs is usually the last integration step in these kinds of mergers because you need the legacy TAC running while customers are still on the old platform, but once the migration deadlines start hitting and the ticket volume shifts to the surviving product line, the second TAC team becomes overhead that the finance org will flag on the next quarterly review.

Where HPE Networking Talent Is Landing

The displaced pool carries a specific set of credentials and product experience. Aruba alumni know ArubaOS-CX, ClearPass NAC, Aruba Central cloud management, and the 802.11 RF stack cold. Juniper alumni know Junos, Mist AI, EX/QFX/MX/SRX platforms, and a CLI that has a devoted following among network engineers who consider it superior to Cisco IOS. Both groups are landing, but in different places.

One pattern worth calling out. The tech layoffs of 2026 have hit networking harder than most segments. The Cisco layoffs earlier this year displaced thousands of network engineers from the legacy switching side of that company. Our Cisco layoffs 2026 analysis covers the details. The HPE-Juniper pool hitting the market at the same time means hiring managers who need network infrastructure talent have the deepest bench available in years. Two major vendors shedding experienced engineers simultaneously. That is unusual. It will not last. KORE1’s average time-to-hire for IT roles is 17 days. The best candidates in this pool will not be available for 17 weeks.

The Salary Picture for Displaced HPE Engineers

Compensation varies sharply by role type and whether the engineer is staying in the vendor/OEM world or moving to an enterprise IT team. Our 2026 network engineer salary guide covers the full benchmark table. The HPE-specific picture looks like this.

Salary data aggregated from ZipRecruiter, Glassdoor, and PayScale as of April 2026, cross-referenced with KORE1 placement data. The variance between sources runs 15-20%, which is normal for networking roles because the same “network engineer” title covers everything from a campus Wi-Fi admin running a 200-AP Meraki deployment at a regional hospital to a service provider backbone architect designing MPLS topologies for a Tier 1 carrier, and those two jobs have almost nothing in common except the word “network” in the LinkedIn headline.

The candidates who are taking the steepest pay cuts are the ones who anchored to HPE’s equity component and are now calculating total compensation against a stock price that was already sliding before the fiscal 2026 outlook disappointed the market and sent HPE shares down another 8% in a single session. That RSU drag is real. Candidates who price themselves on base-plus-realistic-equity are closing faster than the ones still calculating total comp off a stock price that no longer exists.

The Tariff Wrinkle

One thing that is not getting enough coverage. HPE flagged approximately $120 million in added operational expenses from U.S. tariffs on imports from Mexico and Canada. HPE manufactures server and networking hardware in both countries. That $120 million comes directly out of the margin on the server business, which was already under pressure from Dell undercutting on PowerEdge AI server pricing and Lenovo gaining share in the enterprise data center segment by bundling aggressive financing terms that HPE’s GreenLake consumption model has not been able to match on a per-unit basis.

Why this matters for the layoffs: the $350 million savings target was set before the tariff impact was fully quantified. If tariffs eat $120 million of margin, the pressure to find the remaining $230 million through headcount becomes more intense, not less. The people hoping the 2,500 figure was a ceiling should be looking at the tariff line instead.

What Hiring Managers Should Do Right Now

Four specific things.

First, if you have an open networking req, widen the keyword filter. An Aruba engineer’s resume says “ArubaOS-CX” and “ClearPass,” not “Cisco IOS” or “Palo Alto.” A Juniper engineer’s resume says “Junos” and “Mist AI,” not “Meraki.” Your ATS keyword filter was probably written around Cisco terminology because that is what most enterprise networks run. That filter is now excluding some of the best-trained networking talent on the market. Fix the filter or tell your recruiter to surface HPE and Juniper alumni manually.

Second, move fast on clearance-eligible Juniper engineers. Juniper MX and SRX hardware sits in classified networks across the Department of Defense. Engineers who supported those deployments and hold active clearances are a tiny pool. Federal integrators know this and are already making offers. If you are in the federal space, this window is measured in weeks.

Third, consider the dual-stack advantage. An engineer who worked at HPE during the Juniper integration and has hands-on experience with both Aruba and Juniper platforms is unusually versatile. They understand two architectures, two management planes, two CLIs, and two approaches to network automation. That breadth is rare, and it costs less than you would expect because these candidates are motivated to move before the next round of integration cuts arrives and before the window of choice narrows into a scramble for whatever is left on the market after the federal integrators and MSPs have picked through the top of the pool.

Fourth, use contract-to-hire if you are uncertain about the long-term headcount. Many displaced HPE engineers are open to contract engagements as a bridge while they figure out whether the next stop is another networking vendor, an enterprise IT team, a cloud provider, or a federal integrator, especially if they suspect the integration-driven layoffs will keep rolling through 2027 as the dual-brand period winds down. A 6-month contract lets you evaluate fit without making a commitment you are not ready for. It also lets the candidate demonstrate the platform retooling that a direct-hire loop might not give them credit for.

So what is HPE’s severance package for 2026 layoffs?

Reports vary, and HPE has not published a standard formula. Employees on Blind and TheLayoff.com have described packages ranging from 60 days of notice with minimal additional severance to several months of salary continuation depending on tenure, role level, and whether you were classified as a “critical transition” resource who needed to stay long enough to hand off institutional knowledge to the surviving team before your own access got revoked. Earlier waves appear to have received better terms than later ones. COBRA continuation has been inconsistent. If you are currently in a notice period at HPE, get the terms in writing and compare against your state’s WARN Act requirements before signing anything.

Are Juniper employees being laid off separately from HPE?

Not separately, no. Juniper Networks ceased to exist as an independent entity on July 2, 2025. All former Juniper employees are HPE employees. The reductions affecting former Juniper roles are part of the same integration-driven restructuring, not a separate action. The distinction matters for severance calculations and benefits continuity, so if you were a Juniper employee, verify how your tenure is being counted in the combined entity.

Which HPE divisions are safest from cuts?

The service provider routing business. Juniper’s MX and PTX platforms have no Aruba equivalent, so there is no overlap to rationalize. HPE GreenLake (the as-a-service consumption platform) is the company’s strategic bet and is actively hiring. The AI networking fabric team building for GPU cluster interconnects is growing. And the SRX firewall and security services team is complementary to Aruba’s ClearPass NAC, so the security side looks additive rather than redundant. Campus wireless, campus switching, and SD-WAN are the risk zones. Everything else depends on how aggressively HPE pursues the $350 million target.

Does Junos experience transfer to other vendor platforms?

48 hours of lab time and it transfers to Cisco IOS-XR, which borrowed heavily from Junos architecture. Arista EOS is even closer in philosophy. The fundamentals of OSPF, BGP, MPLS, VXLAN, and EVPN do not change between vendors. What changes is the CLI syntax, the automation framework (Juniper’s PyEZ versus Cisco’s pyATS versus Arista’s eAPI), and the management plane. An experienced Junos engineer can be productive on a Cisco or Arista network within a week. The deeper retooling is on the automation and orchestration side, not the protocol side.

Realistically, how long does it take displaced HPE network engineers to find new roles?

Three to six weeks for senior engineers with JNCIP/JNCIE or CCIE-level credentials, active clearances, or data center fabric experience. Six to ten weeks for mid-level engineers without certifications or with primarily campus wireless backgrounds. The federal integrator pipeline is fastest. Cloud networking transitions take longest because the retooling runway is real. KORE1 has placed IT professionals at an average of 17 days across all roles, but networking tends to run slightly longer because hiring managers want to see lab competency on their specific platform during the interview loop, and a network engineer who has spent ten years in Junos needs at least a weekend with a home lab to demonstrate fluency on Cisco IOS-XE or Arista EOS to an interviewer who is looking for muscle memory, not just theoretical understanding.

If you are a hiring manager with an open networking, infrastructure, or SD-WAN position and want access to the HPE-Juniper displaced talent pool, reach out to our team. We are actively sourcing from this pool across 30+ U.S. metros. If you are a displaced HPE or Juniper engineer, same link. KORE1’s 92% twelve-month retention rate means we are placing people into roles that stick, not just filling reqs.