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 62E Developmental Engineer — overview, pay, training, civilian translation, reviews
62EO1-O2

Developmental Engineer

O-1 to O-2 (Junior Officer) · Space Force

O1–O2O3–O4
HEADS UP

62E Developmental Engineer is the SF's technical engineering officer specialty — running materiel development and engineering at Space Systems Command (SSC) product offices in Los Angeles AFB and the various SSC product center detachments. The Defense Acquisition Workforce certification framework under DAWIA (codified in 10 U.S.C. § 1701 et seq. and implemented under DoDI 5000.66) is the load-bearing institutional credential pipeline. Engineering technical depth + the SSC program-office context shape the 62E career from day one.

The Honest MOS Read
62E Developmental Engineer is the Space Force's developmental engineering officer career field — the officer specialty responsible for the technical engineering side of space materiel development and the engineering integration with the SF acquisition enterprise. As a brand-new O-1 / O-2 Guardian developmental engineer, your accession route (USAFA STEM commissioning, AF ROTC engineering commissioning, OTS direct accession with engineering background, or direct SF accession from civilian engineering work) brought you through commissioning with an accredited engineering degree (ABET-accredited engineering programs are the canonical accession source), then through 62E technical training. The SF inherited the 62E AFSC from the AF when the service stood up; verify current career field structure against current SF / SSC messaging given ongoing SF AFSC restructuring iterations. Space Systems Command (SSC) is the institutional anchor for 62E Guardians. SSC headquartered at Los Angeles AFB, CA — one of the three SF Field Commands (alongside Space Operations Command at Peterson SFB and Space Training and Readiness Command at Peterson SFB) — runs the SF's materiel development and acquisition mission. SSC's subordinate product offices, program executive offices, and the various engineering and program management organizations across Los Angeles, Kirtland AFB (Space Vehicles Directorate of Air Force Research Laboratory, with SF integration), Patrick SFB (Space Launch Delta 45 and the integrated launch enterprise), Vandenberg SFB (the western launch range), and the various contractor-collocation locations are where 62E Guardians work. The product offices structure runs the operational engineering work. Program offices for the major SF programs — the GPS III / GPS IIIF satellite program, the Next-Generation OPIR (NGG) missile warning satellite program, the Space Development Agency (SDA) Tranche programs (the proliferated low Earth orbit constellation programs that have been delivering since 2024), the Wideband Global SATCOM (WGS) follow-on, the Advanced Extremely High Frequency (AEHF) follow-on, the Space-Based Infrared System (SBIRS) sustainment and follow-on, the National Security Space Launch (NSSL) program with the SpaceX / ULA / Blue Origin launch service procurement contracts, the various ground-system programs — each carry 62E billets at the junior engineer / engineering-lead level. The Defense Acquisition Workforce certification under DAWIA (Defense Acquisition Workforce Improvement Act, codified in 10 U.S.C. § 1701 et seq. and implemented under DoDI 5000.66) is the load-bearing institutional credential pipeline for 62E officers. The DAWIA framework restructured in 2022 (the Back-to-Basics restructure consolidated certification levels from three to two — Practitioner and Senior Practitioner — across the various functional areas including Engineering & Technical Management, Program Management, Contracting, and the others). Engineering & Technical Management certification at the Practitioner level is the entry-tier DAWIA credential expected by the 62E officer career timeline; Senior Practitioner certification follows at the field-grade level. Defense Acquisition University (DAU) courses are the primary training venue; the DAU course catalog is publicly published and the 62E course requirements should be verified against current SSC messaging and the DAU course catalog. The SF acquisition workforce context matters institutionally. The Space Force has been building its acquisition workforce from the AF inheritance plus direct accession plus selective lateral transfers across the first five years; the SF acquisition workforce is structurally smaller than the AF acquisition workforce by a meaningful factor. The Assistant Secretary of the Air Force for Space Acquisition and Integration (SAF/SQ) — stood up under the SF acquisition reform legislation — is the senior civilian acquisition authority for SF programs. The SSC commander (a SF Lt Gen) reports to SAF/SQ for acquisition oversight. The SF acquisition workforce institutional culture is being built in real time around the SSC product offices. The Space Force institutional context applies. SF officer promotion to O-2 (1st Lt) at 24 months commissioned under DOPMA; O-2 to O-3 board at 4 years commissioned, historically very high select. The Guardian Talent Management framework emphasizes developmental progression — for 62E officers, the developmental cadence runs through engineering technical depth + DAWIA certification + product-office program experience as the visible career signals. The post-service market for SF 62Es is structurally elite. The commercial space industry expansion has been driving structural demand for engineers with combined engineering depth + SF acquisition / program-office experience + active clearance. SpaceX, Blue Origin, ULA, Rocket Lab, Lockheed Martin Space, Northrop Grumman Space, Raytheon Space (the various platform contractors), the SDA contractor base (the various LEO satellite manufacturers), and the broader aerospace startup ecosystem hire former SF 62E officers at materially higher compensation than active-duty pay scales.
Career Arc
  • 01Commission (USAFA STEM / AF ROTC engineering / OTS / direct SF accession) — 62E career field designation with ABET-accredited engineering degree.
  • 0262E technical training and initial DAWIA Engineering & Technical Management certification courses at DAU.
  • 03First assignment: SSC product office at Los Angeles AFB or detachment — junior engineer / engineering-lead.
  • 04DAWIA Engineering & Technical Management Practitioner certification — institutional credential pipeline.
  • 05Program experience: GPS, NGG, SDA Tranche, MILSATCOM, NSSL, or ground-system program engineering work.
  • 06~24 months: O-2 (1st Lt) pin-on under DOPMA.
  • 07~48 months: O-3 (Capt) board, historically very high select for SF.
