Rivian Cut 300 on June 16. Figure and Optimus Will Take the Diagnostics IC.
Rivian's June 16, 2026 layoff hit "service and customer" teams. Inside that label sit OTA, HV, and ADAS engineers humanoid robotics will hire fast.
On June 16, 2026, Rivian confirmed it cut up to ~300 workers, less than 2% of its ~15,200-person workforce, one week after R2 SUV deliveries began. Every wire desk and EV forum is repeating the company's own line: the cuts hit "service and customer" teams, "including sales and marketing." If you read that and moved on, you just left a pool of EV diagnostics, OTA, and high-voltage engineers on the table for Figure, Optimus, Agility, and 1X to pick up.
The label is misleading on purpose. Rivian's service organization is not a call center. It is one of the most software-dense field engineering orgs in the EV industry, and the people who were cut are the same archetype humanoid robotics companies are paying signing bonuses for right now.
What "service and customer" actually contains at Rivian
Read Rivian's own careers and support pages and the picture changes fast. Rivian's remote diagnostics product description says the service team can "find issues in real time" and "push an OTA update to resolve the issue without the vehicle leaving the owner's sight." That is not a service advisor. That is a diagnostics engineer with telemetry access and OTA deploy rights.
Inside the service org, Rivian's published growth paths include software technicians, low-voltage electrical (LVE) specialists, diagnostic technicians, prototype technicians, and testing and development technicians. The diagnostic engineer JD for Low Voltage and Body Controls reads like a backend role: "develop and continuously improve diagnostic content (testing procedures, evaluation logic, automated scripts) within Rivian's offboard diagnostic ecosystem" and "leverage telemetry, product data and diagnostic data to drive continuous improvement in service processes, manufacturing quality, and software design."
The OTA team JD goes further: "engineers on the OTA team are responsible for end-to-end definition, development, and integration of OTA at the vehicle level," with a hard requirement for "familiarity with vehicle diagnostics and common UDS services." Rivian also posts Service Engineer II, ADAS roles out of Irvine. None of that is sales and marketing.
The Sr. Field Service Engineer archetype
Rivian publicly profiled one of its own Sr. Field Service Engineers at the factory: 16 years in automotive, the last 11 on high-voltage vehicles, six on EVs, prior roles at Tesla, Ferrari, Maserati, and Mercedes-Benz. His team "runs the Advance Diagnostics department, trains and mentors technicians, and creates diagnostic content for service."
That is the median seniority of the engineering subset inside what just got cut. Not entry level. Not customer-facing. The kind of profile that takes nine months to source cold in any normal quarter.
Why this is a robotics pool, not an automotive one
The reflex move is to assume ex-Rivian service engineers will land at Lucid, Polestar, Ford Model E, or Tesla. Some will. The bigger and quieter market is humanoid robotics.
Figure AI's humanoid robots are already working shifts at BMW's Spartanburg plant; Figure 02 and 03 handle warehouse logistics, parts sorting, and repetitive assembly. Amazon is deploying Agility Robotics' Digit in fulfillment centers for tote-moving and shelf-stocking. Tesla is running Optimus on pilot production lines in Fremont. Every one of those deployments needs a field service and diagnostics function that does not yet exist at scale.
Current-generation humanoid robots cost between $100,000 and $300,000 per unit, require significant integration engineering, and have uptime rates that are still improving. The job description for keeping a fleet of high-voltage, sensor-laden, OTA-updatable machines running at a customer site is the job description Rivian just printed 300 copies of and handed to the market.
What carries over
- High-voltage troubleshooting and safety. Rivian's HV stack and a Figure 03 actuator stack rhyme more than they differ.
- Offboard diagnostic tooling. UDS, telemetry pipelines, evaluation logic, automated scripts. Robotics has none of this mature in-house.
- OTA delivery. The Rivian and Volkswagen Group Technologies JV (RV Tech) in Irvine exists because OTA at vehicle scale is hard. Engineers who shipped it for Rivian are immediately useful at any robotics company past pilot.
- Telemetry-driven quality loops. Rivian closes the loop between field data, manufacturing quality, and software design. Robotics is still trying to build that loop.
The 30 to 45 day arbitrage
Rivian shed these people on June 16. R2 deliveries started June 9. The press cycle is locked onto the R2 launch and Rivian's profitability story (the automotive segment lost about $6,000 per vehicle in Q1 2026, which is why fixed costs are on the block). By the time competitors realize the cut included diagnostics ICs and Sr. Field Service Engineers, severance windows close and signing bonuses spike.
The label "service and customer" is doing the work of a non-disclosure agreement. It buys Rivian time and costs sourcers candidates.
Recruiters who move this week, on LinkedIn and GitHub, beat the wave. Recruiters who wait for "ex-Rivian engineer" to start trending in their ATS dashboards will pay 25% more for the same person in September.
This is the exact gap Refolk was built for. The LinkedIn title says "Service Engineer II." The work was OTA integration on a UDS stack. Boolean strings on a job title will not find this person. A plain-English description of who they actually are will.
How to actually source the pool
Stop searching on "Rivian engineer"
That query returns the obvious roles: powertrain, autonomy, infra. The pool you want sits under "Service Engineer," "Field Service Engineer," "Diagnostic Engineer," "Service Technician," "OTA Integration Engineer," and "ADAS Service Engineer." Some of the strongest candidates have "Technician" in the title and a software portfolio underneath it. That mismatch is why most sourcers will miss them.
Search the metros, not the company
Rivian service engineering clusters in Irvine and LA, Seattle, Denver, the NY metro, Tampa, and Spring, TX. Those are also the metros where humanoid pilots and robotaxi fleets (Waymo, Zoox) are scaling. Search by metro and skill set, not company alumni list. You will pick up the recent departures plus the people thinking about leaving once their friend's WARN window closes.
Read the adjacent JDs
The RV Tech JV in Irvine is hiring Sr. OTA Software Integration Engineers. Electrify America, ChargePoint, Revel, Waymo, and Zoox all hire the same diagnostics/OTA/HV profile. If you are recruiting for a humanoid robotics company, post the JD against those keywords, not against "robotics." The ex-Rivian engineer searching today is typing "EV field service" and "OTA integration" into the search bar, not "humanoid."
Use plain English, not Booleans
The single biggest sourcing leak this week is the gap between how Rivian titled these roles and how the engineers describe their actual work. Field service engineer sourcing is a semantic problem now, not a keyword problem. Tools like Refolk let you describe the candidate the way the candidate would describe themselves on a phone call, then pull the matching profiles across GitHub, LinkedIn, and the open web in one pass.
What to message, and when
The press hook gives you a clean opener. Most ex-Rivian engineers reading their phones this week do not want to be told they were laid off. They want to be told their work is portable.
A first message that lands:
"Saw the June 16 news. The diagnostic content and OTA work your team shipped for R1S and R2 is the same problem Figure and Agility are trying to solve at fleet scale. We are hiring a Field Reliability Engineer for a humanoid deployment at [customer]. UDS, telemetry, HV. 20 minutes this week?"
That message will out-perform a generic "exciting opportunity" outbound by a factor most recruiters would not believe if you put it on a slide. It works because it names the work, not the company.
Three things not to do
- Do not lead with "I saw you were impacted by the recent layoffs." Engineers hate that sentence. Lead with the work.
- Do not assume seniority from title. Service Engineer II at Rivian can mean ten years of HV experience. Ask, do not filter.
- Do not wait for the "ex-Rivian" badge to appear on LinkedIn. Many will update in 30 to 60 days. By then your competitor has signed them.
The bigger pattern
This is the fourth round of Rivian cuts since the start of 2024. October 2025 took roughly 600 (about 4.5% of the workforce at the time), tied to slowing EV demand after the federal tax credit expired. Each round has hit a slightly different slice of the org. The June 16 round is unusual because it landed on the service side at exactly the moment R2 deliveries (Rivian guided 20,000 to 25,000 R2 units in 2026 within a 62,000 to 67,000 total) shifted technical weight onto service centers, not the factory.
Every R2 ships to a buyer's nearest Service and Demo Center, not the factory. The service org carries unusual technical weight right now. Which is why the engineers Rivian cut on June 16 are more senior, more software-fluent, and more reusable in robotics than the headline suggests.
The recruiters who win this pool are the ones who treat the press release as marketing copy and read the JDs instead.
FAQ
How many Rivian engineers were actually laid off on June 16, 2026?
Rivian said the cut was "less than 2%" of its roughly 15,200-person workforce, which puts the total at up to about 300 roles. The company described them as concentrated in "service and customer" teams "including sales and marketing." That phrasing covers a meaningful engineering subset: diagnostic engineers, OTA integration engineers, Sr. Field Service Engineers, and ADAS service engineers. The exact engineering count is not disclosed, but the JDs Rivian was actively running before the cut tell you the subset is real and non-trivial.
Why would a humanoid robotics company hire an ex-Rivian service engineer?
Because the job is structurally the same. Humanoid robots are high-voltage, sensor-laden, OTA-updatable machines deployed at customer sites with uptime SLAs. That is also what an R1S or R1T is. Rivian's service engineers have already built the offboard diagnostic tooling, UDS-layer content, and telemetry pipelines that Figure, Agility, and Optimus teams are now standing up for the first time. The skill transfer is closer to lateral than it looks.
What titles should I search for when sourcing ex-Rivian engineers on LinkedIn?
Look beyond "Engineer." Search Service Engineer, Field Service Engineer, Sr. Field Service Engineer, Diagnostic Engineer, Service Technician, Software Technician, LVE Specialist, OTA Integration Engineer, and Service Engineer II ADAS. Cross-reference with prior employers Tesla, Ferrari, Maserati, and Mercedes-Benz to surface the senior HV cohort. The Irvine, LA, Seattle, Denver, NY metro, Tampa, and Spring TX clusters will return most of the pool.
How fast does this window close?
Roughly 30 to 45 days. Severance and benefits cliffs concentrate decision-making in that window, after which the strongest candidates have either signed somewhere or stopped picking up. By August, signing bonuses for ex-Rivian HV and OTA engineers will reflect the broader market catching on. Move in June and early July, or pay a premium in the fall.