# Qualcomm's India Cuts Hit Wi-Fi Teams. 1 in 25 Profiles Says Wireless

_Qualcomm calls its India layoffs performance-focused, but they hit Wi-Fi, Bluetooth, RF and GNSS teams. How to find those engineers by stack, not title._

- Canonical URL: https://www.refolk.ai/blog/qualcomm-india-layoffs-wifi-gnss-engineers-sourcing
- Published: 2026-11-18
- Reading time: 9 min
- Keywords: Qualcomm layoffs India, hire Wi-Fi Bluetooth firmware engineers India, source RF GNSS engineers, Qualcomm laid off engineers hiring

Qualcomm started cutting jobs in India on November 9, and its CEO calls the cuts "performance-focused." The reports say something else: the first round landed on senior, long-tenured engineers, and the possible reductions sit in the RF, Bluetooth, Wi-Fi and GNSS teams. If you hire connectivity engineers, ignore the label and look at the stack. The catch is that most of these engineers' profiles never name it.

## What happened in Qualcomm's India layoffs?

Qualcomm's first India round began on November 9. Reports put 1,000 or more roles at risk across the country, where Qualcomm has major engineering sites in Bengaluru, Hyderabad, Chennai and Delhi NCR. Qualcomm has not confirmed a number.

Here is what has been reported so far:

- **Start date:** November 9, for the first India round.
- **Scale:** WION reports 1,000 to 1,500 employees could be affected. Industry estimates cited by The Economic Times are lower, at 600 to 1,200.
- **Who:** The first round focused on senior engineers and similar staff with many years at Qualcomm (The Week).
- **Which teams:** Moneycontrol reported possible reductions in the RF, Bluetooth, Wi-Fi and satellite navigation teams. It also said the depth of the cuts in each team is unclear.
- **Exit terms:** An extra month's salary for anyone who signs separation documents within three days. Digit reports severance of 3 to 5 months' salary.
- **What comes next:** India Today expects a second wave in January 2027.

For scale, India held 36% of Qualcomm's 50,257 employees in 2023, about 18,100 people (TrendForce). Even the high estimate is under a tenth of that base. So this is not a site shutdown. It is a targeted cut, and for a recruiter the target is the part that matters.

## Is "performance-focused" the right way to read the cuts?

Only partly. Cristiano Amon's October memo, which Reuters reviewed, describes a "performance-focused reduction" after annual reviews, but the same memo says the changing business needs different competencies and skills. That second line is about which capabilities Qualcomm wants to keep, not a verdict on individual engineers.

The mechanism matters. Amon tied the reduction to annual reviews, so the ratings were how the cut got carried out. When leadership decides it needs different skills, the people on the stack that lost priority are the ones who get rated out. A strong 802.11 engineer on a team that lost priority gets the same exit letter as a weak engineer anywhere else.

### What the 47.7% Blind figure actually measures

A widely shared number says 47.7% of Qualcomm employees questioned manager bias. That's wrong. The figure is the **share of Qualcomm layoff discussions on Blind that cited politics or favouritism**, based on Blind's internal AI analysis (People Matters). For comparison:

- 47.7% of discussions cited politics or favouritism
- 34.2% cited cost or performance
- 87% of the Qualcomm discussions came from India

Those numbers measure what employees were talking about, not what happened. They don't prove bias. They do show that the people closest to the cuts mostly don't believe the performance story. Put that next to Amon's own language about skills and the reasonable reading is that this cut followed teams.

> When a cut follows a capability, the team someone sat on tells you more than the rating they got.

## Why won't an employer or title filter find them?

A title filter misses India's wireless engineers because most of them don't call themselves wireless engineers. In Refolk's index, 23 of 25 sampled India profiles with WLAN skills carry generic titles like Senior Engineer or Staff Engineer. Only 1 says "Wireless Engineer."

A generic title is a ladder title, like "Senior Engineer" or "Staff Engineer", that names a level but not a domain. The US pool labels itself by domain far more often: 10 of 25 US profiles from the same query say "Wireless Engineer."

