Skip to main content
HonestMOS
●InvestigationsCongress made VA disability claims free to file. An entire industry charges veterans anyway — and nobody can stop them.→
←Back to ET Electronics Technician — overview, pay, training, civilian translation, reviews
ETE6

Electronics Technician

E-6 (Staff Sergeant) · Navy

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

ET1 is where the Chief board becomes a current administrative action, not a future aspiration. The LCPO is already reading your eEVAL profile against the board's selection criteria, and the combat systems officer is deciding whether your name goes on the pre-INSURV workup brief as the LPO who owns the division or as the one who still needs management. CDI qualification is not optional at this rank — it is the credential that makes you the division's maintenance authority. Get it if you do not have it.

The Honest MOS Read
Electronics Technician First Class (ET1, E-6) is the LPO seat — and the transition from section lead to LPO is larger than the single paygrade suggests. At ET2 you were the senior petty officer the section reported through; at ET1 you are the division's first enlisted leader, the person the combat systems officer briefs around, the person the ETs read for the standard when the wardroom is not looking. The LCPO is present but is operating at the department level; the division runs on your daily execution. The LPO function at ET1 is four parallel responsibilities running simultaneously. First, maintenance accountability: you own the division's CSMP posture, the PMS completion rate across all work centers, the ESWP tag-out log authority, and the pre-INSURV and ISIC inspection readiness — not by doing the maintenance yourself but by building the system that produces clean documentation and defensible numbers every cycle. The combat systems officer should be able to brief the division's readiness status from the weekly report you hand him without recasting the numbers. Second, personnel development: you write four to six eEVALs per cycle that determine the next ET2 and ET3 advancement slate. The eEVAL is not a performance review — it is the advancement document. The ET2 whose eEVAL bullets do not name measurable section outcomes is the ET2 whose FMS suffers for it, and that is on you. Third, NEC and commissioning pipeline management: you are producing NEC-pipeline entries, LDO and CWO electronics track packets, and STA-21 and MECP commissioning applications from your division, tracked and briefable to the LCPO by name and target cycle. Fourth, your own Chief board preparation — the package is being built now, in this tour, not the week before submission. CDI (Collateral Duty Inspector) qualification is the ET1's maintenance-authority credential. The CDI is the command's designated inspector for maintenance actions that require a higher-level review before signing off — a qualified CDI is the person whose signature on a CSMP closure means the action is complete to the command's satisfaction, not just the petty officer's. On a surface combatant with a complex electronics suite, the ET1 who is not CDI-qualified is an LPO whose maintenance authority is limited in ways the LCPO has to work around. If you checked into the ET1 billet without CDI qualification, that is the first administrative action after assuming the LPO role. INSURV preparation is the annual accountability cycle for the ET1 LPO on a surface combatant. INSURV — the Board of Inspection and Survey — is the highest-stakes maintenance inspection the ship faces, and the electronics and combat systems division's material readiness is one of the board's primary assessment areas. The ET1 who owns the division's INSURV posture means: every CSMP discrepancy is current and accurately described, every deferred MRC has written authorization on file, every calibration record is accurate and the test sequence was actually run, and every tag-out log entry is complete. The INSURV inspector does not accept the verbal explanation; he reads the documentation and audits the numbers. The pre-INSURV workup is when the ET1 discovers what the division's actual documentation posture is — and the LPO who finds surprises during the workup is the LPO who was not managing the posture throughout the year. The ISIC relationship at ET1 is the external accountability layer the LPO learns to navigate directly. The ISIC (Immediate Superior in Command) type commander inspection program conducts periodic readiness assessments of the ship's combat systems and electronics posture. The ET1 LPO will brief the ISIC inspection team directly on the division's readiness numbers, maintenance posture, and discrepancy status. This is not a brief you rehearse the day before — it is the division's actual posture, which means the documentation has to be clean, current, and defensible before the inspectors arrive. The ET1 whose readiness brief is backed by actual documentation is the LPO the combat systems officer does not have to coach before the ISIC visit. The Chief board conversation at ET1 is a current administrative action. The LCPO is reading the ET1's eEVAL profile, conducting quarterly counseling sessions that are specifically about the board, and making an assessment of whether this ET1 is on the Chief-board-competitive trajectory. The ET1 who is not having that conversation explicitly — asking the LCPO where the gaps are, what the eEVAL profile needs to say, what the command endorsement looks like — is the ET1 who discovers at submission that the package is not competitive. The Chief board is built from the daily leadership of the ET1 tour; the package submission formalizes what was already visible in the record.
Career Arc
  • 01Check into the ET1 LPO billet with CDI qualification in progress or already awarded — the first 60 days establish whether the combat systems officer sees an LPO who owns the division or one who still needs the LCPO to backstop maintenance decisions.
  • 02CSMP posture and PMS completion rate brought to a defensible baseline within the first quarter — division's documentation posture known to the ET1 personally, not by report alone.
  • 03First eEVAL cycle: four-to-six evaluations written with measurable accomplishments, section outcomes, and pipeline production bullets the senior rater can defend at a wardroom board.
  • 04NEC pipeline and commissioning program output running: at least one ET2 NEC packet submitted per year, LDO or CWO electronics track conversation active with the eligible ET2s, STA-21 or MECP referral made for any qualifying sailor.
  • 05Chief board preparation active with LCPO: quarterly counseling sessions specifically about the board, eEVAL profile reviewed for competitiveness, command endorsement conversation started at the 12-month mark of the ET1 tour.
  • 06INSURV preparation owned from the first inspection cycle — not as a reactive workup event but as the annual culmination of year-round documentation discipline.
  • 07Senior Enlisted Academy application under consideration at Senior Chief threshold; post-Navy market research started by the 18-month mark — Raytheon, L3Harris, Northrop, NAVSEASYSCOM GS pipeline, FTSC civilian technical track.
