If you were in the January or May 2026 Reality Labs cuts, your resume is probably losing you interviews you should be winning. Recruiters at Anduril, Figure, and Waymo are calling ex-RL C++ engineers the rarest portable talent on the market, but the same recruiters admit they do not instinctively reach for a VR resume when they are filling a robotics req.
That gap is a labeling problem, and it is fixable in an afternoon.
Why Reality Labs alums look invisible to robotics recruiters
The pool is not rare, the tagging is. In Refolk's index of professional profiles, about 313 US engineers hold a "Robotics Software Engineer / Autonomy Engineer / Perception Engineer" title with C++, but a targeted keyword query for people who pair "Reality Labs" or "Oculus" with C++ returns single-digit counts. That is roughly a 100:1 gap between the demand-side vocabulary and the supply-side self-description.
The mechanism is boring. Applicant tracking systems, LinkedIn Recruiter searches, and internal sourcing tools filter on literal strings: SLAM, VIO, Kalman, ROS, PREEMPT_RT. A Quest hand-tracking engineer who shipped a Kalman-filtered VIO pipeline against a sub-30ms budget usually wrote none of those tokens on their profile. Their bullets say "AR/VR," "immersive experiences," "Codec Avatars." The recruiter's boolean skips them.
313 US robotics/autonomy/perception ICs with C++ against single-digit ex-Reality Labs profiles surfacing in Refolk's index.
The 2026 layoff math and where the cohort is landing
Meta cut roughly 1,000 to 1,500 Reality Labs employees in January 2026, another ~700 across five divisions in March, and began notifying about 8,000 more the week of May 20, 2026, while freezing ~6,000 open reqs. That is an effective 14,000-slot reduction across the year. A California WARN filing tied to the January round permanently cut 272 employees by March 20, 2026: 53 at Playa Vista and 219 at Burlingame.
Where they are going, per recruiting-industry reads since January:
- Anduril (Costa Mesa): founded by Oculus co-founder Palmer Luckey, grew from 4,490 to 8,200 employees in a single year, 600+ open reqs in 2026, total comp reaching $340K.
- Figure: humanoid perception stack, explicitly stretching levels for candidates with Codec Avatars or Quest on the resume.
- Waymo: multiple open Mountain View systems roles.
- Tesla Optimus, Skydio, Apple Vision Products Group: all sourcing aggressively from the same pool.
- Zipline (South San Francisco): Senior/Staff perception on the Droid delivery team, a softer landing than defense.
- Agility Robotics: the top employer in Refolk's Robotics-SWE-with-C++ pool, a humanoid analog to Meta's avatar work.
Same-day offers are real, but they are a mechanical consequence of two facts, not enthusiasm. Cleared C++ headcount is inelastic, and defense-adjacent shops are funded to buy out unvested Meta RSUs. If you do not quantify your unvested RSU cliff in the first recruiter call, you leave the sign-on money on the table.
| Segment | Count / figure |
|---|---|
| Reality Labs headcount cut, Jan 2026 round | ~1,000 to 1,500 (10 to 15% of RL) |
| Total Meta 2026 layoffs, May round | ~8,000 employees |
| US "Robotics/Autonomy/Perception Engineer" + C++ pool | 313 |
| Reality Labs / Oculus + C++ profiles on the open market | 3 (single digits) |
| Ratio of robotics demand roles to visible RL-tagged supply | ~100:1 |
| Anduril open reqs, 2026 | 600+ |
| Anduril headcount growth, 2024 to 2025 | 4,490 to 8,200 (+83%) |
The skill port is one-to-one, and a real JD proves it
Quest hand-tracking and Codec Avatars are closer to humanoid perception than to gaming. A Rivet Industries "Software Engineer, Sensor Fusion" listing from February 2026 asks for C++ real-time systems, state estimation, SLAM/VIO, and OpenXR. That is nearly a direct copy of a Reality Labs tracking-team JD with the word "avatar" swapped for "robot."
The port maps cleanly:
- Head and hand tracking becomes state estimation and multi-sensor fusion.
- Inside-out SLAM on Quest becomes visual-inertial odometry (VIO) for autonomous navigation.
- Real-time avatar rendering under a compositor budget becomes PREEMPT_RT-style real-time Linux control loops.
- Custom silicon adjacency becomes DSP/FPGA-adjacent perception pipelines.
- OpenXR runtime work stays OpenXR runtime work; Rivet actually asks for it by name.
Reality Labs alums can legitimately claim they beat robotics real-time budgets in production. Robotics sensor fusion targets roughly 30 to 35 ms per frame. Quest hand-tracking targets are tighter. Write that number down. It is the single most persuasive line in the rewrite.
The line-by-line resume rewrite
Rewrite the top third of the resume so a robotics recruiter's boolean matches on the first pass. Everything else is secondary.
1. Kill the "AR/VR Engineer" title line
Replace it with the function, not the product. "Perception and Real-Time Systems Engineer, C++" reads on both a Waymo req and a Meta internal transfer form. If your last title was literally "Software Engineer, Reality Labs," append the discipline in parentheses: "Software Engineer, Reality Labs (Tracking and Perception)."
2. Rewrite the summary in the destination's vocabulary
Robotics hiring managers screen for: ROS, Gazebo, Kalman filters, SLAM, multi-sensor calibration, PREEMPT_RT, state estimation, VIO. None of those words appear on a conventional VR resume even when the work is identical. Name the ones you actually did. Do not name the ones you did not.
3. Convert every avatar/XR bullet into a robotics-native bullet
Example rewrites, using the exact terminology from robotics JDs:
-
Before: "Owned hand-tracking pipeline for Quest 3, improving gesture recognition latency."
-
After: "Shipped a C++ visual-inertial state estimator (6-DoF, EKF-based) running at sub-30ms end-to-end on constrained silicon, calibrated across four cameras and an IMU."
-
Before: "Contributed to Codec Avatars real-time rendering."
-
After: "Built low-latency perception-to-render pipeline with multi-sensor calibration and real-time scheduling constraints comparable to PREEMPT_RT robotics stacks."
-
Before: "Optimized SLAM for standalone headsets."
-
After: "Production SLAM/VIO on embedded ARM, meeting hard real-time budgets tighter than typical 30 to 35 ms robotics sensor-fusion targets."
Rewriting 12 to 20 bullets into destination-vocabulary bullets is the actual work, and it is the exact work Refolk takes off you: paste the Anduril or Figure posting, get your own resume back rewritten in that posting's language, with your Reality Labs history intact underneath.
4. Add a "Systems and Tooling" line with the tokens
Even if you only touched them adjacently at Meta, name the ones you can defend in an interview: C++17/20, ROS 2, Eigen, Ceres, GTSAM, OpenCV, CUDA, Linux real-time, Bazel. Recruiters filter on strings. Interviewers test on depth. Get past the filter first.
5. Score the fit before you send
Do not send the same rewrite to Anduril, Zipline, and Waymo. Each has a different center of gravity: Anduril wants shipped hardware and clearance-adjacent signal, Waymo wants systems reliability, Figure wants humanoid-specific perception. Refolk scores how well you actually fit each posting before you apply, so you can see whether a rewrite is landing at 62% or 88% for a given req and where the gaps are.
The Palmer Luckey channel is undervalued
Anduril is the single most culturally aligned landing spot for a Reality Labs alum, and almost nobody is playing it that way. Palmer Luckey co-founded Oculus. Anduril grew from 4,490 to 8,200 employees between end of 2024 and end of 2025 (an 83% jump) and has 600+ open reqs in 2026. Total comp reaches $340K.
The right resume for Anduril leads with hardware-adjacent shipping evidence, not model quality metrics. Ship dates, silicon collaboration, thermal or power constraints, on-device inference: those are the bullets that read as native to Costa Mesa. If your Reality Labs work touched the XR2 team, the compositor, or any on-device ML, that belongs in the top third of the page.
The scarcity is not a supply problem, it is a labeling problem, and it is fixable in an afternoon.
How to signal you left on your own terms without oversharing
Voluntary leavers screen differently from involuntary ones, and most Q1 2026 Reality Labs resumes were people who read the internal tier memo and left before severance. Recruiters know this. What they want to see is one clean line, not a paragraph.
Options that work:
- "Departed Meta in Q1 2026 to focus on humanoid perception and real-time autonomy."
- "Left Reality Labs after the January reorg to move into robotics full-time."
- "Chose to exit during Meta's 2026 restructuring."
Options that hurt you:
- Anything that names your tier or performance rating.
- Anything that sounds bitter about the org change.
- Anything that implies you were surprised. Senior ICs are supposed to read the room.
For the involuntary cohort, the WARN-filing dates are public. There is no shame in "Impacted by the March 2026 WARN action at Burlingame." Recruiters at Figure and Anduril have been triaging those lists directly.
Negotiating the unvested RSU buyout
Anduril, Figure, and several robotics shops are actively reimbursing unvested Meta RSUs as sign-on, but only if you ask in the first call. Senior IC comp at frontier labs routinely clears $750K total comp with 18-day time-to-offer cycles. That is your floor.
Bring three numbers to the first recruiter call:
- Unvested RSU value at your last Meta grant price, cliff by cliff.
- Refresh grants you were on track for in the next performance cycle.
- A target total comp anchored on the $750K frontier-lab benchmark, adjusted for the destination's cash-vs-equity mix.
The cover letter is the wrong place to negotiate, but it is the right place to signal that you know what you are worth.
FAQ
Should I keep "Reality Labs" on my resume at all?
Yes, but not as the headline. Reality Labs is a positive signal to any hiring manager who has been paying attention: it is the largest concentrated bet on real-time perception outside of the autonomy majors. Keep the org name as the employer, put the discipline (Tracking, Perception, Rendering, Compositor) in your title line, and rewrite the bullets in destination vocabulary. The goal is to survive the boolean filter and then win the human read.
How different should my resume be for Anduril vs. Waymo vs. Figure?
Different enough that a recruiter can tell you read the posting. Anduril wants hardware shipping evidence and mission-system framing. Waymo wants systems reliability, safety cases, and calibration rigor. Figure wants humanoid-specific perception and manipulation-adjacent work. Reordering the top five bullets per posting is usually the highest-leverage edit.
Do I need ROS on my resume if I never used it at Meta?
Only if you can defend it in an interview. Naming ROS or ROS 2 you have never touched is the fastest way to lose a phone screen. What you can honestly name is the equivalent: publish-subscribe messaging, node graphs, real-time scheduling, sensor drivers. Frame the analog explicitly ("Meta-internal pub-sub equivalent to ROS 2 topics") and pick up a weekend ROS project before your first onsite. Robotics teams respect fast learners more than fake ones.
Is defense off-limits if I do not have a clearance?
No, but be honest about the timeline. Anduril and its peers sponsor clearances for strong C++ ICs, and the process runs in parallel with onboarding. What kills candidacies is claiming clearance you do not have. State your current status ("no active clearance, eligible, willing to sponsor") in one line near the top of the resume or in the cover letter. For candidates who want to avoid the clearance path entirely, Zipline, Waymo, Figure, Skydio, and Agility Robotics are all hiring from the same pool without it.