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
ITE7

Information System Technician

E-7 (Sergeant First Class) · Coast Guard

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

ITC (E-7) is where the job stops being about running the compliance program and starts being about owning the C4I readiness culture at the command. The chiefs' mess initiation cycle at TRACEN Petaluma, CA is your first ITC event — it is not a ceremony, it is a deliberate cultural reset. After it, the command reads the IT shop by what you tolerate in the ATO and what you push back on in the ISSO's brief, not by what the IT1 produces week to week.

The Honest MOS Read
ITC — Chief Petty Officer, E-7 — is the first rank in the Coast Guard's Information Systems Technician rating where the title 'Chief' carries institutional weight that changes how every person in the command interacts with you, including the people who outrank you. The anchor pin at a CG command is not decoration — it is a signal to the commanding officer, the ISSO, the C4I officer, and the District IT staff that you are the enlisted authority on cybersecurity posture and network readiness for the command, and that your read on the ATO's health is the one they rely on. The Chief Petty Officer Academy (CPOA) at TRACEN Petaluma, CA is the formal entry point. Every ITC in the CG went through it; the curriculum covers leadership, the CPO heritage, and the institutional obligations of the Mess. The CPO initiation cycle — run by the Mess at the command, not by the chain of command — is a separate rite of passage that the CG takes seriously as a cultural institution. Chiefs who treat the Mess work as optional overhead are noted and that read circulates in the senior enlisted network faster than any formal evaluation process. The Mess is not an ancillary obligation at ITC; it is a primary one alongside the technical compliance work. The compliance program ownership at ITC is materially different from IT1. At IT1, you ran the STIG scans and wrote the POAM entries. At ITC, you are responsible for the program's posture — the culture of compliance that determines whether the IT1 catches a STIG benchmark update before the ISSO does, whether the POAM entries have accurate remediation dates or aspirational ones, whether the ATO documentation is continuously maintained or updated in a pre-audit surge. The ISSO and the Authorizing Official interface is now yours to own: you brief the command on cybersecurity posture, you advise the commanding officer on ATO risk, and you push back — in the office, before the decision — on risk acceptance decisions that exceed what the ATO envelope actually authorizes. The ITC network in the CG is small and dense. The service has approximately 150 to 200 ITCs across all active commands at any given time (verify current end-strength against CGPSC workforce data); every ITC at your paygrade knows you by name and knows the quality of the compliance program your unit runs. The District ITC network — the senior IT chiefs at your District's major commands and sectors — shares information on ATO findings, DISA assessment outcomes, and personnel-board results. The ITC who has a clean compliance record and a strong EER history is known positively in that network; the one whose unit generated a critical DISA finding or had an ATO lapse is also known. There are no secrets in a 150-person professional community. The Senior Enlisted Leadership Course (SELC) is the professional development marker for ITCs who are competitive for senior chief. The SELC — conducted at TRACEN Petaluma — is the CG's formal senior enlisted leadership curriculum; completing it before the ITCS selection board cycle opens is a board-competitive signal. It is distinct from the CPOA, though both are at Petaluma; the CPOA is the E-7 entry-level course and the SELC is the E-8 preparation course. The post-CG planning horizon at ITC is 36 to 48 months, not theoretical. The federal civilian and contractor markets that hire credentialed CG IT chiefs are highly specific about credential currency and clearance status: USCG civilian IT Specialist GS-09 through GS-13 at USCG District or Area commands, DHS/FEMA/TSA civilian IT positions, DoD contractor network and cybersecurity roles (L3Harris, Booz Allen Hamilton, SAIC, Leidos, ManTech, Peraton), and the federal cleared-contractor market at DHS or USCYBERCOM support billets. The ITC who plans this transition with the credential and clearance in active maintenance, and who has identified two or three specific roles through the ITC network, is the one who lands well. The one who runs through 20 years without a post-service plan and then discovers that the GS hiring process takes eight months is the one who takes whatever role opens first.
Career Arc
  • 01ITC pinned following chief board selection under current CG advancement policy; CPO initiation cycle and Chief Petty Officer Academy at TRACEN Petaluma, CA.
  • 02Command C4I readiness culture ownership — ATO documentation, ISSO interface, POAM compliance program, and the cybersecurity posture brief to the commanding officer.
  • 03Senior Enlisted Leadership Course (SELC) at TRACEN Petaluma — the board-competitive signal for ITCS consideration.
  • 04ITC network engagement at the District level — shared situational awareness on DISA findings, ATO assessment outcomes, credential pipeline gaps, and billet distribution.
  • 05IT1 mentorship toward chief board readiness — EER trajectory, credential stack, C-school pipeline, awards record, and the Mess sponsorship conversation.
  • 06Broader billet exposure — CAMS, District CIS staff, TRACEN cadre, or CG Cyber Command — as career-broadening options before the ITCS window.
  • 07ITCS (E-8, Senior Chief Petty Officer) selection via CG senior enlisted board process.
