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 IT Information System Technician — overview, pay, training, civilian translation, reviews
ITE6

Information System Technician

E-6 (Staff Sergeant) · Coast Guard

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

IT1 (E-6) is the rank where the compliance program is yours to own — not oversee. The ITC sets the vision; you run the ATO cycle, sign the POAM entries, manage the STIG remediation calendar, and put your name on every change ticket the shop generates. Chief board readiness is the underlying mission from the day you pin IT1 — the credential stack, the EER profile, and the chiefs' mess sponsorship conversation are live variables right now, not future-tense planning.

The Honest MOS Read
IT1 — Petty Officer First Class, E-6 — is the senior petty officer tier in the Coast Guard's Information Systems Technician rating and the rank where the compliance program stops being something you execute for someone else and starts being something you are accountable for in full. You have survived the SWE cycles under COMDTINST M1000-series, held the CompTIA Security+ CE long enough to pursue the next IAT rung, and accumulated enough STIG scan and POAM management cycles that you know what clean looks like and what a papered-over CAT I finding smells like before the Authorizing Official's office calls. The seat varies significantly by billet. At a small boat station or a medium-endurance cutter, you may be the only credentialed IT on site — the IT1-in-charge who runs every compliance action, network fault, and help-desk escalation without a peer to check your work. At a Sector or a District information management office, you are the senior working tech under a handful of ITCs, and the job is running the day-to-day program while the chief handles the command interface. At a Coast Guard Communications Area Master Station (CAMS Atlantic at Chesapeake, VA or CAMS Pacific at Point Reyes, CA), or in a CG C4I program billet, the technical scope expands materially — larger network infrastructure, broader system portfolios, and more direct engagement with DISA assessment teams. Every billet has the same thread: the ATO documentation is your shop's compliance output, and the ATO lapses under IT1 watch get named. The cybersecurity program ownership is the defining IT1 job. DoDD 8140.01 and its predecessor DoD 8570.01-M created a credential-based workforce management structure that maps every IT billet to an IAT (Information Assurance Technical) level and requires the billet holder to carry the appropriate baseline certification. At IT1, most billets require IAT Level II (CompTIA Security+ CE minimum) and many senior billets push toward IAT Level III (CompTIA CASP+ CE, or an equivalent in the current DoDD 8140.01 workforce category framework). The credentialing is not a checkbox — it is the technical credibility that earns you the standing to push back in the ISSO's brief when a deferred STIG finding or a proposed configuration exception would push the system inventory outside its ATO boundary. The ATO cycle is the program's spine. Every information system your command operates under a DoD or DHS authorization framework requires an Authority to Operate — a documented decision by an Authorizing Official that the system's security posture, documented in the system's Security Plan and POAM, is acceptable. The IT1 is the working-level owner of the documentation: the STIG compliance scan outputs, the POAM entries with accurate status and remediation dates, the system configuration baselines, the hardware/software inventory, the account-management audit records. When the ATO comes up for review and the ISSO or the AO finds a stale POAM entry with a false remediation date, or a STIG scan that was run against a superseded benchmark file, or an Active Directory account audit that wasn't conducted on schedule, that finding points to the IT1 who owned the program. The chiefs' mess sponsorship is not a passive process. In the Coast Guard, the transition from petty officer to chief is culturally governed by the Mess itself — the chief CPO initiation cycle is run by chiefs, evaluated by chiefs, and decided by the Mess. IT1s who make ITC are the ones who accumulated the visible institutional credentials — CASP+ CE or equivalent, multiple C-schools, a clean EER profile over multiple reporting periods, awards consistent with compliance program leadership and incident response, and a chief CPO sponsor in the Mess who can speak to their judgment under fire. The sponsor conversation is live at IT1 — if you do not know which ITC or ITCS is your institutional advocate, that is the gap to close first. The post-service credential conversation is also live at IT1. The CG is a small service and IT1 is early enough in the career curve that the IAT credential stack, the active clearance, and the CGPSC-documented compliance record represent the floor of a competitive federal civilian or contractor compensation package — not the ceiling. Federal civilian GS-09 to GS-12 Information Technology Specialist positions inside USCG, DHS, or DoD are a direct translation; cleared contractor roles at L3Harris, Booz Allen, SAIC, Leidos, and ManTech are a realistic post-service track for a credentialed IT1 who planned the transition 24 months out.
Career Arc
  • 01IT1 advanced via SWE under COMDTINST M1000-series; IAT Level II (CompTIA Security+ CE) held; IAT Level III (CASP+ CE or DoDD 8140.01 equivalent) in active pursuit.
  • 02ATO program ownership at the unit level — STIG compliance, POAM management, IAVM patch cycle, Active Directory account audit, and the ISSO interface.
  • 03Multiple C-schools on record — Cisco routing and switching, Microsoft server infrastructure, DINFOS or CG-specific IT C-school pipeline; credential stack beyond the Security+ baseline.
  • 04EER profile building across multiple reporting periods under at least two different ITCs — the trend the chief board or the SWE cycle reads.
  • 05Chief board sponsorship conversation active — identify the ITC or ITCS in the Mess who will carry your name through initiation; close the credential, LDC course, and awards gaps the board will see.
  • 06Post-CG credential and market planning begins in earnest — USCG civilian IT Specialist pipeline, cleared contractor track, DHS / USCYBERCOM support billets.
  • 07ITC (E-7) selection via board-based Chief advancement process under current CG policy.