Common Screwups
  • ×Assuming the Chief board packet will assemble itself from a good eEVAL record. The board reads the package as a whole — the warfare device, the NEC, the command endorsement, the education credit, the eEVAL narrative across the ET1 tour — and the ET1 who has not been managing the package with the LCPO's specific guidance discovers at submission that one element is missing or weak. The gap that could have been addressed eighteen months out cannot be addressed the week before the package is due.
  • ×Going around the LCPO to the combat systems officer or the department head on a division-level technical decision or personnel matter. The goat locker tracks the ET1 who works around the chain at this rank more carefully than it tracked the ET2, because the ET1 is in the LCPO's direct span of influence and the combat systems officer will route the conversation back through the LCPO before the ET1 returns to the space. Walk in with the disagreement; walk out aligned.
  • ×Letting the CSMP documentation drift because the maintenance tempo is high and the inspectors are not inbound. The ET1 who cleans up the CSMP two weeks before an ISIC visit is the LPO the ISIC inspector identifies — retroactive CSMP entries are visible in the OMMS-NG timestamp audit trail, and the inspector reading a cluster of corrective action entries dated the week before the visit knows what he is looking at. The documentation has to be current throughout the year, not current when it matters.
  • ×Writing eEVAL bullets that describe activities rather than outcomes — 'performed PMS maintenance on assigned systems' rather than 'restored four CSMP category-A discrepancies within 72 hours, maintaining zero deadline impact during TSTA-III.' The eEVAL bullet is an advancement document; the activity description advances no one.
  • ×Treating the CDI qualification as optional because the LCPO can cover the sign-off authority gaps. The CDI qualification is the command's maintenance authority credential, and the ET1 LPO who is not CDI-qualified is limiting the division's independent maintenance execution in ways that follow the ET1's record into the Chief board review.

A Day in the Life

  • 0500-0545Wake. If duty section ET1, review the overnight maintenance log and watch turnover: any system casualties that opened overnight, any CSMP entries that need LPO review before quarters, any tag-out status changes that require the ESWP log update before the safety petty officer's morning check.
  • 0545-0630Command or divisional PT. The ET1 LPO's presence and performance at PT sets the standard the division reads — no excuses, no falling out, no leading from the quarterdeck.
  • 0630-0730Hygiene, chow, utilities on. Pre-quarters: pull the division's OMMS-NG section report, review CSMP status across all work centers, check parts-pipeline ETA updates overnight, confirm the day's PMS assignments against the MRC due list, review the ESWP tag-out log for active tags affecting today's maintenance. Brief yourself on the division's posture before the LCPO briefs the department.
  • 0730-0800Quarters. LCPO puts out department-level tasking. As LPO, you have 90 seconds to brief the division: today's maintenance assignments by system and by ET, the training evolution scheduled for the afternoon, any CSMP follow-up from overnight, any ESWP tag-out status affecting today's work. Own the brief — it is your division.
  • 0800-1130Primary maintenance period. On a complex casualty day, the ET1 is on the bench for the multi-system troubleshoot — coordinating ET2 assignments across systems, running the TM fault-isolation on the primary fault while the ET2s work the secondary systems, and building the wardroom brief from what is being found in real time. On a PMS execution day, the ET1 is verifying ET2 CSMP closure countersignatures, CDI-signing maintenance actions that require LPO inspection authority, and walking the work centers for documentation quality — not supervising the maintenance, but confirming the paper trail matches the work.
  • 1130-1230Chow. Before leaving the space: tool accountability check for all work centers, tag-out log review if tags are active, OMMS-NG quick check on any MRCs that were supposed to close this morning.
  • 1230-1430Division training and personnel development block. ET2 NEC counseling session if scheduled — pull the current NAVADMIN before the session. eEVAL drafting during the evaluation window. Chief board package review with the LCPO if a quarterly counseling session is on the schedule. INSURV preparation mock-walk of a specific system family if the annual cycle requires it.
  • 1430-1530Administrative and readiness documentation block. Weekly readiness status document updated for the combat systems officer. Parts-ordering pipeline checked — overdue parts get a call to the supply petty officer now, not at Friday review. CSMP accuracy check against the 3-M coordinator's current report. Any eEVAL input drafts for the current period.
  • 1530-1600End of day. Division tool sub-accounts reconciled, tag-out log reviewed and secured, CSMP status updated, overnight watch turnover notes prepared for any open system discrepancies. If a INSURV or ISIC visit is inbound, the documentation readiness check runs now — not the day before the inspection.
  • 1600-1630Liberty or duty section watch. Duty: the ET1 is the senior electronics watchstander on the duty section — casualty response calls route to the ET1 overnight, and the ESWP authorization for after-hours maintenance runs through the ET1 on duty.
  • 1630-1900Personal time. Chief board preparation work — reviewing the current Chief board NAVADMIN, tracking eEVAL narrative gaps identified at the last LCPO counseling, building the education credit documentation. Post-Navy market research at the 18-month mark: Raytheon, L3Harris, NAVSEASYSCOM GS pipeline, FTSC civilian technical positions.
  • 1900-2100ET2 counseling follow-ups if anyone had a personnel or career question during the day. Prep the next day's maintenance plan and the weekly readiness brief draft.
  • Pre-INSURV workup (6-8 weeks out)The ET1's day compresses to maintenance-and-documentation-only. Every CSMP entry is reviewed for accuracy, every deferred MRC authorization is verified on file, every calibration record is audited for completeness. The ET1 who finds surprises during the workup is the one who was not running the monthly internal audits. The one who arrives at the workup with a clean documentation posture experiences the workup as a verification of existing practice.
  • Deployment / WESTPAC surgeLPO independent execution — no daily LCPO check-ins for the maintenance decisions, the CSMP entries, and the ET2 development. The division's performance during surge is the most visible test of the ET1's LPO tenure. The wardroom and the LCPO are watching whether the standard holds when the schedule is 12-14 hours and the parts pipeline is measured in weeks.