Common Screwups
  • ×Phoning DAWIA certification progression. The DAWIA Practitioner credential is the visible engineering-officer career signal; absence at the LT timeline reads as a developmental gap to SSC leadership.
  • ×Treating the SSC program-office work as routine engineering. The institutional craft of materiel development + the acquisition lifecycle context shape the 62E career; passive engagement compounds.
  • ×DUI / Article 15 / clearance compromise — terminal for SF career given the clearance dependency of essentially every 62E program and the small-service institutional memory.
  • ×Underestimating the commercial space market positioning timing. SF engineering experience + active clearance + DAWIA credentials + 4-6 years TIS is the optimal post-service positioning window.
  • ×Missing the Guardian Talent Management developmental engagement. SF officer development is more deliberate than legacy AF; passive engagement at the technical engineering career field compounds.

A Day in the Life

  • 0600Arrive at SSC Los Angeles AFB. Badge into the program office space. Check overnight contractor correspondence — any anomaly reports, schedule change notices, or RFI responses that arrived after close of business.
  • 0615-0700Review the day's schedule: IPT prep, TIM attendance, AI tracker review, any CDR artifact deliverables due. Flag any contractor deliverable that is past due; draft escalation note to the CE if it has aged more than 3 days.
  • 0700-0800Integrated Product Team (IPT) or sub-IPT meeting. Take structured notes: every action item assigned gets an owner, a due date, and a closure criterion. Send the AI list to the program office distribution within 2 hours of meeting close.
  • 0800-1000Technical deliverable review. A contractor has submitted a test plan or interface control document for government review and comment. Work through the document against the contract CDRL and the SEP; mark up discrepancies against specific requirement paragraphs.
  • 1000-1130Technical interchange meeting (TIM) with contractor SE team. Active engagement: take notes, ask clarifying questions on any integration concern mentioned in passing. The item the contractor mentions once and doesn't repeat is the risk you flag in the post-TIM read-out.
  • 1130-1200Draft the TIM read-out: attendees, topics, open items identified, AIs assigned. The read-out goes to the distribution list before end of business.
  • 1200-1300Lunch. Eat with the program office team. The culture of the program office — how the PM talks about the contractor, how the CE characterizes the program's real risk posture — is transmitted in informal conversation more than in formal meetings. Listen.
  • 1300-1430Risk register update. Review the current risk register against any new information from the morning's TIM. Revise likelihood/consequence ratings if warranted; draft updated mitigation actions for the CE's review. New risks get an initial entry before EOD.
  • 1430-1600DAWIA coursework or self-development. DAU online courses during the enrollment window; technical reading (DoDI 5000.85 milestone chapter, DAFMAN 63-101 technical review section, DAU SE Fundamentals Guide chapter) when between formal courses. Treat this block as protected — program office urgent-but-not-important taskers are the enemy of certification completion.
  • 1600-1700OPR support-form maintenance. Once per week, add one bullet to the running draft support form. Action verb, named program, measurable outcome. The officer who maintains a running draft delivers a complete support form to the rater on day one of the OPR window; the one who writes it from memory in the last week delivers a less accurate version.
  • 1700-1730End-of-day correspondence. Respond to any RFIs or action requests that arrived during the afternoon. Flag anything requiring CE or PM decision for the next morning's meeting.
  • 1730Depart. The program office culture at SSC is professional but not uniformly 0600-2200; the normal garrison day is 0600-1730 with occasional longer days for review preparation. The engineers who consistently leave before the work is done are visible; the ones who consistently stay later than necessary without delivery are also visible.
  • 1900-2100Personal time. Physical fitness maintenance — DAFMAN 36-2905 PFA in a 10,000-person service is visible fast. If a CDR preparation cycle is active, evening technical reading is warranted; the morning markup is better when the previous evening included document review.