Common Screwups
  • ×Treating the Chiefs Mess work — the initiation cycle, the climate sensing, the discipline reviews, the new-arrival sponsorship — as overhead while the compliance calendar runs. The Mess is the job at ITC. The IT technical work is also the job. The ITC who executes one and neglects the other does not make ITCS.
  • ×Going public with disagreement — with the ISSO, the C4I officer, the District CIS staff, or the commanding officer. You take it in the office; you document your recommendation in writing; you walk out aligned. An ITC who vents to the IT1s about an ISSO decision has poisoned the well for the next time the command needs to trust the IT shop's compliance advice.
  • ×Inflating EER blocks on a favored IT1. The District ITC network sees the inflation pattern across multiple cycles and the senior enlisted community discounts the ITC's recommendations the next cycle without telling him why.
  • ×Allowing an ATO lapse or a critical DISA finding to develop under watch because 'the IT1 manages the program.' At ITC the ATO posture is your compliance program. The IT1 is your executor, not your surrogate.
  • ×DUI / financial misconduct / fraternization / OPSEC breach. The IT rating's senior enlisted network is small and the institutional memory is long; one integrity incident at ITC ends the ITCS candidacy and shapes the post-CG credential reference landscape permanently.

A Day in the Life

  • 0530–0630PT — the ITC who doesn't set the physical readiness example is the one the IT1s notice. The PFT score is a visible number in a small command.
  • 0630–0730Shower, breakfast, review overnight monitoring alerts and any IT1 escalations from evening watch. The overnight is the IT1's to handle; the ITC reads the summary, not the ticket queue.
  • 0730–0800Morning standup with the IT shop and the Mess prep check-in — is there a discipline case, a climate issue, or a new arrival the Mess needs to address before the day's workload starts?
  • 0800–0900ISSO coordination — the ITC's relationship with the command ISSO is a weekly formal brief and a daily informal pulse. What ATO items are coming up, what DISA benchmark updates landed overnight, what configuration change requests are pending an ATO boundary review?
  • 0900–1030POAM and ATO review — not running the scans, but reviewing the IT1's POAM update from the previous week: are the remediation dates accurate or aspirational, are the CAT I findings moving toward closure or accumulating risk acceptance paperwork, is the ATO review horizon within the 90-day visibility window?
  • 1030–1200Command C4I readiness brief preparation or delivery — CO/XO readiness brief, DCMS quarterly review, or District CIS site visit prep. Frame every metric as readiness and risk language, not IT status language.
  • 1200–1300Lunch — eat with the Mess when possible. The chiefs' mess lunch table is where climate signals surface before they become formal issues.
  • 1300–1430IT1 development — sit-down with one IT1 per week on the development map: credential gap, SWE study calendar, C-school timing, EER bullet review for the current period, awards package that is past due.
  • 1430–1600Technical currency — SELC reading material, DoDD 8140.01 update review, NIST publication notes, or a DISA STIG release review for the system classes the unit runs. The ITC who drifts technically is the one the IT1 routes around.
  • 1600–1700EER drafting — the ITC's primary documentation output. The EER bullets for the IT1s and IT2s are the advancement record the CGPSC reads; write them as if the community manager is reviewing every word against the performance outcomes in the ticket system and the POAM records.
  • 1700–1800After-hours compliance calendar review and weekly ISSO status update note — what is the ATO posture status going into the weekend, what actions are due Monday, and what does the IT1 on duty need to know?
  • 1800–2100Family and personal recovery. The ITC who does not protect this time builds a sustainability problem that the Mess eventually notices in the form of a chief who is short with subordinates and long on compliance anxiety.
  • 2100–2200SELC preparation or post-CG planning — review the federal IT Specialist job posting landscape, maintain the credential renewal calendar, check in with the ITCS network on billet openings and career-broadening opportunities.