Weekly Cadence

Monday is the heaviest planning day. After quarters the ET1 updates the weekly OMMS-NG due list against the maintenance plan, confirms ET2 system assignments for the week, checks the parts pipeline for any ETAs that affect this week's schedule, and builds the weekly readiness status document for the combat systems officer. The LCPO's guidance at Monday quarters defines the department-level priorities; the ET1 translates those priorities into specific work-center assignments before the division breaks for the maintenance period. The LPO who arrives at Monday quarters with the week's maintenance plan already drafted — system by system, ET by ET — is the one the LCPO trusts to run the division during his absence. Tuesday and Wednesday are core production days. Complex troubleshoots run in the primary maintenance periods, CDI sign-offs run as maintenance actions complete, ET2 CSMP closure countersignatures run throughout both days. The ET1's most consequential action on Tuesday and Wednesday is the documentation verification before every CDI sign-off and every CSMP closure countersignature — the safety check that the ET2's work was complete and the system is actually operational before the entry closes. The CSMP that closes without the operability verification is the CSMP that fails the next inspection, and the countersignature on it is the ET1's. Thursday carries the eEVAL and personnel pipeline administrative load. ET2 NEC counseling sessions are scheduled in the afternoon — with the current NAVADMIN on the table. eEVAL draft work runs Thursday if the evaluation window is open. Friday is the weekly wrap: CSMP accuracy audited against the 3-M coordinator's report, parts pipeline checked, tag-out log reviewed, and the weekly counseling touchpoint with the LCPO — division status summary, pipeline names and status, Chief board package progress update. The ET1 who brings a prepared division summary to the Friday touchpoint — maintenance posture, pipeline status, eEVAL drafts in progress — is the LPO the LCPO describes as managing the division independently. Pre-INSURV and pre-ISIC periods collapse the administrative rhythm into maintenance-and-documentation-only; the eEVAL and pipeline work compresses into stand-down windows, but the CSMP verification discipline and the CDI sign-off standard never compress.

