Sunrise's 450 Cuts: Why 9 Glattbrugg Engineers Should Target UBS, Not Salt

On September 21, 2026, Sunrise told staff it is evaluating up to 450 cuts from a 2,900-person workforce, and it did something unusual: it spared the shops. Retail, sales, customer service, and apprentices are largely excluded, which means the 16% headline lands almost entirely on network, IT, and corporate roles in Glattbrugg. If you are one of those engineers, the pivot you need is not to Salt. It is into Zurich enterprise IT, and the window is the Q4 2026 syndicom consultation.

What Sunrise actually announced on September 21

Sunrise could eliminate up to 450 full-time jobs from a 2,900-person workforce, with the impact concentrated on non-retail roles and a syndicom consultation scheduled for Q4 2026. Combined with 147 cuts finalized in the summer, the total reaches roughly 600 by early 2027.

The details that matter for your CV:

• 450 potential cuts from 2,900 FTE, announced by the Glattbrugg, Zurich-based operator.
• 147 already gone from a round announced at the start of 2026 and completed over the summer.
• Retail, sales, customer service excluded; apprentices excluded entirely.
• Q4 2026 consultation with employee representatives and syndicom.
• Sunrise has not been profitable since 2022 and has posted net losses every year since, so a third restructuring is not off the table.

CFO Jany Fruytier told AWP the earlier 147 cuts would reduce personnel costs by about 5%. Run the same math on 450 and you get roughly 15% of payroll, which only works if the cuts land on senior expert engineers and corporate staff, not junior support. Syndicom spokesperson Dominik Fitze told AWP that announcing massive job cuts for the second time within a few months puts the entire workforce in a permanent state of emergency.

The 16% headline hides a 25 to 30% cut rate on network and IT

Because retail, sales, service, and apprentices are protected, 450 cuts do not fall on 2,900 people. They fall on a base closer to 1,600 to 1,800, which pushes the effective cut rate on network, IT, and corporate roles into the 25 to 30% range. If your CV is built for the "top 15%" story, it is calibrated to the wrong probability.

The second twist is tenure. Fruytier's payroll math implies the cuts have to hit senior salaries to hit the 15% savings target. In practice, that means expert network engineers, architects, and program leads carry more risk than the mid-level operations staff they manage. If you have ten years at Sunrise or a predecessor, do not read tenure as protection. Read it as a target on your compensation line.

Why "just move to Salt" is a trap

Salt is not the exit. The August 24, 2026 memorandum of understanding between Salt and Sunrise on multi-operator core network sharing (MOCN) exists precisely so both operators can stop running two separate RAN teams in the roughly 70% of Swiss mobile sites classified as medium-density or rural.

Read the deal on its own terms:

• MOCN plus RAN sharing covers the majority of both operators' geographic footprint.
• Salt Capex 2025: CHF 239.2 million. Sunrise Capex 2025: CHF 478.7 million. The combined pool of roughly CHF 718 million is the budget MOCN sharing is designed to shrink.
• Salt CEO Max Nunziata and Sunrise CEO André Krause both signed. The public framing is efficiency.

In Refolk's index of professional profiles in Switzerland, Salt does not appear in the top 10 telco employers of network and IT engineers. Sunrise employs 9 of the 51 Switzerland-based network or IT engineers currently working in telecommunications; Salt shows zero in the top 10. That is a company that already runs lean, about to remove more shared infrastructure work from its plate. Sending a RAN-heavy CV there is fishing in a pond someone just drained.

Where Switzerland's network engineers actually work

The largest employer of Switzerland-based network and IT engineers in Refolk's index is UBS, not a telco. Banks and pharma, based in Zurich, hold more of the enterprise-network talent pool than the entire mobile industry combined.

Here is the shape of the market you are pivoting into:

Two things fall out of that table. First, telecom is 11% of the network-engineer inventory in Switzerland; the other 89% is where the volume actually is. Second, Zurich is not a diversification story. It is the story. Nine of the top ten regional concentrations are in the Zurich metro, which is exactly where a Glattbrugg engineer already lives.

The CV rewrite: from RAN operator to Zurich enterprise engineer

Rewrite the top third of your CV so a UBS, AXA, or Cornèr Banca screener does not have to translate telecom jargon into banking risk language. Bank IT hiring managers screen for change management, audit trails, and regulator-adjacent vocabulary because their own promotions depend on passing FINMA inspections, not on how well you know a Nokia baseband.

Concretely, do this:

1. Replace vendor names with control language. "Ericsson RAN, Nokia core, Cisco transport" becomes "multi-vendor network operations under formal change management, 24/7 SLA, RCA within 4 hours."
2. Foreground ITIL and change advisory board experience. Every incident you owned that went through a CAB is a bullet. Banks care about the process, not the packet capture.
3. Translate MOCN and RAN sharing into "multi-tenant infrastructure." That phrase reads correctly to cloud and enterprise reviewers who will never learn what a gNodeB is.
4. Name the compliance frame you worked under. FINMA circulars if you touched them, ISO 27001 if your team was audited. Do not invent, but do not hide.
5. Move Sunrise-specific projects into "regulated telecom operator" framing. A hiring manager at Incyte or Nestlé is not benchmarking you against a Salt engineer. They are wondering whether you can run a change window without breaking their production.