Weekly Cadence

The weekly rhythm for a junior 62E at an SSC program office is anchored to the program review calendar rather than a watchbill. Unlike operational SF career fields, there is no shift rotation; the program office works a standard garrison schedule with surge periods driven by milestone review preparation cycles. A Milestone B prep cycle — typically 6-12 weeks of intensive technical documentation review, Systems Engineering Plan revision, and independent review team preparation — is the highest-tempo period in the program office year. The engineer who has not maintained the technical baseline documentation throughout the preceding 12 months is the engineer who is scrambling during the prep cycle. On normal non-surge weeks, the rhythm runs across IPT meetings (usually two to three per week at the program or sub-IPT level), contractor TIM attendance, technical deliverable review, risk register maintenance, and DAWIA coursework. The IPT and TIM schedule is set by the PM's calendar; protect your DAWIA course windows before the PM's calendar crowds them. The engineering tasks that matter institutionally — the CDR artifact markup, the risk register currency, the AI tracker accuracy — are the tasks that get done between formal meetings, not during them. The junior engineer who fills all the meeting time with passive attendance and has no protected block for actual engineering work is the engineer who is always behind on the review cycle. The developmental engagement cycle runs quarterly under the Guardian Talent Management framework. The 62E career-field manager and the SSC senior engineering officer conduct developmental conversations on a published schedule; the junior officer who arrives at the developmental conversation with a documented DAWIA enrollment date, a named program milestone achieved, and a specific question about the next developmental assignment is the officer the career-field manager has a substantive conversation with. The officer who shows up without preparation gets a generic conversation and a generic recommendation. In a small service, generic recommendations are not the outcome you want.

Key Skills — How to Drill Each

  1. 01
    Read and mark up a contractor Preliminary Design Review package — identify open design issues, interface risks, and requirements traceability gaps before the review board convenes.
    The PDR package is the contractor's argument that the design is ready to proceed to detailed design. Your job is to find the holes before the chief engineer sits down with the contractor at the review table. Start with the requirements traceability matrix: every Level 1 and Level 2 requirement should trace to a design element and a planned verification method. Pull the interface control documents and verify the interface definitions are stable and signed. Look at the open items list from the previous technical interchange meeting and confirm every open item has a disposition. The chief engineer who receives your pre-PDR markup with three specific technical risks and their closure criteria is the chief engineer who starts trusting your technical read. The one who receives a clean "looks good to me" is the one who does the markup herself and wonders why she needs a junior engineer.
  2. 02
    Manage a technical action item tracker with owner, due date, and non-vague closure criterion for every open item.
    The AI tracker is the institutional memory of every technical review the program office has ever held. If it's stale, incomplete, or has AIs that say "closed" without a closure document, the next independent review team will find it and the chief engineer will be explaining it to the PEO. Own the tracker like it's the record of what you did this year — because it is. Every new AI gets an owner (a specific name, not "contractor"), a due date (a specific date, not "ASAP"), and a closure criterion (a specific deliverable or decision, not "when resolved"). Aged AIs get escalated to the chief engineer before they turn red on the dashboard; the CE does not want to see a six-month-old open AI for the first time at a program management review.
  3. 03
    Brief engineering risk status to the program chief engineer — one slide, three risks, likelihood/consequence/mitigation, no fluff.
    The CE brief is not a status report. It is a decision brief. The CE needs to know: what are the top risks, how likely are they, what happens if they materialize, what is the mitigation plan, and what decision do you need from her to close the risk. The slide that lists fifteen risks and says "mitigation in work" for all of them is not a decision brief — it's a reading assignment the CE doesn't have time for. Pick the three that matter most, explain the technical basis for the likelihood and consequence ratings, and name the specific mitigation action and the person responsible. If you need a resource decision or a contractor directive from the CE to close a risk, say that on the slide. The CE who leaves the brief without knowing what she needs to do has been briefed by someone who doesn't yet understand what a chief engineer does.
  4. 04
    Apply the Systems Engineering Plan and program technical baseline documents to assess whether a contractor deliverable meets the contractual requirement.
    The SEP defines the technical management process the program is committed to; the contract SOW and CDRLs define what the contractor is required to deliver. Your job is to sit at the intersection. When a contractor submits a technical deliverable — a test plan, an interface control document, a preliminary design product — pull the relevant CDRL and the SOW paragraph it flows from, then read the deliverable against the requirement. Does the test plan cover the test events listed in the CDR entrance criteria? Does the ICD include the interface parameters specified in the contract? The reviewer who can cite the specific contract paragraph and the specific SEP section when she marks up a deliverable is the reviewer the contractor takes seriously. The one who says "this doesn't look right" without a citation gets a polite response and no change.
  5. 05
    Execute DAWIA Engineering & Technical Management Practitioner certification on the published career-field timeline.
    The DAWIA certification is not background noise — it is the institutional signal that you are building the credential the SF acquisition community requires. The Back-to-Basics restructure (post-2022) consolidated the E&TM certification requirements; verify the current course requirements against the DAU course catalog and the current 62E career-field guidance. Identify the required DAU courses, check enrollment wait times (some courses book out 6-12 months), and lock in your enrollment dates in the first 90 days at your first assignment. The 62E officer who completes Practitioner certification ahead of the career-field timeline is the officer the chief engineer recommends for the next developmental assignment. The one who arrives at the O-3 board without it has a gap the board answers without your input.
  6. 06
    Maintain TS/SCI clearance discipline: self-report foreign contacts, no SCIF physical security lapses, no classified-handling deviations.
    Every major program the 62E career field supports — GPS III, NGG, SDA Tranche satellites, AEHF/EHF follow-on, NSSL — is classified. Your clearance is the prerequisite to every billet in the career field. The self-report requirement under DoDM 5240.01 covers foreign contacts, foreign travel, cohabitation changes, financial distress, and elicitation attempts — report before the next poly, not during it. SCIF physical security is not negotiable: phone in the lockbox, no exceptions. The junior engineer who treats the clearance maintenance requirements as bureaucratic friction is the engineer who generates a Security Information File review that follows every subsequent read-on for the rest of the career. The SSO at SSC Los Angeles knows every junior officer on the program; the one with a clean clearance record is the one who gets put in front of sensitive compartment read-ons without administrative friction.