Key Skills — How to Drill Each

  1. 01
    Run a department-level PMS review — CSMP status, deferred MRCs across all work centers, parts pipeline, upcoming ISIC and INSURV liabilities — in a brief the combat systems officer can defend at the CO's readiness sync without rewriting the numbers.
    Build a standard weekly status document: one page, organized by system, with current CSMP discrepancies listed by category (CAT-A mission-limiting, CAT-B degraded, CAT-C administrative), deferred MRCs with authorization dates and deferral reasons, parts on order with expected ETA, and any qualifications expiring in the next 30 days. Present it to the combat systems officer in the format he uses for the CO's sync — which means you need to know what that format looks like before you build the document. The ET1 whose weekly brief the combat systems officer drops into his slide deck without reformatting is the LPO the CO's sync refers to by name. The one whose brief requires a rewrite every week is the LPO who has not learned the format his chain uses.
  2. 02
    Write an eEVAL block the senior rater can defend at a wardroom board: measurable accomplishments, named outcomes, not generic maintenance descriptors.
    Draft every eEVAL in this structure: action verb + specific object + measurable result + command-level impact. 'Managed 3-M PMS program for 14 electronics systems' tells the board nothing. 'Closed 11 of 12 CSMP category-A discrepancies prior to TSTA-III, sustaining zero mission-limiting downtime during the ship's final pre-deployment assessment' tells the board the sailor owns the maintenance program and the ship went to deployment ready. Collect the data during the evaluation period — CSMP closure rates, INSURV finding counts, NEC pipeline output, watch qualification board pass rates — so the draft in the final month is populating a format with real numbers, not reconstructing a story from memory.
  3. 03
    Lead a complex multi-system casualty restoration — electronics fault implicating power distribution, cooling, and deckplate MRC simultaneously — coordinate across work centers, and report status to the wardroom with the TM reference behind every decision.
    The multi-system casualty at LPO level is a coordination problem as much as a technical one. Assign the ET2s to specific systems by their NEC and system familiarity, establish a status check interval (every 30 minutes during active restoration, not when someone feels like reporting), and own the wardroom brief yourself: 'SPY-1 is degraded due to power supply fault in the PDC. I have ET2 [name] on the power distribution isolation and ET2 [name] on the SPY-1 bench. TM procedure [chapter and section] governs the repair sequence. Timeline is two hours to partial restoration, four hours to full capacity.' That brief answers every question before it is asked and does not require the combat systems officer to follow up for status.
  4. 04
    Defend a combat systems readiness brief to the department head and XO — current CSMP discrepancies, deferred PMS, equipment deadlined, TSTA and INSURV liabilities — in plain language with a specific bring-back date for every open item.
    The bring-back date is the discipline the wardroom measures the LPO against. Every open item in the readiness brief needs a date the LPO is committing to, not a vague 'in work' or 'as soon as parts arrive.' 'Parts ordered 14 days ago, expected arrival this Friday, repair takes six hours, system back to fully mission capable by Saturday afternoon' is a commitment. 'Waiting on parts' is a status without accountability. Practice the brief format with the LCPO before the first department-head sync; the ET1 who walks in with a brief that has bring-back dates on every item is the one the department head stops asking follow-up questions.
  5. 05
    Mentor an ET2's NWAE / NEC / LDO / commissioning packet from idea to selection — and counsel honestly when the path is wrong for the sailor's actual career goals and family situation.
    The honest mentoring session covers what the brochure does not: the duty station after the C-school, the operational tempo of the billet the NEC feeds, the family impact of a specific pipeline against the ET2's actual family situation, and the LDO board's competitive requirements against the ET2's current eEVAL profile and NEC record. Pull the current NAVADMIN before any NEC session. For LDO/CWO conversations, read the MILPERSMAN articles governing the selection process and introduce the ET2 to a working LDO or CWO in the electronics community — not a recruiter, an actual officer who went through it. The ET2 who gets pushed into the wrong path by an ET1 too busy to counsel honestly is the ET2 asking how to reclass in three years, and that reflects in the ET1's pipeline production record.
  6. 06
    Own the INSURV preparation cycle from January through the inspection date — not as a workup event but as the annual culmination of year-round documentation discipline.
    The ET1 who treats INSURV preparation as a pre-inspection activity is the one who finds documentation gaps at T-minus-30 days that require retroactive CSMP entries — visible in the audit trail and read by the inspector as the cleanup they are. The ET1 who treats INSURV as the annual external validation of a maintenance discipline he has been running all year arrives at the inspection with clean documentation and a readable maintenance history. Starting in January: monthly internal mock-inspection of one system family per month, quarterly CSMP accuracy audit against the 3-M coordinator's report, and a running list of deferred MRCs with written authorizations on file. The INSURV inspector reads the whole year; make the whole year defensible.

Manuals & References — What Chapters Matter

  • NSTM Chapter 320 — Electronics and NSTM Chapter 300 — Electric Plant / ESWP
    At ET1 LPO level, NSTM Chapter 320 is the document you cite when an ET2 brings you a technical question and the document the ISIC inspector cites when he finds a maintenance deviation. Know which section governs which category of maintenance action — not by memory, but by having read the chapters with enough depth that you can navigate to the relevant section faster than the inspector can cite it. Chapter 300 ESWP is the authority you apply when you authorize a tag-out and the authority you cite when the safety officer asks why the isolation was required. At ET1 you are signing tag-out log entries; know the governing document.
  • NAVSEA system TMs across the full combat systems suite the division owns: SPY-1 / Aegis Weapons System (SWOS/NAWS pipeline docs), AN/SPS-67, AN/SPS-48E, AN/UYK computer systems, AN/WSC-3 SATCOM, navigation suites
    The ET1 LPO does not have every TM memorized — but knows which TM covers which installed configuration for every system in the division, and can navigate the ET2 to the right chapter in under two minutes when the casualty is live. Configuration control matters at LPO level: the engineering change history of the installed equipment determines which TM version applies, and the ET1 who allows maintenance to run off a superseded procedure is the LPO responsible for the finding when the INSURV inspector asks what procedure was used.
  • OPNAVINST 4790.4 — Ships 3-M Systems Procedures (current series)
    At ET1 you are the person defending the division's 3-M posture at ISIC and INSURV level. Know the deferral authorization chapters, the CSMP entry requirements, the corrective action documentation standards, and the 3-M coordinator's audit rights — well enough to brief the combat systems officer on what the inspector will look at before the inspection, not after. The ET1 LPO who can open OPNAVINST 4790.4 to the relevant chapter in the inspector's presence and discuss the governing language is the LPO who can mount a substantive defense. The one who says 'I thought we were in compliance' without the document is not mounting anything.
  • OPNAVINST 3430 series — Electronics and EW policy and applicable NAVSEAINST / NAVSEASYSCOM instructions for the weapons and combat systems suite
    The policy layer above the equipment TMs governs what is authorized at the division level and what requires external technical authority. At ET1 LPO level, knowing which OPNAVINST governs the systems you brief to the combat systems officer is the difference between a technically defensible brief and one that the department head questions. RADHAZ controls, combat systems interface requirements, and Type Commander maintenance authority are all in this layer; the ET1 who has not read the governing OPNAVINST for the systems he owns is the LPO who finds out about it during a safety investigation.
  • MILPERSMAN — enlisted personnel action articles at LPO visibility: advancement, retention, NJP, separation, CDI designation
    At ET1 you are writing eEVALs, managing NEC packets, counseling sailors through re-enlistment decisions, and potentially initiating administrative actions that the LCPO reviews before routing. Know the MILPERSMAN articles governing the actions you are executing or recommending — not as a JAG substitute, but as the competent LPO who arrives at the LCPO's office with the relevant article pulled and a specific question, rather than a general description of what happened and a request for guidance.
  • NAVPERS 18068 Vol II + the current NEC source-rating NAVADMIN + current Chief Petty Officer Selection Board NAVADMIN
    The NEC pipeline mentoring and the Chief board preparation both run off current documents. The NAVPERS 18068 catalog entries and the NEC source-rating NAVADMIN are the basis for every NEC counseling session — pull the current cycle's NAVADMIN before any packet conversation, not last year's. The Chief board NAVADMIN is the document that defines what the board reviews and what the competitive package looks like for the current board year — pull it and read it with the LCPO in the same session.