Common Screwups
  • ×Phoning the IAT Level III credential pursuit. The CASP+ CE or its DoDD 8140.01 successor-category equivalent is the ITC billet's technical credibility baseline; arriving at the chief board without it is arriving to a gunfight with a pocket knife.
  • ×Letting the ATO or POAM drift during a heavy underway or operational cycle. The compliance program is a continuous obligation, not a surge-and-recover rhythm; a CAT I finding that runs open through two ATO review windows is the kind of finding the District CIS staff names in an audit, and it names the IT1 who owned the program.
  • ×Treating the chiefs' mess sponsorship as something that happens to you. If you are competitive on paper and invisible to the Mess, you are not competitive in the room where it counts.
  • ×DUI / Article 32 / NJP in a small service with a long institutional memory. The IT rating's senior enlisted network is tight — every ITCS and ITCM knows every IT1 by name and by the quality of the compliance program they run. One integrity incident rewrites the read.
  • ×Missing the civilian credential cross-walk window. The IAT credential stack and the active clearance are highly marketable in the federal civilian and contractor market; the IT1 who waits until two years before retirement to start the credential and clearance maintenance conversation is leaving money and options on the table.

A Day in the Life

  • 0530–0630PT — unit or self-directed; the IT shop is small enough that the IT1's physical readiness is visible to the ITC and the command, and an IT1 who is below average on PFT performance is a visible gap on the chief board record.
  • 0630–0730Shower, breakfast, check email and any overnight help-desk tickets or network monitoring alerts before the workday opens. The IT2 on duty handles first-responder tickets; anything escalated overnight lands in your queue with a description of what was tried.
  • 0730–0800Morning standup with the IT shop — ticket queue status, open POAM actions due this week, any ATO review items coming up in the next 30 days, any IAVM alerts published overnight. Two minutes per person, no rabbit holes; the ITC is in or has delegated this to you.
  • 0800–1000STIG compliance program work — running scans on the current cycle's assigned system class, reviewing STIG Viewer outputs for new findings, updating POAM entries with accurate remediation status, drafting risk acceptance documentation for any CAT I items that require AO signature this cycle.
  • 1000–1130Network and systems administration actions — change tickets reviewed and executed for the day's authorized work: switch port changes, AD account provisioning/deactivation based on personnel actions, group policy updates, backup verification, DNS/DHCP administrative actions.
  • 1130–1230Lunch and a 20-minute review of the DISA STIG portal for any updated benchmark files on system classes in the current ATO scope — new STIG releases happen on an irregular cadence and an IT1 who finds out about a new benchmark from the ISSO instead of the portal is already behind.
  • 1230–1400IT2 and IT3 development — qualification board preparation with an IT3 working toward IT2-level work authorization, or study session review with an IT2 in the SWE study cycle, or a one-on-one EER discussion about the performance bullets for the current period. The development work is the program that survives after you are gone.
  • 1400–1530Network documentation update — verify the topology diagram reflects current infrastructure, patch panel assignments are current, server inventory matches the ATO system boundary documentation, hardware end-of-life dates are tracked. The documentation the District CIS staff reads on a site visit is either current or it is a finding.
  • 1530–1600ISSO coordination — weekly touch with the command's Information Systems Security Officer on open POAM items, any active IAVM compliance actions, upcoming ATO review preparation, and any configuration changes proposed by the operations department that require an ATO boundary assessment before execution.
  • 1600–1700C-school and certification study — CASP+ CE exam preparation, current Cisco or Microsoft course module if in an active C-school pipeline, or DoDD 8140.01 workforce category documentation review if the framework update has changed the credential mapping for your billet. This hour does not yield to the help-desk queue unless the network is down.
  • 1700–1800After-hours ticket review, system backup verification, and shift handoff note to the duty IT (if your command has a duty rotation) — system status, any open actions with context, and the next day's STIG or POAM milestone.
  • 1800–2100Personal time — physical recovery, family, community. The ITC who has been in the rating for 16 years will tell you: the IT1 who does not protect the off-hours burns out before the chief board cycle.
  • 2100–2200CASP+ CE study or professional development reading — DoD STIG update notes, NIST publication release notes, a chapter of the current certification study guide. The credential does not pass itself.