Weekly Cadence

Monday is the ISSO and ATO week. The ITC starts the week with the ISSO touch-base — what is the ATO status, what POAM items moved over the weekend, what DISA benchmark or IAVM update came out that changes the compliance picture. The IT1's POAM update lands in the ITC's review queue by end of Monday; the ITC reviews for accuracy and realism, not just completeness. The Mess meeting — if scheduled weekly at the command — is Monday evening. Midweek is C4I readiness and development. The command readiness brief, the IT1 development sit-down, and the EER drafting block all live in the Tuesday–Thursday window when the compliance calendar is in a steady state. The SELC study and technical currency work happens in the Thursday afternoon block — non-negotiable unless the command is in an ATO review or a cybersecurity incident response. Friday is documentation and network engagement. The ITC's weekly status note to the District ITC network — a one-paragraph ATO posture summary shared with the senior IT chiefs at the District's other major commands — goes out Friday afternoon. This is not a reporting requirement; it is the shared situational awareness that makes the ITC network useful when an ITCS billet opens or a DISA assessment is scheduled. The Friday afternoon also covers the transition brief for the weekend duty IT: system status, any open POAM actions that need monitoring, and the escalation contact.

Key Skills — How to Drill Each

  1. 01
    Run the command's cybersecurity compliance and IT program as the senior IT chief — DISA STIG posture, POAM management, IAVM patch compliance, ATO documentation, Active Directory security baseline, and the ISSO interface.
    The ITC who is still personally running STIG scans has not made the transition from IT1 to ITC. Your job is building the IT1 and IT2 who run the scans correctly, reviewing the POAM outputs with the judgment to identify when a finding is accurately documented versus when it is papered, and standing behind the compliance posture in the ISSO brief with enough technical depth to answer the hard question about why a particular CAT II finding has been deferred for two cycles. Own the program through your petty officers, not around them.
  2. 02
    Advise the commanding officer, the C4I officer, and the ISSO on network and cybersecurity posture honestly — including the things the command cannot see.
    Brief the CO on the ATO status in the language of readiness and risk, not IT metrics. 'Our POAM has one open CAT I finding with a 30-day risk acceptance in place and ISSO signature; the remediation window closes in 14 days and I am confident we will close it' is a brief. 'We have some compliance items in progress' is not. The CO needs to know whether the network's ATO posture is a risk to operations; your job is to make that read accurate, clear, and timely.
  3. 03
    Mentor three to four IT1s into chief-board-competitive candidates — EER trajectory, DoDD 8140.01 credential profile, C-school pipeline, awards record, leadership course completion, Mess sponsorship.
    Build the development map for each IT1 at the start of the first reporting period: credential gaps, C-school timing, SWE study calendar, award eligibility for the work they are already doing, and the Mess sponsorship conversation you are going to have with the appropriate chief. The IT1 who makes chief is the one whose ITC built the map, not just observed the progress.
  4. 04
    Brief the Sector or District commander, the DCMS, or the cutter CO on IT and cybersecurity readiness — patch compliance percentage, ATO status, help-desk resolution rate, network uptime, and the things the command cannot see from the bridge.
    The command brief is not a status update — it is a risk advisory. Frame every metric against the operational readiness question: does the current compliance posture allow the command to operate under the ATO's authorization, or is there a gap that creates legal or operational risk? The CO who hears this framing from the ITC is the CO who trusts the ITC's push-back when a proposed change would move the system outside its ATO boundary.
  5. 05
    Walk a cybersecurity incident, an unauthorized access event, or an ATO compliance finding as the senior enlisted IT authority — identify the broken control, the configuration drift, or the qualification gap before the investigating officer names it.
    The post-incident walk-through is the ITC's credibility moment. Before the investigating officer arrives, walk the IT1 through the incident timeline: what was the first indicator, what control failed, what the change log shows, what the AD audit trail shows, where the STIG benchmark file was on the date of the event. The ITC who can present the investigating officer with an accurate, complete incident chronology — including the control failure the command did not want to acknowledge — is the one the CO trusts with the next hard compliance conversation.
  6. 06
    Sit in the Chiefs Mess on discipline cases, climate sensing, EO posture, and new-arrival sponsorship — and translate the Mess's observations into actions the command will fund and the IT division will execute.
    The Mess exists partly to give the CO a senior enlisted advisory layer that is not in the formal chain of command. When the Mess identifies a climate problem, a conduct issue, or a morale signal the command has not seen, the ITC's job is to carry it to the CO in terms the CO can act on — not as gossip, not as complaint, but as a readiness issue with a recommended action. The ITC who skips Mess work because the compliance calendar is full is the one whose CO eventually finds out about a problem through a formal complaint instead of through the senior enlisted layer that should have flagged it first.