Manuals & References — What Chapters Matter

  • DoDI 5000.85 — Major Capability Acquisition.
    The policy framework that defines Milestone A, B, and C decision structure, the Acquisition Decision Memorandum content, the Independent Cost Estimate requirements, and the acquisition documentation baseline for every SF major capability acquisition program. Read the milestone decision chapters before your first milestone review preparation cycle so that you understand what the MDA staff is looking for in the technical engineering artifacts. The PDR/CDR milestone criteria, the Systems Engineering Plan requirements, and the test and evaluation master plan requirements all flow from DoDI 5000.85.
  • DAFMAN 63-101/20-101 — Integrated Life Cycle Management.
    The DAF-level acquisition management DAFMAN that governs SF program execution across the full lifecycle. The Chapters on technical management (SEP requirements, technical review criteria, systems engineering risk management) are the ones the SSC chief engineer and the PEO technical advisor read when they assess your program's engineering baseline. Read the technical review entrance and exit criteria sections before your first PDR or CDR preparation cycle; the DAFMAN is what the independent review team cites when it findings your program.
  • DoDI 5000.66 — Defense Acquisition Workforce Education, Training, Experience, and Career Development Program.
    The DAWIA framework document. Read it to understand the certification structure (Practitioner / Senior Practitioner), the functional area requirements (Engineering & Technical Management is your lane), and the career-field developmental expectations at each grade. The DoDI 5000.66 framework is what the career-field manager and the Guardian Talent Management process cite when they evaluate your developmental progression; knowing the framework means you can manage your own development rather than waiting for the institution to manage it for you.
  • DAU Systems Engineering Fundamentals Guide (publicly available at dau.edu).
    The foundational SE reference the DAU E&TM Practitioner curriculum is built around. It covers systems thinking, requirements development, functional analysis, design synthesis, design verification, and technical reviews (SRR/PDR/CDR/PRR structure). Read the technical review chapters before your first program-office review cycle. The DAU guide is the reference the DAU E&TM Practitioner course instructors use; reading it before the course means you spend the course applying the framework rather than learning the vocabulary.
  • USSPD 1 — U.S. Space Force Doctrine Publication 1, The Spacepower Doctrine.
    The institutional frame for the SF acquisition mission. The 62E officer who understands how the programs she supports connect to the SF's warfighting functions — space superiority, space domain awareness, space access and sustainment — is the engineer who can explain the operational significance of a technical decision to the program manager and the PEO. Read it in the first 30 days of the first assignment; it frames the institutional identity of the SF acquisition workforce.

