Skip to main content
HonestMOS
●InvestigationsHow EUCOM shelved a tax break for 9,000 troops in Poland — for five years.→
←Back to RW Robotics Warfare Specialist — overview, pay, training, civilian translation, reviews
RWE7

Robotics Warfare Specialist

E-7 (Sergeant First Class) · Navy

E1–E3E-4E-5E-6E-7E8–E9
HEADS UP

You are one of the first RW chiefs. There is no thirty-year-old goat locker tradition to inherit — you are building it. The sailors behind you will wear the anchor because you established what it means in this rate. Don't treat that lightly.

The Honest MOS Read
Robotics Warfare Chief Petty Officer (RWC, E-7) is, in 2025-2026, an institution being founded. The goat locker for this rate did not exist when NAVADMIN 036/24 was issued in February 2024. The first generation of RW chiefs — whoever they are — will write the definition of what the anchors mean in this rating. That is the context you carry into the mess. As LCPO you run an unmanned systems department — on a surface combatant, in an MCM command, in an expeditionary or special operations support element, at a TYCOM unmanned systems staff — with 10-30 RWs and the enlisted execution running from your deckplate up. You write Chief-quality eEVALs that pick the next RW1 and RWC advancement slate. You sit at department head sync as the senior enlisted unmanned systems voice. You walk the spaces during a real mission cycle, a TYCOM readiness assessment, or a safety investigation and identify the broken procedures before the inspector does. The technical credibility imperative is higher in RW than in most rates at this stage of the rating's development. The wardroom may have limited familiarity with autonomous systems employment doctrine, and the program offices are still in dialogue with the fleet about how the systems are best used. The RWC who can brief the CO on DoD Directive 3000.09 requirements, translate a NTTP update into deckplate training decisions, and represent the enlisted perspective in a TYCOM readiness review without hiding behind a PowerPoint is not just doing his job well — he is filling an institutional gap the Navy is counting on the first RW chiefs to fill. The safety-of-use standard is the hill to defend absolutely. DoD Directive 3000.09 exists for a reason, and the first safety incident involving an unauthorized autonomous weapons activation on a Navy platform will have consequences that extend well beyond the unit involved. The RWC who enforces the standard under operational pressure — who says 'we do not have authorization for that autonomy level' when the section officer pushes for a timeline the policy does not support — is the chief the wardroom learns to respect rather than the one who enabled a headline. Hold the line. The goat locker tradition for RW is being established right now. What does the RW Chief's Mess look like? How does it hold itself? What is the standard the mess enforces on itself before it enforces it on the deckplate? The first group of anchors in this rate defines the answers to those questions for the generation behind. Take the responsibility as seriously as you would want the sailors wearing it in twenty years to have taken it.
Career Arc
  • 01CPO Initiation / CPO 365 transition complete; LCPO role assumed with a division training plan, qualification matrix, and readiness tracking system established within the first 90 days.
  • 02First full eEVAL cycle as LCPO — write evaluations the section officer signs without rewriting; ensure RW1s have Chief-board-competitive records in progress.
  • 03TYCOM readiness assessment / inspection with no senior-enlisted-attributable safety-of-use or documentation findings.
  • 04Pipeline output — advanced NEC, NSW support, commissioning programs — producing at least one selectee per year from the division.
  • 05Senior Enlisted Academy (SEA) timeline: scheduled or completed before competing for command CMC slot.
  • 06Senior Chief slate conversation begins with the CMC — two to three years out, but the record under construction now is the one the board reads.
Common Screwups
  • ×Safety-of-use integrity incident as LCPO — the first RWC generation cannot afford to be the generation that produced the Navy's first unauthorized autonomous weapons incident. The investigation that follows touches the TYCOM and DoD-level oversight, and the career is over.
  • ×NJP, financial misconduct, fraternization — career-ending at every paygrade; at Chief, it also sets the institutional precedent for what the first RW goat locker allowed.
  • ×Stopping personal PT and technical currency because 'I'm a Chief now' — the deckplate reads the anchor wearer who stopped growing faster than they read the one still in the fight.
  • ×Going public with disagreement on autonomous systems employment policy or program-office decisions. Take it in the office. Walk out aligned. The autonomous systems community is small.
  • ×Treating the RW LPOs' training and qualification output as their problem, not as the LCPO's accountability. The department's readiness number is the chief's number.