This is the exact rewrite Refolk does end to end: paste the UBS or AXA posting, and Refolk rebuilds your CV from your own history in the vocabulary that posting is actually screening for, then drafts the cover letter and scores how well you fit before you send anything. If you are applying to 15 Zurich enterprise roles across banking, pharma, and hyperscalers, that is 15 different rewrites, not one master CV.

Timing: apply during consultation, not after notices land

Apply now, during the Q4 2026 syndicom consultation, before formal notices trigger a wave of near-identical Sunrise CVs onto LinkedIn. Candidates who move during consultation are still employed, unhurried on severance timing, and sitting in a smaller applicant pool.

The mechanics of the timing arbitrage:

• Now through Q4 2026: consultation runs; the 9 Sunrise network or IT engineers in Refolk's index (and a wider pool of adjacent corporate staff) know they are exposed but have not been served notice. Most are frozen.
• Notice window (early 2027): the pool moves. LinkedIn "Open to Work" banners appear. Banking recruiters start filtering by "ex-Sunrise" as a shortcut, and your CV looks like every other one.
• Post-notice (Q2 2027): severance timing forces speed over fit. This is where auto-apply tools tank ratios and interviews dry up.

Apply in the first window and you are the person quietly evaluating options, not the person job-hunting under a clock. Recruiters read the difference in the first line of your outreach.

Adjacent landing zones outside banking

Beyond the big banks, three tiers of employers historically absorb displaced Swiss telecom network staff, and each wants a slightly different CV.

• Cablex, Quickline, UPC Schweiz. Telecom-adjacent infrastructure. Refolk's index shows Quickline (4), cablex (2), UPC Schweiz (2), Cablegroup (2) in the top 10 telco employers of Swiss network engineers. Keep your RAN and transport language here; they read it natively.
• Hyperscaler and platform: Google Zurich, HPE, Kyndryl, Wipro. Cloud networking, SRE-adjacent roles. Rewrite in SRE vocabulary (SLOs, error budgets, on-call rotations). Google Zurich appears in Refolk's index with 2 network engineers, so volume is real but small.
• Pharma and industrial IT: Incyte, Nestlé. Regulated environments, closer to banking than to telco in how they screen. ITIL and audit language travel best here.

The referral surfaces recruiters actually watch

Two or three of the following Swiss communities move the needle for a network engineer job search more than another cold LinkedIn apply:

• syndicom. The union is running your consultation; its network extends into other Swiss employers that hire out of Sunrise.
• swissICT. Zurich-heavy professional association, useful for warm intros into UBS and the mid-tier integrators.
• SwiNOG (Swiss Network Operators Group). Where the actual network engineers show up. Sponsors include the employers you want.
• DINAcon. Broader Swiss digital community, weaker on pure networking but strong on public-sector IT and cantonal employers.

None of these will get you hired on their own, but presence on two of them plus a CV rewritten for the specific posting is a substantially different signal than a cold apply.

FAQ

Should I wait until Sunrise formally announces my role is affected before updating my CV?

No. The Q4 2026 syndicom consultation is the exact window when the applicant pool is smallest and you are still employed, which is the strongest position to negotiate from. Once notices are issued in early 2027, a wave of near-identical Sunrise CVs will hit LinkedIn and recruiters will start filtering aggressively. Rewriting during consultation costs you nothing if you stay; it saves you months if you do not.

Is Salt actually hiring Sunrise engineers after the MOCN deal?

Very selectively, and not in the volume the "just move to Salt" narrative implies. The August 24, 2026 MOU is explicitly about consolidating RAN work across roughly 70% of Swiss mobile sites, which reduces net demand for RAN and transport engineers on both sides. Salt does not appear in the top 10 Swiss telco employers of network engineers in Refolk's index, suggesting it already runs lean. Treat Salt as one target among ten, not the plan.

How different does my CV need to be for UBS versus Google Zurich versus Nestlé?

Very different at the top, similar underneath. UBS wants change management, audit trails, and ITIL vocabulary; Google Zurich wants SRE language (SLOs, error budgets, on-call, automation); Nestlé sits between the two with a regulated-environment tilt. The underlying project history is the same, but the top third of the CV and the cover letter should be rewritten per posting.

What if I want to stay in telecom despite the market?

Target the telecom-adjacent infrastructure tier rather than the mobile operators. Quickline, cablex, UPC Schweiz, and Cablegroup collectively hold a meaningful share of Swiss telco network engineers in Refolk's index and are less exposed to the MOCN consolidation than Salt or Sunrise. Your RAN and transport vocabulary reads natively there, which shortens the rewrite and preserves the depth of your experience.