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
ITE8-E9

Information System Technician

E-8 to E-9 (Senior NCO) · Coast Guard

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

ITCS and ITCM (E-8 and E-9) are the rating standard — what every IT in the service measures the credential floor against and what every ITC is trying to become. At this tier the job is the rating itself: the billet distribution, the credential pipeline, the compliance culture at commands you have never visited, and the post-CG transition conversation you have honestly with junior chiefs who are watching whether the rating is worth 20 years. Plan the second career 36 to 48 months out. The market for a credentialed, cleared senior CG IT chief is competitive; the one who plans it owns the conversation.

The Honest MOS Read
ITCS — Information Systems Technician Senior Chief Petty Officer (E-8) — and ITCM — Information Systems Technician Master Chief Petty Officer (E-9) — are the apex of the CG's IT rating enlisted career and among the most technically and institutionally credentialed senior enlisted positions in the service. At this tier the day-to-day job description visible from below is misleading: it looks like a bigger version of the ITC job. It is not. The ITCS and ITCM are managing the rating itself — the credential pipeline, the billet distribution, the compliance culture across dozens of commands, and the institutional memory that no single ATO documentation package can contain. As ITCS you are typically the senior IT chief at a major sector or district information management office, the senior enlisted IT advisor at a Coast Guard Communications Area Master Station (CAMS Atlantic at Chesapeake, VA, or CAMS Pacific at Point Reyes, CA), the senior enlisted presence in the CG's C4I programs or Command, Control, Communications, Computers, and Intelligence operations functions, or a leadership-cadre billet at TRACEN Petaluma running the IT A-school or C-school pipeline and shaping the rating's training standards. As ITCM you are on the senior enlisted or command master chief track — at a major Sector, a District headquarters, the CG Cyber Command (verify current organizational name against CGPSC and Commandant policy), the CG Communications System Center or its successor organization, Atlantic or Pacific Area headquarters, or as Command Master Chief at a large cutter or major shore command — and your name is on the slate the service reads at the senior-enlisted council and the CGPSC workforce planning sessions. The cybersecurity posture advisory role at ITCS and ITCM is materially different from the ITC's compliance program ownership. You are not running the ATO cycle — you are advising the Area CIO, the District commander, or the Sector commander on the C4I readiness posture across a portfolio of commands. The command that has a lapsed ATO or a critical DISA finding under your Area advisory portfolio is a command whose ITCS or ITC failed to maintain the standard you set — and your advisory role is to identify that gap before the DISA assessment team does. This requires institutional situational awareness across the IT rating network that the ITC cannot see from a single command's server room. DoDD 8140.01 and the evolving federal cybersecurity workforce framework are the ITCS and ITCM's primary external reference. The policy has been in active revision from the older DoD 8570.01-M IAT/IAM/IASAE structure toward the DCWF (DoD Cyber Workforce Framework) work-role categories; the ITCS who is current on the workforce category mapping, the approved certification list, and the emerging requirements (zero-trust architecture, cloud infrastructure, OT/ICS security — verify DISA and CISA policy for current CG applicability) is the one the CGPSC community manager and the Area CIO trust as the rating's technical authority. The NIST Cybersecurity Framework, NIST SP 800-207 (Zero Trust Architecture), and the CISA CPGS (Cross-Sector Cybersecurity Performance Goals) are increasingly relevant to the IT rating's senior enlisted advisory role as the DoD and DHS move toward enterprise-level cybersecurity standards that exceed the STIG-and-POAM baseline. The ITCS who can brief the Area CIO or the CG CISO on zero-trust implementation implications for the service's network architecture — not just the compliance posture — is the one the service needs and the one the post-CG market is looking for. The post-CG market at ITCS and ITCM is exceptionally strong for those who have planned the transition. USCG civilian IT Specialist positions at GS-11 through GS-13 (and GS-14 for senior program management roles) are the direct federal civilian translation; DHS cybersecurity and IT program management positions, DoD cleared-contractor roles at L3Harris, Booz Allen Hamilton, SAIC, Leidos, ManTech, Peraton, and MITRE FFRDC are the cleared-contractor translation. USCYBERCOM and NSA contractor support billets are available to ITCSs with the clearance level and the operational cyber background from CG Cyber Command or C4I program office tours. The IT chief who holds an active IAT Level III credential, a CISSP or equivalent, and a documented 20-year federal network administration record walks into the hiring manager's office with the negotiating position — not the application form.
Career Arc
  • 01ITCS pinned following senior enlisted board process; Senior Enlisted Leadership Course (SELC) at TRACEN Petaluma, CA completed; credentials at IAT Level III with CISSP or equivalent under pursuit.
  • 02Senior IT chief at major sector or district, CAMS Atlantic/Pacific, CG C4I programs, or TRACEN Petaluma cadre — ITCS billet portfolio builds the rating community visibility.
  • 03ITCM consideration — Command Master Chief candidacy at a major cutter or shore command, or senior IT advisor at CG Atlantic/Pacific Area or District headquarters.
  • 04Rating slate board participation per CGPSC tasking — billet distribution, credential pipeline shortfalls, retention analysis, emerging C4I system requirement advocacy.
  • 05Post-CG transition planning actively managed 36 to 48 months out — credential currency, clearance maintenance, federal civilian pipeline, contractor market targeting.
  • 06ITCM tenure — senior enlisted council, command climate ownership, and the mentorship of two to three ITC-to-ITCS pipeline candidates per assignment cycle.
  • 07Terminal leave and retirement — the credential package, the clearance, and the institutional reputation the post-CG market calls about.