A Day in the Life

  • 0500–0600Personal PT or unit PT with the division — the LCPO who skips PT sends a message the deckplate reads before quarters.
  • 0700Division quarters; LCPO addresses all hands on the day's plan, safety word, and any personnel items.
  • 0715–0800LCPO-to-department-head sync: division status, day's mission or maintenance schedule, personnel or readiness issues to surface, section officer's priorities for the week.
  • 0800–1000LCPO walkthrough of spaces: systems status, log verification, quality-control check on overnight maintenance, RW1 check-in on training event status for the day.
  • 1000–1100Administrative and leadership work: eEVAL drafts, pipeline packet reviews, Chief board preparation, NEC pipeline status updates, counseling sessions with RW1s.
  • 1100–1200Department head sync preparation (if scheduled); readiness brief review; any pending safety-of-use authorization reviews.
  • 1200–1300Lunch; informal check-in with section on afternoon schedule.
  • 1300–1600Mission execution (if LCPO is operating as senior operator on a high-priority evolution) OR continued administrative and supervisory work: personnel counseling, training plan update, readiness report to section officer, goat-locker obligations.
  • 1600–1700End-of-day LCPO review: all division logs current, all discrepancies reported, all personnel accounted for. Section officer briefed on any evening items.
  • 1700 onwardLiberty or watch as required. Professional reading (SEA list, autonomous systems doctrine, CPO leadership literature) in the evening.

Weekly Cadence

The LCPO's week is structured around the division's output and the department head's schedule, not around the chief's personal preference. Monday through Wednesday in a garrison cycle tend to carry the heaviest administrative load — eEVAL work, pipeline packet reviews, training plan execution, TYCOM preparation. Thursday and Friday tend to carry the heavier leadership engagement — counseling sessions, mess obligations, section officer alignment. In a deployed or contingency cycle, the week compresses differently than it does in garrison. Mission cycles stack, maintenance windows shrink, and documentation discipline becomes harder to maintain precisely when it matters most. The LCPO who has built the habits in garrison — daily log verification, standing quality-control checks, pre-launch authorization review — maintains them in the deployed environment without having to rebuild from scratch. The goat locker obligations are also a weekly commitment in a way the LPO role is not. CPO 365 activities, initiation cycle (if applicable), mess meetings, and the informal mentoring relationships that the anchors create with junior sailors — these are the parts of the week that do not appear on the plan of the day but are real obligations the LCPO carries.

Key Skills — How to Drill Each

  1. 01
    Run an LCPO's mess of RWs — accountability, training, readiness, discipline, family, finance — with a weekly cadence the wardroom and department head can predict.
    Build the weekly cadence calendar at the beginning of each month and share it with the section officer and the department head: what is being trained, when the PMS inspections run, when the readiness reports go to the section officer, when the eEVAL profile reviews happen. The LCPO whose section runs on an internally predictable schedule does not have the department head calling to ask about things the section should already have communicated.
  2. 02
    Defend the department's unmanned systems readiness, safety-of-use records, and TYCOM inspection posture at command-level sync without rewriting.
    Run the mock inspection quarterly — pull the TYCOM checklist, walk through it against actual division records, identify and close gaps before the inspector arrives. Brief the readiness status in a format the section officer and the department head can take to the CO verbatim. The numbers that require your verbal interpretation to make sense are not ready to brief upward.
  3. 03
    Hold the line on autonomous systems safety-of-use standards under operational pressure.
    Know DoD Directive 3000.09 well enough to engage specifically — not 'the policy doesn't allow this' but 'Section 4(c) of the directive requires [specific human authorization] for [autonomy tier X]; the mission profile as briefed requires that authorization to be in place before launch.' The section officer who receives a specific policy reference from the LCPO takes the question to the wardroom differently than the one who receives a vague objection.
  4. 04
    Translate the rate's evolving doctrine into deckplate training decisions within 90 days of a new NAVADMIN or NTTP update.
    Subscribe to the NAVADMIN distribution for RW-relevant policy updates. Read every update the day it is published. For each update that affects training or qualification standards, build a briefing for the next weekly section sync: what changed, what it means for the section, what is being updated in the training plan. The LCPO whose section is always current on doctrine is the LCPO the section officer cites when the department head asks who is keeping the autonomy-warfare picture clean.

