Robotics Warfare Specialist

You are the first generation of a rating that did not exist two years ago. Nobody in the goat locker pinned their anchors as an RW — which means you are building the floor you will eventually stand on.

You are coming out of a pipeline that is still being refined: A-school at a Naval training command (verify the current course location and length before quoting — the curriculum and schoolhouse were still being formally established as of early 2025), covering foundational unmanned systems operation, robotics theory, autonomous vehicle maintenance, and the DoD Directive 3000.09 rules-of-engagement framework for autonomous weapons. When you check aboard — a surface combatant integrating unmanned surface or underwater vehicles, a Mine Countermeasures (MCM) command operating autonomous clearance systems, a Naval Special Warfare support element, or whatever billet the detailer cut you — you are the junior operator and maintainer on a platform that the senior enlisted may only have owned for a year or two themselves. You run pre-mission checks on unmanned systems, assist with launch and recovery operations, maintain operator logs, clean and inspect sensors, and stand whatever watch the command builds for its RW personnel. You study PQS (which may be freshly written), drill on the unmanned system safety procedures your command operates under, and do the unglamorous support work the section needs filled. The rate is new enough that you may be one of the first RWs your command has ever seen — treat that as a responsibility, not an excuse.

• 01Conduct pre-launch and post-recovery inspections on the unmanned systems the command operates — follow the approved checklist without improvising, every time, because the system that skips a step is the system the CO hears about.
• 02Operate the mission control station or operator console on your platform's UxV (unmanned surface, underwater, aerial, or ground vehicle) under direct supervision of a senior RW or qualified watch officer.
• 03Document mission logs, maintenance actions, and discrepancy reports cleanly — the log is the system's history and the LPO's first stop when something breaks in the next mission cycle.
• 04Apply DoD Directive 3000.09 safety protocols and human-in-the-loop / on-the-loop control disciplines as taught in the schoolhouse — never operate autonomous weapons modes beyond the authorization your chain of command has published.
• 05Conduct basic field maintenance and corrective maintenance at the operator level: battery changes, sensor cleaning, propulsor checks, tether inspections, and the maintenance steps the platform's operators manual authorizes.
• 06Knock out PQS line items on the LCPO's timeline and study for the NWAE cycle — the slow RWSN becomes the slow RW3 candidate, and the rate is too new to carry passengers.