Weekly Cadence

Monday sets the compliance week. The POAM review is the first real work of the week — what is due in the next 14 days, what is overdue, and what needs an ISSO signature before it becomes a critical finding. The IT2s have the ticket queue. You have the compliance calendar and the change-ticket review queue for anything that touches production infrastructure. The ISSO debrief is either Monday afternoon or Tuesday morning depending on command rhythm; it is never missed. Midweek is where the technical depth happens. The STIG scans, the AD account audits, the backup verification cycles, and the IT3 and IT2 qualification board work all live in the Wednesday–Thursday block when the help-desk queue is relatively steady. The C-school and certification study schedule is carved out of midweek afternoons and does not move for anything short of a network casualty or a POAM crisis. Friday is documentation and transition. Update the network topology diagram, verify the ATO documentation is current, brief the ITC on the week's compliance status, and write the after-action for anything that required an incident report or a change-ticket deviation. If there is a District CIS site visit on the horizon, Friday afternoon is the pre-visit self-assessment walk-through with the IT2 who will be answering questions.

Key Skills — How to Drill Each

  1. 01
    Own the unit's cybersecurity compliance program — DISA STIG posture, POAM management, IAVM patch compliance, ATO documentation currency, and the ISSO interface.
    Build the compliance calendar on day one: STIG scan cadence for every system class, POAM review dates, IAVM patch window by CVSS severity, ATO review date, and account audit frequency. Keep it posted where the IT2s can see it and the ITC can read the status at a glance. The ISSO should never have a surprise from your shop — brief the ISSO proactively on every open CAT I and every approaching deadline, not reactively after the AO review calls.
  2. 02
    Serve as the technical authority on hard network and systems casualties — switch VLAN faults, domain controller replication breaks, firewall ACL conflicts, backup failures — and direct the fix without rebuilding instead of diagnosing.
    The rebuild instinct is the IT2 default; the IT1 discipline is systematic fault isolation before touching a config. Work the OSI model from the physical layer up, document each isolation step in the change log before you execute it, and stop when you have identified the root cause rather than when the symptom disappears. The outage that recurs because the symptom was cleared instead of the cause is the one that generates a second incident report with your name on both.
  3. 03
    Run the unit IT qualification and work-authorization program — IT3 and IT2 qualification boards, change-ticket authorization levels, STIG sign-off authority, and the training record that survives a District CIS staff site visit.
    Keep the qual matrix current and visible: what each petty officer is authorized to touch, what requires IT1 co-sign, what requires ITC review. The authorization level is calibrated to demonstrated competence, not paygrade — an IT2 who has run ten supervised STIG remediation cycles and can brief the finding correctly earns expanded authorization; one who cannot explain the CAT I severity framework does not.
  4. 04
    Mentor IT2s toward IT1-SWE readiness and chief-board-eligible performance — study plans, EER blocks, C-school pipeline, certification prep, and the awards and recognition record that the advancement final multiple runs on.
    Sit down with each IT2 at the start of each performance period and build the development plan explicitly: SWE bibliography study calendar, certification target, C-school window in the underway schedule, and the two or three performance outcomes that will produce a measurable EER bullet. The IT2 who passes the IT1 SWE on the first attempt is the one whose IT1 built the calendar — not told them to study harder.
  5. 05
    Write clean, measurable EER inputs for IT2s and IT3s — observable performance, metric-backed results, zero inflation.
    Build the bullet format around outcomes the command can verify: STIG finding closure count and CAT I rate, help-desk resolution rate, SWE study milestones, certification timelines. The ITC uses your bullets as the primary record; an EER narrative that says 'worked hard and showed initiative' is a waste of a bullet block that the advancement slate will discount. Write it as if the District IT staff is going to audit the ticket system to verify your numbers.
  6. 06
    Sit in the command ISSO brief and push back honestly when a deferred finding, a proposed configuration exception, or an operational shortcut would push the system inventory outside the ATO boundary.
    The pushback is done in private, before the decision becomes an AO finding, with a written recommendation that names the risk clearly. You are not the compliance officer — the ISSO is — but you are the working-level technical authority, and the ISSO who does not hear the concern from the IT1 before it becomes a finding will read the incident report and note that the senior tech did not flag it. Document your recommendation; if the decision goes the other way, document that too.

