←Back to 2E1X1 Communications-Computer Systems — overview, pay, training, civilian translation, reviews
2E1X1E1-E3
Communications-Computer Systems
E-1 to E-3 (Junior Enlisted) · Air Force
HEADS UP
Welcome to the Help Desk. You will spend your first year resetting passwords, imaging workstations, and explaining to a colonel why his CAC card is not reading. This is not glamorous. It is also not optional — you are building the technical foundation that separates the 2E1s who last from the ones who bail at four years.
The Honest MOS Read
You are a junior communications technician at the entry tier, and the honest truth about this job is that it is two different careers stacked on top of each other. The first career is the one you are living right now: Help Desk support for a few thousand base users who range from highly skilled to people who cannot find the Start menu. You will answer trouble tickets. You will image laptops. You will escort contractors through secure areas. You will learn what a STIG is, and then you will learn to hate STIGs in the way only people who have applied them to two hundred workstations can hate them.
The second career is the one the Air Force is quietly building for you: a DoD 8140-compliant IT specialist with real certifications, real sysadmin experience, and real networking chops. The gap between those two versions of the job is the thing nobody tells you at MEPS. The Help Desk work is real and necessary — without it, base operations grind — but the career is built in the margins. The Airman who finishes CompTIA Security+ in the first year and starts working on Network+ while everyone else is watching Netflix is the one who gets the server room assignment instead of the next ticket queue rotation.
Keesler AFB is where you got the theory. Your first unit is where you find out which of it survives contact with reality. The answer is: more than you think, but in ways you did not expect. The OSI uses the network. The flight line uses the network. The clinic uses the network. When something breaks and an aircraft cannot receive maintenance data because the LAN segment is down, that is on you and your shop, and the urgency is immediate and non-negotiable.
The civilian IT market is paying close attention to exactly what you are learning. A junior SrA with Security+ and eighteen months of actual systems administration experience is worth between $65,000 and $85,000 in most US markets. You are not making that. You know you are not making that. The question you are going to have to answer at around your three-year mark is whether the promotions, the stability, and the retirement math outweigh that gap. That calculation starts here, with how hard you work to actually learn the job versus just survive the tour.
Career Arc
["Graduate technical school at Keesler AFB and arrive at your first duty station as an Airman Basic or Airman First Class assigned to a Communications Squadron", "Spend the first six to twelve months on the Help Desk rotation \u2014 ticket queue, user support, workstation imaging, account management in Active Directory", "Complete CompTIA Security+ (required for DoD 8140 IAT Level II baseline) \u2014 this is not optional and the sooner you complete it the sooner you get real work", "Start working server room or network infrastructure rotations under your 5-level supervisor \u2014 this is where the real training happens", "Pursue 5-level upgrade training through CDC completion and on-the-job tasks while accumulating time in position", "Reach SrA with functional competence in at least one specialty area: server administration, network infrastructure, or cybersecurity compliance (STIG)"]
Common Screwups
["Losing or mishandling a CAC card or classified media \u2014 one incident creates a security report, commander notification, and a mark that follows you", "Performing unauthorized changes to a production system without a change request ticket \u2014 even if the change fixes the problem, the process violation is the offense", "Failing CompTIA Security+ past the second attempt \u2014 it delays your upgrade training, flags you in the unit, and commanders notice", "Missing CDCs deadlines or failing the CDC test \u2014 forces a retest cycle and can delay your 5-level completion by six months or more", "Letting your physical fitness or dress standards slip while everyone assumes the comms troop is just sitting at a computer all day \u2014 commanders and first sergeants look for reasons, and a failed PT test from a desk-job Airman reads as a discipline problem"]
A Day in the Life
[{"time": "0630", "activity": "PT formation with the squadron. The comms shop may or may not do organized PT \u2014 depends on the unit. If they do not, you are responsible for getting your own PT in."}, {"time": "0730", "activity": "Accountability formation. Flight chief reviews the day's priorities. Trouble ticket queue review."}, {"time": "0800", "activity": "Help Desk opens. First wave of tickets \u2014 password resets, CAC issues, workstation connectivity. You are handling the queue alongside one or two other junior Airmen."}, {"time": "0930", "activity": "Escalated ticket work \u2014 something the Help Desk cannot resolve remotely. You pull the laptop and bring it to the bench."}, {"time": "1000", "activity": "Scheduled task: workstation imaging for a newly reporting unit member or a machine that failed last month's SCAP scan."}, {"time": "1130", "activity": "Shop standup \u2014 brief with your 5-level or 7-level on anything open, anything coming due, any system notifications from AFNOSC or MAJCOM."}, {"time": "1200", "activity": "Lunch. One hour. First sergeant will notice if you are consistently late back."}, {"time": "1300", "activity": "Afternoon ticket queue. This is usually heavier than the morning \u2014 users have had half a day to break things."}, {"time": "1430", "activity": "CDC study hour if your shop supports it, or individual study time if you are squared away on tickets. This is when you work on Security+ if you have not passed it yet."}, {"time": "1530", "activity": "End-of-day ticket documentation. Close resolved tickets properly. Handoff anything that needs overnight monitoring."}, {"time": "1600", "activity": "Duty day ends for most. If you are on-call rotation, you have a phone and a laptop."}, {"time": "After hours", "activity": "Self-study or cert prep at home. The Airmen who pass Security+ in their first six months are not doing it on duty time."}]
Weekly Cadence
Monday through Friday runs on a rhythm that is mostly driven by the ticket queue. Mondays are heavier because users have accumulated issues over the weekend. Fridays are lighter on tickets but heavier on administrative tasks — compliance reports, access reviews, any week-close paperwork your section requires.
Tuesday or Wednesday will typically have some form of training requirement — whether that is formal CDC time, a unit training day, or a scheduled maintenance window where you get to work on infrastructure instead of supporting users. These windows are valuable and good junior 2E1s treat them as such.
The rhythm breaks when something on the network breaks. A core switch goes down, a SCAP finding turns into an emergency remediation, or AFNOSC pushes a time-sensitive patch. When that happens, the schedule does not matter anymore. You work the problem until it is resolved. That is the job.
Key Skills — How to Drill Each
[{"skill": "Active Directory and user account management", "how": "Every user on base touches AD. Learn the real structure \u2014 OUs, GPOs, group membership, privilege escalation. Volunteer to be the one who handles account creation and termination. When you understand the OU structure for your base, you understand the base."}, {"skill": "STIG application and SCAP compliance scanning", "how": "Download the current DISA STIGs for Windows and run SCAP Compliance Checker against a lab machine first, then a production workstation. Learn which findings are CAT I versus CAT II versus CAT III. Your shop will have a standard baseline \u2014 know what every deviation means and who approved it."}, {"skill": "Basic TCP/IP networking and troubleshooting", "how": "When a user cannot connect, learn to actually trace the problem: workstation NIC, switch port, VLAN assignment, DHCP lease, DNS resolution, firewall rule. Do not just reimage the machine and call it fixed. Use Wireshark at least once on a live problem."}, {"skill": "Trouble ticket documentation", "how": "Write tickets that a person with no context could read six months later and understand exactly what happened, what you tried, and what fixed it. Lazy ticket notes protect nobody and burn the next tech who touches the problem."}, {"skill": "CompTIA Security+ exam preparation", "how": "Study with the official CompTIA CertMaster or Professor Messer's free video series. The test is DoD-required and your shop leadership will track your progress. Pass it the first time \u2014 second attempts draw attention you do not want."}]
Manuals & References — What Chapters Matter
[{"ref": "DAFI 17-101, Information Technology Portfolio Management", "why": "The foundational AFI governing how the Air Force manages IT systems \u2014 you need to know the policy framework you are operating inside, especially what requires approval."}, {"ref": "DISA STIG Library (public.cyber.mil/stigs)", "why": "Every system you touch must meet STIG requirements. Bookmark the Windows and network device STIGs and understand the severity categories before your first compliance scan."}, {"ref": "DoD 8140.01 Cyberspace Workforce Management", "why": "This is the policy that drives your certification requirements. Understand which IAT level your position requires and what certifications satisfy it."}, {"ref": "AFI 33-200 series, Information Assurance", "why": "The Air Force-specific implementation of information assurance policy \u2014 covers your responsibilities for handling CUI, managing systems, and reporting incidents."}, {"ref": "CompTIA Security+ Study Guide (SY0-701 current version)", "why": "Not a .mil doc, but it is the certification that unlocks your upgrade training. Treat it like required reading from day one."}]
Standards — How to Hit Each
[{"standard": "DoD 8140 IAT Level II baseline (CompTIA Security+) within first year", "how": "Register through your unit's training office. Most bases have a testing contract with Pearson VUE. Do not wait for someone to schedule it for you \u2014 ask."}, {"standard": "5-level upgrade training CDCs completed within 24 months", "how": "Work through your CDC volume systematically and do not let it pile up. The end-of-course test has a passing score requirement \u2014 treat the CDCs like a real course, not paperwork."}, {"standard": "Annual IA awareness training and systems access recertification", "how": "Your unit will have a tracked deadline. Miss it and your account access gets suspended, which shuts down your ability to do the job. Put it on your calendar the first day of the fiscal year."}, {"standard": "Physical fitness standards (USAF ACFT requirements)", "how": "Yes, you work at a desk. The standard is the same. A failed fitness assessment from a comms troop reads as unmotivated to a first sergeant, and unmotivated junior Airmen do not get the interesting assignments."}]
Technical Mistakes — Concrete Consequences
[{"mistake": "Making changes to a production system without a change request", "consequence": "Your change causes an outage. You have no paperwork. You are now the person who caused an unplanned outage with no authorization. The squadron commander will hear about this by COB."}, {"mistake": "Connecting an unauthorized device to the NIPR or SIPR network", "consequence": "Immediate security incident report. If it was a personal device, you are looking at a UCMJ Article 92 and possibly loss of your clearance. There is no version of this that ends well."}, {"mistake": "Applying a STIG finding fix to production without understanding what it does", "consequence": "Some STIG remediations break functionality. A well-intentioned fix that disables a service the flight surgeon's office depends on will produce a very fast and very loud call to your shop chief."}, {"mistake": "Closing a trouble ticket as resolved without confirming with the user", "consequence": "The problem was not actually fixed. The user calls back angrier. Your ticket metrics look dishonest. The shop chief notices patterns in your closure rate."}]
Career Decisions at This Rank
[{"decision": "When to pursue additional certifications beyond Security+", "analysis": "Security+ is the floor, not the ceiling. CompTIA Network+ is a natural complement and strengthens your networking work. CySA+ moves you toward cyber work that is genuinely interesting and more transferable. The question is whether you want to build depth in a specialty or breadth across multiple areas. In a base communications squadron, breadth is more useful. In a MAJCOM or cyber unit, depth matters more. Start with the cert your shop is most short on."}, {"decision": "Help Desk versus infrastructure \u2014 which rotation to push for", "analysis": "The Help Desk is where everyone starts, but it is not where you want to stay. Volunteer for server room work, network infrastructure tasks, or any project that gets you out of the ticket queue. These assignments are where you learn the skills that matter for promotion and for the civilian market when you separate. A 5-level who spent four years only on Help Desk is less competitive than one who spent two years on Help Desk and two years managing servers."}, {"decision": "Whether to go for early Airman Below the Zone promotion", "analysis": "BTZ promotion to SrA is competitive and varies by wing and group. Your EPR must be solid, your fitness must be solid, and someone senior must think you are ready. If you are passed over for BTZ it does not define your career, but if you are in the running, make sure your documentation is complete \u2014 all CDCs done, Security+ passed, no negative paperwork. The comms career field promotes well overall because people keep leaving."}]
How the Seat Varies by Unit Type
[{"unitType": "Base Communications Squadron (CS)", "reality": "This is where most junior 2E1s land. You support the entire installation's IT infrastructure. It is a large shop with specialists in multiple areas. The work is steady and broad. The pace is driven by the ticket queue and compliance cycles."}, {"unitType": "Communications Flight within an Operations Group", "reality": "Smaller shop attached to a flying unit. You are supporting the infrastructure that connects to aircraft operations \u2014 not the avionics, but the networks and systems those operations depend on. Higher operational tempo, closer integration with flying ops, more visible when something breaks."}, {"unitType": "Deployed/Expeditionary", "reality": "Everything is harder, simpler, and more important simultaneously. You might be running a small tactical network with equipment that has been around longer than you have. You will troubleshoot things you were never trained on. There is no second tier of support. You fix it or it stays broken."}]
What Good Looks Like at This Rank
A high-performing junior 2E1 is the Airman who finishes their CDCs ahead of schedule, passes Security+ on the first attempt, and then starts asking what else they can work on instead of waiting to be assigned something. They know the base network topology better than Airmen one rank above them. When a trouble ticket comes in that is actually interesting — a weird routing problem, a STIG finding that is creating a conflict — they are the one the 5-level calls over to look at it.
They also document everything. Every change they make. Every fix they attempt. Every weird error message they see. The comms world runs on institutional knowledge and the juniors who build the habit of capturing that knowledge become indispensable. The ones who just close tickets and go home stay on the Help Desk longer than they want to.
At this rank, you are not expected to be an expert. You are expected to be hungry. The difference between a junior 2E1 who gets promoted on first look and one who waits two cycles is usually not talent — it is whether they treated the first year as training or as time to survive.
Preview — The Next Rank
SrA is where the job actually starts. By the time you pin on that stripe you should have your Security+, a functional understanding of the base network architecture, and at least one secondary specialty beyond Help Desk. The expectation at SrA is independent task execution — your supervisor tells you what needs doing and you go do it without hand-holding.
The civilian market is going to start actively recruiting you around the eighteen-month mark. LinkedIn will find you. Veterans in tech will reach out. A 2E1 SrA with Security+ and real systems work is not hard to place. Think carefully about what the Air Force still offers that the civilian market does not: structure, free certifications, the ability to get a TS/SCI, and the chance to work systems and networks at a scale most private-sector juniors will never see. That clearance is worth real money. The question is whether it is worth it to you to stay long enough to monetize it in uniform, or take the immediate salary.
FAQ
2E1X1 E1-E3 — Frequently Asked Questions
Q01What does a E1-E3 2E1X1 (Communications-Computer Systems) actually do?
Complete 2E1X1 initial skills training at Keesler AFB, MS. Learn networking fundamentals — TCP/IP, routing, switching, wireless protocols, and the DoD network architecture that governs Air Force information systems.
Q02What's the most important thing to know as a E1-E3 2E1X1?
Welcome to the Help Desk.
Q03What mistakes get E1-E3 2E1X1 soldiers fired or relieved?
["Losing or mishandling a CAC card or classified media \u2014 one incident creates a security report, commander notification, and a mark that follows you", "Performing unauthorized changes to a production system without a change request ticket \u2014 even if the change fixes the problem, the process violation is the offense", "Failing CompTIA Security+ past the second attempt \u2014 it delays your upgrade training, flags you in the unit, and commanders notice",…
Q04What's next after E1-E3 for a 2E1X1 (Communications-Computer Systems) in the Air Force?
SrA is where the job actually starts.
Q05What manuals and regulations does a E1-E3 2E1X1 need to know cold?
DoD 8570.01 (Cybersecurity Workforce), AFI 17-1301 (Computer Security), applicable AFMAN and AFPD for communications systems, Keesler AFB 2E1X1 training publications, CompTIA Security+ (baseline certification)
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