Standards — How to Hit Each

  • CDI qualification awarded within the first 90 days of the ET1 LPO billet — the LPO who is not CDI-qualified is limiting the division's maintenance authority from the first week.
    The CDI qualification process requires the command's training program, a command-specific examination, and designation by the commanding officer per OPNAVINST 4790.4. The ET1 who arrives at the LPO billet without CDI should initiate the qualification process at the first Monday meeting with the LCPO — not at the six-month counseling. Ask the LCPO for the command's CDI training materials, build the qualification calendar, and brief the LCPO at the 30-day mark on progress. The combat systems officer will ask at the first department-head sync whether the ET1 is CDI-qualified; the answer should be 'in process, completion date is [specific date],' not 'I am working on it.'
  • Division-level CSMP and PMS posture defensible at department head and CO level every cycle — zero ET1-attributable CAT-I maintenance findings at INSURV during the LPO tenure.
    Zero CAT-I findings during an INSURV tenure is not luck — it is the result of a maintenance discipline the LPO built and enforced throughout the year. Monthly internal audits of CSMP accuracy, quarterly reviews of deferred MRC authorizations, and pre-inspection mock-walks of the documentation posture are the tools. The ET1 who discovers a CAT-I finding during the actual INSURV inspection is the LPO who did not run the monthly internal audit. The CAT-I finding with the ET1's name on the department roster goes into the Chief board review; the zero-finding INSURV tenure is the record the Chief board reads.
  • Chief board packet competitive with LCPO validation — eEVAL profile, warfare device, NEC, education credit, command endorsement all addressed before T-minus-12 months from submission.
    T-minus-12 months is the last window to address structural gaps in the Chief board package. The eEVAL narrative needs to show section leadership outcomes across the ET1 tour — not just maintenance performance, but personnel development, pipeline production, and command-level impact. The warfare device should be current and backed by a qualification board record the LCPO can cite. The NEC should be in the record and the C-school documented. Education credit — CLEP, CCAF, college courses — should be verified in the service record. The command endorsement conversation with the commanding officer should have happened by T-minus-18 months. The ET1 who is addressing these elements at T-minus-3 months is the ET1 who submits a rushed package that reads like one.
  • NEC pipeline output producing at least one selectee or in-pipeline entry per year from the division — briefable to the LCPO and combat systems officer by name.
    Track the division's NEC pipeline by name: which ET2 is targeting which NEC, which cycle, what is the current packet status, what is the estimated C-school date. Bring the pipeline status to the monthly counseling with the LCPO as a named list, not a count. The ET1 LPO who can brief 'ET2 [name] has the 2879 C-school date confirmed for [month], ET2 [name] has the 2791 packet submitted for [cycle], ET3 [name] is building toward 1426 in the following cycle' is the LPO the combat systems officer cites when the Type Commander asks what the ship's electronics pipeline is producing. The one who gives the LCPO a headcount without names is the one who has not been managing the pipeline.
  • PRT Good High or better; BCA in standard; warfare device (SW or SS as applicable) current and backed by an actual qualification board record.
    Good High at E-6 LPO is the standard the division reads off the ET1's performance — the LPO who fails the PRT or comes close sets a floor that the ET2s read as permissive. Build the training program before the official PRT cycle and run practice events at training pace, not race pace on test morning. The warfare device currency matters more than the junior ETs understand and the board already told you: the eEVAL bullet for a current, board-backed warfare device is one of the few bullets the senior rater can write without qualification. If the device lapsed, the renewal board is the first administrative priority after CDI.