Common Screwups
  • ×Confusing seniority with technical currency. The DISA STIG benchmarks, DoDD 8140.01 workforce category updates, NIST publication revisions, and zero-trust architecture requirements move faster than a 24-year career's institutional memory. The IT2 who just completed the current DISA training knows that corner better than you do. Let them brief it and stand behind them. The rating network sees who is honest about the gap.
  • ×Allowing an ITC at a subordinate command to run a drifted ATO or a sloppy compliance program without intervention. The District CIS assessment team hears about it when that unit's ATO generates a critical finding, and the investigating officer names the senior enlisted advisor who tolerated it.
  • ×Treating the warm-up to retirement as if the job is over. Until you walk out of formation for the last time, the rating is still your job — and the rating reads what you tolerated in your last two years more than what you built in your first twenty.
  • ×Stopping personal PT and technical engagement because 'I am at District now.' The IT shop respects the rating's most senior anchors only as long as they can still read a POAM, interpret a STIG finding, and walk through the server room without looking like a visitor.
  • ×Waiting until 12 months before retirement to begin the federal civilian or contractor job search. The USAJOBS application process for competitive GS positions takes three to eight months from application to reporting date; the contractor market moves faster but requires active networking with the ITCS and ITCM alumni network that you should have been cultivating for the past four years.

A Day in the Life

  • 0530–0630PT — the ITCM who stops setting the physical readiness example is the ITCM who has abdicated the most visible leadership signal in a small service. The PFT score at ITCM is still a number the junior ITs see.
  • 0630–0730Shower, breakfast, senior enlisted council or CMC morning prep — if there is a command climate issue, a discipline case, or a senior enlisted advisory item that needs to be in front of the CO today, this is when it is framed.
  • 0730–0830Area CIO or District commander morning update — the ITCM's primary command interface at this tier. ATO portfolio status, any DISA assessment findings from the previous week, any C4I readiness advisory item that the commander needs to know before the day's operational decisions are made.
  • 0830–1000IT rating community management work — reviewing ITCS EER drafts, preparing for or following up from a CGPSC rating slate board call, drafting a workforce advisory memo on a credential pipeline gap or billet distribution imbalance that the community manager needs to address in the next slate cycle.
  • 1000–1130ITC development conversations — one ITC per week for a development map review: credential status, SELC timing, broadening billet candidacy, EER trajectory, and the specific performance outcome the ITC is building for the ITCS board submission.
  • 1130–1230ISSO or C4IT Service Center coordination — enterprise-level cybersecurity posture update, any DISA or CISA guidance that has been published in the last 30 days that affects CG network architecture or compliance requirements, and the ITCM's advisory position on implementation timing.
  • 1230–1330Lunch — with the senior enlisted council or the CMC community when available. The senior enlisted network at this tier functions partly through informal channels; the ITCM who eats alone every day is not working the network the job requires.
  • 1330–1500ATO portfolio visibility review — not running scans, but reviewing the ITCS's ATO renewal schedule summary: which commands have ATOs coming up in the next 90 days, which POAM resolution timelines are realistic, where is the compliance risk concentrated in the current portfolio.
  • 1500–1630Technical currency — NIST SP 800-207 zero-trust architecture update reading, DoDD 8140.01 workforce category mapping review, DISA STIG release notes for the system classes in the command portfolio. The ITCM who stops reading the policy releases is the ITCM whose advisory brief cites superseded requirements.
  • 1630–1730Post-CG transition advisory conversations — one junior chief per month for an honest, numbers-based transition conversation: credential profile, current GS-12 IT Specialist salary at their likely retirement location, current contractor rate range, USAJOBS posting review for the roles matching their credential stack. The ITC who plans the transition owns it; the one who doesn't takes what opens first.
  • 1730–1900Senior enlisted council obligations — Mess meeting, discipline review, climate report preparation for the CO, or new-arrival sponsorship follow-up. At ITCM these obligations are not overhead; they are the job the anchor pin represents.
  • 1900–2100Personal time — family, physical recovery. The ITCM who does not protect the off-hours is the ITCM the Mess eventually notices is running on fumes, which is not the read the rating's most senior member should produce.
  • 2100–2200CISSP or DoDD 8140.01 update review, or preparation for the next day's senior advisory brief. The credential renewal and the technical currency are not optional at this tier — they are the professional standard the rating inherits from you.