Manuals & References — What Chapters Matter

  • COMDTINST M5500.13 (current series) — Coast Guard Information and Life-Cycle Management Manual
    The governing publication for CG IT systems management, information assurance policy, and network administration standards. At IT1 you are the unit authority on what the manual requires, not just the person who read it once. Verify the current revision against the CG Directives System — this instruction has been revised periodically and the version number matters when you cite it in a POAM or a compliance recommendation.
  • DoDD 8140.01 — Cyberspace Workforce Management (and predecessor DoD 8570.01-M)
    The DoD-wide framework mapping IT billets to workforce categories and baseline certification requirements. At IT1, know which workforce category your billet is designated under the current DoDD 8140.01 framework, what the baseline certification requirement is, and what the next credential tier requires. The policy has evolved from the 8570.01-M IAT/IAM/IASAE structure toward the newer DCWF work roles — know which framework your command and the CGPSC are currently enforcing.
  • DISA STIGs (current release) — Security Technical Implementation Guides
    Current benchmark files published on the DISA STIG portal for every OS, application, and network device class you administer. At IT1 you are the program manager for STIG compliance; the version of the benchmark matters because DISA publishes updates that change finding severity levels, add new controls, or supersede previous checks. Running a compliance scan against a three-cycle-old benchmark file produces a report the ISSO will reject.
  • NIST SP 800-53 (Rev 5) — Security and Privacy Controls for Information Systems and Organizations
    The federal control framework that DISA STIGs implement. At IT1 you reference SP 800-53 control families when writing POAM remediation justifications, explaining STIG findings to the ISSO, and understanding why a particular control matters. The SP 800-53 control identifier in the POAM entry is what the AO's office reads when evaluating risk acceptance — citing the control family correctly signals technical credibility.
  • NIST SP 800-37 (Rev 2) — Risk Management Framework for Information Systems and Organizations
    The RMF process that underlies the ATO workflow. At IT1 you live in the Assess and Authorize steps — understanding the full RMF cycle (Prepare, Categorize, Select, Implement, Assess, Authorize, Monitor) tells you where your compliance actions fit in the ATO lifecycle and what the AO is looking for in the documentation package.
  • CIM 1610-series — Coast Guard Enlisted Employee Review (EER)
    The EER is the primary personnel record for advancement and retention. At IT1 you write the bulk of the inputs for IT2s and IT3s; know how the EER mark and the supervisor narrative drive the SWE final multiple and the chief board read. The CIM 1610 series governs format, rating definitions, and the prohibition on inflation — write to the standard, not to what the petty officer wants to see.

