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

Steelworker

E-6 (Staff Sergeant) · Navy

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

Making SW1 means you are the LPO — the senior enlisted voice on the project site, the person who writes the eEVALs that pick the next advancement slate, and the person whose name is on the Chief board packet under active construction. The goat locker conversation starts now whether or not you have pinned SW1 yet. The LCPO is already looking at your project record and your pipeline output. Everything you do as SW1 either builds the Chief board packet or does not, and there is no neutral.

The Honest MOS Read
You are the LPO of the SW section or the construction platoon, and the job has shifted from executing structural steel to owning it. The SW2s under your supervision run the daily project work; your job is to make sure the standard they run it to is the right standard, the documentation they produce survives a NAVFAC inspection, and the sailors under them are developing toward the next paygrade rather than marking time. The construction project at SW1 is the same structure it was at SW2 — a NAVFAC-contracted steel frame, a diving-support platform, a hardened magazine — but the relationship to that project is different. You are the person the project OIC calls when the NAVFAC QC rep raises a formal nonconformance, when the structural engineer issues an RFI on a field condition, or when the erection schedule is slipping and the OIC needs to understand why and what it takes to recover. The SW1 who cannot hold a technical conversation with a CEC lieutenant who has never seen a real pour is the SW1 whose project gets managed by the officer instead of the other way around. Know the spec better than the person asking the question. The eEVAL cycle at SW1 is consequential in a way that earlier cycles were not. You are writing the evaluations that determine whether an SW2 advances or waits another cycle, whether an SW3 is competitive or not. The inputs you write — the measured, specific, project-outcome-based blocks that the CO signs — are the documents that either advance your sailors or do not. An LPO who writes generic eEVAL inputs because he does not want to invest the time is an LPO who does not keep good sailors. The Chief board packet is the other parallel track. The LCPO is watching whether the SCW device is complete, whether the eEVAL profile shows the kind of senior-enlisted leadership the board is looking for, and whether the project record demonstrates that you can manage a platoon-level scope without hand-holding from the OIC. At SW1, you cannot separate the job from the board preparation — they are the same thing. The Chief board reads the project record you built as a petty officer, and the project record you build as SW1 is the most recent and most heavily weighted part of it.
Career Arc
  • 01SW1 crow pinned: LPO assignment — first eEVAL cycle writing evaluations for SW2s and SW3s; project execution plan responsibility for the platoon's full construction scope.
  • 02SCW device completion: if not already pinned, the Seabee Combat Warfare device qualification is the first administrative priority. The LPO without it is visible on the Chief board packet.
  • 03Chief board packet construction: eEVAL profile review with the LCPO, award package, project record documentation — the board packet is built now, not assembled in the six months before convening.
  • 04First deployment as LPO: multi-phase structural project managed from execution plan through NAVFAC final turnover — the project record that the LCPO describes to the Chief selection board.
  • 05Pipeline output: SW2 and SW3 advancements under your leadership, SCW completions, NEC selectees — the LCPO and the CO can name the sailors who advanced because of your mentoring.
  • 06Senior Chief board approaching: the LPO who has pinned SW1 and is building a clean two-deployment record as LPO is the sailor the LCPO mentions to the CMC for the Senior Chief conversation.
Common Screwups
  • ×Falsifying project QC documentation — signing a weld log for uninspected welds, accepting a material certification that was not received. At SW1 this is not just an NJP — it is the end of the career in a rate that certifies structural safety to the Navy. The investigation traces through every QC document you signed, and the question is not just whether this entry was false but whether any of them were.
  • ×Fraternization with a subordinate. The LPO who crosses the personal relationship line with a sailor in the platoon creates a command climate problem that the XO, the CO, and the goat locker all handle — and all remember. The Chief board reads the permanent record, not the informal resolution.
  • ×Financial misconduct or indebtedness that reaches the command. At SW1, financial problems that generate JAG referrals or command involvement are a career stopper. The security clearance implication alone — financial vulnerability is a suitability concern — can affect NEC qualifications and deployment assignments.
  • ×DUI or alcohol incident. At petty officer first class, an Article 15 for DUI typically means reduction to E-5, suspended bust, and a fitness report that the Chief selection board reads. Recovery from a DUI at SW1 is rare and takes years; the Chief board sees the record.
  • ×Treating the Chief board packet as something you build in the final year before eligibility. The sailors who do not select Chief in the SW rate almost always have the same profile: competent petty officer, clean record, but eEVAL profile that does not show sustained LPO-level leadership across multiple deployment cycles. Build the packet from the day you pin SW1.