• —DoD Directive 3000.09 — Autonomous Weapons Systems (the governing DoD policy on human-operator control requirements; every RW learns this before they touch an armed UxV).
• —OPNAVINST 3500 series — Navy training policy and readiness standards (the umbrella the rating's PQS and watchbill qualifications inherit from; pull the current version).
• —NTTP 3-20.8 (or current equivalent) — Unmanned Surface Vehicles and associated NTTP publications for unmanned systems employment; verify the current edition from the Navy Doctrine Library.
• —Platform-specific operators manual and maintenance instructions for the unmanned systems your command operates — these are the technical bibles your LPO expects you to own.
• —SECNAVINST 5239 series — Department of the Navy Cybersecurity / IA Program (RW platforms have significant cyber and C2 attack-surface; you learn this baseline before you are trusted alone in the spaces).
• —NAVPERS 18068 series — the NEC catalog; watch the RW-source NEC entries closely, because this rating's NEC pipeline is still being formally published; pull the current source-rating NAVADMIN before any career discussion.

• —All PQS line items signed off on the LCPO's timeline — the rate is new enough that PQS packages may be freshly written; own the current version and do not let the "rate is new" reality become a reason to coast.
• —Operator qualification on the specific unmanned systems your command fields, signed by the appropriate certifying authority before you operate unsupervised.
• —PRT Good Low or higher; BCA in standard. Robotics Warfare does not have an exemption from the PRT — and the ship operations, launch and recovery evolutions, and field environments this rating works in demand physical readiness.
• —Annual cybersecurity awareness training completed on deadline — RW platforms have software and C2 interfaces; a careless RW creates cyber risk the command cannot see coming.
• —Safety qualification on all autonomous systems the command operates, including emergency shutdown and human-override procedures — a missed safety step on an armed or high-energy system is a reportable incident and a command investigation.

• —Improvising a maintenance step or skipping a pre-launch checklist item because "we just did it an hour ago." The system does not know how long ago the last check was, and the CO will ask.
• —Operating an unmanned system in a mode or at an autonomy level you have not been authorized for by the chain of command. DoD Directive 3000.09 is not a suggestion; an unauthorized autonomy-level activation is a safety incident regardless of outcome.
• —Logging a mission action incompletely or correcting an error by overwriting instead of annotating. The log is a legal document on a government system; the correct action is an annotated correction, not an erasure.
• —Letting a battery charge cycle run unattended past the authorized monitoring interval. Thermal runaway on a LiPo or lithium-ion pack in an enclosed compartment is a fire, and the RWSN whose name was on the log is in the chain of investigation.
• —Posting any image, schematic, or operational detail about the unmanned systems to social media. Unmanned systems capabilities are OPSEC-sensitive; the intelligence value of even a seemingly innocuous photo is real, and the OPSEC officer will not be the only one who finds it.

The good RWSN is the sailor whose log entries the LPO does not rewrite, whose pre-launch checklists come back complete every time, and who asks the questions the schoolhouse raised about autonomous systems employment during the AAR instead of during the mission brief. By the end of the first year the senior RW trusts them on a controlled evolution, and the LCPO is already talking about the next pipeline slot.

You are a petty officer in a rating that is still writing its own legacy. The crow means you own a watch on the unmanned systems and at least one RWSN is watching how you carry it — without thirty years of chiefs telling you what that looks like for an RW.

You hold a qualified watch or operator position on the command's unmanned systems — whether that is the mission control station on an unmanned surface vehicle (USV) supporting surface warfare or mine countermeasures, the ground control station on an unmanned aerial vehicle (UAV) in an ISR or MCM role, the operator console on an unmanned underwater vehicle (UUV), or a combined-arms autonomous systems cell on a larger surface combatant or expeditionary command. You run day-to-day operations: pre-mission planning, mission execution under the watch officer's supervision, post-mission maintenance, discrepancy reporting, and the log that the section leader reads the next morning. You start training incoming RWSNs on PQS line items and the platform operator skills, and you execute the leading petty officer's training plan instead of just showing up for it. The NEC conversation is real now — pull the current source-rating NAVADMIN and look at the RW-coded NEC tracks that are being stood up (advanced operator, maintenance, systems integrator, special operations support); the pipeline is younger than the rate itself, and what your buddy heard last year may already have changed. The NWAE for RW2 is on your radar; study the BIB with the same discipline the IT3s and HM3s bring to theirs.

• 01Execute a complete mission sequence on the command's primary unmanned system — pre-mission check, launch, mission execution, recovery, post-mission maintenance — without the senior RW having to correct your sequence.
• 02Troubleshoot common operator-level faults on the mission control station and the unmanned vehicle: communication dropouts, GPS degradation, sensor faults, battery/power anomalies — and document the corrective action the maintenance crew needs.
• 03Train a new RWSN on a PQS line item or an operator skill and have them productive faster than the pipeline would alone — safety discipline first, platform skills second.
• 04Brief a short post-mission summary to the LPO or the section officer: mission profile flown or executed, any anomalies, system status, readiness for the next cycle — clean enough that the watchstander does not have to fill in the gaps.
• 05Maintain the mission logs, maintenance records, and configuration documentation for the unmanned systems the section owns — the record is the system's identity and the chain of custody the NAVAIR / NAVSEA / SYSCOM technical representative reads at the next configuration review.
• 06Execute emergency shutdown and override procedures on the autonomous systems the command operates — in the dark, in the rain, under time pressure — because the evolution that goes wrong does not announce itself.

• —DoD Directive 3000.09 — Autonomous Weapons Systems (you are now explaining this to RWSNs; know it by paragraph, not just by concept).
• —NTTP 3-20.8 (unmanned surface vehicles) and associated NTTP/NTTP publications for the unmanned system family your command operates (verify current editions from the Navy Doctrine Library before quoting).
• —Platform operator's and maintenance manual for the specific UxV your command fields — this is what the technical representative tests you on and what the SUPPO's PMS schedule maps to.
• —DoDM 8140.03 — Cyberspace Workforce Qualification (RW platforms have embedded software and C2 interfaces; if your billet is coded for a cyber work role, know your cert requirements).
• —NAVPERS 18068 series + current NEC source-rating NAVADMIN — read the RW NEC entries before you talk to the career counselor; verify codes, because the rate is new enough that NEC designators are still being formalized.
• —Current NWAE Bibliography for Advancement (BIB) for RW3 / RW2 — pull it from MyNavyHR and own it; the BIB is the test and the test is the BIB.

• —Full mission-qualified operator on the command's primary unmanned system, signed by the appropriate certifying authority and standing the position without supervisory override.
• —NWAE for RW2 prep documented on the LCPO's timeline; BIB study log defensible.
• —PRT Good Medium or better; BCA in standard. The launch-and-recovery evolutions and the expeditionary environments this rating operates in make physical readiness a real-work requirement, not a paper one.
• —All cybersecurity and IA training completed on schedule — RW platforms are cyber-attack surfaces and a lapsed cert on the operator creates exploitable risk.
• —At least one NEC pipeline packet in motion or clearly on the roadmap — advanced operator, maintenance NEC, or the special operations support track if your command supports NSW elements.

• —Making an undocumented configuration change to a mission system because "it fixes the fault." The technical-directive and configuration-management chain for unmanned systems is unforgiving; an undocumented mod is a reportable safety deviation and the section head's headache at the next TYCOM inspection.
• —Reporting a system "green" on mission readiness when it is not. The watch officer plans against the readiness board; an RW3 who inflates status to avoid a hard conversation creates the gap that surfaces in the middle of the mission.
• —Continuing a mission evolution when the human-override authority is unreachable. If the C2 link degrades and the authorization chain is broken, the published abort procedure is the only valid action — autonomous systems that keep running without valid command authority are the exact scenario DoD Directive 3000.09 was written to prevent.
• —Sharing mission imagery or sensor data outside cleared and authorized channels. Even degraded imagery from an unmanned system's sensor pass can reveal capability, geometry, and operational patterns; the OPSEC review is not a formality.
• —Skipping the post-mission maintenance because the next shift will "get to it." The discrepancy that goes unlogged is the discrepancy the next crew discovers mid-mission, and the RW3 whose name is last on the log is the first name in the debrief.

The good RW3 is the petty officer the LPO trusts on a night evolution without standing over his shoulder — because the pre-mission log is complete, the system came back in the same configuration it left in, and the post-mission discrepancy report was in the section leader's inbox before quarters the next morning. His NEC packet is in motion and the LCPO already knows his name for the RW2 slate.

You are the working senior RW — element lead in fact even when the title is unofficial. The rate is young enough that your knowledge of the platform and the doctrine is real equity, not just time-in-service.

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. You train and qualification-sign two-to-four RW3s and RWSNs, build the element training plan, and manage the mission readiness posture the LPO briefs to the section officer. You write the maintenance and operator documentation the platform technical representative and the TYCOM inspector read. You own the safety-of-use records for the autonomous systems under your charge. You mentor NEC packets — the advanced operator, the maintenance technician, or the NSW-support RW tracks — and counsel honestly (pull the current source-rating NAVADMIN before any packet discussion; the NEC catalog for this rating is still filling in). The NWAE for RW1 is no longer abstract; the eEVAL trait average against your peer RW2s is how the next slate reads your record. The rate is building its own senior NCO corps right now — you are part of the first generation of petty officers teaching the next one what an RW looks like.

• 01Lead 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.
• 02Run a maintainability and readiness tracking system for the unmanned systems the element owns — PMS completion, discrepancy closure, configuration-management records, and the TYCOM readiness report that matches the deck-plate status.
• 03Onboard a new RW3 or RWSN and have them qualified on the mission position faster than the schoolhouse pipeline alone, including safety-of-use and DoD Directive 3000.09 discipline from day one.
• 04Write a defensible post-mission report on any anomaly, safety deviation, or mission abort — timeline, what happened, immediate actions taken, root cause, corrective action, lessons learned — to the standard the technical representative and the chain of command can defend.
• 05Brief the element's readiness status and operator qualification posture to the LPO or the section officer in terms the wardroom will not rewrite — systems status, crew currency, next maintenance window.
• 06Identify an autonomy or safety-of-use concern in mission planning and raise it through the chain of command before the evolution launches, not during it.

• —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, not off the version on the share from last year.
• —OPNAVINST 3500 series — readiness standards; the section's readiness posture the LPO briefs to the section officer is built off the OPNAV standard.
• —Current NWAE BIB for RW1 — own it; the Enlisted Advancement Worksheet (EAW) clean and the study log defensible.
• —Safety Management System / Command Safety Investigation guidance applicable to unmanned systems operations at your command — when something goes wrong, the RW2 who can walk the chain of events in the safety-investigation framework is the one the chain of command trusts.

• —Lead operator or element leader qualification current on the command's primary unmanned system — the LPO does not schedule an evolution without knowing you can run it.
• —Element readiness — mission-capable systems, operator currency, PMS completion — at or above the command average every cycle.
• —NWAE for RW1 prep on the LCPO's timeline; eEVAL trait average and ranking that supports EP / MP; the LCPO knows your number before the board reads it.
• —PRT Good High or better; BCA in standard; warfare device pinned where the billet qualifies (SW / EXW / FMF as platform and assignment drive).
• —Safety-of-use and autonomous systems authorization records for the element in clean order — every evolution logged, every authorization documented, no retroactive corrections.

• —Letting an RW3 sit a lead operator position they are not fully certified on because the watchbill is short. The safety-of-use chain runs through you at RW2; the incident investigation will too.
• —Briefing mission readiness numbers you have not personally validated against the deck-plate status. The watch officer plans against the board; the anomaly that surfaces mid-mission because the board was wrong has your name on the maintenance record.
• —Accepting a verbal mission change request from a senior officer without getting it documented. Scope creep on an unmanned systems mission is how human-control discipline breaks; the written authorization record is what protects everyone.
• —Closing a safety or maintenance discrepancy without a verified corrective action because the mission cycle is tight. The discrepancy that goes "closed" without a real fix is the failure mode that surfaces on the next evolution.
• —Missing the window to update a safety-of-use record when the autonomy level or payload configuration changes. Configuration control on armed or high-energy unmanned systems is absolute; the record that does not match the system is an open investigative finding.

The good RW2 is the petty officer the LPO names when the section officer asks who is running the mission crew tonight. The element's readiness numbers brief without caveat, his RW3 has a qualification packet on the table, and his eEVAL bullets read action-result-impact instead of generic filler. He sits the RW1 NWAE on a documented study log and the goat locker already knows him.

You are the LPO. The Chief packet conversation is real. The wardroom calls you by name. And in a rate this new, the standard you set right now is the one your juniors will teach for the next decade.

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. You run 5-20 RWs, write four-to-six eEVALs per cycle for the RW2s and RW3s who are going to pick the next advancement slate, and build the department training plan. You defend the unmanned systems readiness posture at department-head sync. You manage the safety-of-use and configuration-control records that the TYCOM and technical representative inspect. You mentor the NEC pipeline — advanced operator, maintenance tech, NSW support track — and counsel honestly when a sailor is chasing the wrong path. The Chief board packet conversation is no longer a future concern — your LCPO is editing your record, your eEVAL profile is being built across the year, and the rating is young enough that the first RW Senior Chiefs will come from the cohort pinning RW1 right now. The Chief you become — or don't — shapes the rate's institutional character for the generation behind you.

• 01Run a division-level unmanned systems readiness brief to the department head — mission-capable systems, operator qualification currency, PMS status, safety-of-use record, open discrepancies — without hiding behind the section officer.
• 02Build and execute a six-month training and qualification plan that produces a fully mission-qualified lead operator and a maintenance-certified RW3 from your section.
• 03Navigate the interface between autonomous systems employment and legal / ROE compliance — brief the section on what DoD Directive 3000.09 requires from the human in the loop at each mission phase, and identify when a proposed mission plan violates that standard.
• 04Mentor an RW2 through a Chief packet build, an NEC pipeline application, or a commissioning program application — and counsel honestly about ADSO, sea-shore rotation math, and whether the path fits the sailor.
• 05Operate as the senior RW on a deployment, detachment, or expeditionary mission — including the call to recommend aborting an autonomous systems evolution when the safety-of-use conditions are not met.
• 06Translate the rate's technical and doctrinal development (new NAVADMIN policy, updated NTTP guidance, emerging system capabilities) into deckplate training decisions the RW2s execute.

• —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.
• —SECNAVINST 5239 series — DON Cybersecurity / IA Program; RW platforms at the C2 level are cyber-attack surfaces and the LPO is responsible for IA compliance at the division level.
• —NAVPERS 18068 series + current NEC source-rating NAVADMIN — you build NEC pipelines off the current cycle.
• —MILPERSMAN articles governing enlisted personnel actions — at RW1 you are in the room for NJP counseling, administrative separation, and advancement administration; know the framework.

• —Chief board packet under construction with the LCPO's eye on every line; eEVAL profile defensible at department head and CO level; warfare device pinned and current.
• —Division-level unmanned systems readiness, PMS completion, safety-of-use records, and configuration-management documentation defensible at TYCOM inspection — every cycle, no caveats.
• —Pipeline output — advanced NEC, NSW support qualification, commissioning programs — producing at least one selectee per year from your division.
• —Emerging doctrine and capability kept current — the rate is too new to coast on what was taught two years ago; the LPO reads the NAVADMINs and updates the training plan.
• —Zero safety-of-use integrity incidents under your LPO tenure. An unauthorized autonomy activation or an undocumented configuration change on a weapons-capable system is a reportable incident at the TYCOM level.

• —Briefing safety-of-use and readiness numbers you have not personally validated. The department head plans the mission off your board; the technical representative catches the gap at inspection and the LPO's record feels it.
• —Letting the rate's newness be an excuse for undisciplined documentation practices. The first generation of RW1s who build sloppy maintenance records and imprecise safety-of-use logs are creating the culture the rate will carry forward.
• —Going around the department head or the LCPO to the wardroom or the Type Commander on unmanned systems doctrine or employment questions. The chiefs talk; the next Chief board sees the pattern.
• —Allowing mission creep on an autonomous systems evolution without written authorization. The human-in-the-loop standard is non-negotiable; verbal mission expansion that was never formally authorized is where accidents and investigations originate.
• —Treating the NEC and commissioning mentoring conversation as a box to check. The RW1 who counsels an RW2 into the right pipeline — or honestly out of the wrong one — is building the rate's bench for the next decade.

The good RW1 is the LPO the LCPO trusts to run the unmanned systems division for a week without daily check-ins. His readiness and safety-of-use numbers brief without caveat; his eEVALs pick RWs above expectation; his pipeline produces advanced NEC, NSW support, and commissioning packets the wardroom signs without rewriting. He sits the Chief selection board with a record that reads itself — and in a rate this young, that record is also a chapter in the rating's own history.

You are the first generation of RW chiefs. The goat locker has never pinned an anchor on this rating before. The standard you build in the mess now is the one the Navy will judge this rate against for the next twenty years.

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. 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 inspection, or a safety investigation and identify the broken procedures before the inspector does. You build the next LPO. You mentor the next NEC pipeline, NSW support candidate, or commissioning selectee. You enforce the standard — including the autonomous weapons safety-of-use standards DoD Directive 3000.09 requires — in uniform, every day, while the deckplate watches. The rate is new enough that you may be literally writing the Chief's Mess tradition for Robotics Warfare. Do not treat that lightly.

• 01Run an LCPO's mess of RWs — accountability, training, readiness, discipline, family, finance — with a weekly cadence the wardroom and the department head can predict and depend on.
• 02Defend the department's unmanned systems readiness, safety-of-use records, configuration-management posture, and TYCOM inspection readiness at command-level sync without your numbers being rewritten.
• 03Operate as the senior enlisted unmanned systems voice on a real mission cycle, TYCOM readiness assessment, or safety investigation — your AAR is what the wardroom briefs up the chain.
• 04Mentor four-to-six RW1s into Chief-board-competitive candidates; counsel at least one advanced NEC pipeline, NSW support, or commissioning program to selection per year.
• 05Translate the rate's evolving doctrine — new NAVADMIN guidance, NTTP publication updates, emerging autonomous systems capabilities and ROE developments — into deckplate training decisions.
• 06Hold the line on autonomous systems safety-of-use standards even when the operational tempo pushes for shortcuts — the RWC who enforces DoD Directive 3000.09 under pressure builds the culture; the one who doesn't becomes the case study.

• —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.
• —MILPERSMAN — fluent in the enlisted personnel action articles; you are in the room for NJP, separation, and high-visibility safety investigation cases.
• —CPO 365 / CPO Initiation guidance, Senior Enlisted Academy reading list — the goat locker holds you to it, and in a rate this new you are also writing what it means for an RWC.
• —Current NAVADMIN messages on Robotics Warfare manning, NEC pipeline development, and force structure — pull each one as it drops; the rate is moving fast.

• —CPO 365 / Initiation transition complete; standing as a Chief in the mess at the deckplate level — not a Chief in title alone, and especially not in a rate where you are one of the first.
• —Department-level unmanned systems readiness, safety-of-use record integrity, and TYCOM inspection posture with no senior-enlisted-attributable findings during your LCPO tenure.
• —Pipeline producing 1+ advanced NEC, NSW support, or commissioning selectee per year — and the wardroom can name them.
• —Zero safety-of-use integrity incidents under your watch. An unauthorized autonomy activation or a falsified maintenance record on a weapons-capable platform is a career-ending event at any rank, and at RWC it takes the rate's reputation with it.
• —Emerging autonomy doctrine and NAVADMIN policy kept current in department training within 90 days of publication — the RWC who is always a generation behind is the RWC the department head calls the TYCOM staff to ask questions the Chief should be answering.

• —Letting the goat locker serve as a social refuge from a technically demanding rate. The deckplate sees a Chief who has stopped learning the systems as clearly as they see a Chief who has stopped doing PT — and in a rate this new, the Chief's technical credibility is the whole ballgame.
• —Allowing the "rate is still developing" reality to become a culture of undisciplined documentation and imprecise safety-of-use records. Sloppy records in the formative years of a rate become the institutional norm that takes a generation to reverse.
• —Going public with disagreement with the unmanned systems program office, NAVSEA, NAVAIR, or the commanding officer's employment decisions. The disagreement happens in the office; you walk out aligned. The goat locker enforces this.
• —Letting an RW1 LPO run a safety-of-use gap because he is "your guy" or "almost a Chief." The TYCOM inspector does not distinguish between the Chief who allowed it and the petty officer who created it.
• —Treating the commissioning and NEC mentoring conversation as a function of the pipeline, not of leadership. The RWCs who build the rate's next generation of warrant officers, LDOs, and senior operators from the ground up are the ones the rate's history records.

The good RWC is the LCPO the CO calls by name and the goat locker defends in the mess. His department's unmanned systems readiness and safety-of-use records brief without caveat; his RW1s pick up Chief; his TYCOM inspection findings are closed before the inspector asks. He is on the Senior Chief slate before the CMC has to ask, and the autonomous systems industry and the DoD unmanned programs office already know his name.

You are the senior enlisted Robotics Warfare voice in the Navy. There are not many of you yet. The policy choices made at your level in the next five years define what this rate becomes — choose carefully.

As RWCS or RWCM you run the senior enlisted unmanned and autonomous systems warfare posture for a Type Commander staff, an unmanned systems program element, a NAVSEA / NAVAIR unmanned systems acquisition or integration command, an expeditionary warfare headquarters, or wherever the force structure places the rate's senior enlisted. You write the eEVALs that pick the next Chief and Senior Chief slate. You sit at command-team sync as the senior enlisted voice on every unmanned systems talent decision — accession, NEC development, retention, credentialing, safety-of-use policy translation to the deckplate, commissioning program endorsements. You translate OPNAV-level autonomous systems strategy and DoD Directive 3000.09 policy updates into command-level training and doctrine decisions. You are, for this rate at this moment, a living institutional memory that the rate itself barely has yet. Start the post-Navy market plan early — defense technology industry, DoD autonomous systems program offices, RAND / MITRE / IDA, cleared robotics and AI companies — because the rate you built is the credential, and the people you developed are the legacy.

• 01Run a senior-enlisted command climate across an RW command or staff that produces certified operators, advanced NEC and commissioning program selectees, and retention at rates above the TYCOM average.
• 02Brief the CO, TYCOM, OPNAV, or DoD autonomous systems policy officials on the enlisted unmanned warfare workforce — capability, risk, training gaps, retention — in language the flag officer can carry up the chain without rewriting.
• 03Sit on Chief selection panels, Warrant Officer accession boards, advanced NEC credentialing reviews, and senior-enlisted promotion panels with the discipline and confidentiality the convening authority requires.
• 04Translate OPNAV / DoD autonomous systems policy — including DoD Directive 3000.09 revisions, autonomous weapons employment guidance, and unmanned systems integration NAVADMINs — into deckplate training decisions at the command level.
• 05Operate as the senior enlisted unmanned warfare voice during a real contingency, TYCOM readiness assessment, or program-office milestone review — your written input is what the O-6 and the SES sign.
• 06Run a Red Cross / casualty or serious-safety-incident response with the dignity it requires. In a rate this new, the senior chief handling the hard calls is also setting the standard.

• —DoD Directive 3000.09 — Autonomous Weapons Systems (you are involved in the policy discussions, not just the compliance reviews).
• —OPNAVINST 5400 series — force structure and unmanned systems integration across the operating forces (you help translate this to enlisted workforce decisions).
• —NTTP 3-20.8 and associated unmanned systems publications (current editions; your command keeps these current because you direct it).
• —MILPERSMAN — fluent in enlisted personnel actions at the senior-enlisted threshold; you are in the room for the NJP, separation, and high-visibility safety investigation cases that involve unmanned systems.
• —Senior Enlisted Academy (SEA, Naval War College Newport RI) reading list and CMC / COB Symposium materials — you translate doctrine and bring it down.
• —NAVADMIN messages on Robotics Warfare force structure, NEC pipeline development, and unmanned systems accession policy — pull each one as it drops and integrate it into command training before the RWCs ask where the update is.

• —SEA fellowship or equivalent senior-enlisted PME complete before competing for command CMC slate.
• —Command-level unmanned systems readiness assessment and TYCOM inspection passed without senior-enlisted-attributable safety-of-use findings during your tenure.
• —Advanced NEC, NSW support, and commissioning program accession pipeline producing 1+ selectee per year from your command — and the wardroom can name them.
• —eEVAL profile the senior rater can defend at command and TYCOM level — your rated chiefs are selecting for Senior Chief and Master Chief on the expected schedule.
• —Zero senior-enlisted-level integrity incidents — safety-of-use falsification, unauthorized autonomy activation, financial mismanagement, fraternization. One ends the career permanently, and in a rate this visible within the autonomous systems community, it does not stay quiet.

• —Pretending to be the current technical authority on a platform generation where you are a version behind. The senior RW who cannot distinguish between the autonomy levels of the systems the rate now fields loses authority the moment the program office representative steps into the room.
• —Letting an RWCS or RWC-led division drift on safety-of-use records and configuration-management documentation because "the inspection will find it." You own the enlisted execution at the command roll-up.
• —Treating the commissioning, NSW support, and advanced NEC mentoring conversation as transactional. The people you develop at RWCM build the Navy's unmanned warfare enlisted bench for the next twenty years.
• —Going public with disagreement with the TYCOM, OPNAV, or the commanding officer's autonomous systems employment decisions. Take it in the office. Walk out aligned. The flag community in the unmanned space is small.
• —Confusing the warm-up to retirement with the job. The deckplate reads who is still working the mission and who is already planning the contractor career. Until you walk out of the final formation, the formation is the job.

The good Master Chief Robotics Warfare Specialist is the senior enlisted voice the CO, TYCOM, and OPNAV-level autonomous systems officials name without prompting. His command's unmanned warfare enlisted slate produces the rate's next chiefs and senior chiefs; his commissioned and advanced NEC pipeline output is in the upper third of the rate; his safety-of-use record is the one NAVSEA program offices cite in workforce-development briefs. When he retires, the defense technology industry, the autonomous systems program offices, and the DoD unmanned warfare policy community have his number — because the rate he helped build is the credential, and the people he developed are the institution.