Standards — How to Hit Each

  • DAWIA Engineering & Technical Management Practitioner certification completed within the career-field published timeline.
    Identify the required DAU courses in the first 30 days, check current enrollment wait times at the DAU catalog (dau.edu), and lock enrollment dates before other program commitments crowd the calendar. The 62E career-field manager publishes developmental timelines; verify the current milestones against current SSC/SAF/SQ guidance. The officer who completes Practitioner certification before the first OPR close date has a credential to put in the support-form input; the officer who completes it after has an explanation to write instead.
  • Assigned program technical action items closed on time with documented closure criteria met.
    Run the AI tracker actively, not reactively. Check it weekly, not when the chief engineer asks for a status. Every AI that is approaching its due date and is not on track for closure needs to be escalated to the owner and briefed to the CE before it turns red — not after. The CE who never sees a red AI on your section's list because you escalate before it ages is the CE who gives you the next developmental engineering task. The one who finds red AIs by reading the dashboard herself has a different conversation with you.
  • TS/SCI clearance maintained clean through the first assignment cycle.
    Treat clearance maintenance as a standing task, not an event. Self-report anything reportable immediately — the investigator who finds an unreported foreign contact at the reinvestigation is reading the gap as an integrity indicator, not a judgment error. Build the SCIF physical security habits in the first week and never deviate. The officer with a clean clearance record at the end of the first assignment has a credential that follows every subsequent billet; the one with a SIF entry is managing that record for the rest of the career.
  • First OPR support-form input delivered on time with at least two named program technical milestones.
    The OPR narrative for a 62E junior officer is built from named program-office accomplishments: "Led PDR technical review for [program name] — identified 7 open design risks, all closed prior to PDR completion." The support form you give the rater should have three to five bullets in this format. Action verb, specific program or deliverable, measurable outcome. Deliver the input two weeks before the OPR close date; your rater needs time to build the stratification narrative. The officer who delivers a blank or generic support form is the officer whose OPR the rater writes from scratch — and the rater's version will not be as accurate as yours.

Technical Mistakes — Concrete Consequences

  • Accepting a contractor deliverable without verifying requirements traceability.
    The independent review team that walks in for the program's annual technical assessment opens the requirements traceability matrix first. An RTM that shows "requirement met" without the backing analysis is a finding on day one; the finding goes in the review report with the program office's name on it. The program manager is now briefing the PEO on why engineering accepted a deliverable without traceability verification. The engineer who catches the gap before acceptance and returns the deliverable for revision has done exactly what she is paid to do; the one who accepted it is explaining the finding.
  • Letting a technical action item age past its due date without escalation.
    Aged AIs are the first thing the next milestone review board reads when it wants to know whether the program office is managing its technical baseline. An AI that is six months past due without a revised due date and an escalation record signals that the program office is not tracking its own open issues. The board finding cites the AI number and the original due date; the program manager explains it to the PEO. The engineer who escalated the aged AI to the CE three months ago has a memo in the record; the one who watched it age without escalation does not.
  • Treating a technical interchange meeting as passive attendance.
    The TIM is the primary venue where contractor technical risk surfaces below the level of formal review. The contractor's lead engineer mentions a subsystem integration concern in passing during the TIM; the engineer who was not taking notes and not asking follow-up questions misses it. The concern becomes a PDR finding six months later. The program manager asks why the issue wasn't flagged earlier; the TIM notes — or the absence of TIM notes — answer the question. Every TIM produces a written read-out with open items identified and assigned; the engineer who runs the TIM read-out process owns the institutional memory of what the contractor said.
  • Missing a DAU course enrollment window for DAWIA Practitioner certification.
    DAU course enrollments fill on a first-available basis; some courses have wait times of 6-12 months depending on class frequency. An engineer who misses the first available window for a required E&TM Practitioner course is now looking at a 12-18 month delay in certification completion. If the delay pushes completion past the career-field published timeline, the developmental record shows a gap. The CE who signs the officer's annual developmental review is noting the certification status; the one who has been told the course is "on the list but not scheduled" is writing a different developmental comment than the one who has been shown a confirmed enrollment date.
  • Posting any assignment-specific, program-specific, or unit-identifying information on any public-facing platform.
    SF acquisition programs — especially OPIR, SDA, and national security space launch programs — are adversary collection priorities. The People's Liberation Army Aerospace Force and Russian intelligence services run open-source collection against US space acquisition programs; a LinkedIn entry that identifies the specific program office and the satellite program you support gives the adversary a collection thread. A single identifiable post from a cleared program-office engineer generates an OPSEC incident report the SSO briefs to the program manager. DAFI 10-701 OPSEC requirements apply to SF acquisition personnel; the engineer who treats social media disclosure as a personal judgment call is the engineer who generates an OPR-period OPSEC incident.