I ran the same skill and title filters (WLAN skill, plus Senior, Staff, Firmware or Wireless Engineer titles) in both countries:

| Metric | India | US |
|---|---|---|
| Total matching profiles | 172 | 42 |
| Titled "Wireless Engineer" (sample of 25) | 4% (1/25) | 40% (10/25) |
| Generic Senior/Staff titles (sample) | 92% (23/25) | 44% (11/25) |
| Qualcomm share of sample | 32% (8/25, incl. QIC) | 8% (2/25) |
| Top region | Bengaluru (10/25) | San Jose (5/25) |

*Source: Refolk's index. Samples are 25 profiles per country, so read the shares as directional.*

> **92%** India WLAN-skilled senior engineers with generic Senior or Staff titles
>
> In the US sample the figure is 44%, so a title search works there and mostly fails in India.

India has about 4.1x as many matching profiles as the US. That makes it the bigger pool, and also the one that is harder to see. Search for the title "Wireless Engineer" and you catch roughly 1 in 25 Indian candidates, against 10 in 25 American ones.

Headlines don't help either. A strict headline search for "Qualcomm WLAN Wi-Fi Bluetooth GNSS RF" among senior India profiles returned **0** in Refolk's index. Part of that comes from requiring every term at once. Still, it shows that people don't write their protocol stack into their headline.

The employer filter has the opposite problem. "Qualcomm" matches every Qualcomm employee regardless of team, and it misses engineers with the same skills at Tata Elxsi (3 of the 25 India profiles), Samsung Electronics (2) or MediaTek (1).

## How do you source RF and GNSS engineers by stack?

Search by skill (802.11, BLE, GNSS, RF), then confirm it with public work: commits and patents. The stack is what got these teams cut, so the stack is also how you find them.

How much public evidence you'll find depends on the stack:

- **802.11 / WLAN:** This one is easiest. Qualcomm's Wi-Fi 7 Linux driver, ath12k, lists its authors by name with quicinc.com addresses, including Karthikeyan Periyasamy and P Praneesh (LWN). Jeff Johnson is another contributor with a Qualcomm address across ath11k and ath12k. The linux-wireless project on Patchwork (patchwork.kernel.org/project/linux-wireless) lets you search by name and shows who sends patches and how recently.
- **Bluetooth, GNSS and RF:** I can't point to a public driver trail like ath12k for these. Patents are the check to lean on: search inventor names against a Qualcomm assignee and read the claims for the stack you need.

Here is why this works. The ath drivers record who wrote what and when, so a commit trail is something you can verify. Patents tie a named inventor to a specific technical claim. A profile title tells you neither.

Doing this by hand means a lot of tabs: Patchwork, patent searches and profiles, then matching names across all of them. [Refolk](/) handles that matching for you. You describe the engineer in plain English, by stack, city and evidence, and you get back people whose commits, patents and profiles line up.

