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
RWE6

Robotics Warfare Specialist

E-6 (Staff Sergeant) · Navy

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

You are the LPO. In a rate this new, the standard you build in this billet is the standard the next generation of RW LPOs inherits. The Chief board is real and the record being built right now is the record the board reads. The goat locker is watching whether you are constructing a rate or just occupying a paygrade.

The Honest MOS Read
Robotics Warfare Specialist First Class (RW1, E-6) is the LPO billet, and in the RW rate it carries more institutional weight than 'LPO' typically does in a mature rating. As one of the first generation of RW1s, you are actively writing what the division leader role looks like for this rate — the training plan templates, the qualification standards, the safety-of-use enforcement culture, the documentation practices that will be passed forward to the RW2s who become RW1s behind you. You run 5-20 RWs as LPO of an unmanned systems division — whether that is a surface ship's unmanned systems department, an MCM detachment, a NSW maritime unmanned systems cell, or another unmanned warfare billet. You write the eEVALs that pick the next RW2 and RW3 advancement slate. You build the department training plan and defend the unmanned systems readiness posture at department-head sync. You enforce the safety-of-use and configuration-management standards that DoD Directive 3000.09 and the platform technical authority require — not as bureaucratic overhead, but as the actual product of what an RW LPO owns. The NEC picture at RW1 should be fully established. The advanced operator, maintenance technician, or NSW support NEC is the technical identity your record carries into the Chief board. The RW1 whose record shows no pipeline NEC is the RW1 whose Chief packet is missing a foundational element. The Chief board timeline is real. The selection board for RW Chief Petty Officers will read the record you have built across the last six to eight years, and the eEVAL profile being built at RW1 is the most weight-carrying piece of that record. The LCPO is editing your record and evaluating the package every quarter. Work with him actively — not reactively. One thing that is specific to the RW rate at this moment: the first generation of RW chiefs will come from the RW1s currently in the seat. They will set the goat locker culture for the rate. The RW1 who brings the same discipline to the LPO role that a mature rate's first class brings — clean documentation, enforced standards, active development of the sailors under him — is building the rate's institutional character. The one who coasts on the rate's newness as an excuse for lower standards is also building the rate's institutional character. Choose which one carefully.
Career Arc
  • 01Pin RW1 via advancement board; assume LPO role with a written division training plan, qualification matrix, and readiness tracking system established within the first 60 days.
  • 02First full eEVAL cycle as LPO — write RW2 and RW3 evaluations that the section officer signs without rewriting; maintain the LCPO's ranking awareness throughout the cycle.
  • 03Advanced NEC current and pipeline output — at least one RW2 advanced NEC or commissioning program application produced within the first year.
  • 04Chief board packet under active construction with the LCPO; eEVAL profile reviewed and gaps identified.
  • 05Warfare device qualification current; professional military education appropriate to the E-6 level completed (CPO Selectee preparation reading, Senior Enlisted leadership coursework as available).
  • 06NSW support qualification, additional platform qualifications, or advanced technical credentials that distinguish the Chief packet from a baseline record.
Common Screwups
  • ×Safety-of-use integrity incident as LPO — an unauthorized autonomy activation or falsified maintenance record that occurs while you hold LPO responsibility is career-ending and triggers TYCOM-level investigation.
  • ×NJP, DUI, drug pop, or financial misconduct — ends the Chief packet and creates the eEVAL notation the board reads.
  • ×Delivering inaccurate readiness reports to the section officer because the deck-plate status is not what you reported. As LPO, the gap between reported and actual readiness is an integrity issue, not an administrative error.
  • ×Failing to build and deliver a functioning division training plan — the LPO whose section cannot produce qualified operators is not fulfilling the primary function of the billet.
  • ×Going around the LCPO to the wardroom or the section officer on personnel, readiness, or policy questions. The chain runs through the chief; the pattern of circumvention shows up in the Chief board package.