Career Decisions at This Rank

  • First assignment program office — advocate for which program?
    The assignment process runs through SF personnel management; junior 62Es have limited direct influence but are asked for preferences. The honest analysis: the program you work on shapes the technical domain you know, the contractor relationships you build, and the post-service market language you can speak credibly. GPS III / GPS IIIF builds the positioning, navigation, and timing (PNT) credential that both DoD and commercial GPS-dependent industries (aviation, autonomous systems, precision agriculture, telecommunications) recognize. Next-Gen OPIR and the SBIRS follow-on build the overhead persistent infrared and missile warning credential that the IC and missile defense contractor base hire against. SDA Tranche programs build the proliferated LEO constellation credential that the commercial smallsat industry (Planet, Spire, SpaceX Starlink supply chain, the various LEO constellation contractors) values most directly. NSSL builds the launch acquisition and range integration credential that the commercial launch industry (SpaceX, ULA, Blue Origin, Rocket Lab, ABL Space) recognizes. All are valid developmental programs; pick based on technical interest, not perceived prestige.
  • AFIT graduate school — apply for the 62E developmental education track or defer?
    The Air Force Institute of Technology at Wright-Patterson AFB runs a graduate school program (AFIT EN — the Graduate School of Engineering and Management) with SF-relevant degree programs in systems engineering, astronautical engineering, and space systems. The AFIT assignment is a developmental education billet that typically runs 18-24 months toward a master's degree. The honest analysis: AFIT timing matters. The optimal AFIT window for a 62E officer is after the first operational assignment (post-LT, at Captain) — you arrive with enough program-office context to apply the engineering graduate curriculum to real program problems, and the master's credential is in the OPR before the O-4 board. The LT who applies to AFIT before completing the first operational assignment loses the program-office experience context that makes the graduate degree useful. The Capt who applies at the 36-month mark arrives at AFIT with the technical questions that two years in an SSC program office has generated.
  • NRO / IC partner exchange tour — pursue or build more SSC depth?
    The National Reconnaissance Office runs program exchange tours for SF acquisition officers; the IC partner interfaces (NGA, NSA, and the broader IC acquisition community) also carry SF billets. The exchange tour puts the 62E officer in the IC acquisition environment, building the interagency acquisition credential and the intelligence community relationships that the NRO program office and the downstream post-service IC market value. The honest trade-off: an NRO exchange tour during the Captain years builds institutional breadth at the cost of SSC program depth. The officer who comes back from an NRO tour to a Major-level SSC program office leads a program that her peer without the exchange tour has been building for two additional years. The institutional breadth is real; the lost program depth is also real. The officer whose career goal is SSC program leadership (PM track) should defer the IC exchange tour until after a first program leadership role. The officer whose goal is the IC acquisition community should pursue the exchange tour at the earliest opportunity.
  • Stay 62E engineering track or cross-flow to 63A program management track?
    The SF, like the legacy AF acquisition community, allows officers to cross-flow between the engineering (62E) and program management (63A) functional areas under career-broadening assignment processes. The honest analysis: the engineering and program management tracks have structurally different career arcs in the SSC community. The 62E track leads toward Chief Engineer, Program Chief Engineer, and Deputy Program Manager (technical) roles; the 63A track leads toward Program Manager and Deputy Program Manager (program management) roles. Both tracks converge at the O-5 and O-6 program leadership level. The cross-flow decision should be driven by whether the day-to-day work of program management — cost/schedule/performance integration, the POM/budget cycle, the source selection process, contractor performance management — is more engaging to you than the day-to-day work of systems engineering — technical review management, requirements traceability, engineering risk analysis. One answer is not more prestigious; both are required by every major space acquisition program.
  • Post-service timing — 4 years, 6 years, or career?
    The post-service market for SF 62E officers is structurally strong and time-sensitive. The optimal market positioning window is 4-6 years TIS: active TS/SCI clearance, DAWIA Practitioner certification complete, one major program milestone (PDR, CDR, or Milestone B) named in the resume, and the SF engineering community network intact. The commercial space industry (SpaceX, Blue Origin, Rocket Lab, ULA, Northrop Grumman Space, Lockheed Martin Space, the SDA contractor base) and the DoD aerospace contractor community (L3Harris, Raytheon Space, Boeing Defense Space, the various system integrators) run active recruiting programs targeting cleared SF engineering officers in this TIS window. The officer who waits until 10+ years TIS to evaluate the post-service market is the officer who has passed the peak recruiting demand window for some commercial space employers; the contractor market remains strong, but the commercial-startup and aggressive-growth employer recruiting intensity peaks at the 4-6 year window.