A Day in the Life

  • 0530Early run or personal PT before formation. The LPO who is physically credible does not have to establish it — the crew already knows.
  • 0600-0700Battalion PT formation — LPO may lead the section's PT element. Know the weekly PT plan and execute it; the SW1 who improvises PT at formation reflects poorly on the section.
  • 0700-0730Chow. Pre-shift planning: review today's AHA against the current scope, confirm crane is scheduled and lift plan is complete, check that rigging and welding gear is accounted for.
  • 0730-0800Pre-shift crew muster and safety brief — the SW1 chairs this. The AHA was built from yesterday's site walk. Brief specifically: this pick, this elevation, this connector, these hazards.
  • 0800-0900Site walk with the SW2s before the crew is fully deployed. Identify any overnight changes to site conditions — equipment moved, new subcontractor on site, weather damage to temporary work. Brief changes to the day's AHA if needed.
  • 0900-1130Project oversight — walk the active erection and fabrication phases, check weld quality before it goes in the log, verify crane pick is executing per the lift plan. Not doing the work — watching the work and making it better.
  • 1130-1300Chow, administrative work. eEVAL drafts, material requisitions, QC log review for the morning's work. The QC log close-out at the end of the day starts here.
  • 1300-1500Afternoon project oversight. Check in with the SW2s on afternoon scope progress. If there are deviations from the day's plan, determine whether the OIC needs to be briefed before end of shift.
  • 1500-1600End-of-day QC documentation close-out, equipment and tool accountability, material status check for tomorrow's work. The QC log is complete and legible before secure.
  • 1600-1700OIC brief if warranted — project status, any open NCRs, tomorrow's priorities. The SW1 who briefs proactively never surprises the OIC.
  • 1700-1900Administrative work: eEVAL inputs, Chief board packet updates, MILPERSMAN research for a sailor issue in the section, NWAE mentoring for an SW2 whose exam cycle is approaching.
  • 1900-2100Personal study — AWS D1.1 current edition review, senior-enlisted PME if applicable, leadership correspondence. The SW1 who stops learning sends a message about the standard he expects from his sailors.
  • 2100Rack. Recovery.

Weekly Cadence

In garrison the SW1's week is administrative more than it is physical. Monday is accountability and equipment status; Tuesday through Thursday are the project or shop execution days, eEVAL draft work in the afternoon, and the ongoing management of the qualification pipeline for the section; Friday is field day, equipment accountability, and week-close administrative tasks. The LPO who uses garrison weeks to build the eEVAL library, maintain the WPQ records, and advance the Chief board packet is the one whose deployment weeks are spent on the project instead of catching up on the administrative backlog. On deployment, the rhythm is driven entirely by the project schedule. The LPO's week is structured around the inspection hold points — the NAVFAC QC rep's required inspections before the work can proceed define the gate dates that organize everything else. The SW1 who understands the inspection hold-point schedule and has the documentation prepared for each one keeps the project moving at the rate the schedule requires. The SW1 who discovers an inspection hold point when the crew is ready to proceed and the documentation is not ready stops the project and explains it to the OIC. The train-up cycle before deployment is the period when the LPO does the administrative work that deployment does not have time for: WPQ currency verification for all welders, rigging hardware inspection and condemnation, crane operator qualification confirmation, and AHA template building from the project documents. The SW1 who deploys with all of this done in advance starts the project; the one who tries to do it on site spends the first two weeks of the project behind the pace.