Standards — How to Hit Each

  • IAT Level II (CompTIA Security+ CE) held; IAT Level III credential (CompTIA CASP+ CE or current DoDD 8140.01 equivalent) in active pursuit or achieved.
    The CASP+ CE (CompTIA Advanced Security Practitioner — Continuing Education) is a 90-question performance-based exam at the IAT Level III tier; the current exam domain breakdown and renewal CEU requirements are published on CompTIA's site. If DoDD 8140.01 has updated the approved baseline certification list for your billet's workforce category, verify the current mapping with your command IAO or the CG CGPSC credentialing guidance — the approved list changes. Build the study calendar around the exam domain percentages, not around what you already know well.
  • Unit STIG compliance program current — no overdue CAT I findings on the POAM without a documented and ISSO-signed risk acceptance; ATO documentation within its review cycle.
    The POAM is a living document, not a historical record. Overdue CAT I remediation dates without a signed risk acceptance are the finding the DISA assessment team and the AO's office look for first because they indicate a compliance program that documents problems without resolving them. Set a 30-day check-in cadence for every open CAT I — either the remediation closes, or a risk acceptance with the ISSO signature is in the file before the next review cycle.
  • IT1 EER profile at the top of the unit cohort across multiple reporting periods under multiple reporting seniors.
    The advancement board or the chief board reads the EER trend, not just the most recent period. A single high-mark EER under a generous reporting senior is less credible than three consistent high-mark EERs under different reporting seniors in different billets. Ask your ITC directly: where does your EER profile rank among the IT1s the command has evaluated over the last three cycles?
  • Multiple C-schools on record — Cisco, Microsoft infrastructure, DINFOS or CG-specific IT pipeline — relevant to the credential tier the ITC billet requires.
    The C-school pipeline is competitive and billet-constrained. Identify the two or three courses most relevant to your technical gaps and the ITC billet credential profile, build the training request before the selection window opens, and clear the watch schedule conflict in advance. The IT1 who has the request ready before the ITC asks is already ahead of the selection cycle.
  • Permanent Cutterman device qualifying sea time, if applicable; awards profile (Achievement Medal, Commendation Medal, Letter of Commendation) consistent with compliance program leadership and incident response work.
    The awards profile is a visible signal on the chief board and the personnel record. A compliance program that runs cleanly for three years with no critical DISA findings, a successful ATO renewal, and a cybersecurity incident response that prevented a reportable breach is an Achievement Medal write-up — write it and submit it. The awards that the command does not write are the ones that never appear on the chief board record.

Technical Mistakes — Concrete Consequences

  • Signing an IT2 work-authorization recommendation because the petty officer is motivated rather than because they can independently manage a POAM entry and work a network fault to root cause without escalation.
    The first unauthorized change the IT2 makes after receiving expanded authorization generates an AO compliance finding, and the ITC reads the recommendation letter back to the IT1 who signed it at the next performance counseling.
  • Letting the unit STIG compliance status drift during heavy operational tempo because the ITC knows the backlog.
    A CAT I POAM entry that runs open for 90 days without a documented remediation or a signed risk acceptance is the first item on the District CIS staff audit checklist; when the audit generates a critical finding, the compliance record names the IT1 who was the program's working-level owner during the drift window.
  • Making a production configuration change — firewall rule modification, DNS entry, domain trust modification — without a change ticket and without the ITC aware.
    The network outage or the compliance anomaly that follows traces to the change log, and the IT1 who made an undocumented production change is explaining it to the ISSO and the commanding officer at the same time — which is not a career-building conversation.
  • Conflating being technically aligned with the ISSO with being personally comfortable. You push back in the office on risk acceptance decisions that exceed what the ATO envelope actually authorizes — before the finding becomes the AO's problem.
    The IT1 who agrees in the meeting and says nothing while a CAT I finding is deferred for a third cycle is the technician the investigating officer quotes in the incident report as having observed the non-compliance without escalating.
  • Treating the DoDD 8140.01 credential renewal and the CEU maintenance cycle as the command admin officer's problem.
    An expired IAT baseline certification on a billet is a compliance gap the ISSO documents in the next ATO assessment, and the CGPSC billet chart names the IT1 in the billet with the lapsed credential — which is a chief board visibility item of the wrong variety.

