Qualcomm's 'Performance' Cuts Track a 20% Handset Drop. Don't Filter Them

Qualcomm says its November cuts are about performance. Plenty of recruiters will take that at face value and quietly drop "ex-Qualcomm, laid off late 2026" to the bottom of the pile. That would be a mistake. The same quarter that set up these cuts saw handset revenue fall 20% while automotive grew 61%, so the label tells you more about which org someone sat in than about how good they are.

What did Qualcomm actually announce?

On October 20, 2026, Reuters reported an internal memo from CEO Cristiano Amon announcing a global "performance-focused reduction" that follows annual reviews, with notifications starting in November. The memo gave no headcount and did not say which departments would be affected.

Here is what the public record does tell you:

• Scale of the company: Qualcomm had about 52,000 employees at the end of FY2025.
• Stated criteria: Amon said business priorities, organizational needs, skills and expertise would all be weighed.
• The tell in the wording: "As we have expanded the business, so have the competencies and skills we require."

Read that sentence about competencies again. A company firing low performers doesn't talk about its skills mix. A company reshaping itself does. This round is a portfolio decision that happens to arrive through the review cycle.

Why does a "performance" label follow the business unit?

When a unit misses its targets, its people get rated against those missed targets, so low ratings pile up inside shrinking units whatever each engineer actually did. A performance-based layoff is a cut where review scores decide who goes. When scores are calibrated against unit goals, they mostly show how the unit did.

Look at Qualcomm's Q3 FY26 numbers:

Add the Apple problem. Amon said Qualcomm's share of upcoming iPhone modems would be well below its earlier 20% estimate, with Apple's own C-series modems (C1, C1X, C2) taking over faster than planned.

20%

Here is how it plays out. In calibration, managers defend their teams against each other. A manager in automotive is defending a team that grew revenue 61%. A manager in handset modems is defending a team whose Apple business is shrinking faster than planned. Two engineers of equal skill come out of that room with different scores. Amon's own criteria, "business priorities" and "organizational needs," are team-level factors by definition.

So treat the label as a marker of which org someone was in, not as a verdict on the person.

Which teams and silicon skills will be in the pool?

Expect the pool to lean heavily toward handset, modem and wireless systems engineering, plus IT and cybersecurity, with fewer people from automotive and data center. That's an educated guess from where the revenue moved and from the last round.

The April 2026 round gives the best guide. The San Diego Union-Tribune's breakdown put about 80% of those cuts in IT, engineering and cybersecurity. Combine that with the revenue picture and the likely skills are:

• Cellular modem and baseband: physical layer, protocol stack, modem firmware
• Wireless systems: RF integration, connectivity, 3GPP standards work
• Handset SoC integration: Snapdragon platform bring-up and validation
• Internal IT and security: the non-silicon share the April round hit hard

Where Qualcomm is still spending tells you who is less likely to go. The AI200 and AI250 inference accelerators, the Alphawave and Modular acquisitions, and the BMW and Stellantis automotive programs are the growth side. Some handset engineers with transferable skills may be moved into those teams rather than cut. Those who aren't moved are the people to call.

Why do title searches miss most Qualcomm engineers?

Qualcomm staff rarely put their domain in their job title, so a search for "modem engineer" mostly turns up Apple and Google people. In Refolk's index of professional profiles, Qualcomm, the largest merchant modem vendor, makes up only 4 to 8% of modem- and wireless-titled profiles.

The numbers:

These shares come from 25-profile samples, so treat them as directional. The pattern is still hard to ignore. San Diego is the top US region (6 profiles, plus 2 more elsewhere in San Diego County). The talent is there, but the titles hide it.

My working theory is that Qualcomm uses ladder titles like "Senior Staff Engineer" or "Principal Engineer" with no domain attached. Apple engineers are more likely to write "Cellular Modem Systems Engineer." If you search on title, you'll find the people who are already employed and hard to move, and you'll miss the people who are about to become available.

The fix is to search on skills, tenure and location together: years at Qualcomm, San Diego or Bengaluru, and modem, LTE, 5G NR or 3GPP showing up anywhere in the profile, repos or publications. Writing that as a Boolean string across LinkedIn and GitHub is slow. Refolk handles it directly: you describe the engineer in plain English, and it searches skills, tenure and the open web, not just the title field.

How do you map the pool before WARN filings land?

Build the list in November from org structure and skills, then use WARN filings to confirm it. Don't wait for the filings to start. The April round had 54 days between notice and effective date, so the filings come too late to give you first contact.

They also undercount. Qualcomm took $97 million in severance-related charges in the first nine months of fiscal 2026. Over the same period, its April California WARN notices covered about 105 workers. Severance charges rose from $29 million in the March quarter to $68 million in the June quarter. That much money spread over a hundred California employees doesn't add up, so most of the cost is landing elsewhere, probably including outside California.