A Day in the Life

  • 0530–0620PT — LPO participates and models the standard, not just supervises.
  • 0700Division quarters — LPO addresses the section; LCPO observes periodically.
  • 0715–0800LPO sync with LCPO: system status, personnel status, day's mission or maintenance schedule, any personnel or readiness issues to surface.
  • 0800–1000Division work period: oversee pre-mission checks or maintenance execution, verify PMS compliance, conduct random quality-control walk of spaces and documentation.
  • 1000–1100Section training period: run or oversee the training event on the LPO's weekly plan; sign PQS line items for qualifying sailors.
  • 1100–1230Administrative work: eEVAL drafts, training plan update, readiness report preparation, NEC pipeline packet reviews, department head sync preparation.
  • 1230–1330Lunch; brief the section on afternoon plan and any schedule changes.
  • 1330–1600Mission execution (if scheduled and the LPO is the most qualified senior operator on the evolution) or continued administrative and supervisory work: personnel counseling, advancement study review, Chief packet development.
  • 1600–1700Section debrief (if evolution occurred); final readiness and log status verification before end of workday; LCPO update on any open items.
  • 1700 onwardLiberty or continued watch. Chief packet study and professional reading in the evening.

Weekly Cadence

The LPO's week is structured around the division's output, not around the LPO's personal work preferences. The first obligation of each morning is knowing the division's status — system readiness, personnel accountability, mission cycle posture — before anyone has to ask. The LCPO who can call the LPO at 0630 and get a clean status brief without hearing 'let me check' has a LPO he can brief up the chain. The training planning function is the most time-consuming discretionary work of the week. The weekly training schedule — what skill, what format, what evaluation, who runs it — is the LPO's product. In a new rate, that product often has to be built from primary sources (NTTP, DoD Directive 3000.09, platform operator's manual, the skills the section officer knows the command needs) rather than from a polished template the previous LPO handed over. Build the template and document it so the sailor who inherits the billet gets something he can use. The administrative load — eEVALs, NEC pipeline packets, commissioning program endorsements, advancement recommendations, personnel counseling — lands most heavily at the end of the evaluation cycle and at the beginning of the advancement season. The LPO who manages this load on a rolling basis (drafting eEVAL bullets quarterly, keeping pipeline packets current throughout the year) does not experience the compression that the LPO who saves everything for the last three weeks faces.

Key Skills — How to Drill Each

  1. 01
    Run a division-level unmanned systems readiness brief to the department head without hiding behind the section officer.
    Build the readiness brief from the deck-plate up: walk the spaces, verify the systems status yourself, confirm the operator qualification currency from the tracking document, check the PMS completion against the schedule. The LPO who briefs numbers someone else gave him is the LPO the department head stops trusting when the first gap surfaces. Brief it in the format the department head uses; if the format is not specified, build one and use it consistently.
  2. 02
    Build and execute a six-month training and qualification plan that produces a fully mission-qualified lead operator and a maintenance-credentialed RW3.
    Start with the end state: who needs to be qualified on what by when, what resources the command has, what the LCPO expects to see at the six-month mark. Work backward: qualification board date, practical preparation period, PQS completion window, knowledge familiarization period, start date. Put it in writing. Share it with the LCPO and the section officer. Update it when the schedule changes. The plan the LPO can defend at any point in the cycle is the plan the section officer cites by name in the next eEVAL endorsement.
  3. 03
    Navigate the interface between autonomous systems employment and DoD Directive 3000.09 authorization requirements.
    Know the policy by section: what autonomy tiers are defined, what human control is required at each tier, what the authorization chain looks like for weapons-capable systems. When the section officer proposes a mission profile that bumps against the policy boundary, the LPO raises the specific question before the launch — not as an objection but as a clarification that produces the written authorization the chain of command needs. The LPO who does not raise the question before the launch is the LPO named in the incident report after.
  4. 04
    Mentor an RW2 through a Chief packet build, an NEC pipeline application, or a commissioning program application.
    The mentoring conversation is not a transaction — it is an ongoing relationship. Know the sailor's record, their ASVAB scores, their NEC pipeline status, their eEVAL profile, their family and financial situation (if relevant to major ADSO decisions). The LPO who knows each sailor's career picture well enough to give specific advice — not generic encouragement — is the LPO whose sailors get selected.