Technical Mistakes — Concrete Consequences

  • Briefing CSMP and readiness numbers to the combat systems officer that have not been personally validated against the 3-M coordinator's current report.
    The combat systems officer relays the ET1's numbers to the department head and the CO's readiness sync. When the 3-M coordinator's monthly report shows a different figure than what the ET1 briefed — three more deferred MRCs, a CSMP discrepancy opened six days ago that was not in the LPO's brief — the combat systems officer comes to the ET1 with the coordinator's report in hand. At that point the ET1 is either the LPO who manages the division's data or the one who is managing the brief of the data. The Chief board package is being built during this tour; 'I did not personally verify those numbers' is a Chief-board-quality answer that the Chief board does not select.
  • Allowing a tag-out authorization gap because the ET1 trusts the ET2 to manage the ESWP log without LPO review.
    The tag-out log is the ET1 LPO's accountability document. When the ESWP audit during an ISIC visit identifies a tag-out that was applied without proper authorization or cleared without the documented isolation verification, the LPO is the person who designated the authority and is accountable for the exercise of it. The ET2 who was trusted to manage the ESWP log unsupervised is not the person the inspector interviews first; the ET1 is. The authorization gap that surfaces during a safety incident is a command-level investigation with the LPO's name on the tag-out log.
  • Confusing personal system knowledge with current technical currency — briefing a system's capability from memory when the installed configuration has been modified since the last C-school.
    Combat systems suites undergo configuration changes — hardware upgrades, software baseline changes, engineering change notices — that affect the technical manual applicability and the system's operational characteristics. The ET1 who briefs the SPY-1's operational parameters from the NEC 2879 C-school curriculum from three years ago may be briefing superseded data on a configuration that has been through two ECNs since then. The SWOS/NAWS program documentation is updated; the ET1 who has not reviewed the configuration update notices since checking aboard is the LPO whose technical brief the NAVSEA technical representative corrects in front of the wardroom.
  • Going public with a disagreement with the LCPO or the combat systems officer — taking the technical or personnel dispute outside the chain before it has been resolved inside the chain.
    The goat locker community on a surface combatant is small and tracks exactly one thing about a Chief candidate: does this ET1 route issues through the chain or around it. The LCPO who hears about a disagreement with the combat systems officer from the combat systems officer — rather than from the ET1 at the next counseling session — is the LCPO who cannot write the Chief board endorsement that describes a sailor who leads within the command's authority structure. The endorsement is the element of the Chief board package that is hardest to recover once damaged, and it is damaged by this faster than by any single maintenance failure.
  • Treating LDO and commissioning program mentoring as a one-time checkbox — mentioning it once at the annual counseling and not following up.
    The LDO and commissioning program pipeline produces the ET community's future officer and warrant corps. The ET1 who identifies a competitive ET2 and does not actively build the package — regular counseling sessions, introduction to a working LDO, review of the MILPERSMAN selection requirements, command endorsement preparation — is the LPO whose pipeline produces zero commissioning program selectees during the ET1 tour. That is visible on the Chief board package as an absence; the Chief board compares LPO tenures by what they produced, and the ET1 who was too busy to mentor commissioning packets is the one whose production record reads blank in that column.

Career Decisions at This Rank

  • Chief board — submit this cycle or build another year of ET1 record
    The Chief board submission decision belongs to the LCPO and the commanding officer at the endorsement stage, but the ET1 who understands the board's selection criteria is the one who influences the outcome. The board reads the eEVAL narrative across the ET1 tour, the warfare device, the NEC, the education credit, and the command endorsement — in combination. An ET1 who submits in the second year of an ET1 tour with a strong eEVAL profile, a CDI qualification, a current warfare device, a NEC, and a LCPO who can defend the package in thirty seconds is a competitive submission. An ET1 who submits after a year with an incomplete eEVAL profile and a LCPO who is still building the package is not. The conversation with the LCPO at T-minus-18 months is the right one to have about timing — not the career counselor's generalized guidance about 'as soon as you are eligible.'
  • Re-enlistment and SRB math at Zone B — stay for Chief or evaluate the civilian and defense market
    The ET1 Zone B re-enlistment window is the point where the civilian market value of an NEC-coded ET1 with CDI qualification, a warfare device, a security clearance, and verified Aegis or combat systems experience becomes concrete enough to run a real comparison. NEC 2879-coded ET1s are presenting to Raytheon Missiles and Defense, L3Harris, Northrop Grumman, and NAVSEASYSCOM GS-11 to GS-13 billets at a level the junior market does not access. The honest analysis: pull the current SRB NAVADMIN before any number is real — SRB rates vary by NEC, zone, and manning. Compare the SRB net of taxes against the specific civilian offer you have with your credentials and clearance, not a hypothetical salary. The ET1 who re-enlists to reach Chief while the credential stack is building is running a different calculation than the one who re-enlists to solve a short-term money problem. If the Chief board is genuinely competitive and the LCPO's assessment supports it, the Chief path has a specific post-Navy market value that the ET1 who separated early does not have.
  • LDO or CWO electronics track packet — the ET1 application window
    The ET1 with the time-in-service, a competitive NEC, an EP or MP eEVAL record across the ET1 tour, a CDI qualification, a warfare device, and command endorsement is in the primary application window for an LDO or CWO electronics track packet. LDO commissions into the officer corps with a technical specialization; CWO is the warrant officer path into the electronics technical-authority track. Both require the commanding officer's endorsement and a competitive record at the officer selection board. The honest test is binary: do you want a technical-authority career as an officer, or do you want to be a Chief? Both are legitimate paths in the ET community and they take you to genuinely different places — LDO and CWO are not 'better' than Chief, they are different, and the right choice depends on where you want to be in fifteen years. Talk to an LDO, a CWO, and a Master Chief. Get the actual view of each seat from someone sitting in it.
  • Next billet — operational fleet assignment versus NAVSEASYSCOM, FTSC, or Type Commander staff
    The ET1's next billet choice shapes the Chief board package in a specific way. A second operational fleet assignment — LPO on a deployed DDG or CG — builds operational eEVAL credibility and gives the Chief board another deployment cycle to read. A NAVSEASYSCOM program office, FTSC senior technical position, or Type Commander staff billet builds program-level technical depth that translates to the post-Navy defense market and federal civilian track differently than fleet service. The ET1 who sequences one operational and one technical-depth tour before Chief pin-on presents the strongest combined narrative. Talk to the detailer and the LCPO in the same conversation about which billet type gaps the current record versus which billet type adds to what is already there.
  • Navy COOL credential completion before Chief pin-on — which credentials to finish now
    The Chief board package benefits from documented credential completion, and the post-Navy market value of completed credentials is real regardless of when the ET1 separates. Navy COOL funds the credentials that translate electronics, combat systems, and radar maintenance experience — CompTIA certifications relevant to the NEC, electronics technician certifications, Aegis-adjacent credentials where available. Sequence the fastest-to-complete and most employer-visible ones for completion before the Chief board submission, so the package includes completed credentials rather than 'in progress' entries. The LCPO notes credential completion on the eEVAL; the completed credential bullet is specific where 'pursuing Navy COOL credentials' is not.

