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
RWE5

Robotics Warfare Specialist

E-5 (Sergeant) · Navy

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

RW2 is where the rate's first generation of real section leaders is forming. The element-leader role is yours to define right now, and the eEVAL you build across this tour is the foundation for the Chief packet you'll need in three-to-four years. The rate is too new to have a deep bench — which means the anchor the goat locker pins will have your thumbprints on it.

The Honest MOS Read
Robotics Warfare Specialist Second Class (RW2, E-5) is the rank at which you shift from 'qualified operator' to 'section-level technical lead.' You are running an element — a crew section on a USV mission cycle, a UUV maintenance cell, the mission-data function on an ISR/autonomous systems cell, or the RW-side of an expeditionary detachment — and the distinction between what you do and what a petty officer first class does is being actively defined by the cohort of RW2s currently holding the seat. The operational load is heavier and less structured than it was at RW3. You are building training plans, not just executing them. You are writing the log format the section uses, not just filling it in. You are raising concerns about mission authorization and safety-of-use with the section officer before the evolution, not after. The DoD Directive 3000.09 human-in-the-loop discipline is now something you enforce on your element, not just observe for yourself. The NEC question should be answered by RW2. The advanced operator, maintenance technician, or NSW support credential is the technical identity that makes the RW2's record look different from the unqualified petty officer at the same paygrade. If you arrived at RW2 without a pipeline NEC in hand or clearly in progress, that gap is visible on your eEVAL ranking and it narrows the NWAE FMS competitiveness the LCPO is calculating for the RW1 slate. The eEVAL dynamic in a new rating at the E-5 level is worth understanding precisely. The Navy Enlisted Advancement System ranks petty officers within their peer group at rating. An RW2 with a small peer group at a command where the LCPO is writing for two or three E-5s faces a different ranking environment than an HM2 in a large medical department. The LPO knows your number; ask him and use that information to direct your professional effort in the right places before the evaluation period closes. The rate is building its senior NCO corps right now. The RW2 who approaches the element-leader role with the same discipline a mature rating's petty officer brings — clean documentation, enforced safety-of-use standards, active training program, honest readiness reporting — is not just doing good work at his current paygrade; he is shaping what an RW chief looks like when the rate produces its first Senior Chiefs. That is not a motivational poster sentence. It is the actual situation, and the RW2s currently holding the seat understand it or they do not.
Career Arc
  • 01Pin RW2 via NWAE; achieve element-lead qualification on the command's primary unmanned system and stand the position without daily supervisory override.
  • 02NEC pipeline completion — advanced operator, maintenance technician, or NSW support qualification — producing a billet-specific technical credential that distinguishes the record.
  • 03Build and execute the first formal section training plan: qualify two RW3s to operator standard within a six-month window.
  • 04NWAE for RW1 study cycle begun; EAW (Enlisted Advancement Worksheet) clean and BIB study log defensible.
  • 05Warfare device pinned where the billet allows (SW, EXW, FMF based on assignment) and PQS record current.
  • 06Chief packet horizon enters the planning conversation with the LCPO — four-to-five years out, but the eEVAL record being built now is the record the board reads.
Common Screwups
  • ×Safety-of-use integrity failure as element lead — an unauthorized autonomy activation or falsified maintenance record on a weapons-capable system while you hold the lead responsibility. This is career-ending at RW2 and triggers investigation at the TYCOM level.
  • ×NJP, DUI, or drug pop — closes every advancement window, every commissioning program, every NSW support qualification path.
  • ×Undocumented configuration modification to a mission system — even a fix that works is an open inspection finding and a potential safety investigation trigger if it bypasses the configuration-management chain.
  • ×Sustained low eEVAL performance without the section-leader performance the rank requires — an RW2 who cannot produce a defensible training plan or run an element is not building the Chief packet record the rate needs its senior NCOs to have.
  • ×OPSEC breach at the element-lead level — sharing mission data, sensor output, or capability details about autonomous systems in an unsecured channel is worse at RW2 than at RWSN because you now have access to more operationally relevant information.