Manuals & References — What Chapters Matter

  • DoD Directive 3000.09 — Autonomous Weapons Systems
    At RW1 you are the first stop when the section officer has a question about what the policy requires from the chain of command. Know it well enough to brief it authoritatively to the department head — not just to explain it to junior sailors.
  • NTTP 3-20.8 and associated unmanned systems NTTP publications, and JP 3-30 series for joint autonomous systems employment
    At the LPO level you are contributing to operational planning for unmanned systems missions, not just executing the plan someone else built. The NTTP and joint doctrine documents are the sources the section officer uses to build mission profiles; the LPO who knows those documents is the one who contributes technically credible input to the planning process.
  • MILPERSMAN — articles governing enlisted personnel actions
    At RW1 you are in the room for NJP counseling, administrative action, NEC pipeline endorsements, and the ADSO decisions that affect your sailors' lives. Know the MILPERSMAN articles that govern the actions you will be part of initiating or executing.

Standards — How to Hit Each

  • Chief board packet under active construction; eEVAL profile defensible at department head and CO level.
    Ask the LCPO to review your full eEVAL profile — every evaluation from the beginning of your career — and identify what the board will see as gaps. Fix what can be fixed before the submission window. The Chief board reads the entire record; the RW1 who only builds the last three years of his record is entering the board with the first three visible.
  • Division-level readiness, PMS, safety-of-use records, and configuration documentation defensible at TYCOM inspection.
    Run your own mock inspection quarterly: pull the TYCOM inspection checklist (verify the current version from the Type Commander's administrative guidance), walk through each item against your actual division records, identify the gaps, and fix them before the inspector arrives. The LPO whose division fails a TYCOM inspection on documentation is the LPO who did not do this.

Technical Mistakes — Concrete Consequences

  • Briefing safety-of-use and readiness numbers you have not personally validated.
    The department head plans mission scheduling against the LPO's readiness brief. The anomaly that surfaces mid-mission because the brief was inflated does not stay in the section — it surfaces at department head sync, at the section officer's credibility review, and in the LPO's next eEVAL endorsement. The LCPO who discovers that the LPO briefed unvalidated numbers acts on that information at Chief board time.
  • Letting the rate's newness be the institutional excuse for imprecise documentation.
    The documentation culture of a new rating is established in its first five years of fleet operation. The RW1 LPOs who accept imprecise logs, incomplete configuration records, and informal safety-of-use tracking in 2025-2026 are creating the institutional norms the rate will carry forward for a generation. The TYCOM inspector who finds those gaps in 2030 will not accept 'we were a new rate' as an explanation.

Career Decisions at This Rank

  • Chief board submission timing: when is the record competitive?
    The RW rate's Chief board timeline will depend on when the Navy establishes sufficient advancement quotas for the rate — pull the current NAVADMIN for Chief selection board eligibility and the year-group considerations for a rate established in 2024. For the earliest cohorts, the advancement timeline to Chief may be compressed relative to a mature rating, or it may require a longer window while the selectee pool builds. The LCPO's honest read of your record against the rate's emerging standard is the most accurate guide; the board does not grade on a curve for a new rate.
  • Long-term assignment: stay in the unmanned systems warfare specialty vs. apply for a broadening assignment (joint duty, instructor duty, program office).
    The RW rate's institutional development will benefit from sailors who have experienced the rate from multiple angles — fleet operator, schoolhouse instructor, program office liaison, joint duty position. At RW1, a broadening assignment (instructor at the RW A-school, assignment to NAVSEA or NAVAIR for an unmanned systems program office, joint duty with a DOD autonomous systems organization) builds a Chief packet that reads differently from a sailor who only has fleet-operator billets. The downside is that a long time away from the operational fleet may narrow the technical currency that the rate's emerging goat locker expects its chiefs to carry.

How the Seat Varies by Unit Type

  • LPO at a surface combatant with an unmanned systems department
    The LPO on a surface ship runs the division within the ship's operational schedule, which does not stop for unmanned systems maintenance windows or qualification boards. The LPO who can integrate the division's readiness and training cycle into the ship's plan of the week — without needing special accommodations the CO has to personally approve — is the LPO the XO describes as 'running a tight division' at the next O-call.
  • LPO at a program office or schoolhouse
    The RW1 LPO at a schoolhouse or program office is working in a less operationally structured environment, with more latitude to shape training curriculum and qualification standards. The risk is losing the operational credibility that a fleet operator assignment builds. Keep at least one foot in the operational world — seek out fleet exercises, underway evolutions, or temporary additional duty opportunities with deploying unmanned systems units — so the Chief board record shows both the program-building work and the operational grounding.

What Good Looks Like at This Rank

The good RW1 in 2025-2026 is the LPO the LCPO can brief without checking. The division's readiness numbers, PMS completion, safety-of-use record, and qualification matrix are all current, documented, and match the deck-plate reality. The section officer does not have to ask for a status update; the update is in his inbox on the schedule the LPO set at the beginning of the cycle. In a rate this new, the good RW1 is also a documentarian — not in the bureaucratic sense, but in the institutional sense. The training plans, qualification standards, and safety-of-use enforcement culture that this LPO builds will be what the RW2s who become RW1s behind him inherit and build on. The LPO who treats that responsibility casually is also making a choice about what the rate becomes. The Chief board sees the record across six to eight years. The RW1 who built clean eEVAL bullets at RW2 and RW3, who held the NEC pipeline together, who produced sailors the wardroom named without prompting, and who ran a division the TYCOM inspector found in order — that RW1 has a record the board reads without confusion. Sit the board with a record like that.

Preview — The Next Rank

RWC is the anchor. The goat locker for RW is being founded right now, by the cohort of sailors who will be the first to pin the CPO anchors in this rate. The expectations are higher in a new rate's formative chief's mess than in a mature one, because there is no tradition to fall back on — only the standard the first chiefs establish. The Chief board process in a new rate also has characteristics worth understanding: the board reads the record on its merits without the benchmark of decades of RW chief records to compare against. A competitive record is competitive because of what it says, not because of where it places in a historical distribution. The RW1 who enters the board with clean eEVALs across every paygrade, an active pipeline output, a NEC-current record, and a division readiness history with no inspection findings is the candidate the board advances — regardless of the rate's youth. After the anchors go on, the job changes in the fundamental way it changes in every rate between E-6 and E-7: the deckplate is your product and the sailor's development is your mission. In RW, there is the additional dimension that you are also building the institutional culture of a rating. Take both seriously.
FAQ

RW E6 — Frequently Asked Questions

Q01What does a E6 RW (Robotics Warfare Specialist) actually do?
You are LPO of an RW division or unmanned systems element — a surface ship's unmanned systems department, an MCM detachment, a NSW maritime unmanned systems cell, or whatever billet the current force structure has created around autonomous and unmanned warfare capability.
Q02What's the most important thing to know as a E6 RW?
You are the LPO.
Q03What does a typical day look like for a E6 RW?
Time-blocked day at the E6 RW rank tier: 0530–0620 PT — LPO participates and models the standard, not just supervises, 0700 Division quarters — LPO addresses the section; LCPO observes periodically, 0715–0800 LPO sync with LCPO: system status, personnel status, day's mission or maintenance schedule, any personnel or readiness issues to surface, 0800–1000 Division work period: oversee pre-mission checks or maintenance execution, verify PMS compliance, conduct random quality-control walk of spaces and documentation,…
Q04What mistakes get E6 RW soldiers fired or relieved?
Safety-of-use integrity incident as LPO — an unauthorized autonomy activation or falsified maintenance record that occurs while you hold LPO responsibility is career-ending and triggers TYCOM-level investigation; NJP, DUI, drug pop, or financial misconduct — ends the Chief packet and creates the eEVAL notation the board reads; Delivering inaccurate readiness reports to the section officer because the deck-plate status is not what you reported. As LPO,…
Q05What career decisions matter most at the E6 RW rank tier?
Chief board submission timing: when is the record competitive? — The RW rate's Chief board timeline will depend on when the Navy establishes sufficient advancement quotas for the rate — pull the current NAVADMIN for Chief selection board eligibility and the year-group considerations for a rate established in 2024. For the earliest cohorts, the advancement timeline to Chief may be compressed relative to a mature rating, or it may require a longer window while the selectee pool builds. The LCPO's honest read of your record against the rate's emerging standard is the most accurate guide;…
Q06What's next after E6 for a RW (Robotics Warfare Specialist) in the Navy?
RWC is the anchor.
Q07What manuals and regulations does a E6 RW need to know cold?
DoD Directive 3000.09 — Autonomous Weapons Systems (you are the first stop when the wardroom has a question about what the policy requires; know it by section).; NTTP 3-20.8 and associated unmanned systems NTTP publications (current editions); JP 3-30 series for joint autonomous systems doctrine where your command operates in a joint context.; OPNAVINST 5400 series — Navy organization and force structure policy; the authority structure for unmanned systems integration 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