Manuals & References — What Chapters Matter

  • COMDTINST M5500.13 (current series) — Coast Guard Information and Life-Cycle Management Manual
    At ITC you are the command authority on what this instruction requires. Verify the current series number against the CG Directives System — this instruction has been revised and the current version number matters when advising the CO or the ISSO on CG-specific IT policy versus DoD-level requirements.
  • DoDD 8140.01 — Cyberspace Workforce Management (and predecessor DoD 8570.01-M)
    At ITC you are the billet compliance authority and the credential program manager for the IT shop. The DoDD 8140.01 framework has evolved from the older IAT/IAM/IASAE structure toward DCWF work roles; verify the current category mapping for your command's IT billets with your ISSO or the CGPSC credentialing program office. The credential requirements the IT1s and IT2s must hold are your responsibility to track and enforce.
  • DISA STIGs (current release) and DISA Risk Management Framework process documentation
    At ITC you are responsible for the posture, not just the scans. Understand the DISA RMF assessment process — how DISA field assessment teams conduct ATO reviews, what critical finding thresholds trigger a findings briefing to the AO, and what documentation the assessment team pulls first. The ITC who understands the assessment process is the one who knows which POAM items need to be clean before the assessment date, not after.
  • NIST SP 800-53 (Rev 5) and NIST SP 800-37 (Rev 2) — Security and Privacy Controls and Risk Management Framework
    At ITC you cite these publications when advising the ISSO and the CO on risk acceptance decisions. SP 800-53 Rev 5 introduced privacy control integration and updated several control families; verify whether your command's ATOs have been updated to reference the Rev 5 control baseline. SP 800-37 Rev 2 introduced the Prepare step and updated the Authorize step — the ITC who can walk the CO through the authorization decision criteria is the one whose risk advice is trusted.
  • Chief Petty Officer Academy (CPOA) reading list and Senior Enlisted Leadership Course (SELC) curriculum, TRACEN Petaluma, CA
    The CPOA and SELC are the CG's formal senior enlisted leadership development programs. Completing the SELC before the ITCS selection board cycle is the board-competitive signal for senior chief consideration. The reading lists are CG-published and available through the CG Institute; they are not optional professional development — they are the documented preparation the CGPSC board associates with senior-chief readiness.
  • CIM 1610-series — Coast Guard Enlisted Employee Review (EER)
    At ITC your bullets pick the advancement slate for the IT1s and IT2s under you and the chief board reads the ITC EER for ITCS nomination. Write the IT1 EERs with the understanding that the District IT staff and the CGPSC rating community manager will read them alongside multiple other IT1 EERs — the ITC who writes the same inflation across a four-year period produces a record the community discounts.

