# 309th Software Engineering Group **Type:** venture **Status:** Draft **Confidence:** Medium **Focus:** flight software, weapons software, mission software, DevSecOps, safety-critical systems, Air Force sustainment **Stage:** Established U.S. Air Force organization; one of the largest defense software groups in the country **Location:** Hill Air Force Base, Ogden, UT (Ogden Air Logistics Complex) **Updated:** 2026-06-19 **Needs-reviewed:** 2026-06-19 **Pull:** *The code that keeps most of the U.S. Air Force combat fleet flying — F-35, F-22, F-16, A-10, ICBMs, cruise missiles, and the B-21 sustainment pipeline.* ## Summary The 309th Software Engineering Group (309th SWEG) is a U.S. Air Force organization at Hill Air Force Base that writes and maintains the flight, weapons, and mission software sustaining most of the Air Force combat fleet — F-35, F-22, F-16, A-10, ICBMs, cruise missiles, and emerging B-21 Raider sustainment. Roughly 2,000+ engineers work here, making it one of the largest defense software organizations in the United States. For the wiki, the 309th is civilizationally important and genuinely excellent engineering for the right person — safety-critical code on actual combat aircraft, modern DevSecOps practices on classified networks, and a talent pipeline into defense-tech startups. It is not a company and not globally category-defining in the startup sense; it is a government organic software depot with government pay scales, clearance gates, and institutional process. Anyone considering this path should also think clearly about the ethics of weapons work. ## Impact Direct impact: every sortie flown by a 309th-sustained aircraft is enabled by this code. Deterrent impact: credible U.S. air power reduces the probability of certain kinds of conflict. The organization has kept pace with industry on DevSecOps — Kessel Run-style agile models, container-based secure development, and software updates to fielded aircraft on modern cadences rather than multi-year sustainment cycles. Second-order impact matters for Utah and the broader defense-software ecosystem. The 309th is a major recruitment pool for defense-tech companies such as Anduril and Shield AI. It also sits at the center of U.S.–China defense-software modernization races: B-21 Raider, Collaborative Combat Aircraft (CCA), Sentinel ICBM, and F-35 Block 4 / TR-3 work all depend on software-first architecture, with significant sustainment responsibility landing here. ## What They Are Building The 309th sustains and modernizes safety-critical, real-time, classified software across legacy and next-generation platforms. Codebases span Ada, assembly, and C interoperating with modernized C++, Rust, and Python components. Work includes F-35 software modernization (Block 4 / TR-3), B-21 sustainment pipeline stand-up, and keeping 50-year-old airframes (A-10, B-52) operational while building software for aircraft that do not yet exist (B-21, CCA). The hard problems are simultaneous: nation-state-adversary cybersecurity, agile delivery on classified networks where you cannot pip-install or pull from GitHub, every change audited, and lives directly downstream if software fails. ## What They Need Now Likely needs include software engineers (systems, embedded, avionics, cybersecurity, DevSecOps) willing to obtain Secret or Top Secret clearances. Former military backgrounds are common but not required. Strong fit for engineers who want code on real combat aircraft, prioritize mission weight over compensation and optionality, and want to live in Utah without a Beltway commute — accepting government pay (typically below private-sector software, with a ceiling around GS-15/DR-IV). ## Who Could Help Useful helpers include clearance-process advisors, veterans' transition counselors, defense-contractor partners (SAIC, Leidos, Northrop, and others supplement the government civilian workforce), and university pipelines feeding embedded and safety-critical software talent. For ethical decision-making, candid mentors who have worked on weapons software are more useful than generic career coaches. ## Utah Context The 309th anchors Hill AFB and the Ogden Air Logistics Complex as Utah's deepest defense-software institution — distinct from comms work at [L3Harris Salt Lake City](l3harris-salt-lake.md), sensing and payloads at [Space Dynamics Laboratory](space-dynamics-laboratory.md), or counter-UAS at [Fortem Technologies](fortem-technologies.md). It connects to range and test infrastructure documented in [Utah Test and Training Range](utah-test-and-training-range.md) and to the broader Wasatch Front defense cluster referenced in guides like the Utah deep-tech map. ## Evidence - [Ogden Air Logistics Complex](https://www.hill.af.mil/Units/OO-ALC/) — Hill AFB overview of the air logistics complex hosting the 309th. - [309th Software Engineering Group overview](https://www.hill.af.mil/News/Article-Display/Article/2555867/) — official Hill AFB article on the organization. - [Kessel Run](https://kesselrun.af.mil/) — DoD DevSecOps context associated with modern Air Force software delivery practices. ## Open Questions - Clearance requirements are an absolute gate — what are realistic timelines and disqualifiers for candidates without prior clearance? - How do government pay bands compare with defense-prime contractor roles co-located at Hill for equivalent work? - Which platform programs (F-35 Block 4, B-21, CCA, Sentinel) are growing headcount versus sustaining legacy fleets? - Public portfolio-building is impossible on classified work — how do engineers here manage long-term career visibility? - Mission ethics: the page should not treat weapons software as neutral — what frameworks do thoughtful engineers use to decide fit? - The legacy tier note ranked this as strong but not globally category-defining — does that framing hold for someone optimizing for combat-aircraft software impact rather than startup equity?