Key Skills — How to Drill Each

  1. 01
    Build and brief a structural steel project execution plan from NAVFAC design documents — phasing, crew assignments, crane needs, QC inspection hold points.
    Build the execution plan from the project documents before the first crew member sets foot on site. Read the structural drawings completely, identify all the inspection hold points the NAVFAC specification requires, map the erection sequence to the construction schedule, and brief the OIC on phasing and risk before the project kickoff meeting. The OIC who hears 'here is our plan, here are the risks, here is how we mitigate them' in the first week trusts the LPO for the rest of the project. The OIC who discovers risks for the first time when they materialize does not.
  2. 02
    Run the battalion's weld QC program for the project scope — daily logs, welder qualification records, hold-point notifications, NCR tracking.
    The weld QC program is a system, not a daily checklist. Build the system at the beginning of the project: set up the weld log format with all required fields (welder stamp, WPS reference, visual acceptance result, inspector initials), confirm WPQ currency for every welder before first arc, schedule inspection hold-point notifications into the project timeline. The NAVFAC QC rep who walks your site and finds the system already running without prompting writes a different inspection report than the one who walks in and has to ask for the documentation.
  3. 03
    Write eEVAL blocks for SW2s and SW3s that the CO can defend at the advancement worksheet board.
    An eEVAL block that the CO can defend is specific — it names the project, the crew size, the structural scope, the weld QC record, the safety record outcome, and the advancement the sailor facilitated in his subordinates. 'Demonstrated outstanding leadership' is not defensible at the advancement worksheet board. 'Led a 6-sailor SW crew through a 4-week structural erection phase in Djibouti; weld QC log accepted without NCR; SW3 advanced to SW2 under his mentoring' is. Write the second kind.
  4. 04
    Mentor SW2 advancement packets and SCW device qualification timelines.
    SW2 mentoring at SW1 is not career counseling — it is specific and scheduled. Review the BIB together, assign study milestones, review mock exam scores, and hold the SW2 accountable for the schedule. For the SCW device, walk through the qualification checklist and assign the blocks that should be completable on this deployment, not 'get it done when you can.' The sailors who advance because of you are the LPO's most visible legacy.
  5. 05
    Serve as the senior technical voice when the CEC OIC asks about structural field conditions, design deviations, or erection feasibility.
    When the OIC asks 'can we field-weld this connection as a fillet instead of the full-pen the drawing shows,' the answer is not 'I will find out.' The answer is 'a fillet weld here changes the moment capacity of the connection — we need an engineering change order from the design engineer before we deviate from the drawing.' Know the structural logic behind the details, not just the specification requirement. The LPO who explains the engineering reason behind the spec requirement is the one the OIC trusts for the rest of the project.

Manuals & References — What Chapters Matter

  • AWS D1.1 — Structural Welding Code – Steel, current edition
    At SW1 you are the senior weld technical authority on the project. Chapter 4 (Qualification) governs your welder qualification program; Chapter 6 (Inspection) governs what the NAVFAC QC rep inspects from; Part C (Prequalification) governs which joint details your SW2s can use without a PQR. The SW1 who can navigate D1.1 in real time during a field dispute with the QC rep is the one who resolves the dispute on the site rather than generating an RFI.
  • OSHA 29 CFR 1926 Subpart R — Steel Erection and EM 385-1-1 Section 21
    You are the competent person named on the site's fall-protection and erection safety program. The NAVFAC safety investigation that follows a recordable connector injury traces from the injury back to the competent person and to every safety document bearing that person's name. Know what the subpart requires for temporary flooring, decking installation, connector fall protection, and anchor-bolt installation tolerances — these are the provisions where field deviations most commonly occur.
  • UFC 3-301-01 — Structural Engineering (NAVFAC), and project-specific NAVFAC specifications
    The project-specific specifications are the law of the contract — they supersede general UFC provisions where they differ. Read the project spec front to back before the first crew member sets foot on site, not after the first NCR. The sections on structural steel inspection hold points, material testing requirements, and welding process restrictions are the ones most commonly missed by LPOs who read the drawings but skip the spec.
  • NAVFAC P-307 — Management of Weight Handling Equipment
    At LPO level, P-307 governs your fleet of rigging equipment and crane operations at the platoon level. The annual inspection and certification requirements for slings, shackles, and lifting devices are administrative responsibilities at SW1 — the equipment that is not certified when the NAVFAC CMO walks the site is grounded until it is. The LPO who tracks certification currency does not have crane operations stopped by an administrative gap.
  • MILPERSMAN — articles governing enlisted advancements, NJP, separation, and retention
    At SW1 you are in the room when these articles apply to your sailors. The MILPERSMAN is not just background knowledge; it governs what you can and cannot do as an LPO when a sailor in your section is in trouble. Know the specific articles before the situation arises, not during. The LPO who has to look up the NJP procedures while the CO is waiting for the recommendation is the LPO who does not look prepared.