A Day in the Life

  • 0500–0530Personal PT if the command does not run morning unit PT, OR preparation for the unit PT formation at 0600.
  • 0600–0700Unit PT formation and exercise, then shower/hygiene.
  • 0700Division quarters — accountability, plan of the day, LCPO passes guidance to the section.
  • 0715–0800Section sync with LPO: system status, mission or maintenance schedule for the day, training events, any personnel issues.
  • 0800–1000Element work period: mission planning and pre-mission checks (if evolution is scheduled), OR maintenance — PMS execution, corrective repair, configuration-management documentation update.
  • 1000–1100RW3 / RWSN training period: PQS review, operator skills drill, post-mission debrief walk-through with junior operators, OR own PME / NWAE study if no training event.
  • 1100–1200Final pre-launch checks or continued maintenance; readiness status update to LPO.
  • 1200–1300Lunch; brief the on-coming section on any open items if a watch rotation applies.
  • 1300–1530Mission execution (if scheduled): crew brief, launch, mission profile monitoring, recovery. OR maintenance: corrective maintenance, sub-system inspection, battery service, log completion.
  • 1530–1700Post-evolution debrief (if mission occurred): what happened, anomalies, lessons learned, system readiness for next cycle. Readiness report to LPO. Log entries verified complete.
  • 1700 onwardLiberty in port; continued watch if underway or contingency cycle. NWAE study or NEC pipeline preparation in the evening.

Weekly Cadence

The RW2's week is structured around the element's mission and maintenance cycle, not around a personal schedule. In a surface combatant during a pre-deployment workup, the week may compress into two or three days of intensive mission execution followed by two days of maintenance and documentation catch-up. The documentation gap that builds during a compressed mission cycle is the gap the TYCOM inspector finds six weeks later — it is the RW2's responsibility to not let that accumulate. The training planning function is where the most discretionary time investment happens. The weekly section training period is the RW2's product to own: what skill is being practiced, what PQS line items are being signed, what evaluation is being run. The LCPO assigns the time block; the RW2 fills it with something defensible. A section training period where the junior operators watched a PowerPoint and went back to maintenance is a wasted event; a period where an operator ran an emergency-procedure drill cold and the element debriefed what happened is worth writing about in the eEVAL. The most significant weekly rhythm change in a new rating is the absence of a deep historical training plan template. The RW2 is often writing the section training schedule from a relatively blank starting point, informed by the platform operator's manual, the NTTP, and whatever institutional knowledge the senior RW1s and the LPO carry. Build your own template from those sources and update it when doctrine or platform updates change the relevant skills.

Key Skills — How to Drill Each

  1. 01
    Lead a mission crew on a complete unmanned systems operation — pre-mission planning, crew brief, execution, recovery, debrief — to a standard the section officer can brief without rewriting.
    The pre-mission brief is the investment that prevents the debrief from being a damage-control exercise. Cover: mission profile, communications plan, abort criteria, emergency procedures, crew responsibilities at each phase, authorization confirmation for the autonomy level the mission requires. Brief it as if the section officer is going to test you on the abort criteria mid-evolution — because on a real contingency, he might. After recovery, run the debrief before the section officer asks: what happened, what deviated, what you decided, what you'd change.
  2. 02
    Run the maintainability and readiness tracking system for the unmanned systems the element owns — PMS completion, discrepancy closure, configuration records, readiness reporting.
    Build a personal tracking system that the LPO can read without your verbal explanation: systems status by day, PMS cards due and completed, discrepancies open and closed, configuration-change records, readiness statement for the next mission cycle. The section officer who can open your tracking document at 0530 and know the element's posture without calling you is the section officer who trusts you with the night evolution.
  3. 03
    Onboard a new RW3 or RWSN and have them qualified on the mission position faster than the schoolhouse pipeline alone.
    The onboarding plan is not verbal — write it down. Which PQS line items in what sequence, who signs each one, when the qualification board is scheduled, what the board will test. Meet with the incoming sailor in the first week and walk through the plan together. Check in weekly. The sailors who qualify faster than the pipeline alone qualify faster because someone built a deliberate plan and held them to it.
  4. 04
    Write a defensible post-mission report on any anomaly, safety deviation, or mission abort.
    Use a consistent structure: (1) timeline — what happened and when, (2) what was observed — sensor readings, system behavior, operator actions, (3) immediate actions taken and by whom, (4) root cause assessment based on available evidence, (5) corrective action taken or recommended, (6) lessons learned for the section. The report that the technical representative and the section officer can both read and get the same picture from is a good report. The one that requires your verbal explanation to make sense is a draft.
  5. 05
    Identify an autonomy or safety-of-use concern in mission planning and raise it through the chain of command before the evolution launches.
    Know the DoD Directive 3000.09 framework well enough to identify where a proposed mission plan exceeds the authorization level in the standing orders. When you find it, raise it specifically — 'this mission profile requires [autonomy mode X] and our standing authorization only covers [autonomy mode Y]; do we have an exception or do we modify the profile?' That question, asked in the pre-mission brief, is the kind of question the section officer remembers at eEVAL time. The question not asked is the one that surfaces in the post-incident report.