How the Seat Varies by Unit Type

  • Aegis DDG / CG (NEC 2879, SPY-1 and MK-7 combat direction system)
    The ET1 LPO on an Aegis combatant is in the highest-inspection-scrutiny, highest-technical-authority environment in the surface ET rate. The division's INSURV posture covers the SPY-1 and combat direction system — the Navy's most complex shipboard electronics suite — and the ISIC inspection standard reflects that complexity. The combat systems officer expects the ET1 to be the wardroom's technical reference on SPY-1 system readiness during operations, not just during maintenance periods. The NAVSEA SWOS/NAWS program documentation is the governing technical authority; the ET1 who is not current on the configuration baseline is not technically current on the system. The post-service value of a verified Aegis LPO tour is recognized specifically by the defense primes — Raytheon, Lockheed Martin, Northrop Grumman — who build and maintain the system.
  • Non-Aegis surface combatant (LHA / LHD / LPD, AN/SPS-67 and AN/SPS-48E baseline)
    The ET1 on a non-Aegis surface combatant runs a broader but less concentrated electronics maintenance division — surface search radar, air search radar, navigation suites, interior communications, electronic warfare support equipment across a large hull. The INSURV standard is high, the work center count is larger, and the diversity of system families means the ET1 LPO is managing more NEC families than an Aegis shop. The NEC pipeline is more likely 1426 and 2791 than 2879. The LHA/LHD assignment adds aviation navigation and combat systems support that is not present on a purely surface-warfare combatant, which broadens the ET1's technical exposure and the eEVAL narrative in a different direction.
  • Shore command / FTSC detachment / Fleet training activity
    The ET1 LPO at a Fleet Technical Support Center detachment or shore technical command is running a maintenance-advisory and depot-maintenance division rather than an operational ship division. The CSMP posture is a different kind of accountability — depot-level repair versus shipboard operational readiness. The eEVAL narrative at a shore command reads as technical depth rather than operational leadership; the Chief board reads both, and the ET1 who has a fleet tour and a FTSC tour has the stronger combined narrative than the one who spent the entire ET1 career at shore commands. The advantage of the FTSC tour is the breadth of ship class exposure — the ET1 who has advised maintenance decisions on four hull classes in two years has a technical currency the single-ship LPO does not have.
  • NAVSEASYSCOM or PEO IWS program office (program support billet)
    The ET1 at a NAVSEASYSCOM or PEO IWS program office billet is the deckplate technical voice in a defense acquisition and systems engineering environment — the enlisted advisor who translates the fleet's maintenance reality into program-level decisions. The eEVAL narrative is program-level rather than division-level, and the Chief board reads the program contribution differently than the division leadership record. The post-service value of this assignment is the highest of the ET1 tour options: the ET1 who has worked directly with NAVSEASYSCOM and PEO IWS engineers and program managers is presenting to the defense contractor and federal civilian market with a network and a context that the purely fleet-based ET1 does not have.
  • Forward deployed unit (FDNF — Yokosuka, Rota, Bahrain)
    The forward deployed ET1 LPO carries a higher operational tempo, more sustained underway time, and more frequent real-world combat systems operations than homeport-based fleet assignments. The CSMP and readiness maintenance in a sustained-deployment environment is what builds the most visible independent LPO leadership record — the ET1 who ran the division's maintenance posture through a WESTPAC without daily LCPO check-ins has an eEVAL narrative the Chief board reads as operational validation. The family situation at a forward deployed location is a real factor; the geographic separation from family support networks is concrete and the ET1 needs to be honest with himself and his family before accepting a forward deployment LPO billet.

What Good Looks Like at This Rank