Standards — How to Hit Each

  • Chief board packet competitive before the first board eligible cycle.
    Pull the current Chief selection board precept from MyNavyHR and read the evaluation criteria the board applies. Build a personal checklist against those criteria: eEVAL profile (sustained EP recommendations across LPO assignments), SCW device pinned, award package documented, leadership school complete. Brief the LCPO on where you are against each criterion at the beginning of every deployment cycle and ask what the LCPO would need to see from this tour to write a strong board recommendation.
  • Project QC documentation accepted at NAVFAC final turnover without outstanding NCRs.
    The final NAVFAC turnover is the LPO's report card. The QC rep who walks the turnover inspection with no outstanding nonconformance reports and a complete documentation package — weld logs, material certifications, inspection hold-point sign-offs, as-built survey data — writes a turnover acceptance that the OIC signs without comment. Work backward from that standard: what does the documentation package need to contain, and is every element being built daily throughout the project, or assembled at the end under pressure?
  • Safety record clean across the deployment cycle — no recordable injuries and no stop-work orders.
    The safety record is not built by reviewing the AHAs at the end of the week; it is built by walking the site at the start of every shift and correcting the hazards before work starts. The LPO who is visible on the site before the crew is at elevation is the LPO whose site does not have recordable injuries. The one who reviews the safety program in the office is the one who finds out about the near-miss three days after it happened.

Technical Mistakes — Concrete Consequences

  • Approving a weld repair procedure that is not qualified under AWS D1.1 because the project schedule is behind.
    A repair weld made without a qualified WPS is a structural defect disguised as a repair. The NAVFAC structural engineer reviews the repair documentation at final turnover; an unqualified repair procedure produces an engineering rejection that requires the connection to be cut out, re-fabricated, and re-inspected. The project delay from a rejected structural connection is measured in days to weeks — far longer than the time lost by stopping work to get the repair procedure approved before executing it.
  • Briefing erection status to the OIC without walking the site that morning.
    The NAVFAC QC rep has been on site every day. When the LPO's status brief does not match the QC rep's inspection record — a column that the LPO says is plumb and bolted that the QC rep marked as requiring re-plumbing yesterday — the OIC knows which version is current and it is not the LPO's. Brief from what you observed, not from what the SW2 reported.
  • Letting a deteriorating safety program run because the NMCB safety officer has not cited it yet.
    The NMCB safety officer's citation is the lagging indicator, not the leading one. The near-miss trend in the safety reports is the leading indicator, and the LPO who sees an increasing near-miss frequency and treats it as a documentation problem rather than a program failure is the LPO who has a recordable injury one month later. The safety officer's citation that follows creates a stop-work, a NAVFAC safety investigation, and a permanent record entry — all of which could have been avoided by acting on the near-miss data earlier.
  • Treating the Seabee Combat Warfare (SCW) device as a check-in-the-box rather than a genuine qualification.
    The SCW device certifies that the petty officer can operate in a combat construction environment — the tactical, weapons, and engineering knowledge required to protect the battalion while building. An LPO who carries the SCW as a paper qualification without the underlying knowledge is the LPO who cannot brief the tactical situation to the OIC during a force-protection evolution on a forward site. The Chief board sees the SCW on the record; the CEC OIC sees whether the SW1 actually knows what it certifies.