Manuals & References — What Chapters Matter

  • DoD Directive 3000.09 — Autonomous Weapons Systems
    At RW2 you enforce this on your element — brief it to new RW3s, identify when a mission plan exceeds what it authorizes, and raise the concern before the launch, not after. Know the policy well enough to answer the section officer's questions without the schoolhouse summary sheet.
  • NTTP 3-20.8 and associated unmanned systems NTTP publications
    The NTTP documents govern tactical employment limits — sea states, communication protocols, mission abort criteria. At the element-lead level you are contributing to mission planning; knowing what the NTTP authorizes and prohibits is how you contribute something technically credible to the pre-mission brief, not just logistics.
  • NAVPERS 18068 series + current NEC source-rating NAVADMIN for the RW rating
    At RW2 you are mentoring NEC pipeline packets for your RW3s and yourself. Pull the current source-rating NAVADMIN before every packet conversation — the NEC designators and school-date availability for a two-year-old rating change between cycles. The LPO and the career counselor both expect you to know the current state of the pipeline.
  • OPNAVINST 3500 series — readiness standards and training policy
    The element readiness posture you brief to the LPO is measured against the OPNAV standard. Know what the standard requires for the unmanned systems mission area at your command's mission level so your readiness report is built against a documented benchmark, not just against what seemed reasonable last month.

Standards — How to Hit Each

  • Element readiness — mission-capable systems, operator currency, PMS completion — at or above the command average every cycle.
    Define 'command average' at the beginning of each maintenance cycle by talking to the LCPO and looking at the readiness report. Then build the element's work plan to exceed that benchmark by one step: if the command average for PMS completion is 85%, your element targets 95%. The element that is consistently above average on measurable readiness metrics is the element the section officer defends at department head sync without caveat.
  • NWAE for RW1 prep on the LCPO's timeline; eEVAL trait average supporting EP/MP.
    The eEVAL at RW2 is determined by how the LCPO ranks you against peer RW2s in the command. Ask the LCPO directly where you are ranked and what the gap is between your current performance and EP-quality performance. Build the study log for the NWAE around the current BIB; verify the BIB for the current cycle from MyNavyHR.
  • Lead operator or element-leader qualification current on the command's primary unmanned system.
    The qualification currency standard for the element lead is stricter than for a qualified operator — you are the person who signs the RW3's currency log. Keep your own currency current by participating in every mission evolution the schedule allows, even when it would be easier to delegate the evolution down. The element lead who stops operating loses the technical credibility the rank requires.