The good ET1 is the LPO the LCPO trusts to run the division during a pre-INSURV workup without daily check-ins — not because he is technically the most capable ET in the space, but because the CSMP is clean before the workup starts, the documentation is current throughout the year, and the ET2s are performing to a standard the LPO built and the LCPO can point to. The combat systems officer does not rewrite the ET1's readiness brief before the CO's sync. The INSURV preparation cycle is the annual validation of a maintenance discipline, not the annual scramble to build one. His pipeline is producing. The NEC packets he is managing have names, target cycles, and current status — not approximate counts. At least one ET2 in the division is in the C-school pipeline or has the packet submitted this year. At least one LDO or commissioning program conversation is active with a qualifying sailor, not because the LCPO asked about it but because the ET1 started it when the sailor's record warranted it. The eEVALs he writes have action-result-impact bullets with specific numbers — CSMP closure rates, INSURV finding counts, advancement selectees — and the senior rater can defend them at a wardroom board without softening the language. The Chief board package is not a future project. It is the accumulated record of this tour: a CDI qualification awarded within 90 days, a warfare device current and backed by a real board record, an eEVAL narrative that reads progression across the tour, a command endorsement conversation that happened at 18 months instead of 3 weeks before submission, and a LCPO who can brief the board panel on this ET1's performance without consulting the package. That is the ET1 who picks up the anchors — not because he worked harder than the others at the end, but because he built the record from the first week.

Preview — The Next Rank

ETCS (E-7) is Making Chief — and the goat locker change is larger than the technical change. The gold-fouled anchors mean the Chief's Mess is yours, the division reads the command's tone off how you stand at morning quarters, and the combat systems officer briefs around you in a way he did not brief around the ET1. The LCPO function at Chief is not the LPO function with a higher paygrade — it is a fundamentally different seat. As ETC you own the division's enlisted execution from the deckplate up: you write the eEVALs that pick the next ET1 slate, you sit at department head sync as the senior enlisted electronics voice, you build the next LPO, and you enforce the standard in the ESWP spaces, the PMS scheduling meeting, and the Chief's Mess — every day, in front of people who are watching whether the anchor you pinned on Thursday is the same person who shows up to work on Monday. The technical role at ETC is still present — you are still the person the division calls at 0200 when the casualty is complex and the ET2s need a decision that requires Chief-level authority. But the primary identity changes. You are not a technician who leads; you are a leader who happens to know the systems. The distinction matters in how you run the mess, how you conduct counseling, and how you handle the Chief's Mess's relationship with the wardroom. The ET1 who has been leading as if he were already a Chief — routing issues through the chain, verifying before signing, holding the standard under schedule pressure, mentoring the pipeline without waiting to be asked — is the one who finds the goat locker transition natural. The ET1 who has been managing up and managing around will find the Chief's Mess has a culture that surfaces that behavior faster than the LPO chain ever did.
FAQ

ET E6 — Frequently Asked Questions

Q01What does a E6 ET (Electronics Technician) actually do?
You are LPO of a work center or division — electronics maintenance division on a surface combatant, the Aegis combat systems division LPO on a CG or DDG, the senior ET aboard a submarine if you went through the nuclear pipeline, or the senior enlisted electronics voice at a shore-side technical department or Fleet Technical Support Center (FTSC) detachment.
Q02What's the most important thing to know as a E6 ET?
ET1 is where the Chief board becomes a current administrative action, not a future aspiration.
Q03What does a typical day look like for a E6 ET?
Time-blocked day at the E6 ET rank tier: 0500-0545 Wake. If duty section ET1, review the overnight maintenance log and watch turnover: any system casualties that opened overnight, any CSMP entries that need LPO review before quarters, any tag-out status changes that require the ESWP log update before the safety petty officer's morning check, 0545-0630 Command or divisional PT. The ET1 LPO's presence and performance at PT sets the standard the division reads — no excuses, no falling out, no leading from the quarterdeck, 0630-0730 Hygiene, chow, utilities on.…
Q04What mistakes get E6 ET soldiers fired or relieved?
Assuming the Chief board packet will assemble itself from a good eEVAL record. The board reads the package as a whole — the warfare device, the NEC, the command endorsement, the education credit, the eEVAL narrative across the ET1 tour — and the ET1 who has not been managing the package with the LCPO's specific guidance discovers at submission that one element is missing or weak. The gap that could have been addressed eighteen months out cannot be addressed the week before the package is due;…
Q05What career decisions matter most at the E6 ET rank tier?
Chief board — submit this cycle or build another year of ET1 record — The Chief board submission decision belongs to the LCPO and the commanding officer at the endorsement stage, but the ET1 who understands the board's selection criteria is the one who influences the outcome. The board reads the eEVAL narrative across the ET1 tour, the warfare device, the NEC, the education credit, and the command endorsement — in combination. An ET1 who submits in the second year of an ET1 tour with a strong eEVAL profile, a CDI qualification, a current warfare device, a NEC,…
Q06What's next after E6 for a ET (Electronics Technician) in the Navy?
ETCS (E-7) is Making Chief — and the goat locker change is larger than the technical change.
Q07What manuals and regulations does a E6 ET need to know cold?
NSTM Chapter 320 (Electronics) and Chapter 300 (Electric Plant / ESWP) — you are the LPO the ET2s come to with the chapter question, not just the citation.; NAVSEA system TMs across the full combat systems suite your division owns: SPY-1 / Aegis (SWOS/NAWS), SPS-67, SPS-48E, AN/UYK computer systems, AN/WSC-3 satellite comm, navigation suites — know which TM covers which configuration.;…

Based on 23 tips from 0 contributors

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