Career Decisions at This Rank

  • Pursue IAT Level III (CASP+ CE or DoDD 8140.01 equivalent) now versus waiting for a command-funded C-school slot.
    The CASP+ CE is a self-study exam that does not require a C-school slot — it requires a study calendar and exam fee. The ITC billet's technical credibility baseline is IAT Level III; arriving at the chief board without it is a visible gap in a small community where every ITC on the board knows the credential requirements. The IT1 who funds the exam out of pocket and studies nights and weekends is 90 to 180 days from closing the gap; the one who waits for command funding may wait through two or three budget cycles. The credential is the gatekeeping item — close it on your timeline, not the command's.
  • SWE and chief board path versus applying for Officer Candidate School or the Coast Guard direct commissioning program.
    The CG's direct-commission Cyber officer pipeline (CG-26 or equivalent C4I officer track — verify current designation against ALCGOFF policy) is a realistic option for a credentialed IT1 with a bachelor's degree. The officer path trades the enlisted-track institutional credential network (ITC/ITCS/ITCM) for a different career arc — commission, OCS, post-commissioning assignment to a C4I or cyber staff billet, and the officer advancement structure. The honest analysis: the IT rating's senior enlisted career is highly credentialed and operationally respected within the CG; the officer cyber path is narrower and more dependent on political visibility at the District and Area CG staff level. An IT1 who loves the technical compliance work and wants to stay close to the network infrastructure generally has a stronger career outcome on the enlisted track. An IT1 who wants the command authority and the broader strategic portfolio should evaluate OCS seriously.
  • Stay operational (sector / cutter billet) versus pursuing a TRACEN cadre or District CIS staff billet for career broadening.
    The CG is small enough that a TRACEN Petaluma IT A-school or C-school instructor billet — or a District CIS staff billet as a senior IT reviewer — is a career broadener that has institutional weight. Operational billets produce the compliance record and the EER profile; instructor and staff billets produce the institutional network and the visibility to the rating's senior enlisted leadership. The chief board reads both; a career that has only operational billets can look linear in a community where the most competitive ITCS candidates have a mixed portfolio. The timing window for a non-operational broadener is typically IT1 year two or three — after the compliance program competency is established and before the chief board submission.
  • Lateral transfer to the ET (Electronics Technician) rating for a broader technical portfolio versus staying in IT.
    The ET rating covers RF communications, GMDSS, radar, and shipboard electronics systems — a broader hardware and signals portfolio than IT's network and cybersecurity focus. The CG allows rating conversion; the trade-offs are real. IT credential value (CompTIA Security+ CE, CASP+ CE, Cisco) translates directly to the commercial IT and cybersecurity market with an active clearance; ET credentials (FCC GROL, GMDSS) translate to commercial maritime and federal telecom. An IT1 planning a post-CG career in federal IT or cleared contracting stays in the IT rating. An IT1 who wants the merchant mariner and commercial maritime lane, or who finds the network compliance work less engaging than the physical RF and systems work, considers the ET lateral.
  • Reenlist past 10 years versus separating with a federal civilian transition plan.
    The 10-year mark is a natural decision window for an IT1 with an IAT Level II or III credential, an active clearance, and a CGPSC-documented compliance record. The federal civilian IT Specialist market at GS-09 to GS-12 compensates materially above E-6 base pay in most duty-station markets; cleared DoD/DHS contractor roles compensate above GS-12 in many cases. The honest calculus: if the chief board is not competitive and the credential stack is already strong, separation at 10 with a transition plan is financially rational. If the chief board is competitive and the ITC community is sponsoring the IT1 actively, the 20-year retirement vesting point and the post-retirement market at ITCS/ITCM credential level are worth the additional 10 years. Run the numbers with the actual current locality pay tables and the CG retirement multiplier — the math is not sentimental.