Technical Mistakes — Concrete Consequences

  • Letting an RW3 sit a lead-operator position they are not certified on because the watchbill is short.
    The safety-of-use authorization chain runs through the qualified operator, not the watchbill scheduler. An unqualified operator on a lead position creates a gap in the authorization chain that does not become visible until something goes wrong — at which point the element lead's signature on the watchbill is the first thing the investigating officer reads. Fill the watch with a qualified operator or take the position yourself.
  • Briefing mission readiness numbers to the section officer that you have not personally validated against the deck-plate status.
    The section officer plans mission execution against your readiness statement. The discrepancy that surfaces mid-mission because the readiness board was optimistic has the RW2's name on the maintenance record and the section officer's credibility at department head sync on the line. Verify the numbers before you brief them.
  • Closing a maintenance discrepancy without a verified corrective action because the mission cycle is tight.
    A discrepancy closed without a real fix is not closed — it is deferred, and the next crew who discovers it mid-mission will find your name on the previous entry. On a weapons-capable unmanned system, an unresolved mechanical or software fault that produces a mission anomaly initiates a safety investigation that starts with the maintenance record.

Career Decisions at This Rank

  • Chief packet preparation: start building the record now vs. waiting until RW1 to focus on the board.
    The Chief Petty Officer selection board does not read the record you have in the year you submit — it reads the career record you built across the last six to eight years. For an RW2 who pinned the crow on a rate established in 2024, that means the Chief packet is largely built at the RW2 and RW1 tiers, not after. The sailor who waits until RW1 to start building the record is entering the board process several evaluation cycles behind. Talk to your LCPO about what a competitive Chief packet looks like for the RW rate specifically — the answer may differ from what applies to a mature rating — and start constructing it now.
  • LDO / CWO commissioning program vs. continued enlisted advancement.
    The RW rate will eventually develop a warrant officer or LDO accession pathway for sailors whose technical depth and leadership potential points toward the commissioned side. Verify the current accession options with the current officer programs detailer — as of early 2025, the RW-specific commissioning pathways were still being developed. The enlisted-to-officer conversation is legitimate to have at RW2 if the record supports it; the career counselor and the commanding officer are the right resources for the current program eligibility requirements.
  • NSW support track at RW2 vs. building depth in the fleet assignment.
    The NSW support qualification (if the billet structure makes it available at the RW2 level — verify with the current NAVADMIN) is operationally demanding and selectivity-filtered. The RW2 who pursues it gains access to the rate's most sophisticated employment scenarios early, but also commits to a higher operational tempo and a longer ADSO in a specialized billet. It is the right move for the sailor who wants the hardest operational seat; it is not the right move for the sailor who wants operational credibility on paper but prefers a more predictable shore-rotation lifestyle.

How the Seat Varies by Unit Type

  • Surface combatant (DDG, LCS, FFG(X)) integrating unmanned surface vehicle capabilities
    The RW2 on a surface combatant runs an element that integrates directly into the ship's warfare mission — USV operations supporting surface warfare, MCM, or ISR are executed within the ship's operational schedule, and the element lead's role is to make the unmanned systems piece work on whatever timeline the ship sets. The physical environment is demanding: deck evolutions in sea state, compressed maintenance windows between watch rotations, and a wardroom that varies widely in its familiarity with what the systems can do.
  • Expeditionary or joint task force autonomous systems cell
    RW2s in expeditionary billets may be operating in a joint environment where the Army, Air Force, and Marine Corps operators working alongside them have different autonomy frameworks and different levels of DoD Directive 3000.09 familiarity. The RW2 who knows his own service's policy framework and can communicate it clearly to a joint team is doing a different kind of work than operating within a Navy-only section. Expect the mission profile to be more varied, the billet structure to be less standardized, and the documentation requirements to sometimes feel like they are being written as you go.

What Good Looks Like at This Rank

