←Back to 2E1X1 Communications-Computer Systems — overview, pay, training, civilian translation, reviews
2E1X1E6
Communications-Computer Systems
E-6 (Staff Sergeant) · Air Force
HEADS UP
Technical Sergeant means you are now managing programs, not just systems. The Air Force expects you to brief the Comm Officer, own the RMF packages, and produce the next generation of SSgts. Every Airman you develop is a direct measure of your NCO performance.
The Honest MOS Read
At TSgt, the 2E1 career field shows you its real face. You are a program manager now. The job is not primarily about fixing things or even configuring things — it is about ensuring that everything your section owns is authorized, documented, compliant, and understood by someone other than you. The technical work remains important, but the bottleneck in your section's performance is no longer technical skill. It is organizational competence, communication ability, and the quality of the NCOs you are developing.
The RMF process is your daily reality. You own the ATOs. You write the POAMs. When AFCYBER or MAJCOM asks about your compliance posture, you are the person who gives the briefing. You are accountable for the accuracy of that briefing in a way that a junior Airman or even an SSgt is not. A false or inaccurate compliance report at your level is not a training issue — it is a leadership failure.
The civilian market comparison shifts at TSgt. You are no longer comparing yourself to junior IT professionals. A TS/SCI-cleared TSgt with RMF program management experience and a proven record of managing enterprise IT systems is looking at $110,000 to $150,000 in the defense contractor space, particularly in the DC/Northern Virginia market or in areas with heavy USAF presence. The retirement math is now doing real work in your favor — twelve years in is not nothing, and the eight-year runway to retirement with a cleared, management-track background is a real financial argument for staying.
The honest truth is that the 2E1 TSgts who separate and go contractor are not making a mistake — many of them do extraordinarily well financially. The ones who stay and make it to CMSgt are also making a good decision — the combination of retirement pay, VA benefits, and a cleared senior consulting career on the back end is a strong outcome. The TSgts who make a bad decision are the ones who drift — neither fully committed to making CMSgt nor seriously planning their transition. Drift at TSgt wastes both the Air Force's investment in you and your own career momentum.
Career Arc
["Pin TSgt and formally assume program management responsibility for one or more IT systems or enterprise-level projects within the communications squadron", "Own the RMF authorization packages for your assigned systems \u2014 this means understanding the ATO status, open findings, and POAM milestones for everything in your portfolio", "Brief the Comm Officer and squadron leadership on compliance posture, project status, and risk items \u2014 you are the technical advisor at the E-6 level", "Drive the NCO development program in your section \u2014 your SSgts' performance is your performance", "Compete for senior NCO leadership roles: flight chief positions, special duty assignments, MAJCOM-level program manager billets", "Evaluate the CMSgt path \u2014 the senior NCO corps is small and the competition is real; the ones who make it are the ones who have a clear record of developing people and managing programs"]
Common Screwups
["Staying in the technical weeds rather than delegating \u2014 TSgt who does the technical work instead of managing it is not developing NCOs, not writing EPRs, and not briefing leadership", "Failing to maintain the accuracy of a compliance reporting package \u2014 an ATO that is reported as clean when it has open findings is an integrity violation, not a paperwork oversight", "Producing EPRs for SSgts that are generic and do not reflect individual performance \u2014 every EPR in your section should read like a tailored document, not a template with names swapped", "Missing a mandatory reporting deadline for a cybersecurity incident \u2014 at TSgt you know the timeline requirements; missing them is inexcusable", "Checking out mentally because the retirement math is starting to look good \u2014 the TSgt who is coasting toward twenty does visible damage to the section"]
A Day in the Life
[{"time": "0600", "activity": "PT. The TSgt sets the standard in the section. If fitness is a problem for an Airman, the TSgt noticed before the first sergeant did."}, {"time": "0730", "activity": "Leadership sync with the flight chief. Review priorities, upcoming deadlines, any staffing or project issues that need officer awareness."}, {"time": "0830", "activity": "RMF portfolio review \u2014 check status on all systems. Any ATO expirations approaching? Any new CAT I findings from overnight SCAP scans?"}, {"time": "0930", "activity": "Project management \u2014 you are leading the migration of a legacy server to a new platform. Today is the status review with the contractor team."}, {"time": "1100", "activity": "Compliance briefing prep \u2014 the quarterly brief to the Comm Officer is next week. Draft is due to your flight chief Friday."}, {"time": "1200", "activity": "Lunch. The retirement calculator on your personal phone has been opened three times this week."}, {"time": "1300", "activity": "SSgt development session \u2014 walking your senior SSgt through how to write a briefing that senior leadership will actually use."}, {"time": "1430", "activity": "EPR review \u2014 two close-outs this month. Read both drafts against the performance record and mark them up."}, {"time": "1530", "activity": "On-call coordination and section close-out."}, {"time": "1630", "activity": "Duty day ends. SNCOA coursework in the evening if you have not completed correspondence."}]
Weekly Cadence
The TSgt week is driven by the program management calendar more than the daily ticket queue. ATO renewal dates, POAM milestone deadlines, compliance reporting windows, and contractor performance review cycles all have fixed timelines that dominate the planning horizon.
Monday is leadership planning — reviewing what is due this week and what is coming up next week. The middle of the week is where the serious work gets done: project coordination, compliance documentation, technical reviews. Friday is close-out and briefing preparation for anything going up the chain Monday.
The NCO development work happens throughout the week in the margins of everything else. One-on-ones are scheduled but the real mentorship is the informal conversation when an SSgt has a problem they cannot solve and brings it to you rather than escalating it past you.
Key Skills — How to Drill Each
[{"skill": "RMF program management \u2014 full authorization lifecycle", "how": "Own every step: system categorization, security control selection, implementation, assessment, authorization, continuous monitoring. Know what every open finding in your POAM means and who is responsible for resolving it. Brief it without notes."}, {"skill": "Technical briefing for non-technical audiences", "how": "Practice translating STIG severity levels and RMF status into terms a squadron commander understands. 'We have 12 CAT II open findings, three of which affect mission-critical systems, with a remediation plan through next quarter' is a briefing. A list of findings is not."}, {"skill": "Contractor oversight and statement of work evaluation", "how": "Many IT functions on Air Force installations involve contractors. TSgts who can evaluate whether a contractor's work meets the technical standard \u2014 and document when it does not \u2014 are invaluable to the Comm Officer."}, {"skill": "Enterprise architecture awareness", "how": "Understand how your installation's systems connect to MAJCOM and enterprise-level infrastructure. Know what the DISA enterprise services are, how NIPRNet and SIPRNet are structured, and where your local systems fit in the larger picture."}, {"skill": "Senior NCO leadership development", "how": "Deliberate mentorship is different from casual guidance. Identify the highest-potential SSgts in your section and create a development plan with them. Specific goals. Specific timelines. Written down and revisited."}]
Manuals & References — What Chapters Matter
[{"ref": "AFI 36-2618 and AFMAN 36-2905 for NCO responsibilities and fitness standards", "why": "At TSgt the standards for NCO conduct and physical fitness are enforced from below as well as above \u2014 your Airmen watch how you live the standards before they follow them."}, {"ref": "DODI 8510.01 and NIST SP 800-37 for RMF program management", "why": "You are briefing these frameworks to officers. Know them at the level where you can answer follow-up questions, not just recite the process steps."}, {"ref": "AFI 17-130, Cybersecurity Program Management", "why": "The Air Force-specific implementation of cybersecurity program management. This is the policy document that defines your TSgt-level responsibilities in writing."}, {"ref": "DISA Cloud Security Requirements Guide", "why": "Enterprise infrastructure is moving toward cloud. If your installation has any cloud-hosted services or hybrid infrastructure, the DISA Cloud SRG defines the compliance requirements you own."}, {"ref": "CISSP Common Body of Knowledge (current edition)", "why": "If you have five years of security experience and have not taken CISSP yet, take it. It is the senior certification in the field and it will follow you into the civilian market when you need it."}]
Standards — How to Hit Each
[{"standard": "All systems in your portfolio have current ATOs and active POAMs", "how": "Build a dashboard \u2014 even a simple spreadsheet \u2014 showing every system you own, its ATO expiration date, and current open findings by severity. Review it weekly. Surprises on this list are failures of process."}, {"standard": "Quarterly compliance briefings delivered to squadron leadership", "how": "Set the meeting on the calendar at the start of the fiscal year. Prepare the brief the week before. Be honest about the risk posture \u2014 a leader who minimizes risk to avoid uncomfortable conversations is a liability."}, {"standard": "TSgt-level professional military education \u2014 USAF SNCOA correspondence or resident completion", "how": "SNCOA (Senior NCO Academy correspondence is the starting point; in-residence is the competitive tier) is the professional development requirement at this rank. Complete the correspondence before your next promotion window."}, {"standard": "CISSP or CASP+ maintained as DoD 8140 IAT Level III qualification", "how": "Track your certification renewal dates the same way you track your system ATO dates. A lapsed certification affects your authorization to manage the systems you are responsible for."}]
Technical Mistakes — Concrete Consequences
[{"mistake": "Signing off on a compliance report without personally verifying the status of CAT I findings", "consequence": "You signed. If an IG inspection finds open CAT I findings on a system you certified as compliant, you are the person who certified it. The word 'fraud' is not too strong for this outcome."}, {"mistake": "Delegating an RMF authorization task to an SSgt without sufficient oversight and missing the ATO deadline", "consequence": "An expired ATO means the system must go offline or operate in an unauthorized state. Either outcome triggers a reportable event and a very uncomfortable briefing to the commander."}, {"mistake": "Allowing contractor work to proceed without proper verification against the PWS", "consequence": "Contractor deliverables that do not meet technical standards are your acceptance problem. Once you accept the work, the government owns the discrepancy. Verify before signing."}, {"mistake": "Failing to report a potential cyber incident because you are not certain it is reportable", "consequence": "When in doubt, report. AFCYBER would rather receive a false positive than discover an unreported incident. The failure to report is itself a reportable finding."}]
Career Decisions at This Rank
[{"decision": "CMSgt path versus lateral transition to a DoD civilian GS position", "analysis": "The CMSgt path is real and achievable in 2E1X1 if your record is strong. The senior NCO corps is small and the competition is other people who stayed because they are good. A GS-13 or GS-14 IT manager on the civil service side can be a strong outcome that preserves many of the same benefits while offering more stability and location control than continued active duty. Some TSgts transition to GS positions at their current installation through Noncompetitive Entry programs after retirement or separation. Both are legitimate paths."}, {"decision": "Whether to take a senior functional assignment at MAJCOM or Air Staff", "analysis": "A tour at MAJCOM or Air Staff exposes you to enterprise-level IT governance and policy at a scale that base or wing jobs do not. If CMSgt is the goal, a MAJCOM tour as a senior NCO functional looks stronger on the record than a third base comms tour. It is also a harder job \u2014 the politics are more complex and the visibility is higher. If you are not willing to operate at that level, it will show."}, {"decision": "Civilian advanced education \u2014 AFIT, Community College of the Air Force, or external degree completion", "analysis": "A bachelor's degree significantly improves both CMSgt candidacy and GS position eligibility on transition. CCAF gives you the associate's degree from your technical training. Most universities with military agreements will credit CCAF toward a bachelor's. If you are within a few years of twenty and do not have a degree, this is the window to complete it."}]
How the Seat Varies by Unit Type
[{"unitType": "Communications Squadron as Flight Chief or NCOIC", "reality": "Running the functional area for a base installation. You own the compliance posture of the entire section and the performance of every NCO in it. This is the standard TSgt role and it is where most 2E1 TSgts spend their time."}, {"unitType": "MAJCOM Functional", "reality": "Working IT policy and enterprise architecture at the major command level. Less hands-on, more advisory. Higher visibility, more bureaucratic complexity. Decisions you make affect multiple installations. Strong resume credential for both CMSgt and civilian transition."}, {"unitType": "Contingency / Deployed Communications", "reality": "Austere environments, minimal support structure, systems that were designed for a different era. You are the senior technical authority on the ground. The problems are harder and the solutions are less elegant. Career-defining experiences happen here."}]
What Good Looks Like at This Rank
The TSgt who is genuinely good at this job produces two things simultaneously: well-managed systems and well-developed NCOs. Those outputs are not separable. A section that is technically sound but has SSgts who cannot brief, cannot write EPRs, and cannot independently manage a project is a failure of TSgt leadership. A section with high-performing NCOs and an IT environment that is drifting out of compliance is the same failure, different face.
The best TSgts are trusted advisors to the Comm Officer. Not because they always have good news, but because the officer knows that what they are being told is accurate. Technical advisors who minimize or obscure bad news to avoid uncomfortable conversations are not advisors — they are a liability that will eventually produce a surprise that damages the commander.
At TSgt in 2E1X1, the people who are succeeding are almost all doing two things: they are completely transparent about the compliance and risk posture of their systems, and they are building SSgts who can eventually replace them. Every other measure of performance is downstream of those two.
Preview — The Next Rank
Master Sergeant is the senior technical advisor tier. The MSgt's value to the unit is not their hands-on technical skill — it is their ability to see the entire communications picture, identify risks before they become crises, and develop TSgts who can manage programs without daily oversight.
The MSgt also navigates the institutional politics of the senior NCO corps in ways that matter for the flight chief and senior functional roles that define the final phase of the enlisted career. Understanding wing and group priorities, building relationships with the Comm Officer and the Operations Officer, and representing the communications function in settings that go beyond the squadron — those are MSgt behaviors.
Start cultivating those relationships now. The TSgt who briefs the Comm Officer clearly and accurately, who is known as someone who brings solutions rather than just problems, is the one who gets trusted with the bigger responsibilities that make the MSgt record look competitive.
FAQ
2E1X1 E6 — Frequently Asked Questions
Q01What does a E6 2E1X1 (Communications-Computer Systems) actually do?
Serve as the section NCOIC for communications systems operations, network operations, or a related function.
Q02What's the most important thing to know as a E6 2E1X1?
Technical Sergeant means you are now managing programs, not just systems.
Q03What mistakes get E6 2E1X1 soldiers fired or relieved?
["Staying in the technical weeds rather than delegating \u2014 TSgt who does the technical work instead of managing it is not developing NCOs, not writing EPRs, and not briefing leadership", "Failing to maintain the accuracy of a compliance reporting package \u2014 an ATO that is reported as clean when it has open findings is an integrity violation, not a paperwork oversight",…
Q04What's next after E6 for a 2E1X1 (Communications-Computer Systems) in the Air Force?
Master Sergeant is the senior technical advisor tier.
Q05What manuals and regulations does a E6 2E1X1 need to know cold?
AFI 17-1301, DoD 8570.01, applicable DISA security publications, MAJCOM communications directorate guidance, unit communications squadron operating instructions
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