Standards — How to Hit Each

  • Chief Petty Officer Academy (CPOA) at TRACEN Petaluma, CA completed; IAT Level III credential (CompTIA CASP+ CE or current DoDD 8140.01 equivalent) held.
    The CPOA is a mandatory ITC milestone and it is not self-scheduled — it is assigned through the CGPSC slating process. The IAT Level III credential is the technical authority baseline that gives the ITC standing to advise the CO and the ISSO on ATO risk. An ITC without the IAT Level III is an ITC whose technical credibility is questioned in the ISSO's office and in the District CIS staff network. Maintain the CEU cycle for the CASP+ CE and verify the current DoDD 8140.01 mapping annually.
  • Unit ATO documentation current and the POAM clean — no overdue CAT I findings without a documented and ISSO-signed risk acceptance; no ATO lapses during the ITC's watch.
    Build a 90-day ATO visibility window: what is the next ATO review date, what CAT I and CAT II items need to be closed or have risk acceptances in place, what STIG benchmark updates have been published since the last scan cycle. The ITC who briefs the ISSO on the ATO status monthly — not because the ISSO asked, but because the ITC owns the posture — is the ITC whose ATO reviews pass without critical findings.
  • Senior Enlisted Leadership Course (SELC) at TRACEN Petaluma, CA completed; on the calendar if competitive for ITCS consideration.
    The SELC slot competes with operational requirements and the CGPSC schedules it through command coordination. The ITC who waits for the command to nominate them for the SELC is the ITC who may miss the window before the ITCS board cycle. Ask the ITCS or ITCM sponsor directly: what is the current SELC wait time, and when does the ITCS board process require SELC completion? Build the timeline accordingly.
  • Unit EER profile clean — the IT1s and IT2s under this ITC are advancing on schedule and the EER narrative is consistent across multiple periods.
    Track the advancement outcome for every IT1 and IT2 who served under your EER authority. If an IT1 failed to advance on the SWE cycle where you gave them a high EER, either the EER narrative did not support the mark clearly enough, or the IT1's performance did not match the mark — either way, that is feedback about the EER's calibration. The CGPSC community manager sees the advancement-outcome-to-EER correlation across the whole rating.
  • Zero senior-enlisted integrity incidents — financial, fraternization, OPSEC, unauthorized system access, or data-handling violations.
    The IT rating's small community means one integrity incident at ITC is permanently visible in the senior enlisted network. There is no procedure to follow here — this standard is a sustained choice. The ITC who makes the integrity call every time, including the time it costs something, is the one the ITCS and ITCM community trusts with a broader compliance portfolio and the ITCS board recommendation.

Technical Mistakes — Concrete Consequences

  • Letting the unit ATO documentation or STIG compliance status drift because 'the IT1 manages the POAM.'
    At ITC the ATO posture is not the IT1's paperwork — it is the ITC's compliance program. A lapsed ATO or an unmitigated CAT I finding in a District CIS audit lands on the ITINC of record; the investigating officer does not call the IT1.
  • Going public with disagreement — with the ISSO, the C4I officer, the commanding officer, or the District CIS staff.
    The ITC who vents to the petty officers about a command decision they disagree with has just told every IT in the shop that the chain of command does not have their chief's full confidence — and the command will eventually hear that read through the Mess network. You take it in the office; you document the recommendation; you walk out aligned.
  • Stopping personal PT and technical currency because 'I am a chief now.'
    The IT shop respects the anchor pin only as long as the ITC can read a STIG finding, interpret a network diagram, and walk a fault isolation procedure without asking the IT2 to explain it. The ITC who drifts technically is the one the IT1s route around on hard problems — and the ISSO notices who is calling the IT1 for technical answers on questions the ITC should own.
  • Inflating EER blocks on a favored IT1 across multiple periods.
    The District ITC network and the CGPSC community manager see the inflation correlation — when the same ITC writes top marks year after year for petty officers who advance at below-average rates, the community discounts the ITC's EER recommendations quietly and without notice, until the ITC's own ITCS board recommendation goes in with less weight than expected.
  • Skipping the Chiefs Mess work — climate sensing, discipline reviews, new-arrival sponsorship — because the compliance calendar is consuming.
    The ITC who is absent from Mess work is the ITC whose CO eventually discovers a command climate problem or a conduct case through a formal complaint that should have been handled at the Mess level. The senior chiefs in the Mess note the absence and it circulates in the ITCS selection network.