Weekly Cadence

Monday is the advisory week-setter. The ATO portfolio visibility review, the senior enlisted council touch-base, and the ISSO or C4IT Service Center coordination call all land on Monday to set the advisory posture for the week. The Area CIO or District commander readiness brief — if scheduled this week — is prepped by end of Monday afternoon so the briefing materials reflect the most current compliance picture. Any DISA publication or CISA guidance that landed over the weekend is reviewed before the Monday brief goes out. Midweek is workforce and community. The ITC development conversations, the CGPSC rating community coordination calls (if scheduled), and the ITCS EER review block all live in the Wednesday–Thursday window. The post-CG transition advisory conversations with junior chiefs are scheduled during this window — one per week, 30 minutes, numbers-based and specific. The technical currency study — NIST and DISA publication reading — is protected in the Thursday afternoon block. It does not move for anything short of a command-level cybersecurity incident. Friday is documentation, outreach, and transition. The weekly ATO portfolio status note to the ITCS network goes out Friday afternoon — one paragraph per major command in the portfolio, ATO status, POAM resolution rate, and any DISA or District CIS advisory items pending. The ITCM's retirement planning block — credential renewal calendar, USAJOBS market review, contractor market networking — runs Friday afternoon alongside the transition advisory follow-up from midweek conversations.

Key Skills — How to Drill Each

  1. 01
    Run a major sector or district IT program as the senior enlisted IT authority — ATO portfolio management, billet qualification and credential compliance across the IT workforce, DISA STIG and IAVM oversight, change management governance, and the senior enlisted interface with the command's ISSO, C4I officer, and commanding officer.
    The program management at ITCS is a portfolio view, not a system view. You track the ATO renewal schedule for every system class in the portfolio, the credential expiration for every IT billet in the command, the POAM resolution rates across the IT1 and ITC workforce, and the DISA assessment timeline against those metrics. The ITCS who briefs the Area CIO on portfolio compliance posture in a quarterly status update — proactively, not in response to an audit finding — is the one the Area CIO calls when a C4I readiness decision needs a senior enlisted technical read.
  2. 02
    Mentor four to six ITCs into ITCS-board-competitive candidates — EER trajectory, DoDD 8140.01 credential profile, broadening assignment timing, SELC completion, command sponsorship.
    The ITCS who produces two ITCS-select candidates from a five-year assignment cycle has done the job. Build the development map for each ITC by the end of the first quarter: credential gap timeline, SELC window, broadening billet candidacy (CAMS or Petaluma cadre or District CIS staff), EER trajectory against the last three cycles, and the awards profile that should have been submitted but was not. The ITC who shows up to the ITCS board with a blank awards section on a four-year record is carrying a gap the ITCS could have closed.
  3. 03
    Sit on an IT rating slate or community manager board per CGPSC tasking — billet distribution gaps, credential pipeline shortfalls, retention analysis, emerging C4I system requirements.
    The slate board is where the rating's institutional decisions are made for three years. The ITCS who sits the board and can identify the billet distribution gaps — the cutter billets that are going unfilled because the sea-time requirement is competing with the credential study calendar, the CAMS billets that are drawing only junior ITCs because senior ITCs are taking shore assignments near family — and can articulate a specific recommendation is the one the community manager implements. Prepare for the board with current CGPSC workforce data; do not rely on anecdote from your last assignment.
  4. 04
    Brief the Sector or District commander, Area commander, or Area CIO on IT and cybersecurity readiness, retention, and the things they cannot see from the bridge or the flag conference room.
    The ITCS brief to the Area CIO or District commander is a risk advisory, not a status update. The things the command cannot see from the flag conference room are: the ATO gap that is being papered over by a risk acceptance that does not reflect current threat intelligence, the credential shortfall that the command is not funded to fix this fiscal year, the patch-compliance problem that is two inspection cycles from a significant finding. Those are the items the ITCS brings to the brief — with a specific recommended action, a cost estimate if relevant, and a timeline. The ITCS who brings only good news is the ITCS whose briefings stop being scheduled.
  5. 05
    Walk the IT division or the network operations center during a cybersecurity incident, an ATO finding, or a critical infrastructure event — identify the broken control or the procedural gap before the investigating authority does.
    The post-incident walk-through at ITCS is not a technical investigation — it is a leadership accountability review. Walk the ITC through the incident timeline with the question: where did the qualification program fail, where did the change management process fail, where did the POAM monitoring fail? The ITCS who can present the command's incident response with a root-cause analysis that names the systemic gap — not just the technical failure — is the one the CO trusts to prevent the next incident.
  6. 06
    Hold the post-service credential conversation with junior chiefs honestly — the path from an active IAT Level III credential to a federal cleared contractor role, the USCG civilian IT Specialist pipeline, the DHS and USCYBERCOM contractor support billet — because the rating loses senior ITs who do not plan, and the slate notices the ITCSs who mentored a generation through it.
    The conversation is specific: what credential does the ITC hold, what is the clearance level, what is the realistic GS-11 to GS-13 salary at the likely duty-station location, what is the contractor rate for the same credential profile. The ITC who knows the numbers plans the transition early enough to own the process. The ITCS who generalizes ('the market is good for IT people') is not giving the ITC the information needed to make a decision. Pull the current USAJOBS GS-12 IT Specialist postings for the ITC's likely retirement location; pull the Indeed or LinkedIn contractor rate ranges for the credential profile. That is the conversation.