How the Seat Varies by Unit Type

  • SSC Program Office — Satellite Programs (GPS, NGG, AEHF/EHF, WGS follow-on) at Los Angeles AFB
    The satellite program office is the institutional center of the 62E career. The work runs on milestone review cycles (SRR / PDR / CDR / TRR / PRR), contractor IPT cadences, and the earned-value and schedule management cycle that runs monthly against the contractor's Integrated Master Schedule. The program office at LA AFB is colocated with the SSC headquarters staff and the PEO offices; the institutional engagement with senior SF acquisition leadership is higher here than at detachments. The technical engineering work is deep: satellite system-level integration, space and ground segment interface management, launch vehicle integration coordination, and the on-orbit operations hand-off engineering. The commercial space market credential built here — satellite system engineering + government acquisition + active clearance — is directly valued by satellite manufacturing and operations companies.
  • Space Development Agency (SDA) Tranche Program Engineering at Pentagon / Various Locations
    The SDA's proliferated LEO constellation programs (Tranche 0, 1, 2, and beyond) run a rapid-acquisition model that is structurally distinct from the traditional major defense acquisition program process. SDA uses firm-fixed-price contracts with aggressive delivery schedules and a deliberately reduced requirement stability period compared to ACAT I programs. The 62E engineer assigned to an SDA-interface role is working in the fastest-paced SF acquisition environment: hardware delivery timelines are compressed (Tranche 0 launched within three years of contract award), the contractor base is non-traditional (SpaceX, York Space, Lockheed, Northrop among others), and the technical review process is adapted to the rapid timeline. The engineering credential here — rapid acquisition, commercial-vendor technical integration, compressed milestone execution — is valued most directly by the commercial smallsat industry.
  • Space Vehicles Directorate / AFRL Kirtland AFB (Research and Development Engineering)
    The Air Force Research Laboratory Space Vehicles Directorate at Kirtland AFB, NM runs the SF's research and technology development pipeline — the science and engineering work that precedes the acquisition programs. 62E officers assigned to AFRL billets work at the transition from S&T to acquisition: managing research programs, supporting technology maturation reviews, and building the technical baseline that the SSC acquisition programs inherit. The work is less program-management-intensive and more technically exploratory than the SSC program office environment. The research credential built here maps to defense science and technology contractor positions (MITRE, Aerospace Corporation, the FFRDC community) and to advanced-degree academic opportunities.
  • National Reconnaissance Office (NRO) Program Exchange Billet
    NRO exchange tours put the 62E officer in the IC acquisition environment for a program or product office working on national intelligence collection systems. The work has the same systems engineering content as the SSC program offices — contractor technical reviews, requirements management, test and evaluation coordination — but the customer set and the classification context are different. NRO programs are typically classified at higher compartment levels and the mission context is intelligence collection rather than military communications or missile warning. The interagency acquisition credential and the IC community relationships built in an NRO tour are specific to the IC aerospace contractor market (the various IC-side primes and the cleared specialty engineering firms that support NRO programs).
  • CCMD Space Acquisition Advisor / Joint Staff Space Engineering Billet
    A small number of SF 62E officers serve in acquisition advisor or space engineering billets at COCOM staffs (INDOPACOM J6 / J4, CENTCOM J6, EUCOM J6) or on the Joint Staff J6. These billets put the acquisition engineer in the operational planning environment, translating space system technical parameters and acquisition timelines into joint capability assessments. The work is less contractor-facing and more joint-staff facing: writing capability assessments, supporting requirements documents, advising on space system technical parameters for operational planners who are not space acquisition specialists. The joint-duty credit (JDA toward JPME-II) and the COCOM senior leadership exposure are real career differentiators for the O-4/O-5 board. The downside: limited access to the contractor program-office technical work that builds the engineering depth the SSC requires at the senior level.

What Good Looks Like at This Rank

The strong junior 62E is the engineer the chief engineer asks to brief the PEO without coaching the content first. That trust is not given at assignment; it is built through 18 months of clean AI tracking, timely PDR markup, risk briefs that name specific mitigations rather than general monitoring, and a DAWIA Practitioner certification that is complete before the first OPR close date. The CE who has had to correct the junior engineer's deliverable reviews twice in the same month is the CE who does not send that engineer to the PEO brief unaccompanied. Off the technical work, this officer has read DoDI 5000.85 before the first milestone review, DAFMAN 63-101/20-101 before the first CDR preparation cycle, and the DAU SE Fundamentals Guide before the Practitioner course. The support-form input she delivers the rater has three bullets with named programs and measured outcomes. The DAWIA enrollment confirmation is in the file before the six-month developmental review. The SCIF physical security discipline is absolute — phone in the lockbox, every time, with no exceptions documented in the SSO's facility file. The institutional dimension of the good junior 62E matters in the small-service context that shapes SF career trajectories. SSC Los Angeles AFB is a concentrated community; the program offices talk to each other, the chief engineers compare reads on the junior engineering officers, and the PEO staff knows the junior engineers who bring real technical analysis to the IPT. The engineer who is known across two or three program office IPTs as the one who finds the requirements traceability gap before the review board is the engineer whose name the program manager uses when the PEO asks for a sharp LT to lead the next milestone preparation. That referral is the first career-shaping event, and it belongs to the engineer who earned it through consistent technical precision.