Career Decisions at This Rank

  • Chief board — apply on first eligibility vs. wait for a stronger packet.
    In a small rating like SW, waiting for a 'stronger packet' is often a mistake — the pool is small enough that a consistently competitive packet is rare, and a one-cycle miss can mean a two-or-three-year wait before the next board where you have seniority advantage. Apply on first eligibility with the strongest packet you have. What makes a SW1 Chief board competitive in a small rating: two or more deployment cycles as LPO with clean QC records and documented pipeline output, SCW device pinned, eEVAL profile showing EP or high MP evaluations across LPO assignments, and an award record that names specific structural projects. The LCPO's recommendation letter is weighted; invest in that relationship from day one as SW1.
  • Pursue the Navy Limited Duty Officer (LDO) or Chief Warrant Officer (CWO) program vs. stay enlisted.
    The LDO program (Civil Engineer Corps community, ED-805 series) and the CWO program are available to petty officers first class with strong eEVAL profiles and educational background. An SW1 with construction engineering education or an associate's degree in construction management is competitive for LDO consideration. The CWO path in the Navy is a smaller pipeline and more competitive. Both require MILPERSMAN 1212-010 and 1212-020 application respectively. The honest career math: as a CEC LDO or CWO you will be doing construction management work similar to what you do as SW1, but with commission authority and a different pay trajectory. If the officer career appeals and the education path is open, SW1 is the right time to apply. The window does not stay open indefinitely.
  • First major professional development school — Senior Enlisted Academy, Seabee combat course, or technical credentialing.
    The Senior Enlisted Academy at Newport is a fleet master chief program that is not typically available until senior chief eligibility, but the preparatory reading and the awareness of what the SEA represents in the senior-enlisted career is useful context at SW1. At this tier, the most valuable professional development schools are the ones that directly build the Chief board packet: leadership courses endorsed by the NMCB (if available through the Type Commander), AWS CWI examination (if not yet completed), and the Seabee Combat Warfare qualification if not yet pinned. Focus the available professional development time on the gaps in the packet rather than the courses that are available but not targeted.

How the Seat Varies by Unit Type

  • NMCB — full deployment cycle as LPO
    The standard SW1 assignment is LPO of the SW section in an NMCB, deploying on the battalion's seven-month cycle. As LPO of a small section in a larger battalion, the SW1 interfaces directly with the battalion operations officer, the CEC project OICs, and the NAVFAC QC reps on every project. The quality of those relationships determines whether the SW section's work gets the resources and support the project requires. The good LPO in an NMCB is known by name to every officer in the battalion.
  • Naval Construction Regiment (NCR) staff
    SW1 LPOs occasionally serve in regiment-level staff assignments — construction quality assurance, training coordinator, or battalion operations support. These assignments remove the direct crew-lead authority but add the administrative and advisory skills that are specifically tested at Chief. An SW1 who does a regiment staff tour and then returns to a battalion LPO role for the Chief board submission typically has a stronger administrative record than one who has only run crews. The tradeoff is losing a deployment project cycle — which is the most visible part of the packet.
  • Joint Construction Task Force — senior SW on site
    A joint construction task force that includes Army engineer units, Air Force RED HORSE, or allied-nation construction forces may have the senior SW as the structural steel subject matter expert for the entire task force, not just the Navy element. This is a visibility environment: the LPO who is the structural authority for a multi-service construction effort is visible at colonel/O-6 level, and the after-action report from that mission is the kind of document the Chief selection board notices. Take these assignments seriously.
  • NAVFAC facilities engineering — QA/QC role
    Some SW1s serve in NAVFAC facilities engineering commands in construction QA or inspection roles — reviewing contractor submittals, witnessing testing, and signing off on NAVFAC contract deliverables. This is the administrative side of construction quality that the LPO normally manages from the contractor side of the fence. The experience builds the documentation and inspector skills that are useful for the post-service CWI or NAVFAC civilian career path.

What Good Looks Like at This Rank