How the Seat Varies by Unit Type

  • Small boat station (IT1 as sole credentialed IT)
    You are the entire IT shop. No IT2 peer, minimal ITC oversight beyond monthly check-ins or phone calls. Every compliance action, every network fault, every help-desk escalation is yours. The ATO documentation and the POAM are yours in full. The advantage: you run the program to your standard without committee. The risk: there is no peer check on your work and the ITC who visits quarterly is not seeing the day-to-day. Build the documentation and the change-log discipline as if the District CIS staff is visiting next week, every week.
  • Sector or District information management office (IT1 in a team under an ITC)
    The program is the ITC's; your job is running the daily execution without requiring the ITC to manage the calendar. The senior IT1 in a District IMO may have one or two IT2s and a non-rate; the compliance calendar, the POAM management, and the STIG scan outputs are your daily work. The ITC handles the ISSO and command interfaces; you handle the technical program. The development path here is faster because you can see the ITC work directly — watch how the ITC briefs the ISSO and prepare to inherit that interface.
  • National Security Cutter or Offshore Patrol Cutter (C4I division under the Chief Engineer)
    The cutter IT1 is embedded in a larger engineering and C4I organizational structure. You answer to the ITC in the C4I division, who answers to the Chief Engineer, who advises the CO. The network infrastructure is shipboard and specialized — SIPRNET connectivity, shipboard LAN architecture, Automated Identification System (AIS) integration, and C2 communications systems that interface with the C4I officer and the OOD. The compliance program runs the same STIG and POAM framework, but the system inventory includes shipboard systems with unique configuration requirements. The operational tempo on a six-month INDOPACOM or Caribbean patrol means the compliance calendar must be maintained underway, not caught up in port.
  • CG Communications Area Master Station (CAMS Atlantic or Pacific)
    The CAMS billets are high-technical-scope, large-infrastructure assignments. CAMS Atlantic (Chesapeake, VA) and CAMS Pacific (Point Reyes, CA) run the CG's long-range communications infrastructure — HF, GMDSS, and various communications relay functions. An IT1 at CAMS is working with a larger network infrastructure, more complex system portfolios, and more direct engagement with DoD and DHS communications oversight than a sector or station billet provides. These billets are career-broadening at the IT1 level and produce an EER record that is visible to the ITCS and ITCM community.
  • TRACEN Petaluma IT A-school or C-school cadre billet
    The IT instructor track at TRACEN Petaluma, CA is the institutional credential-building path. You are shaping the next IT cohort, writing and delivering technical curriculum, evaluating A-school students, and building the institutional read on the rating's entry-level pipeline. The technical work is lighter than an operational IT shop — you are not running a production ATO cycle daily. The career value is the visibility to the CG's senior IT leadership (TRACEN leadership, the rating force master chief, the community manager) and the network in the chiefs' mess cadre at Petaluma that sponsors the most competitive chief board candidates.

What Good Looks Like at This Rank

The good IT1 is the senior tech the ITC sends on a solo District CIS staff site visit without a chaperone and without a pre-brief phone call to the District staff. The STIG compliance report is current on every system class, the POAM has no overdue CAT I entries without a signed risk acceptance, the change logs are complete back to the last audit cycle, and the ATO documentation is within its review window. The IT2 who answers the District staff's questions about the POAM remediation process does so without looking at the IT1 for permission, because the IT1 built the qualification program that gave the petty officer the vocabulary and the judgment to handle the question. That after-action is one page because there were no surprises — the only meaningful note is that the unit's change-ticket discipline is a reference standard for the sector. The IT1 who looks good on paper but cannot earn that site visit is the one who manages the compliance record without building the team that runs the program. The sustainable version is the petty officers who advance on schedule, the ITC who wrote the strongest chief board endorsement of the last five cycles because the IT1's EER record and credential stack gave him something real to say, and the command ISSO who calls the IT1 first — before the District CIS staff — when a STIG finding needs a technical explanation. That combination is what a chief's moss sponsorship is built on. Post-service the same IT1 walks into the federal civilian IT Specialist pipeline (USCG civilian GS-09 to GS-12, DHS/DoD contractor) with a credential stack, an active clearance, a documented compliance record, and a reference network in the ITC and ITCS community that the hiring official will call. The IT1s who plan this conversation 36 months out — not three months before retirement — land in the roles the market is competing for. That is what the ITC wants to see and that is what the chief board reads when a competitive candidate's career planning is visible in the record.

