←Back to 2E1X1 Communications-Computer Systems — overview, pay, training, civilian translation, reviews
2E1X1E5
Communications-Computer Systems
E-5 (Sergeant) · Air Force
HEADS UP
You are a staff sergeant now, which means you are formally responsible for the people under you, not just the systems. The comms career field will promote you fast if you are good — because everyone who is bad at this job leaves for the private sector, and the ones who stay move up.
The Honest MOS Read
The Staff Sergeant in a communications squadron is the functional backbone of the shop. You are senior enough to own complex technical problems and junior enough to still be in the weeds when the work requires it. That combination is exactly what the flight needs from you. The 7-level flight chief manages the flight. The officers handle the administrative and strategic layer. You are the person who actually knows how the servers are configured, where the weird STIG exception lives, and which piece of network infrastructure has been held together with the IT equivalent of baling wire for the past two years.
You are also, now formally, a supervisor. That word has weight. The junior Airmen in your section are your responsibility in a way that goes beyond technical training. Their EPRs, their CDC completion, their fitness, their conduct — the Air Force holds you accountable for the environment you create. A section that performs well reflects well on you. A section that falls apart reflects poorly regardless of whether you caused the individual failures.
The civilian market reality does not go away at SSgt — it gets more complex. You have now been in long enough that the retirement math starts to matter. Ten years of service is real money left on the table if you separate at twelve. The 2E1 SSgt who has a TS/SCI, CISSP-eligible experience, and a track record of managing IT projects is worth $90,000 to $130,000 in the defense contractor market right now. You can feel the pull. The people who handled that math at SrA and decided to stay are now looking at a different calculation: six more years to retirement, a TS/SCI that stays with you, and a GS or contractor career on the back end that looks materially better than jumping ship at SSgt without a retirement.
The SSgt year is also where your EPR language starts to matter for master sergeant eligibility. The promotion scores compound. Bullets that describe real impact — 'managed RMF authorization for X systems; maintained ATO for Y users; reduced ticket backlog by Z percent' — are the ones that stack up. Vague activity descriptions do not help you. Learn to write, or find someone who writes well and model your language after theirs.
Career Arc
["Pin SSgt and immediately take formal supervision responsibility for the junior Airmen in your section \u2014 they are your charge now", "Complete or maintain your 7-level upgrade training as applicable \u2014 the technical certification that comes with the 7-level is the foundation for the program management work ahead", "Assume program management responsibilities for one or more IT systems or projects \u2014 this is the SSgt-level work that produces the EPR bullets that drive TSgt eligibility", "Pursue CISSP, CASP+, or CySA+ as the next certification tier \u2014 these distinguish you from SSgts who stopped at Security+", "Begin developing the next generation of 5-levels under you \u2014 the Air Force measures NCO quality by the quality of the NCOs and officers they produce", "Evaluate the TSgt competition picture \u2014 with poor retention in the career field, SSgt-to-TSgt can move quickly for performers, but the peer competition is other people who also stayed knowing the field was short"]
Common Screwups
["Writing generic EPR bullets that describe activity instead of impact \u2014 'managed Help Desk operations' tells a promotion board nothing; 'reduced mean ticket resolution time by 22 percent' does", "Neglecting the development of junior Airmen because you are more comfortable doing the technical work yourself \u2014 this is called being a good technician and a bad NCO", "Letting a junior Airman under you fail a fitness assessment, CDC test, or security compliance requirement without visible corrective action on your part \u2014 that failure shows up on your section's record", "Getting promoted into NCO status and immediately losing touch with the hands-on technical work \u2014 the SSgt who cannot do the job anymore is a liability, not a leader", "Missing the reenlistment or continuation window while undecided about staying \u2014 the decision needs to be made intentionally, not by default"]
A Day in the Life
[{"time": "0600", "activity": "PT. At SSgt you are expected to be a fitness example in your section. If PT is a struggle for one of your Airmen, this is the time you find out."}, {"time": "0730", "activity": "Section accountability and morning sync. Review the day's tickets, projects, and any priority changes from the flight chief."}, {"time": "0800", "activity": "Staff work \u2014 POAM updates, change request reviews, any compliance reporting that is due."}, {"time": "0930", "activity": "Project oversight \u2014 checking in on the infrastructure project your senior SrA is running. Not doing it for them; answering questions and removing roadblocks."}, {"time": "1030", "activity": "One-on-one with a junior Airman \u2014 CDC progress check, fitness status, any concerns."}, {"time": "1130", "activity": "NCO council or flight leadership sync depending on the day."}, {"time": "1200", "activity": "Lunch. An hour. The contractor recruiter's email from last week is still unread. You know it is there."}, {"time": "1300", "activity": "EPR work \u2014 drafting bullets for an Airman whose close-out is in three weeks."}, {"time": "1430", "activity": "Technical deep work \u2014 you are hands-on with the RMF documentation for a system coming up for ATO renewal."}, {"time": "1530", "activity": "Section close-out \u2014 verify ticket queue status, make sure on-call handoff is documented, check in with anyone who had a hard day."}, {"time": "1630", "activity": "Duty day ends. CISSP study in the evening \u2014 you are targeting a test window next quarter."}]
Weekly Cadence
The SSgt week runs on two parallel tracks: the operational track (systems, tickets, projects, compliance) and the people track (Airman development, EPRs, counselings, training tracking). Neither track can be neglected without consequences.
Monday is priority-setting and the weekly leadership sync. Wednesday is typically where the heavy technical work gets done — the blocks in the middle of the week are where you push the project work forward. Friday is admin close-out, tracking review, and making sure the section is in good shape for the weekend.
The people track does not have a dedicated day — it happens in the margins of every day. The one-on-one conversations, the informal technical mentoring, the EPR bullet capture that happens when something notable occurs. The SSgt who only thinks about people management on Friday afternoons is the one who gets surprised by an Airman failure on a Monday morning.
Key Skills — How to Drill Each
[{"skill": "IT program management and system authorization", "how": "Learn the Risk Management Framework process end-to-end. Understand what it takes to get and maintain an ATO for a system. Know what a Plan of Action and Milestones looks like and how to brief it. This is the work that distinguishes the SSgt from the SrA."}, {"skill": "Section supervision and NCO leadership", "how": "Hold weekly or biweekly one-on-ones with every Airman in your section. Know where they are on CDCs, certifications, fitness, and personal goals. A supervisor who does not know these things about their people is not actually supervising."}, {"skill": "Virtualization and cloud infrastructure", "how": "If your installation has virtualized servers or any cloud presence, get hands-on with those platforms. VMware vSphere knowledge and basic Azure or AWS familiarity are increasingly expected and significantly increase civilian market value."}, {"skill": "Technical writing and documentation", "how": "At SSgt you are writing SOPs, change requests, and briefings. Clarity and precision matter. A well-written SOP that your Airmen can follow without asking for clarification is a leadership multiplier."}, {"skill": "Mentorship and training design", "how": "Designing on-the-job training for junior Airmen is different from explaining a task once. Build a deliberate training progression \u2014 here is what you know on day one, here is what you should know at 90 days, here is what I expect by six months. Track progress against it."}]
Manuals & References — What Chapters Matter
[{"ref": "AFI 36-2618, The Enlisted Force Structure", "why": "The foundational document defining what NCO responsibilities are. Read it at SSgt. Know what the Air Force expects of you in writing, so you are not discovering it through mistakes."}, {"ref": "DODI 8510.01, Risk Management Framework for DoD IT Systems", "why": "RMF is the authorization process for every DoD IT system. At SSgt you may own systems in the ATO pipeline. Understanding the process means you can manage it rather than just respond to it."}, {"ref": "AFI 17-1301 and current AFMAN for cybersecurity compliance", "why": "The specific technical guidance for cyber hygiene and compliance in the USAF. Know what is mandated versus what is best practice \u2014 the difference matters when you are writing exception requests."}, {"ref": "NIST SP 800-37 (RMF Guide)", "why": "The NIST source document for Risk Management Framework. Understanding the original framework makes the DoD implementation clearer and makes you more credible in joint or interagency environments."}, {"ref": "CompTIA CASP+ or CISSP study materials", "why": "CASP+ satisfies DoD 8140 IAT Level III and is achievable without the five-year experience requirement that CISSP has. It is the next certification tier for an SSgt who wants to be taken seriously as a senior technician."}]
Standards — How to Hit Each
[{"standard": "DoD 8140 IAT Level II maintained; work toward Level III qualification", "how": "Audit your certification stack. Security+ is the floor. CASP+ or CISSP is the ceiling for the enlisted side. Know where you are in that progression and set a timeline."}, {"standard": "EPR close-out on time with accurate, impact-focused bullets", "how": "Your EPR is due when it is due. Work backwards from the close-out date. Start capturing bullets in real time as the year happens rather than trying to reconstruct them in the last two weeks."}, {"standard": "Section training records current \u2014 every Airman's CDCs, certs, and mandatory training tracked", "how": "Own a tracker. Not a mental note \u2014 a real document that you update when tasks are completed. When the flight chief asks about your section's training status, you have an answer in thirty seconds."}, {"standard": "Change management compliance \u2014 all production changes documented and authorized", "how": "Model the behavior you expect. If you own a system and you are making changes without tickets, your junior Airmen will follow your example. The paperwork is the standard."}]
Technical Mistakes — Concrete Consequences
[{"mistake": "Allowing a system under your management to fall out of compliance and not reporting it", "consequence": "A CAT I open finding on a system you own is a reportable event. Discovering it during an IG inspection rather than through your own compliance process means the failure is documented as systemic, not incidental."}, {"mistake": "Building undocumented system configurations that only you understand", "consequence": "When you PCS, the system goes with you in your head. Your replacement cannot maintain it properly. Outages follow. The unit chief traces it back to your time in the position."}, {"mistake": "Failing to escalate a security incident in the required timeframe", "consequence": "AFCYBER has mandatory reporting timelines for cyber incidents. Missing a reporting window is itself a compliance violation, separate from whatever the incident was. Twenty-four hours is not very long."}, {"mistake": "Approving a junior Airman's work without actually checking it", "consequence": "You signed. You own it. The SCAP scan that was submitted as clean but actually had open findings \u2014 that is your name on the report."}]
Career Decisions at This Rank
[{"decision": "Reenlist or separate at the six to eight year mark", "analysis": "This is the hardest decision in the 2E1 career. By SSgt you have real skills, a security clearance, and enough experience to be genuinely hireable. The defense contractor market for TS/SCI-cleared IT professionals is competitive and the salary gap is real. On the other side: you are roughly halfway to retirement if you count from enlistment. The retirement value of twenty years is not trivial and the GS or contractor career on the back end of a retirement is a materially different financial position than separating at eight years without a pension. There is no universal right answer. Run the numbers honestly."}, {"decision": "Whether to pursue a commissioning program (AFIT, OTS via force shaping)", "analysis": "Some 2E1s go officer through the Force Shaping opportunities that occasionally open. If you have a degree or are close to one, it is worth understanding the pathway. 17S or 17D (cyberspace) officers came from this career field and the experience crossover is real. This is not a common path but it is a real one."}, {"decision": "MAJCOM, operational, or deployed assignment for the next PCS", "analysis": "Base comms is where you built the foundation. A MAJCOM or numbered air force assignment exposes you to enterprise-level IT architecture and policy. An operational assignment \u2014 with an air operations center, a contingency communications unit, or a deployed element \u2014 gives you the resume bullet and the experience that shapes the rest of the career. Both are worth considering. Base comms for a third tour is comfortable but not developmental."}]
How the Seat Varies by Unit Type
[{"unitType": "Base Communications Squadron", "reality": "Large shop with full career field coverage. As SSgt you likely own a functional area \u2014 server administration, network operations, or cybersecurity. The pace is steady. The politics of a large organization are present. Good for developing junior Airmen because there is volume."}, {"unitType": "Expeditionary Communications Unit", "reality": "Smaller, leaner, higher tempo. Deployments are real and more frequent than base comms. The systems are more austere and less redundant. The problems are harder and the support structure is thinner. Builds credibility and resilience fast."}, {"unitType": "Air Operations Center Communications", "reality": "Supporting the nerve center of air campaign planning and execution. The network you maintain is the one the CAOC uses to coordinate operations. The consequences of downtime are operationally visible at the O-7 level. High pressure, high visibility, and a different type of urgency than base IT."}]
What Good Looks Like at This Rank
A high-performing SSgt in 2E1X1 runs the tightest section in the flight. Every Airman's CDCs are on track. Every certification is current. Every system they own has an up-to-date POAM and nobody is surprised by a compliance finding. That level of organizational competence is not accidental — it is built through weekly one-on-ones, real-time documentation, and a supervisor who knows exactly where every moving part is.
On the technical side, the best SSgts are still the people the flight chief calls when a project is complex enough to matter. They have not retreated entirely into administration. They can sit down at a workstation and work through a problem, and they are better at it than they were at SrA because they have developed the ability to see the system rather than just the symptom.
They also know how to write EPRs that actually reflect what their Airmen accomplished. The difference between a section whose members get promoted on first look and a section whose members wait two cycles is often the quality of the supervisor who is capturing and articulating their work. Good NCOs make their people look as good as they are.
Preview — The Next Rank
Technical sergeant is a program manager more than a technician. The hands-on work still exists, but the TSgt's primary product is the performance of the section, the quality of the systems documentation, and the accuracy of the compliance reporting that goes up the chain.
You will own systems in the full sense — from requirements through authorization through operations through decommissioning. You will brief officers on technical risk. You will write the statements of work that define what contractors do on your installation. That is a different job than fixing workstations and remediating STIGs.
Start thinking now about what it means to communicate technical risk in terms that non-technical people can understand and act on. That translation skill — turning a STIG finding severity chart into a clear explanation of what it means for mission execution — is what separates TSgts who are trusted advisors from TSgts who are just senior technicians.
FAQ
2E1X1 E5 — Frequently Asked Questions
Q01What does a E5 2E1X1 (Communications-Computer Systems) actually do?
Perform advanced communications and IT systems maintenance.
Q02What's the most important thing to know as a E5 2E1X1?
You are a staff sergeant now, which means you are formally responsible for the people under you, not just the systems.
Q03What mistakes get E5 2E1X1 soldiers fired or relieved?
["Writing generic EPR bullets that describe activity instead of impact \u2014 'managed Help Desk operations' tells a promotion board nothing; 'reduced mean ticket resolution time by 22 percent' does", "Neglecting the development of junior Airmen because you are more comfortable doing the technical work yourself \u2014 this is called being a good technician and a bad NCO", "Letting a junior Airman under you fail a fitness assessment, CDC test,…
Q04What's next after E5 for a 2E1X1 (Communications-Computer Systems) in the Air Force?
Technical sergeant is a program manager more than a technician.
Q05What manuals and regulations does a E5 2E1X1 need to know cold?
AFI 17-1301, DISA STIGs, DoD 8570.01, applicable NIST publications, AFI 17-1302 (Communications System Security), unit cyber security program publications
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