The good SW1 is the LPO the project OIC can brief to the commodore without preparation. When the commodore asks 'what is the structural status of the project,' the OIC says 'ask my LPO' — and the SW1 who walks into that conversation with the weld log, the erection schedule, and the outstanding NCR count in his head does not need the OIC to run interference for him. That is the relationship the good SW1 builds in the first two weeks of a project, and it holds for the entire deployment. His SW2s know the Chief board packet is something they are building now. He reviews their eEVAL profiles at the beginning of every tour, identifies the gaps — missing warfare device, no AWS certification, eEVAL ranking too low to be competitive — and assigns specific actions to fill them. The sailors who advance under his LPO tenure are the ones the CMC mentions when the LCPO asks about the platoon's pipeline output. The LCPO does not have to remind him about the SCW device, the award package, or the eEVAL submission deadline. The Chief board packet is under active construction before the LCPO asks about it, and the LCPO's input is 'I would add this specific project outcome to the third evaluation block' rather than 'you need to get started on this.' The good SW1 is the sailor the LCPO trusts to handle the platoon without checking in — which is the best possible endorsement for the Chief selection board.

Preview — The Next Rank

Chief SWC is a different job in a way that SW1 is not a different job from SW2. As a chief, the standards you hold are not just for your crew — they are for the entire rate as it is represented in the battalion and in the NMCB community. The BU2 in a different platoon who hears that a Chief Steelworker approved a lift without a completed plan forms an opinion about what chiefs in the SW rate look like. That is the weight of the anchors that is not written in the MILPERSMAN. The goat locker is a new operating environment with its own standards — the Chief's Mess runs the enlisted climate of the battalion, and the new chief who does not understand what that means within the first 90 days finds out the hard way. The CPO Academy transition is not a graduation ceremony; it is the beginning of the accountability structure that comes with the rate. The chiefs who earn the mess's respect do it the same way they earned the crew's respect: by knowing the craft, holding the standard, and being visible on the site when the work is hard.
FAQ

SW E6 — Frequently Asked Questions

Q01What does a E6 SW (Steelworker) actually do?
You are LPO of a SW crew or a construction platoon — 10-20 Steelworkers from SWCN through SW2 — and you own the structural steel output, the safety record, and the enlisted execution from the deckplate to the finished frame.
Q02What's the most important thing to know as a E6 SW?
Making SW1 means you are the LPO — the senior enlisted voice on the project site, the person who writes the eEVALs that pick the next advancement slate, and the person whose name is on the Chief board packet under active construction.
Q03What does a typical day look like for a E6 SW?
Time-blocked day at the E6 SW rank tier: 0530 Early run or personal PT before formation. The LPO who is physically credible does not have to establish it — the crew already knows, 0600-0700 Battalion PT formation — LPO may lead the section's PT element. Know the weekly PT plan and execute it; the SW1 who improvises PT at formation reflects poorly on the section, 0700-0730 Chow. Pre-shift planning: review today's AHA against the current scope, confirm crane is scheduled and lift plan is complete, check that rigging and welding gear is accounted for,…
Q04What mistakes get E6 SW soldiers fired or relieved?
Falsifying project QC documentation — signing a weld log for uninspected welds, accepting a material certification that was not received. At SW1 this is not just an NJP — it is the end of the career in a rate that certifies structural safety to the Navy. The investigation traces through every QC document you signed, and the question is not just whether this entry was false but whether any of them were; Fraternization with a subordinate.…
Q05What career decisions matter most at the E6 SW rank tier?
Chief board — apply on first eligibility vs. wait for a stronger packet — In a small rating like SW, waiting for a 'stronger packet' is often a mistake — the pool is small enough that a consistently competitive packet is rare, and a one-cycle miss can mean a two-or-three-year wait before the next board where you have seniority advantage. Apply on first eligibility with the strongest packet you have. What makes a SW1 Chief board competitive in a small rating: two or more deployment cycles as LPO with clean QC records and documented pipeline output, SCW device pinned,…
Q06What's next after E6 for a SW (Steelworker) in the Navy?
Chief SWC is a different job in a way that SW1 is not a different job from SW2.
Q07What manuals and regulations does a E6 SW need to know cold?
AWS D1.1 — Structural Welding Code – Steel; you are the senior technical authority the project OIC calls when the QC rep rejects a weld or disputes a repair procedure.; OSHA 29 CFR 1926 Subpart R — full subpart; a recordable connector injury on your erection site opens a NAVFAC safety investigation with your name in the title block.; EM 385-1-1 — full manual; you are the safety officer's enforcement arm on the project, and the sections you quote stop injuries before they happen.

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