Preview — The Next Rank

ITC (E-7, Chief Petty Officer) is where the job description changes in a way that is not fully legible from below. The compliance program you have been running as the technical owner becomes the program you are responsible for at the command level — not in the server room but in the ISSO brief, the commanding officer's readiness report, and the District CIS staff audit response. The ITC who is still personally running STIG scans and POAM remediation is an ITC who has not made the transition; the ones who last are the ones who built IT1s and IT2s who run the program and then got out of their way. The Chief Petty Officer Academy at TRACEN Petaluma, CA is the first event that happens after pinning — the CPO initiation cycle and the CPOA course are a deliberate cultural break from the petty officer career. The Mess is a real institution with real expectations; the ITC who treats the Mess work as overhead is the one the senior chiefs in the Mess note quietly and the one who does not see a ITCS billet recommendation when the window opens. Professionally, the ITC inherits the C4I readiness culture ownership. The ATO documentation is your compliance program, the POAM is your compliance record, and the ISSO is your peer relationship rather than your supervisor relationship. The technical gap-closing is still yours — the CASP+ CE CE renewal, the new STIG benchmark familiarity, the evolving DoDD 8140.01 workforce framework — but the way you exercise it is through the IT1s who are looking to you to set the standard, not through your own hands on the keyboard. That transition is the job of the first 18 months at ITC.
FAQ

IT E6 — Frequently Asked Questions

Q01What does a E6 IT (Information System Technician) actually do?
You are typically the senior enlisted IT at a small boat station or sector IT shop, the LPIO of the communications and information systems department at a district, or the senior IT technician in the C4I division on a National Security Cutter or Offshore Patrol Cutter under the Chief Engineer or the Command's IT officer.
Q02What's the most important thing to know as a E6 IT?
IT1 (E-6) is the rank where the compliance program is yours to own — not oversee.
Q03What does a typical day look like for a E6 IT?
Time-blocked day at the E6 IT rank tier: 0530–0630 PT — unit or self-directed; the IT shop is small enough that the IT1's physical readiness is visible to the ITC and the command, and an IT1 who is below average on PFT performance is a visible gap on the chief board record, 0630–0730 Shower, breakfast, check email and any overnight help-desk tickets or network monitoring alerts before the workday opens. The IT2 on duty handles first-responder tickets; anything escalated overnight lands in your queue with a description of what was tried,…
Q04What mistakes get E6 IT soldiers fired or relieved?
Phoning the IAT Level III credential pursuit. The CASP+ CE or its DoDD 8140.01 successor-category equivalent is the ITC billet's technical credibility baseline; arriving at the chief board without it is arriving to a gunfight with a pocket knife; Letting the ATO or POAM drift during a heavy underway or operational cycle. The compliance program is a continuous obligation, not a surge-and-recover rhythm;…
Q05What career decisions matter most at the E6 IT rank tier?
Pursue IAT Level III (CASP+ CE or DoDD 8140.01 equivalent) now versus waiting for a command-funded C-school slot — The CASP+ CE is a self-study exam that does not require a C-school slot — it requires a study calendar and exam fee. The ITC billet's technical credibility baseline is IAT Level III; arriving at the chief board without it is a visible gap in a small community where every ITC on the board knows the credential requirements. The IT1 who funds the exam out of pocket and studies nights and weekends is 90 to 180 days from closing the gap;…
Q06What's next after E6 for a IT (Information System Technician) in the Coast Guard?
ITC (E-7, Chief Petty Officer) is where the job description changes in a way that is not fully legible from below.
Q07What manuals and regulations does a E6 IT need to know cold?
COMDTINST M5500.13 (current series) — Coast Guard Information and Life-Cycle Management Manual. You are the unit authority on what this publication requires and where the configuration boundary ends.; DoD 8570.01-M / DoDD 8140.01 (current revision) — Cyberspace Workforce Management. At IT1 you are the billet compliance and credential tracking authority for the IT shop; your ITs' certifications are your professional-development program.;…

Based on 14 tips from 0 contributors

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