Manuals & References — What Chapters Matter

  • COMDTINST M5500.13 (current series) — Coast Guard Information and Life-Cycle Management Manual
    At ITCS and ITCM you are the rating's walking authority on what this instruction requires — and you are advising the Area CIO or District commander on when CG-specific policy diverges from or aligns with DoD-level requirements. Verify the current series against the CG Directives System and note where the CG's implementation of DoD cybersecurity requirements differs from the parent policy.
  • DoDD 8140.01 — Cyberspace Workforce Management and the DoD Cyber Workforce Framework (DCWF)
    The DCWF is the evolving replacement for the older IAT/IAM/IASAE structure; workforce category designations are shifting. At ITCS and ITCM you are the community's credential compliance authority and the rating's institutional memory for the DoD 8140 framework as it evolves. Track the DCWF work role categories that apply to CG IT billets and understand how the approved certification list maps to the current workforce categories — the CGPSC community manager uses your institutional knowledge to implement CG-specific workforce management policy.
  • NIST SP 800-53 (Rev 5), NIST SP 800-37 (Rev 2), and NIST SP 800-207 (Zero Trust Architecture)
    At ITCS and ITCM you are advising senior leadership on risk posture, not running compliance scans. SP 800-207 (Zero Trust Architecture) is increasingly relevant as the DoD and DHS move toward zero-trust network architecture requirements; the ITCS who can brief the Area CIO on ZTA implementation implications for CG network architecture is the one the service needs as the architecture transition accelerates. NIST publications are freely available on the NIST CSRC website; read the executive summaries and the applicability sections before the next Area CIO readiness review.
  • COMDTINST M1000-series — Coast Guard Personnel Manual (senior enlisted sections on command master chief obligations, senior enlisted council, and the CGPSC workforce management framework)
    At ITCM you sign as the senior enlisted on the command's compliance posture and you sit on the senior enlisted council. Know the CMC obligations under the Personnel Manual: what the commanding officer expects of the CMC in terms of climate reporting, the EO posture, and the enlisted welfare function. The CMC who reads the Personnel Manual's senior enlisted section as optional professional development has not made the ITCM transition.
  • CISA Cybersecurity Performance Goals (CPGs) and CISA Zero Trust Maturity Model
    CISA (Cybersecurity and Infrastructure Security Agency) publishes cross-sector cybersecurity performance goals and the federal zero-trust maturity model that DHS components — including the Coast Guard — are implementing. The ITCS who is current on CISA CPG applicability to CG IT infrastructure is the one whose advisory brief to the Area CIO reflects the current federal cybersecurity posture requirement, not just the legacy STIG-and-POAM baseline.
  • Senior Enlisted Leadership Course (SELC) curriculum and Command Master Chief community professional development reading list, TRACEN Petaluma, CA
    The SELC is the gateway to the ITCS candidacy pool and the Command Master Chief program materials at Petaluma are the ITCM's continuing professional development framework. Staying current on the curriculum — attending CG senior enlisted leadership conferences, contributing to the SELC reading list through the TRACEN cadre channels — keeps the ITCS and ITCM visible as institutional contributors to the rating's professional development program.