Career Decisions at This Rank

  • Pursue a broadening billet (CAMS, District CIS staff, TRACEN cadre, CG Cyber Command) versus staying in operational billets for the ITCS board.
    The ITCS selection board reads the breadth of the ITC career alongside the compliance record and the EER profile. An ITC with two or three operational billets and one broadening billet (CAMS, Petaluma cadre, or a District CIS staff position) presents a more complete picture than one with four operational billets in similar units. The CAMS billets (Chesapeake, VA and Point Reyes, CA) are the highest-technical-complexity broadening assignments in the IT rating; a CAMS ITC billet produces an EER record and a technical depth that the ITCS board recognizes. The TRACEN Petaluma cadre billet produces visibility to the senior IT leadership that matters for the ITCM pipeline. Discuss the timing with your ITCS or ITCM sponsor — the right broadening assignment at the right point in the ITC timeline is a material board advantage.
  • ITCS candidacy versus lateral move to a CG officer warrant program (CWO Information Systems) or direct commission cyber officer.
    The CG's Chief Warrant Officer program allows senior enlisted members to lateral into the warrant officer corps; the Information Systems (WO-4) specialty is the IT-adjacent warrant track. The direct commission cyber officer path (via the CG's officer accession programs for prior-enlisted) is also available for ITCs with the appropriate education. The honest analysis: the ITCS and ITCM career is the most direct path to senior technical and community leadership in the IT rating; the warrant and officer paths trade the rating community leadership for broader command authority and the officer career track. An ITC who is competitive for ITCS and ITCM is generally best served by the enlisted track. An ITC who wants the commission authority and has the bachelor's degree should evaluate the direct commission or warrant path before the age and service window closes.
  • Reenlist past 16 years versus separating with a federal civilian or contractor transition.
    The 16-year mark with an IAT Level III credential and an active clearance is the point where the federal civilian and contractor market is most accessible before the 20-year vesting point. GS-11 to GS-13 IT Specialist positions at USCG Districts, DHS, FEMA, or DoD commands; cleared contractor roles at L3Harris, Booz Allen, SAIC, Leidos, and ManTech in the $95K–$160K range depending on clearance level and location. The honest math: if the ITCS board is not competitive this cycle and the credential stack and post-CG plan are solid, separation at 16 with a targeted civilian or contractor position is financially superior to three more years in the E-7 band waiting for a board that may not select. If ITCS is competitive and the 20-year retirement math is favorable at the duty station location, the additional four years are worth it. Run the numbers with the current locality pay tables; do not rely on anecdote.
  • Maintain the CASP+ CE versus pursuing a higher-level credential (CISSP, CEH, or a DoDD 8140.01 advanced workforce category certification).
    The CISSP (Certified Information Systems Security Professional) from (ISC)² is the credential the federal civilian IT Specialist market — and the DoD/DHS contractor market — recognizes as the senior cybersecurity professional baseline. The CASP+ CE satisfies the DoDD 8140.01 IAT Level III requirement; the CISSP satisfies the IAM (Information Assurance Management) Level III and IASAE (Cybersecurity Architect) requirements in the older 8570.01-M framework and maps to comparable categories in the newer DoDD 8140.01 DCWF structure. The ITC who holds the CASP+ CE and adds the CISSP is the one the federal civilian and contractor hiring market reads as a complete senior cybersecurity professional. Budget the study calendar: the CISSP requires five years of verified cybersecurity experience (most ITCs qualify) and an exam preparation commitment of 60 to 90 hours over three to four months.
  • Stay as ITINC at current command through the ITCS window versus accepting a hardship-duty or sea-duty billet for the career points.
    The CG CGPSC billet management system weighs sea time, duty-station hardship, and the command portfolio when evaluating ITCS candidates. An ITC who has served only shore assignments at comfortable duty stations may present a less competitive billet history than one who took the harder sea-duty or CAMS assignment when it was offered. The ITC network at the District level knows which billets are career-broadening and which are comfortable-but-limiting. Ask your ITCS or ITCM sponsor directly: does my current billet portfolio tell a competitive ITCS story, and what assignment would make it stronger?