Preview — The Next Rank

Captain in the 62E career field is when SSC stops evaluating whether you can manage a PDR action item list and starts evaluating whether you can lead a CDR. The Mission Ready equivalent for the 62E engineer is the independently-chaired technical review: the officer who runs the CDR board from the entrance-criteria closure through the RID adjudication and the written board finding, without the chief engineer backstopping every decision, has reached the institutional threshold that defines Captain-level SE maturity. Every senior engineer in the program office has an opinion about which junior engineers are CDR-ready and which are still building the foundational technical depth. You want to be unambiguously in the first category by the 36-month mark. The Captain years are also when the DAWIA Senior Practitioner certification cycle begins. Verify the current E&TM Senior Practitioner course requirements against the DAU catalog; the course stack and the experience-hour requirements are the certification building blocks you need to have calendared before the Major board window. The Major board reads the developmental record; an unexplained Senior Practitioner gap at Captain requires the record to answer for it. The field-grade trajectory in the 62E career — Chief Engineer, Deputy PM (technical), and eventually Program Manager or SSC senior engineer — is decided largely by what happens in the Captain years at the SSC program office. The officer who has chaired a CDR, retired a major technical risk, and mentored two junior LTs through their DAWIA Practitioner certification is the officer the PEO puts in front of the USD(A&S) staff when the Major board selection is pending. The one whose Captain years are a sequence of IPT attendance without a named milestone in the record has a harder story to tell.
FAQ

62E O1-O2 — Frequently Asked Questions

Q01What does a O1-O2 62E (Developmental Engineer) actually do?
You work in a product office at Space Systems Command (SSC), Los Angeles AFB — or one of SSC's program detachments at Kirtland, Vandenberg, or Patrick — supporting the technical engineering baseline of a major space program.
Q02What's the most important thing to know as a O1-O2 62E?
62E Developmental Engineer is the SF's technical engineering officer specialty — running materiel development and engineering at Space Systems Command (SSC) product offices in Los Angeles AFB and the various SSC product center detachments.
Q03What does a typical day look like for a O1-O2 62E?
Time-blocked day at the O1-O2 62E rank tier: 0600 Arrive at SSC Los Angeles AFB. Badge into the program office space. Check overnight contractor correspondence — any anomaly reports, schedule change notices, or RFI responses that arrived after close of business, 0615-0700 Review the day's schedule: IPT prep, TIM attendance, AI tracker review, any CDR artifact deliverables due. Flag any contractor deliverable that is past due; draft escalation note to the CE if it has aged more than 3 days, 0700-0800 Integrated Product Team (IPT) or sub-IPT meeting.…
Q04What mistakes get O1-O2 62E soldiers fired or relieved?
Phoning DAWIA certification progression. The DAWIA Practitioner credential is the visible engineering-officer career signal; absence at the LT timeline reads as a developmental gap to SSC leadership; Treating the SSC program-office work as routine engineering. The institutional craft of materiel development + the acquisition lifecycle context shape the 62E career; passive engagement compounds;…
Q05What career decisions matter most at the O1-O2 62E rank tier?
First assignment program office — advocate for which program? — The assignment process runs through SF personnel management; junior 62Es have limited direct influence but are asked for preferences. The honest analysis: the program you work on shapes the technical domain you know, the contractor relationships you build, and the post-service market language you can speak credibly. GPS III / GPS IIIF builds the positioning, navigation, and timing (PNT) credential that both DoD and commercial GPS-dependent industries (aviation, autonomous systems, precision agriculture,…
Q06What's next after O1-O2 for a 62E (Developmental Engineer) in the Space Force?
Captain in the 62E career field is when SSC stops evaluating whether you can manage a PDR action item list and starts evaluating whether you can lead a CDR.
Q07What manuals and regulations does a O1-O2 62E need to know cold?
DoDI 5000.85 — Major Capability Acquisition. The policy framework that defines Milestone A/B/C decision structure for SF acquisition programs.; DAU SE Guide (Systems Engineering Guide for Systems of Systems) — the DAU resource 62E engineers use to calibrate SE rigor requirements.; DAFMAN 63-101/20-101 — Integrated Life Cycle Management. The DAF acquisition management DAFMAN governing SF program execution.

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