Manuals & References — What Chapters Matter

  • DoD Directive 3000.09 — Autonomous Weapons Systems
    You are the first stop when the CO, the XO, or the section officer has a question about autonomous weapons policy at the operational level. Know it by section and paragraph; brief it to the wardroom when the rate's employment scope requires it.
  • NTTP 3-20.8 and associated unmanned systems NTTP publications; JP 3-30 series for joint autonomous systems doctrine
    The NTTP and JP doctrine documents are what the section officer's mission planning is built on. The LCPO who can discuss the NTTP employment limits with the section officer as a peer — not as a technician who handles the maintenance side — is the LCPO who shapes how the command uses the rate.
  • MILPERSMAN — enlisted personnel actions at the chief threshold
    You are in the room for NJP, separation, NEC pipeline endorsements, commissioning program endorsements. Know the articles that govern what happens in those rooms.
  • CPO 365 / CPO Initiation guidance and Senior Enlisted Academy reading list
    The goat locker tradition you are building for RW draws on the broader CPO tradition. CPO 365 and the SEA reading list are the foundation of what it means to wear the anchors in any rating — the RW-specific version builds on that foundation.

Standards — How to Hit Each

  • TYCOM readiness assessment with no senior-enlisted-attributable safety-of-use findings.
    The safety-of-use standard is absolute. Every autonomous systems operation is logged with the authorization level, the human-control chain in place, and the post-mission outcome. Every deviation from the approved profile is documented and investigated. The LCPO who runs the division this way never has an attributable TYCOM finding; the one who allows informal practice to drift from formal policy eventually will.
  • Pipeline producing 1+ advanced NEC or commissioning selectee per year.
    Keep a pipeline tracker — every RW1 and RW2 in the division, their NEC pipeline status, their commissioning program eligibility, their career timeline. Review it with each sailor quarterly. The LCPO whose pipeline tracker is current can name the next selectee before the section officer asks.

Technical Mistakes — Concrete Consequences

  • Letting the goat locker serve as a refuge from a technically demanding rate.
    The first generation of RW chiefs who stop maintaining technical currency set the rate's institutional expectation that chiefs in this rating do not need to know the systems. That expectation, once established, is extremely difficult to reverse — and it produces chiefs who cannot have a substantive technical conversation with the program office or the section officer about the platforms the division operates.
  • Allowing imprecise safety-of-use documentation to become the section's informal standard.
    The documentation culture established by the first generation of RW LCPOs is the culture the rate carries forward. Informal safety-of-use records in 2025-2026 become the normalized institutional standard by 2030 — and the 2030 TYCOM inspector will not accept 'that is how we have always done it' as a compliance response.

Career Decisions at This Rank

  • Senior Enlisted Academy timing and command CMC slate preparation.
    The SEA fellowship (Naval War College Newport RI) is the PME milestone that gates Command Master Chief and Chief of the Boat consideration. The RWC who completes SEA early is competing for CMC/COB billets from a more mature position. The SEA application and selection process involves the CMC's endorsement and the TYCOM's review — work with the CMC early to understand the command's timeline and the TYCOM's SEA quota situation.
  • Pursue a program office or schoolhouse assignment vs. staying fleet-operational.
    The RW rate will need chiefs in program office billets (NAVSEA, NAVAIR unmanned systems program offices), schoolhouse roles (A-school instructor, curriculum development), and TYCOM staff positions to build the institutional infrastructure the rate needs for its second decade. These assignments build a different kind of record than a fleet-operational LCPO billet — broader policy visibility, program-management experience, and relationships with the officer community that the fleet chief does not build in the same way. The tradeoff is operational currency. Both paths can produce a competitive Senior Chief record; the question is which one fits the sailor's goals and the rate's needs at this stage.

How the Seat Varies by Unit Type

  • LCPO at a surface combatant during deployment
    The deployed RWC is the senior enlisted voice on unmanned systems employment for a ship that may be operating in a contested environment. The TYCOM is watching; the section officer is relying on the LCPO to hold the safety-of-use standards that the autonomous warfare community cannot afford to have violated on a deployed platform. The operational tempo and the decision-making pressure are both real.
  • LCPO at a schoolhouse or program office
    The RWC at a schoolhouse or NAVSEA/NAVAIR program office is shaping the rate from a different angle — curriculum, qualification standards, program-office doctrine integration. The deckplate is different (students or program staff instead of operators) and the accountability chain is different, but the standard the LCPO holds is the same. The first chiefs in these billets are writing the institutional knowledge base the fleet will draw on for decades.

What Good Looks Like at This Rank