$97M

A practical mapping sequence:

1. Start with skills, not titles. Pull current Qualcomm engineers with modem, baseband, RF or 3GPP signals and long tenure, focused on San Diego.
2. Add Bengaluru and Hyderabad. Bengaluru (4) edges out San Diego (3) in Refolk's global modem sample. India returned zero under strict US-style filters, which looks like a skill-tagging gap, not an absence of people. None of these engineers will show up in California filings.
3. Tag by likely org. Handset, modem and connectivity go to the top. Automotive and data center go lower, because those teams are more likely to absorb people than cut them.
4. Watch addresses, not headlines. The April filings were unusually fragmented: twenty notices ranging from one worker to nineteen, at roughly nineteen separate addresses. The Union-Tribune counted 104 jobs across 11 San Diego facilities. A building address can tell you which team was hit.
5. Track the official sources. Check the California EDD WARN report weekly, and the San Diego County Workforce Partnership for local notices.

Step 1 is where most sourcing time goes, because you are looking for people whose profiles don't say what they do.

Who else is competing for these engineers?

Apple and Google are the main buyers, and Apple is hiring for this work right now. Between them they employ 68% of the US modem and wireless profiles in Refolk's US sample, and Apple has posted for a cellular modem systems engineer focused on 6G.

Apple is building its own C-series modems to replace Qualcomm's, so engineers who spent years on Qualcomm modem stacks are exactly who it wants. Neither Apple nor Google has any reason to discount the "performance" label. If you hesitate over it while they don't, they'll get the best of the pool.

For anyone trying to recruit semiconductor engineers outside the big platform companies, that's a hard position. You're competing with Apple's brand for a small group: only 26 US profiles in the index clear both the title and skill filters. And the window is short, because strong engineers from this cut won't stay on the market long.

Speed matters more than polish here. Reach out in November with a specific technical reason for contacting this person. A generic "saw you might be exploring" message lands in the same inbox as Apple's recruiters and loses.

How do you screen and approach engineers from a shrinking unit?

Judge the work and ask about the team, never about the rating. Silicon engineering leaves evidence you can check, so strong engineers caught in a weak unit are easier to identify than in most fields.

Signals worth checking:

• Tapeouts: how many chips they took to tapeout, and what they owned on each
• Shipped Snapdragon generations: which products their work went into
• 3GPP contributions: standards work is public and attributed
• Scope over time: whether they took on more ownership across generations even as the handset business shrank
• Internal mobility attempts: if they tried to move to automotive or data center and couldn't, that says more about the org than the engineer

Read the org context both ways. An engineer from automotive or the AI200 program who was cut while those units grew deserves a closer look, because the "team, not person" explanation is weaker there.

In outreach, don't mention the layoff at all. Lead with their work: "I saw your name on 5G NR contributions and you've shipped modem work across several Snapdragon generations. I'm hiring for a wireless systems lead." They know why you're writing.

The rating tells you where someone sat in the org chart. Their tapeouts tell you how good they are.

In the interview, these questions work:

• "Which org were you in, and how did its revenue line do this year?"
• "What did your team ship in the last two cycles, and what did you own?"
• "How did priorities change once the Apple modem outlook shifted?"

These avoid making the candidate defend a number that a calibration room set based on handset revenue. Most will bring up the context themselves, and how clearly they explain it tells you about their judgment.

The question to avoid is "Why were you rated low?" Strong candidates will hear it as an insult and accept another offer. And from Apple's 6G modem posting, there will be other offers.

FAQ

Are Qualcomm's November 2026 layoffs really about individual performance?

Partly, but mostly not. Amon's memo lists business priorities, organizational needs and skills as criteria, and it came after a quarter where handset revenue fell 20% and automotive rose 61%. When ratings are calibrated against unit goals, low scores cluster in shrinking units, so the label largely reflects which team someone was on.

Where will laid-off Qualcomm engineers be located?

San Diego is the center, and it's the top US region for modem and wireless profiles in Refolk's index. But $97 million in nine-month severance set against about 105 California WARN workers suggests much of the pool is elsewhere. Bengaluru leads Refolk's global modem sample, so include Bengaluru and Hyderabad in your search.

When should I start sourcing from the Qualcomm layoffs?

In November, as notifications begin. The April 2026 round had 54 days between WARN notice and effective date, and Apple and Google, which hold 68% of US modem and wireless profiles in Refolk's sample, are hiring now. If you wait for the San Diego WARN filings, you'll be calling people who already have offers.

Why can't I find Qualcomm modem engineers with a title search?

Qualcomm makes up only 4 to 8% of modem- and wireless-titled profiles in Refolk's index, even though it's the largest merchant modem vendor. Its engineers tend to list ladder titles like "Senior Staff Engineer" without a domain. Search on skills, tenure and location instead, and confirm with public work like 3GPP contributions.