> **Example search:** "Senior engineers in Bengaluru, Hyderabad or Chennai who worked on 802.11 or BLE firmware at Qualcomm, with Linux wireless commits or patents" - [run it on Refolk](https://www.refolk.ai/s/sahmdkpfqf)
>
> A ranked shortlist matched on the protocol stack rather than the job title, with the commit, patent or profile evidence attached to each person.

## Where are Qualcomm's connectivity engineers outside Bengaluru?

Bengaluru leads, but Tamil Nadu is the market most searches miss. In Refolk's India sample, Bengaluru holds 10 of 25 WLAN-skilled senior profiles, while Chennai, Salem and Madurai together hold 6, twice Hyderabad's 3.

That matters because Chennai is one of Qualcomm's major India engineering sites, and because many sourcing searches stop at "Bengaluru OR Hyderabad." If your role allows remote work in India, put Tamil Nadu in the search on purpose.

Hyderabad is still a real market and one of Qualcomm's major sites. It just shows up thinner in a 25-profile sample. Use the city split to decide where to widen the search, not as a ranking.

> **Engineering roles open in Bangalore** - [see the open roles](https://www.refolk.ai/jobs/search?family=engineering&location=bangalore)
>
> Live engineering postings in the city where most of the sampled WLAN talent sits.

## Why reach out in November instead of January?

Reach out in November because the three-day early-exit bonus brings departures forward. Employees who sign separation documents within three days reportedly get an extra month's salary, so the first wave is free now, before the second wave India Today expects in January 2027 adds both candidates and competition.

The money also affects how you pitch. Digit reports severance of 3 to 5 months' salary. One self-reported Reddit case put a package at about 15 to 16 months' salary after five years, though that's an anecdote and hasn't been verified. Either way, many of these engineers aren't desperate. Someone with months of runway will judge your role on the work, not just the speed of the offer.

Your competition is already in the data. Tata Elxsi, Samsung Electronics and MediaTek show up among the top employers for these profiles in Refolk's index, so they already hire this skill set. Before January, the advantage goes to whoever reaches the right 802.11 or GNSS engineer first.

That is also where most searches stall. You might have 172 India profiles that look plausible on paper, and if the sample holds, more than nine in ten carry a generic Senior or Staff title. Checking each one against commits and patents by hand is slow, and the employers already hiring this skill set aren't waiting.

## What should the first message to a Qualcomm engineer say?

Start with their stack and your problem, and leave out the layoff and the performance framing entirely. Treat these people as senior engineers whose team was deprioritized, because that's what the evidence says they are.

A simple sequence:

1. **Name the work.** "Your ath12k patches" or "your patent on GNSS signal acquisition" shows you looked them up. "Your experience at Qualcomm" shows you didn't.
2. **State the stack you need.** Say 802.11, BLE, GNSS or RF, and the layer you mean, not "wireless."
3. **Say what's different.** Many first-round engineers had long tenures at Qualcomm. Tell them plainly what your scope, team size and silicon roadmap look like.
4. **Respect the timeline.** Some will sign within the three-day window and want a break. Offer a conversation, not an application link.
5. **Ask who else.** Senior engineers know who else on their team got cut. One good conversation can map an entire Bluetooth or RF group.

The fifth step is where the real pool shows up. A team cut together can often be hired together.

## FAQ

### How many Qualcomm employees in India are affected by the layoffs?

Qualcomm hasn't confirmed a number. WION reports 1,000 to 1,500 employees could be affected, while industry estimates cited by The Economic Times put the range at 600 to 1,200. Either way, it's a small share of Qualcomm's India workforce, which was about 18,100 people (36% of 50,257) in 2023. That supports the view that the cuts targeted specific teams rather than whole sites.

### Were the laid-off Qualcomm engineers low performers?

The evidence doesn't support reading it that way. Cristiano Amon's memo calls the cuts "performance-focused," but it also says the business needs different competencies and skills. Reports place the cuts in RF, Bluetooth, Wi-Fi and GNSS teams and among senior, long-tenured staff. On Blind, 47.7% of Qualcomm layoff discussions cited politics or favouritism, against 34.2% citing cost or performance. Judge each engineer on their own work.

### Where can I find public evidence of a Qualcomm Wi-Fi engineer's work?

Start with the Linux kernel. Qualcomm's ath11k and ath12k Wi-Fi drivers list authors with quicinc.com addresses, and the linux-wireless project on Patchwork lets you search patches by name. For Bluetooth, GNSS and RF, where there's no comparable public driver trail, patent searches by inventor name and Qualcomm assignee are the most reliable check.

### Will there be more Qualcomm layoffs in India?

India Today expects a second wave in January 2027. That will add candidates, but it will also bring more competition from employers like Tata Elxsi, Samsung Electronics and MediaTek, which already appear among the top employers for these profiles. The engineers leaving in the November round, especially those who took the three-day early-exit bonus, are available sooner and are being contacted by fewer recruiters.

---

_From the Refolk blog. More posts: https://www.refolk.ai/blog/index.md_