Standards — How to Hit Each

  • Senior Enlisted Leadership Course (SELC) graduate; command master chief billet, ITINC of a major sector or district IT organization, or senior enlisted IT advisor at a CG major command — the visible ITCM track.
    The ITCM pipeline runs through specific billet sequences the CGPSC community manager and the senior enlisted council track. Understand the current ITCM billet sequence — which ITCS billets feed the ITCM candidacy pool, which CMC billets have historically produced ITCMs, what the typical billet count and service-length window is for ITCM selectees. Ask the current ITCM directly: what does the CGPSC look for in the ITCM record that is not visible in the EER summary?
  • IAT Level III credential (CompTIA CASP+ CE or current DoDD 8140.01 equivalent) held; CISSP or equivalent IAM/IASAE-level credential under active maintenance.
    The CEU renewal cycle for CASP+ CE (75 CEUs per three-year period), Security+ CE (50 CEUs per three-year period), and CISSP (120 CPE hours per three-year cycle) requires active management. Build a renewal calendar that front-loads the CEU accumulation in the first 18 months of each cycle — the ITCS who discovers in month 34 that 40 CEUs are still needed is the ITCS whose credential lapses on the most visible compliance audit in the rating.
  • Command ATO and STIG compliance posture clean — no lapsed ATOs, no overdue CAT I POAM items without documented risk acceptance, zero DISA or District CIS audit critical findings during tenure.
    At ITCS and ITCM the compliance posture standard is: the DISA field assessment team visits a command in your advisory portfolio and finds no critical findings. That standard requires the ITCS to build a 90-day visibility window across every command's ATO portfolio — not to run the scans, but to know which ATO renewal is approaching and which POAM remediation timeline is realistic versus aspirational. The ITCS who discovers a critical finding from a DISA assessment report that they did not know was coming has failed the advisory function.
  • Command EER profile clean — the ITCs and IT1s under this ITCS are pinning on schedule and the EER narrative is consistent across multiple periods and multiple commands.
    Track the advancement outcomes for every ITC and IT1 who served under your EER authority across the full ITCS tenure. If the advancement rate is below the community average, identify whether it reflects EER calibration drift, credential pipeline gaps, or billet assignment timing. The CGPSC community manager tracks this data; the ITCS who is tracking it proactively and can identify the gap is the one whose workforce advisory input is implemented.
  • Zero senior-enlisted integrity incidents — financial, fraternization, OPSEC, unauthorized system access, or data handling violations. At ITCS and ITCM the record is the only thing the senior enlisted council sees.
    There is no procedural guidance here — at ITCS and ITCM the integrity standard is sustained by choice, every day, through 28 years of decisions under circumstances where the right choice cost something. The ITCS or ITCM who makes the right call every time, visibly and without qualification, is the one the junior IT community holds as the rating standard. That is the job description at this tier, accurately stated.

Technical Mistakes — Concrete Consequences

  • Going public with disagreement with the ISSO, the C4I officer, the Area CIO, the District CIS staff, or the commanding officer.
    The ITCM who vents about a command decision to the junior chiefs in the Mess has just told the entire senior enlisted community that the rating's most senior NCO does not trust the chain of command — and the read circulates from the Mess network to the CGPSC community manager's awareness faster than any formal reporting process. You take it in the office; you document the recommendation; you walk out aligned.
  • Confusing seniority with technical currency — treating the DoDD 8140.01 update, the new STIG benchmark, the NIST SP 800-207 zero-trust guidance, or the CISA CPG revision as things the IT2 needs to know.
    The ITCS or ITCM who stops reading the DoD and NIST publication releases is the senior chief whose advisory brief to the Area CIO cites a superseded compliance framework. The IT field moves faster than a 24-year career's institutional memory; the senior ITs who maintain their technical currency are the ones whose advisory brief the Area CIO uses and the ones whose post-CG market value remains competitive.
  • Stopping personal PT and technical engagement because 'I am at District now.'
    The IT shop respects the rating's most senior anchors only as long as the ITCS can still read a POAM, interpret a STIG finding, and walk through the server room without looking like a visitor. The ITCM who last saw a network diagram two assignments ago is the ITCM whose advisory brief relies on what the ITC told him, not what the ITCM observed — and the senior IT community notices the gap before the Area CIO does.
  • Letting an ITC run a drifted ATO or a sloppy STIG compliance program at a subordinate unit because 'the ITC has it handled.'
    The first time that unit's ATO is flagged in a DISA assessment or a critical infrastructure event generates an investigative review, the investigating officer names the senior enlisted IT advisor who was in the advisory portfolio and tolerated the compliance drift. At ITCS and ITCM the advisory relationship to subordinate commands is not optional oversight — it is the job.
  • Treating the pre-retirement period as if the job is winding down.
    The rating reads what the ITCM tolerated in the last two years as clearly as it reads what the ITCM built in the first twenty. An ITCM who coasts through the final 18 months — missing Mess meetings, deferring ITC development conversations, allowing compliance drift — writes the legacy the rating inherits. The ITCSs who observed those last two years are the ones who will set the standard for the next decade; what they observed is what they implement.