The good RWC in the rate's formative years is the LCPO whose name the CO knows before the section officer finishes the sentence. His division's readiness numbers match the deck-plate, his RW1s are building Chief-board-competitive records, his safety-of-use documentation is in order, and the TYCOM inspection finds nothing attributable to his tenure as LCPO. Beyond the individual performance metrics, the good RWC in 2025-2026 is building something that extends past his own service: the institutional culture of the RW goat locker. What do the RW anchors mean? How does this mess hold itself? What does the chief enforce on himself before he enforces on the deckplate? These questions are being answered by the first cohort of chiefs in this rate, and the answers will be passed forward for decades. The RWC who takes that responsibility seriously — who models the technical currency he requires of his LPOs, who holds the safety-of-use line absolutely, who builds sailors who go on to become chiefs and senior chiefs with clean records — is doing more than performing well in the seat. He is writing the first chapter of what the RW rating's chief's mess tradition looks like. Write it with the same discipline you would want a sailor to bring to a pre-launch checklist.

Preview — The Next Rank

RWCS is a seat that may not be occupied in large numbers for the first several years of the rate's existence — the advancement pipeline for a rate established in February 2024 will take time to produce Senior Chiefs in volume. The first RWCS selectees are going to be in very small numbers and in very visible positions. That visibility is both an opportunity and an accountability: the first RW Senior Chiefs will be setting the rate's senior-enlisted institutional culture at every echelon from Type Commander staffs to program offices to major command CMC slates. The Senior Chief slate process for RW will involve board consideration of the rate's small and rapidly evolving advancement pool. The chief whose record reads cleanly across every paygrade — clean eEVALs, active pipeline output, strong readiness and inspection history, documented technical currency — is the chief the board advances in a small rate with limited comparative data. Do not wait for the rate to mature to build a competitive record. Build it now.
FAQ

RW E7 — Frequently Asked Questions

Q01What does a E7 RW (Robotics Warfare Specialist) actually do?
As RWC, you are LCPO of an unmanned systems or robotics warfare department — on a surface combatant, in an MCM command, in an expeditionary / special operations support element, or at a TYCOM unmanned systems staff — running 10-30 RWs and owning the enlisted execution from the deckplate up.
Q02What's the most important thing to know as a E7 RW?
You are one of the first RW chiefs.
Q03What does a typical day look like for a E7 RW?
Time-blocked day at the E7 RW rank tier: 0500–0600 Personal PT or unit PT with the division — the LCPO who skips PT sends a message the deckplate reads before quarters, 0700 Division quarters; LCPO addresses all hands on the day's plan, safety word, and any personnel items, 0715–0800 LCPO-to-department-head sync: division status, day's mission or maintenance schedule, personnel or readiness issues to surface, section officer's priorities for the week, 0800–1000 LCPO walkthrough of spaces: systems status, log verification, quality-control check on overnight maintenance,…
Q04What mistakes get E7 RW soldiers fired or relieved?
Safety-of-use integrity incident as LCPO — the first RWC generation cannot afford to be the generation that produced the Navy's first unauthorized autonomous weapons incident. The investigation that follows touches the TYCOM and DoD-level oversight, and the career is over; NJP, financial misconduct, fraternization — career-ending at every paygrade; at Chief, it also sets the institutional precedent for what the first RW goat locker allowed;…
Q05What career decisions matter most at the E7 RW rank tier?
Senior Enlisted Academy timing and command CMC slate preparation — The SEA fellowship (Naval War College Newport RI) is the PME milestone that gates Command Master Chief and Chief of the Boat consideration. The RWC who completes SEA early is competing for CMC/COB billets from a more mature position. The SEA application and selection process involves the CMC's endorsement and the TYCOM's review — work with the CMC early to understand the command's timeline and the TYCOM's SEA quota situation; Pursue a program office or schoolhouse assignment vs.…
Q06What's next after E7 for a RW (Robotics Warfare Specialist) in the Navy?
RWCS is a seat that may not be occupied in large numbers for the first several years of the rate's existence — the advancement pipeline for a rate established in February 2024 will take time to produce Senior Chiefs in volume.
Q07What manuals and regulations does a E7 RW need to know cold?
DoD Directive 3000.09 — Autonomous Weapons Systems (you are now the institutional voice on this policy at the command level; know it well enough to brief the CO).; NTTP 3-20.8 and associated unmanned systems tactical publications (current editions; you are responsible for keeping the department's doctrine library current).; OPNAVINST 5400 series — force structure and integration of unmanned systems in the operating forces.

This playbook has no tips yet. Be the first to share what you know.

Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards