Qualcomm's 'Performance' Cuts Land in November. Search Hyderabad First
Qualcomm's 2026 layoffs are labeled 'performance' but follow a 20% handset revenue drop. Where its modem engineers sit, and how to source them before November.
On Oct 20, Reuters reported a memo from Cristiano Amon telling Qualcomm staff to expect a global "performance-focused reduction." Notifications start in November, and the memo gives no headcount. If you hire wireless, modem or embedded engineers, the next few weeks are your window. The two easy mistakes are reading "performance" as "the weak ones" and waiting for a public filing that may never appear.
What did Qualcomm announce, and how big is it?
Qualcomm announced global job cuts that follow its annual employee reviews. Notifications begin in November. The company has not said how many jobs, which locations or which divisions. Every number beyond that is rumor.
Here is what the memo does and does not say, per the Reuters report and follow-up coverage:
- Says: cuts are global and follow annual reviews.
- Says: "business priorities, organizational needs, skills and expertise" will be considered.
- Says: "As we have expanded the business, so have the competencies and skills we require."
- Does not say: how many jobs will go, where, or in which divisions.
For scale, Qualcomm had about 52,000 employees as of September last year. Blind's layoff tracker lists this round at 3,500 people, or 7%. A separate India-tagged Blind post claims a 20% performance-based reduction. Those two figures disagree, and Reuters could not confirm the scale, so treat both as noise until Qualcomm reports earnings on Nov 4.
Why is the "performance" label a weak signal?
The label is weak because the memo itself puts business priorities, organizational needs and skills right next to performance. When a business line shrinks, its engineers land on the cut list whatever their individual output.
The business numbers explain the timing. Handset revenue fell 20% to $5.09 billion last quarter. Automotive revenue rose 61% to $1.59 billion over the same period. Meanwhile, Apple is moving its iPhones off Qualcomm modems. The iPhone 16e, 17e and iPhone Air ship with Apple's C1 or C1X modem, and the C2 is expected in the 18 Pro series this year. The patent licensing agreement between Apple and Qualcomm expires in March 2027.
Here is why that matters for anyone screening candidates. Review-driven cuts are usually relative: each organization gets a target, and managers rank people against their own teammates. If a handset modem group is told to shrink, it still has to give up names, even when every engineer on it would rank in the top half somewhere else. The rating shows how much the company values that team's roadmap. It does not show whether the engineer can close an L1 timing bug on new silicon.
Amon's own line about "competencies and skills we require" says this outright. Some of these engineers are leaving because Qualcomm's growth has moved away from handsets, not because they fell short.
A weak rating on a shrinking team tells you about the team's future, not the engineer's.
Where are Qualcomm's modem engineers, by the numbers?
In Refolk's index of professional profiles, India has more self-described modem firmware engineers than the US (94 vs 78). For "Qualcomm 5G modem," Hyderabad beats San Diego 8 to 4 in a 25-profile sample. If your search plan starts and ends in San Diego, you are missing a large share of the people.
| Query (headline keyword) | Market | Total profiles | Top region (sample share) | Top employer (sample share) |
|---|---|---|---|---|
| "modem firmware" | US | 78 | San Diego, 9/25 (36%) | Apple, 9/25 (36%) |
| "modem firmware" | India | 94 | Bengaluru, 13/25 (52%) | Apple, 3/25 (12%) |
| "Qualcomm 5G modem" | US + India | 122 | Hyderabad, 8/25 (32%) | Qualcomm, 7/25 (28%) |
| India vs US, "modem firmware" | n/a | 1.21x | n/a | n/a |
Totals come from the index. Shares come from 25-profile samples, so read them as direction, not precision. Headline matching also undercounts, because plenty of modem engineers never put their specialty in their headline.
That undercount matters more than it seems. In the India "modem firmware" sample, the common titles were "Member of Technical Staff" and "Staff Engineer." In the "Qualcomm 5G modem" sample they were "Senior Software Engineer," "Senior Engineer" and "Principal Engineer." The 78 and 94 are the people who label themselves. The real population sits behind generic titles, and the lazy keyword search never reaches it.
Why won't WARN filings show the full picture?
Federal WARN only applies to layoffs of 50 or more employees at a single site within 30 days, and India has no equivalent public filing. Cuts picked person by person after reviews tend to spread across many sites, so each site can stay under the threshold.
The WARN Act (Worker Adjustment and Retraining Notification Act) is the US law that requires advance notice of large layoffs, and state filings under it are how most recruiters track cuts. Qualcomm's earlier rounds show up there:
- October 2023: about 1,258 cuts across San Diego and Santa Clara.
- September 2024: 226 in San Diego.
- April 2026: 104 in San Diego, out of a round of 128 split across 11 sites, weighted toward senior technical roles.
That April round is the warning sign. A round of 128 spread across 11 sites already ran thin at the site level. A review-based global cut could easily produce small filings in San Diego and nothing at all in many other places.
India is harder still. Blind's Oct 28 roundup described Qualcomm and Arista workers in India getting "quiet warnings and unexplained cuts." A related Blind survey headline reads "44% Say Layoffs Are Decided Abroad as India Is 'Cheaper and Legally Quieter.'" Blind threads, WARNTracker and WhatLayoff will pick up signals, but they lag, and they only show you the people who post.
Going after the people directly beats waiting for a filing. Refolk searches GitHub, LinkedIn and the open web for the engineers themselves, so a cut that never gets filed doesn't leave you blind.
Who else is recruiting these engineers?
Apple, mostly. In Refolk's index, Apple employs 9 of a 25-profile sample of US engineers with "modem firmware" in their headline. That is 2.25x Qualcomm's 4. Intel (3) and MediaTek (2) round out the top employers.
Apple is still building out its C2 and C3 modems, and its San Diego and Cupertino teams are well placed to pick up the strongest people first. Apple even shows up first in the India "modem firmware" sample, with 3 of 25. When notifications go out, Apple's recruiters are likely to be in the inboxes of the best L1 and protocol-stack engineers already. A company that starts outreach after the Blind posts appear is picking from whoever is left.
For a company without Apple's brand or its own modem program, this is a hard role to fill. A few hundred people describe themselves accurately. A big incumbent knows them by name. The window is a few weeks long. A contingency agency charges its fee and still starts from the same thin keyword list, and an in-house sourcer burns days just building the list.
How do you find Qualcomm modem engineers who don't say "modem"?
Search on employer history plus protocol-stack skills, not titles. Most of these engineers call themselves "Senior Engineer" or "Member of Technical Staff," so a title search for "modem firmware engineer" covers only a small part of the market.
Two terms are worth knowing. 3GPP is the standards body that defines LTE and 5G, and engineers who have shipped against specific 3GPP releases list them. L1/PHY is the physical layer, the lowest part of the modem stack, where DSP firmware and signal processing live. Those terms turn up in skills sections even when the headline says nothing.
A search that actually reaches this group:
- Anchor on employer history. Current or past Qualcomm, plus Apple, Intel and MediaTek, the other top employers in the index.
- Add stack terms, not titles. 3GPP, 5G NR, LTE, L1/PHY, protocol stack, DSP firmware.
- Widen the map. Hyderabad and Bengaluru first, then San Diego and Santa Clara.
- Accept generic titles. MTS, Staff Engineer, Senior Engineer, Principal Engineer.
- Filter on nothing related to "performance." You can't see ratings, and they wouldn't tell you much anyway.
Writing that as a Boolean string across LinkedIn and GitHub is slow, and it still breaks on spelling variants and on profiles that only mention the work in a project line. Refolk handles exactly that kind of search: you describe the person in plain English and get a ranked shortlist back from GitHub, LinkedIn and the open web.
Run the same query again with Apple, Intel or MediaTek in place of Qualcomm. Engineers who have moved between those four companies are often the deepest in the market, and they are the ones Apple will call first.
How should you screen them if "performance" isn't a filter?
Screen on technical depth and on which side of Qualcomm's business the person worked in, not on why they left. Where they sat in the business tells you more than the reason for the exit.
Questions that do the work:
- Which product line? Handset modem, automotive or something else. With handset revenue down 20% and automotive up 61%, a cut from a handset modem group says less about the individual than a cut from a growing group. Even in a growing group, the memo's "skills" criterion means the cut may reflect a change in technology.
- Which layer? L1/PHY, L2/L3 protocol stack, or DSP firmware. These are different hires.
- Which 3GPP releases did they ship against, and on which chipsets?
- What did they debug on real silicon? Lab bring-up, field testing and carrier certification all count.
- What do they want next? Many will want to stay in wireless. Some will want to move toward automotive, the segment where Qualcomm's own revenue is growing.
Don't ask about their review rating. You won't get a useful answer, and it pushes the conversation onto Qualcomm's restructuring logic instead of the candidate's work.
What should you do before November notifications land?
Build the list now and reach out before the notifications, framing the message around the work rather than the layoff. People who haven't been notified yet will still reply to a message about a hard modem problem. They won't reply to "sorry to hear about Qualcomm."
A working timeline:
- Now to Nov 4: build the Hyderabad, Bengaluru and San Diego lists and send your first outreach. Lead with the problem your team is solving.
- Nov 4: Qualcomm reports earnings. Listen for which divisions get mentioned and which don't.
- November: notifications begin. Expect Blind posts first, small or missing WARN filings in the US, and silence in India.
- March 2027: the Apple-Qualcomm patent licensing agreement expires, which may put more pressure on the handset side.
FAQ
How many people is Qualcomm laying off in 2026?
Qualcomm has not said. The memo reported by Reuters on Oct 20 names no headcount, no locations and no divisions. Blind's tracker lists 3,500 people (7%), and an India-tagged Blind post claims 20%, but neither is confirmed. For scale, Qualcomm had about 52,000 employees as of September last year.
Are Qualcomm's performance-based layoffs a sign of weak engineers?
Not reliably. Amon's memo lists business priorities, organizational needs and skills alongside performance, and the cuts follow a 20% drop in handset revenue as Apple moves to its own C-series modems. An engineer on a shrinking handset modem team can be cut by a relative ranking even if they are strong. Screen on 3GPP, L1/PHY and DSP depth instead.
Where are laid-off Qualcomm semiconductor engineers located?
San Diego is the best-known hub, and past WARN filings cover San Diego and Santa Clara. But in Refolk's index, India has 1.21x as many "modem firmware" headline profiles as the US. Bengaluru tops the India sample, and Hyderabad outranks San Diego for "Qualcomm 5G modem" profiles 8 to 4.
Will Qualcomm file WARN notices for this round?
Possibly for some US sites, but not necessarily. Federal WARN applies only to 50 or more layoffs at one site within 30 days, and review-based cuts tend to spread across many sites. The April 2026 round of 128 was already split across 11 sites. India has no comparable public filing, so a large share of affected engineers may never show up in any tracker.
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.