Career Decisions at This Rank

  • ITCM candidacy versus a DoD or federal civilian lateral transition at the 20-year mark.
    The ITCM slate in the CG selects from a pool of one to two ITCSs per cycle in the IT rating; it is a narrow gate. The ITCS who is competitive for ITCM has a specific billet portfolio, SELC completion, a clean EER trend across multiple commands, and a Mess sponsorship from the current ITCM community. The ITCS who is not competitive for ITCM at the 20-year mark has a strong federal civilian or contractor transition profile if the credential stack is current and the clearance is active. GS-12 to GS-14 IT Specialist positions inside USCG, DHS, or DoD, and cleared contractor roles in the $110K–$180K range, are the 20-year market for a credentialed ITCS. The decision is financial, family, and career-satisfaction; run the retirement math honestly against the federal civilian and contractor salary projections before making it.
  • Pursue the CISSP certification versus maintaining the CASP+ CE as the primary credential at ITCS/ITCM tier.
    The CISSP is the credential the federal civilian IT Specialist market and the DoD/DHS contractor market recognize as the senior cybersecurity professional baseline for management and advisory roles. The CASP+ CE satisfies the DoDD 8140.01 IAT Level III technical requirement; the CISSP satisfies the IAM Level III and IASAE requirements and maps to DCWF work roles in cyber management and architecture. The ITCS who holds both is the hiring manager's candidate profile for GS-13/14 IT roles and senior contractor positions. The CISSP exam requires 125 to 175 questions (adaptive format) and five verified years of cybersecurity experience; most ITCSs qualify on experience. Budget 60 to 90 hours of study over three to four months. The credential is worth the preparation investment at this tier.
  • TRACEN Petaluma cadre billet versus operational or staff ITCS billet for the final ITCS assignment before ITCM consideration.
    The TRACEN Petaluma IT A-school cadre billet is the institutional leadership assignment that produces visibility to the senior CG IT leadership and the CGPSC community manager. The ITCS who served a Petaluma cadre tour is known by institutional reputation in the rating's senior enlisted network in a way that an operational ITCS billet at even a major sector does not produce. The trade-off: a Petaluma cadre billet is less operationally intense than a major sector ITCS billet, which means the EER narrative relies more on institutional contribution (curriculum development, student evaluation standards, cadre leadership) and less on operational compliance outcomes. Both are ITCM-competitive; the Petaluma cadre billet adds the institutional visibility dimension. Discuss the timing with the current ITCM before accepting the assignment.
  • CMC (Command Master Chief) track versus ITCM community-program track.
    The CG's senior enlisted community has both the Command Master Chief path (CMC for a major command or large cutter, where the ITCM is the command's senior enlisted leader across all rates) and the community program management path (senior IT advisor at a major Area or District command, rating force master chief track). The CMC path produces broader command authority and cross-rate senior enlisted leadership experience; the community program path produces deeper IT-rating institutional leadership. The ITCM who aspires to the CMC track needs to demonstrate senior enlisted leadership competencies beyond the IT compliance domain — climate, welfare, discipline, and community-of-action capability across all rates. The ITCM who is the rating's technical and institutional authority is best served by the community program track. Discuss both paths with the current ITCM and the CGPSC senior enlisted advisor before the ITCM slate process opens.
  • Plan the federal civilian transition versus the cleared contractor transition at 20+ years.
    The federal civilian IT Specialist path (USCG civilian GS-09 through GS-13/14, DHS, DoD) offers stability, federal benefits continuation, and TSP contribution matching — the stability of the government career track in a different suit. The cleared contractor path (L3Harris, Booz Allen Hamilton, SAIC, Leidos, ManTech, Peraton — or independent consulting with a specific cleared-contractor portfolio) offers materially higher compensation in the $130K–$200K range for ITCS/ITCM credential profiles, at the cost of benefits portability and employment stability. Most senior ITCSs and ITCMs do both over the post-CG career arc: a GS federal civilian role at 20 years for the benefits bridge and stability, then a lateral to a contractor role at GS-13/14 years of service (when the federal retirement benefit is established) for the compensation increase. The sequence matters; plan it 36 to 48 months out with a financial advisor who understands the military retirement to federal civilian to contractor income layering.

How the Seat Varies by Unit Type

  • Major sector or district information management office (ITCS as senior IT chief)
    The sector or district ITCS is the senior IT chief across the largest command portfolio in the CG IT rating. The compliance program spans multiple subordinate units' network infrastructure, the CAMS interface (if in the geographic footprint), and the District CIS staff advisory relationship. The IT workforce under the ITCS includes multiple ITCs, IT1s, IT2s, and IT3s; the EER throughput is the highest in the rating. The institutional visibility from a District-level ITCS billet is the most direct ITCM candidacy feeder.
  • CG Communications Area Master Station (CAMS Atlantic or Pacific)
    The CAMS ITCS manages the most technically complex IT infrastructure in the CG enlisted IT career. CAMS billets are large-scale communications relay infrastructure with a broader system portfolio and more direct DISA and interagency oversight than any sector or district assignment. The technical scope — HF communications, GMDSS relay, satellite communications, and various CG communications network functions — is the broadest in the IT rating. The ITCS who served a CAMS billet is known in the ITCM candidacy pool as the technically deepest senior chief in the rating.
  • CG Cyber Command or C4I programs office (ITCS as senior enlisted program advisor)
    The CG Cyber Command or C4IT Service Center ITCS is the senior enlisted cybersecurity advisor in the CG's enterprise cyber defense and C4I acquisition programs. The daily work is advisory and program management — working alongside CG officers, DoD CYBERCOM counterparts, and contractor support personnel on enterprise cybersecurity operations, architecture planning, and acquisition program technical requirements. The ITCS who serves this billet is the one the post-CG contractor market at DHS and USCYBERCOM is looking for specifically.
  • TRACEN Petaluma IT A-school or C-school cadre (ITCS as senior enlisted instructor leader)
    The Petaluma cadre ITCS sets the rating's training standards and shapes the technical and professional curriculum for the CG's IT workforce. The daily work is curriculum development, student evaluation, and instructor leadership — less operational compliance, more institutional standards-setting. The institutional visibility from the Petaluma cadre assignment is unmatched in the rating; the senior CG IT leadership and the CGPSC community manager know the Petaluma cadre ITCS by name. The ITCM track through Petaluma is the route most directly visible to the Commandant's senior enlisted leadership.
  • Command Master Chief at a major cutter or shore command (ITCM as cross-rate senior enlisted leader)
    The CMC assignment takes the ITCM outside the IT rating community management role and into the command's senior enlisted leadership across all rates and all programs. The ITCM's technical IT credibility remains the billet-qualifying factor, but the daily work is climate, welfare, discipline, retention, and the CO's senior enlisted advisory relationship — not ATO documentation. The CMC assignment produces the broadest CG senior enlisted leadership credential in the ITCM career and is the most direct path to the senior enlisted council at the Area or Commandant level.

What Good Looks Like at This Rank

The good ITCS and ITCM is the senior enlisted every IT in the service knows by face and reputation before they ever serve in the same command. The sector or district IT program runs because the ITC's standard on STIG compliance, POAM discipline, IAVM currency, change-management integrity, and DoDD 8140.01 credential tracking is not negotiable — because the ITCM set it and the ITCS enforced it. The ITCs pin ITCS. The IT1s pin ITC. The TRACEN A-school students know the name because the rating force master chief referenced it in the first week of class as the institutional standard for compliance program ownership. The command-level impact is direct and measurable. The sector or district IT program under ITCS leadership has no lapsed ATOs during the tenure, no critical DISA assessment findings, and a credential pipeline where every billet holder is at or above the DoDD 8140.01 baseline requirement. Those are not aspirational metrics — they are the specific ITCS performance outcomes the CGPSC community manager tracks across the service and the ones the Area CIO cites when the ITCS is recommended for the ITCM slate. The ITCM who can point to a five-year tenure with zero critical DISA findings across a major sector portfolio is the ITCM whose advisory brief to the next Commandant's C4I review is invited, not tolerated. Post-service the same ITCM walks into the federal IT market as the senior person in the room, not the candidate. The credential stack — IAT Level III, CISSP, 25 years of federal network administration with an active clearance and a CGPSC-documented compliance record — is the hiring manager's target profile, not the minimum qualification. USCG civilian IT Specialist GS-13 positions, DHS/USCYBERCOM contractor support billets at $150K–$200K depending on clearance level and location, and MITRE FFRDC or federally-funded research and development center roles in cybersecurity architecture and policy are the ITCM-level post-CG outcomes for those who planned the transition 36 to 48 months out, maintained the credentials, and built the professional network in the IT and cybersecurity community that the post-CG market calls first. The credential package the ITCM walks out with, and the mentorship pipeline of ITCSs and ITCMs that follow, are the rating's legacy — accurately stated.