How the Seat Varies by Unit Type

  • Sector headquarters (ITC as chief of the IT/CIS department)
    The sector ITC has the broadest compliance portfolio of any station-level assignment — multiple subordinate units' network infrastructure, help-desk support across the sector's commands, and the District CIS staff interface on ATO reviews and compliance findings. You are managing a multi-IT1 shop, writing EERs on four or five petty officers annually, and coordinating the compliance program across a geographic span that includes small boat stations with part-time IT coverage. The ISSO relationship is the primary command interface; the DCMS is the administrative authority. This billet produces the strongest EER throughput in the IT rating.
  • National Security Cutter or Offshore Patrol Cutter (ITC in the C4I division under the Chief Engineer)
    The cutter ITC manages the ship's network and C2 communications infrastructure at sea. The operational tempo is high — six-month INDOPACOM or Caribbean patrols require maintaining the ATO compliance program, IAVM patch cycles, and STIG scan schedules underway without shore-based IT support infrastructure. The ITC reports to the Chief Engineer and advises the C4I officer; the CO interface happens through the readiness brief at the flag level. The cutter billet produces sea-time currency for the Permanent Cutterman device and a hard-operational EER record.
  • Coast Guard Communications Area Master Station (CAMS Atlantic or Pacific)
    The CAMS ITC manages a large, high-complexity IT and communications infrastructure supporting the CG's long-range communications network across the Atlantic or Pacific area. CAMS billets are the highest-technical-complexity assignments in the IT rating, with a broader system inventory, more direct DISA and DHS oversight, and more engagement with DoD and interagency communications requirements than any other enlisted IT billet in the service. An ITC-level CAMS assignment produces the most technically credible EER record in the rating and is the most direct feeder for the ITCS community-leadership pipeline.
  • TRACEN Petaluma IT A-school or C-school cadre
    The Petaluma cadre ITC shapes the rating's entry-level and advanced training pipeline. The daily work is curriculum delivery, student evaluation, and course development — less compliance calendar, more instruction and standards-setting. The career value is the visibility to the senior IT leadership at TRACEN and the CGPSC community manager, who tracks the cadre ITCs as candidates for the most senior institutional billets. The ITC who served a Petaluma cadre tour is the one the rating's senior enlisted network knows by institutional reputation.
  • CG Cyber Command or C4I program office support billet
    The CG Cyber Command (verify current organizational name against CGPSC) and the CG's C4IT Service Center manage the service's cybersecurity operations and C4I acquisition programs. An ITC-level billet at Cyber Command or a C4I program office is not a traditional operational compliance assignment — it is a staff and program management role working alongside CG officers, DoD counterparts, and contractor support personnel. The technical scope is broad (enterprise-level cybersecurity policy, acquisition program management, operational cyber defense) but the day-to-day is more advisory and less hands-on than an operational IT shop. These billets produce the most direct post-CG transition credentials for federal civilian cybersecurity or cleared-contractor work at DHS or USCYBERCOM.

What Good Looks Like at This Rank

The good ITC is the chief the District CIS staff calls when they hear a unit's ATO review is generating critical findings — not to investigate, but to ask what that ITC's unit did to prevent it. This chief's unit is the reference for what a clean compliance program looks like: the POAM has no overdue CAT I items, the ATO documentation is current through the last review cycle, the STIG scan outputs are against current benchmark files, the AD account audit was run on schedule and the orphaned account count is zero. The IT1 who answers the District staff's questions during the site visit knows the answers because the ITC built the qualification program that gave the petty officer the language and the judgment — not because the ITC told him what to say. The Mess work is equally visible. The ITC who is running the initiation cycle, doing the climate sensing, attending the discipline review discussions, and sponsoring new arrivals into the command culture is the ITC whose command has a lower friction level on the things that eventually cost money and people — the grievance that does not get filed, the conduct issue that gets addressed before it becomes an NJP, the first-term member who re-enlists because a chief asked honestly whether the coast guard was working for them. The technical compliance record and the Mess performance are not separate tracks; the ITCS board reads them as one picture. When the ITC leaves the unit, the standard stays for at least one more rotation cycle. The IT1 that chief mentored runs the compliance program to the ITC's standard, not to the baseline the instruction requires. The EER profile the chief wrote on three IT1s over five years produces two ITCs and one officer-lateral — a measurable outcome in a 200-person rating. That is the ITC career, accurately stated. Post-service the same ITC walks into a federal IT Specialist billet or a cleared contractor cybersecurity role the week after terminal leave starts because the credential is current, the clearance is active, and the CGPSC compliance record is the hiring conversation, not the gatekeeping step.