The good RW2 in 2025-2026 is the petty officer whose element runs clean when the LPO is on leave. The training plan is posted, the PMS cards are current, the operator qualifications are tracked, the readiness report matches the physical state of the systems, and the section officer does not have to call for an update on anything the RW2 is responsible for. In a rate that is still establishing its institutional norms, the RW2 who builds a disciplined section is doing more than performing well at his current paygrade — he is demonstrating what an RW element leader looks like. The chiefs and senior chiefs who evaluate RW2 eEVALs over the next several years are going to be forming their view of what the rate's second class should be capable of. Be the example they calibrate the standard against, not the problem they use to define the floor. The Chief packet horizon is four-to-five years away, but the record being built right now is the one the board reads. Every clean element debrief, every documented qualification, every mission anomaly caught before the evolution and raised properly through the chain — that is the record accumulating on the eEVAL profile. The RW2 who understands that does not wait for someone to tell him what good looks like.

Preview — The Next Rank

RW1 is the LPO billet. The shift from element lead to LPO is significant in every rate; in RW, it is also the moment when the sailor becomes one of the primary shapers of what the RW rating looks like to the wardroom, the TYCOM, and the sailors who will join the rate over the next five years. The LPO in RW right now is writing the standards — training plans, qualification matrices, safety-of-use enforcement culture — that will be passed forward. That is a larger responsibility than the title implies, and the RW2 who approaches the RW1 promotion with that understanding will use the tenure differently than the one who sees it as a normal promotion step. The Chief packet conversation becomes an active planning exercise at RW1. The eEVAL at RW1 is the most weight-carrying evaluation in the sailor's record for the Chief board, and the LCPO is building the next Chief candidate from the first day the sailor pins the chevron. The RW1 who shows up to that conversation already understanding what a competitive RW Chief packet looks like — because he asked at RW2 — is already ahead.
FAQ

RW E5 — Frequently Asked Questions

Q01What does a E5 RW (Robotics Warfare Specialist) actually do?
You run an operator or maintenance element on the command's unmanned systems — leading a crew section on a USV mission, running the UUV maintenance cell, managing the mission data for an UAV/ISR element, or owning the RW-side of an expeditionary MCM detachment.
Q02What's the most important thing to know as a E5 RW?
RW2 is where the rate's first generation of real section leaders is forming.
Q03What does a typical day look like for a E5 RW?
Time-blocked day at the E5 RW rank tier: 0500–0530 Personal PT if the command does not run morning unit PT, OR preparation for the unit PT formation at 0600, 0600–0700 Unit PT formation and exercise, then shower/hygiene, 0700 Division quarters — accountability, plan of the day, LCPO passes guidance to the section, 0715–0800 Section sync with LPO: system status, mission or maintenance schedule for the day, training events, any personnel issues, 0800–1000 Element work period: mission planning and pre-mission checks (if evolution is scheduled), OR maintenance — PMS execution, corrective repair,…
Q04What mistakes get E5 RW soldiers fired or relieved?
Safety-of-use integrity failure as element lead — an unauthorized autonomy activation or falsified maintenance record on a weapons-capable system while you hold the lead responsibility. This is career-ending at RW2 and triggers investigation at the TYCOM level; NJP, DUI, or drug pop — closes every advancement window, every commissioning program, every NSW support qualification path;…
Q05What career decisions matter most at the E5 RW rank tier?
Chief packet preparation: start building the record now vs. waiting until RW1 to focus on the board — The Chief Petty Officer selection board does not read the record you have in the year you submit — it reads the career record you built across the last six to eight years. For an RW2 who pinned the crow on a rate established in 2024, that means the Chief packet is largely built at the RW2 and RW1 tiers, not after. The sailor who waits until RW1 to start building the record is entering the board process several evaluation cycles behind.…
Q06What's next after E5 for a RW (Robotics Warfare Specialist) in the Navy?
RW1 is the LPO billet.
Q07What manuals and regulations does a E5 RW need to know cold?
DoD Directive 3000.09 — Autonomous Weapons Systems (you are now the section's subject-matter expert; brief it to new arrivals and challenge any mission plan that does not account for it).; NTTP 3-20.8 and associated unmanned systems tactical publications for your platform family (current editions; verify from the Navy Doctrine Library before instructing).; NAVPERS 18068 series + current NEC source-rating NAVADMIN — you mentor career packets off this,…

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