Preview — The Next Rank

There is no next rank for the ITCM. The job after ITCM is the post-CG transition — and the ITCM who has planned it is the one who owns the conversation. The federal IT and cybersecurity market at the ITCM credential level is not competitive in the sense that the SWE and the chief board were competitive; it is negotiated. The hiring manager is not evaluating whether to hire the ITCM — they are evaluating which role to offer first. That is the difference 24 years of planned credential development, active clearance maintenance, and a documented CGPSC compliance record produces in the federal IT market. For the ITCM who is the rating force master chief or the senior enlisted advisor for the IT rating community — a function the CGPSC assigns to the most senior ITCMs per their community management structure — the next responsibility is the rating's institutional health for the decade after retirement. The billet distribution decisions made at the slate board, the credential pipeline investments advocated in the CGPSC workforce planning sessions, and the ITC development conversations that produced two ITCS selectees and one future ITCM are the institutional legacy. That is the ITCM's professional output, accurately measured. The post-CG generation reading this entry will be the ITCSs and ITCMs who replace the current cohort. The credential standard they inherit — IAT Level III, CISSP, DCWF framework literacy, zero-trust architecture awareness, and a post-CG transition plan that was built at IT1 instead of discovered at terminal leave — is the ITCM's contribution to the rating they leave behind. Build it intentionally; the rating reads what you tolerated in your last two years as clearly as what you built in your first twenty.
FAQ

IT E8-E9 — Frequently Asked Questions

Q01What does a E8-E9 IT (Information System Technician) actually do?
As ITCS you are typically the senior IT chief at a major sector or district information management office, the senior enlisted IT advisor at a Coast Guard Communications Area Master Station (CAMS Atlantic at Chesapeake, VA or CAMS Pacific at Point Reyes, CA), the senior enlisted presence in the CG's Command, Control, Communications, Computers, and Intelligence (C4I) programs office, or a leadership-cadre billet at TRACEN Petaluma running the IT A-school or C-school pipeline.
Q02What's the most important thing to know as a E8-E9 IT?
ITCS and ITCM (E-8 and E-9) are the rating standard — what every IT in the service measures the credential floor against and what every ITC is trying to become.
Q03What does a typical day look like for a E8-E9 IT?
Time-blocked day at the E8-E9 IT rank tier: 0530–0630 PT — the ITCM who stops setting the physical readiness example is the ITCM who has abdicated the most visible leadership signal in a small service. The PFT score at ITCM is still a number the junior ITs see, 0630–0730 Shower, breakfast, senior enlisted council or CMC morning prep — if there is a command climate issue, a discipline case, or a senior enlisted advisory item that needs to be in front of the CO today, this is when it is framed,…
Q04What mistakes get E8-E9 IT soldiers fired or relieved?
Confusing seniority with technical currency. The DISA STIG benchmarks, DoDD 8140.01 workforce category updates, NIST publication revisions, and zero-trust architecture requirements move faster than a 24-year career's institutional memory. The IT2 who just completed the current DISA training knows that corner better than you do. Let them brief it and stand behind them. The rating network sees who is honest about the gap;…
Q05What career decisions matter most at the E8-E9 IT rank tier?
ITCM candidacy versus a DoD or federal civilian lateral transition at the 20-year mark — The ITCM slate in the CG selects from a pool of one to two ITCSs per cycle in the IT rating; it is a narrow gate. The ITCS who is competitive for ITCM has a specific billet portfolio, SELC completion, a clean EER trend across multiple commands, and a Mess sponsorship from the current ITCM community. The ITCS who is not competitive for ITCM at the 20-year mark has a strong federal civilian or contractor transition profile if the credential stack is current and the clearance is active.…
Q06What's next after E8-E9 for a IT (Information System Technician) in the Coast Guard?
There is no next rank for the ITCM.
Q07What manuals and regulations does a E8-E9 IT need to know cold?
COMDTINST M5500.13 (current series) — Coast Guard Information and Life-Cycle Management Manual. You are the rating's walking authority at your command on what the manual requires.; DoD 8570.01-M / DoDD 8140.01 (current revision) — Cyberspace Workforce Management. You are the community's credential compliance authority and the rating's institutional memory for the DoD 8140 workforce management framework as it evolves.; DISA STIGs, NIST SP 800-53 (Rev 5),…

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