Preview — The Next Rank

ITCS (E-8, Senior Chief Petty Officer) is the rating standard. Every ITC in the service knows who the ITCSs are by name and by the quality of the commands they came from; every junior IT is looking at the ITCS career to decide whether the rating is worth pursuing past the first enlistment. The ITCS who is managing a major sector or district IT program, or advising the Area CIO on C4I readiness, is setting the credential and compliance standard that the rating inherits for the next five years. The SELC completion and the ITCS board process are the near-term gates. The board considers the full ITC career — EER trajectory across multiple periods and multiple reporting seniors, credential profile (IAT Level III held, CISSP or equivalent under pursuit), broadening billet diversity, sea time, and the Mess performance record that the senior enlisted community knows informally before the board convenes formally. The ITC whose ITCS sponsor has specific, recent, observable examples of the ITC's judgment under fire is the ITC whose board endorsement means something. At ITCS, the scope expands to the rating community. Sitting on IT rating slate boards per CGPSC tasking, advising the District commander or Area CIO on C4I workforce readiness and retention, and holding the post-CG transition conversation honestly with junior chiefs — these are the ITCS obligations that live above the ITC's compliance program ownership. The ITCS who treats those obligations as optional will be visible to the ITCM community as a senior chief who never fully made the transition from chief to senior chief. That read follows the career through the ITCM candidacy window.
FAQ

IT E7 — Frequently Asked Questions

Q01What does a E7 IT (Information System Technician) actually do?
You are typically the Chief Information Systems Technician in Charge at a sector or district IT shop, the senior IT chief in the C4I department of a National Security Cutter or Offshore Patrol Cutter under the Chief Engineer, or a senior billet at a Coast Guard Communications Area Master Station (CAMS) or a CG telecommunications center.
Q02What's the most important thing to know as a E7 IT?
ITC (E-7) is where the job stops being about running the compliance program and starts being about owning the C4I readiness culture at the command.
Q03What does a typical day look like for a E7 IT?
Time-blocked day at the E7 IT rank tier: 0530–0630 PT — the ITC who doesn't set the physical readiness example is the one the IT1s notice. The PFT score is a visible number in a small command, 0630–0730 Shower, breakfast, review overnight monitoring alerts and any IT1 escalations from evening watch. The overnight is the IT1's to handle; the ITC reads the summary, not the ticket queue, 0730–0800 Morning standup with the IT shop and the Mess prep check-in — is there a discipline case, a climate issue, or a new arrival the Mess needs to address before the day's workload starts?,…
Q04What mistakes get E7 IT soldiers fired or relieved?
Treating the Chiefs Mess work — the initiation cycle, the climate sensing, the discipline reviews, the new-arrival sponsorship — as overhead while the compliance calendar runs. The Mess is the job at ITC. The IT technical work is also the job. The ITC who executes one and neglects the other does not make ITCS; Going public with disagreement — with the ISSO, the C4I officer, the District CIS staff, or the commanding officer. You take it in the office;…
Q05What career decisions matter most at the E7 IT rank tier?
Pursue a broadening billet (CAMS, District CIS staff, TRACEN cadre, CG Cyber Command) versus staying in operational billets for the ITCS board — The ITCS selection board reads the breadth of the ITC career alongside the compliance record and the EER profile. An ITC with two or three operational billets and one broadening billet (CAMS, Petaluma cadre, or a District CIS staff position) presents a more complete picture than one with four operational billets in similar units. The CAMS billets (Chesapeake, VA and Point Reyes,…
Q06What's next after E7 for a IT (Information System Technician) in the Coast Guard?
ITCS (E-8, Senior Chief Petty Officer) is the rating standard.
Q07What manuals and regulations does a E7 IT need to know cold?
COMDTINST M5500.13 (current series) — Coast Guard Information and Life-Cycle Management Manual. You are the senior authority in the unit on what the manual requires and where the configuration boundary ends.; DoD 8570.01-M / DoDD 8140.01 (current revision) — Cyberspace Workforce Management. You are the billet compliance authority and the credential program manager for the IT shop at your command.;…

Based on 14 tips from 0 contributors

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