Amazon Cut Up to 250 Devices Coders. 1,839 US Profiles Say 'Lab126'
Amazon cut up to 250 devices jobs and named no locations. How to find Lab126 engineers by keyword, Vega OS and Fire OS instead of a company filter.
If you want to hire the engineers Amazon cut from Devices and Services on Oct 28, 2026, you have no list to work from. Amazon confirmed the cuts but gave no headcount and no location, and Reuters' "up to 250 jobs, mainly software roles" is a ceiling, not a count. The only recent Sunnyvale WARN filing predates this round, and a complete one may never appear. To find these engineers, search for what they built. The employer field won't do it.
What did Amazon actually confirm about the devices layoffs?
Amazon confirmed cuts in Devices and Services but gave no headcount and no location. The only number in public is Reuters' "up to 250 jobs, mainly software roles," and that is a ceiling, not a count.
Several outlets rounded it to a flat 250. Don't plan around that figure. Amazon's spokesperson called it "a small number of roles." Here is what is on the record:
- Oct 28, early morning: staff were told by text and email.
- The internal message came from Cherie Robinson, VP of HR for Devices and Services. It cited "a thorough review of our structure."
- Same day: Amazon announced five new Alexa devices, including a redesigned Echo Show 16, the Alexa Photo Frame and the Echo Time clock.
- Oct 27, the day before: Amazon published a memo from Terk Terkowitz, VP and Distinguished Engineer in Stores. It called token usage, AI-tool adoption and code-change counts "deeply flawed" metrics, and it still told managers to look at the bottom 10% of teams by AI adoption.
- Background: Amazon had already shut down its internal KiroRank leaderboard in May 2026 after staff gamed it.
Nothing public ties the memo to the cuts. But the people you contact have probably seen both, and that affects how your outreach lands (more on that below). For scale: Amazon has cut more than 57,000 corporate jobs since 2022, about 16% of its corporate workforce. Next to that, a devices round of up to 250 is small. For a single devices unit, it isn't.
Why won't a WARN notice give you the list?
California's WARN law only covers sites with 75 or more employees, so a cut spread across several offices may never show up as one public number. The last devices round shows how much a filing can miss.
A WARN notice is an advance filing an employer must submit to the state before a mass layoff. In California the notice period is 60 days. In May 2025, Reuters reported about 100 devices cuts. About a week later, a California filing listed 33 people at Lab126's 1100 Enterprise Way and 6 at 11th Ave, both in Sunnyvale.
The cause is structural. When a cut is spread across Sunnyvale, Seattle, Boston, Austin and India, no single California address may cross the threshold. Amazon's most recent Sunnyvale WARN covered 70 roles at 1160 Enterprise Way (SJC13), effective Oct 20, 2026. That filing predates this round and gives no reason, so don't treat it as this list.
What to check each week:
- The California EDD WARN database, for 1100 Enterprise Way and 11th Ave in Sunnyvale.
- The Washington ESD WARN database, for Seattle-area Amazon filings.
- Any filing dated after Oct 28 that names Devices, Lab126 or a Sunnyvale address.
How big is the Amazon Lab126 talent pool?
In Refolk's index of professional profiles, 1,839 US profiles and 503 India profiles mention "Lab126." Even if every cut landed on a US Lab126 person, the 250 ceiling would be at most 13.6% of the US group.
Lab126 is Amazon's devices group, headquartered at 1100 Enterprise Way in Sunnyvale and behind Kindle, Fire TV and Echo. Here is how the searchable pool breaks down:
| Segment | Count | Note |
|---|---|---|
| US profiles mentioning "Lab126" | 1,839 | Refolk's index |
| India profiles mentioning "Lab126" | 503 | Refolk's index |
| US software engineers with Embedded Linux skill | 1,627 | Refolk's index |
| US to India Lab126 ratio | 3.7x | Derived |
| Reuters ceiling vs US Lab126 profiles | ≤13.6% | Assumes all cuts were US Lab126 |
| Share of sample still at Amazon (US vs India) | 56% vs 76% | Samples of 25, directional |
The top US regions in the sample are the SF Bay Area, Sunnyvale, San Jose and San Francisco. One sampled title shows the seniority involved: "Senior Software Development Manager, Application Framework and SDK, Vega OS."
The last row matters most. About 44% of the US sample has already left Amazon. They're founders now, or they work at AMD or Airbnb. So a "Lab126" keyword search mostly returns current staff and long-gone alumni, and the people cut on Oct 28 are a small slice of the results. To find them, look for an Amazon role that ended in October 2026 or a recent "Open to Work" flag.
Why does the Amazon company filter miss Lab126 engineers?
Lab126 people list their employer in two different ways, so any single company filter drops some of them. Search the keyword and both employer names together.
In the US Lab126 sample, current employers split between "Amazon Lab126" (10) and plain "Amazon" (4). Filter on "Amazon" and you lose the first group, which is the bigger one. Filter on "Lab126" and you lose the people who folded the division into the parent company.
Refolk is built for this gap. You describe the person in plain English, including what they built and when they left, and you get back a ranked shortlist. You don't have to guess how each person filled in their employer field.
Once you have that list, sort by end date, then by "Open to Work." Alumni who left years ago need their own campaign with a different pitch. Don't put them in the same sequence.
Why is "embedded Android" the wrong search for half this group?
Amazon's newer devices run Vega OS, which is Linux plus React Native, not Android. Many of the devices engineers cut this week will describe themselves as Linux or JavaScript framework engineers, not Android engineers.
Fire OS is Amazon's operating system built on Android. Vega OS is its Linux-based replacement, built with React Native, and its developer tools used to be called "Kepler." Vega already runs on the Echo Hub, the Echo Show 5 (3rd gen) and the Echo Spot. An embedded Android search finds the Fire OS veterans and misses everyone who moved to Vega.
Search terms that cover both stacks:
- "Lab126" as a keyword, not a company
- "Vega OS" and "Kepler" (the earlier name for the tooling)
- "Fire OS" for the Android-era engineers
- "Embedded Linux" with "React Native"
- "Sunnyvale" as a location tiebreaker
A workable Boolean: ("Lab126" OR "Vega OS" OR "Fire OS" OR "Kepler") AND ("Embedded Linux" OR "React Native" OR "Android").
Search for the operating system they shipped, not the company that paid them.
The market data backs this up. In Refolk's index, 1,627 US software engineers list Embedded Linux as a skill. Neither Amazon nor Lab126 appears among the top employers in that sample, which Meta, NVIDIA, Google and Intel lead. A skill search on its own sends you to people who already work in big tech. A Lab126 cut is one of the rare times a group of embedded Linux and device-framework engineers comes onto the market at once, and building that list one Boolean string at a time can take weeks you may not have.
The fix is to pair the skill with the product. "Embedded Linux" plus "Echo Show" or "Vega OS" gives you a short list of exact matches instead of 1,627 generalists.
Should you source Amazon Lab126 engineers in India?
Yes. India accounts for 21% of combined Lab126 profiles in Refolk's index, and Amazon gave no locations for this cut, so a US-only search could miss a meaningful share of it.
The India sample clusters in Bengaluru, Chennai and Hyderabad, and it looks different from the US sample. 76% are still at Amazon, compared with 56% in the US. Both figures come from samples of 25, so treat them as directional. A "Lab126" search in India therefore returns more current employees and fewer alumni, which makes a recently ended role easier to spot.
If you have a Bengaluru or Hyderabad engineering hub, run the same Boolean there now. California and Washington filings won't cover these people, so the end dates on their profiles are your signal.
What should the first message to an Amazon devices engineer say?
Lead with the device and OS work they would do, and skip anything about AI-usage dashboards. Write it so it works whether or not the person was actually cut.
The second point matters because you will contact up to 1,839 US profiles to reach at most 250 affected people. Most of the people you message still work at Amazon or left years ago. Opening with "sorry to hear about the layoff" offends the first group and confuses the second. Write a message that a happy current employee would also want to read:
- Name the product they shipped (Echo Show, Kindle, Fire TV, Vega OS).
- Name the concrete problem your team has: a board bring-up, a framework rewrite, a power budget.
- State the stack plainly, including whether it is Linux, Android or both.
- Add one sentence about how your team measures engineers.
The fourth point comes from this week's news. The Terkowitz memo called AI-usage metrics "deeply flawed" but still pointed managers at the bottom 10% of teams by adoption, five months after KiroRank was shut down for being gamed. Engineers coming out of that environment will be wary of any pitch built on AI productivity numbers. A single line saying you judge people on the devices they ship will do a lot of work.
Timing matters as much as wording. Rerun the same search every week, because the signals you want show up gradually after Oct 28: a new end date, an "Open to Work" flag, a move from "Amazon" to a new employer.
FAQ
How many people did Amazon lay off in its devices unit in October 2026?
Amazon hasn't said. Reuters reported "up to 250 jobs, mainly software roles," which is a ceiling, and Amazon's spokesperson called it "a small number of roles." Treat 250 as the maximum. In May 2025, public California filings accounted for only about 40% of a reported devices cut.
Has Amazon filed a WARN notice for the Lab126 layoffs?
No filing for this round has been reported. The most recent Sunnyvale WARN covered 70 roles at 1160 Enterprise Way (SJC13), effective Oct 20, 2026. It predates the Oct 28 cuts and gives no reason. Check the California EDD and Washington ESD databases weekly, and keep in mind that California's law only covers sites with 75 or more employees.
What is the difference between Fire OS engineers and Vega OS engineers?
Fire OS is built on Android, so its engineers usually list Android framework and embedded Android skills. Vega OS is the Linux-based replacement built with React Native, and its tools were once called Kepler. Vega engineers often describe themselves as Embedded Linux or React Native framework engineers. If you don't search both stacks, you'll miss half the group.
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.