←Back to 62E Developmental Engineer — overview, pay, training, civilian translation, reviews
62EO1-O2
Developmental Engineer
O-1 to O-2 (Junior Officer) · Air Force
HEADS UP
You are entering the acquisition workforce as a junior engineer, not a working engineer. The 62E commission is not about designing systems — it's about managing the programs, contracts, and technical risks that bring systems into the Air Force inventory. The faster you internalize that distinction, the faster you stop being frustrated by what the job actually requires.
The Honest MOS Read
The Developmental Engineer commission is one of the most cognitively demanding entry paths in the Air Force, and nothing about the first assignment tells you that clearly enough. You commission with an engineering degree, you survive the Acquisition 101 onboarding, and then you get handed a seat on a program office at AFLCMC at Wright-Patt, Hill, Eglin, or one of the other acquisition centers — and you discover that your thermodynamics coursework is approximately 5% of what this job demands.
At 2Lt and 1Lt, your primary role is learning the acquisition system from the inside. That means reading program documentation — Systems Engineering Plans, Test and Evaluation Master Plans, Contract Data Requirements Lists — until you understand what each document is trying to control and why. It means sitting in Source Selection Evaluation Board rooms and learning how technical evaluation criteria translate into contract award recommendations. It means supporting Preliminary Design Reviews, Critical Design Reviews, and Test Readiness Reviews as the junior technical contributor who handles the pre-brief data-pull, the action item tracking, and the read-ahead packages. The senior engineers are running the room. You are making sure the room is ready.
The engineering work itself is real, but it is filtered through the program office lens. You are not designing avionics. You are evaluating whether a contractor's avionics design meets the specification, identifying where the technical risk sits, and briefing your program manager on what the risk means for cost and schedule. That is an engineering job. It is also a management job, a contract job, and a communication job simultaneously.
AFMC is the command that owns most of your 2Lt/1Lt career. Specific center depends on platform: AFLCMC at Robins manages C-17/C-130 sustainment; Hill manages F-35 sustainment; Eglin manages munitions, electronic warfare, and F-35 DT&E; Hanscom manages C2/cyber systems. AFRL gives a completely different experience — research-focused, less program-office pressure, more technical depth. Know which track you landed on and understand what the mission of your specific center is before you show up.
The DAU requirement starts immediately. Defense Acquisition University courses — online and resident — are mandatory for career field qualification, and they run on top of your primary job, not instead of it. ACQ 101 is the entry course; you will be working toward Acquisition Professional Development Program (APDP) certifications throughout your 2Lt/1Lt window. Take them seriously. The material is actually useful once you stop treating it as checkbox training.
Career Arc
["Commission and complete Acquisition 101 / DAU foundational courses, report to first program office assignment.", "2Lt window: learn the program's technical baseline \u2014 SEP, TEMP, CDRLs, contractor data structure.", "Sit on at least one technical review milestone as a supporting engineer: PDR, CDR, or TRR.", "Begin APDP certification track (Engineering, Test and Evaluation, or Program Management \u2014 depends on assignment).", "1Lt window: begin leading a narrow technical element \u2014 subsystem risk tracking, T&E coordination, requirements traceability.", "Evaluate Captain's Career Course timing and AFIT application window for advanced degree.", "O-3 IPZ: ~3.5-4 years commissioned \u2014 first major promotion gate."]
Common Screwups
["Treating DAU courses as checkbox items and ignoring the material \u2014 the officers who learn acquisition policy at 2Lt aren't cramming at O-4 when they're managing a $2B program.", "Letting the contractor drive the technical narrative \u2014 at every level, your job is to independently evaluate contractor claims, not accept them.", "Confusing a good working relationship with a contractor with an appropriate one \u2014 OGE financial disclosure exists for a reason, and even the appearance of improper relationships ends careers in the acquisition community.", "Missing AFIT or DAU resident course opportunities because the program office is short-staffed \u2014 the program will always be short-staffed; take the education window when it appears.", "Showing up to technical reviews without reading the documentation \u2014 you will be exposed immediately, and the contractors and senior engineers will remember."]
A Day in the Life
[{"time": "0630-0730", "activity": "Arrive at program office. Review overnight contractor data system updates \u2014 any CDRLs due or recently submitted."}, {"time": "0730-0800", "activity": "Morning standup with the program team \u2014 schedule, action items from yesterday, today's priorities."}, {"time": "0800-0930", "activity": "Contractor technical data review \u2014 reading a recently submitted data product (test report, analysis, engineering change proposal) against the spec and contract requirements."}, {"time": "0930-1000", "activity": "DAU online course module \u2014 30 minutes of dedicated coursework; the program office won't protect this time for you, so you protect it yourself."}, {"time": "1000-1130", "activity": "Coordination meeting with the contractor's chief systems engineer on an open action from last week's PDR \u2014 tracking the closure criteria and documenting the government position in the action item register."}, {"time": "1130-1200", "activity": "Draft brief slides for the upcoming milestone decision briefing \u2014 pulling technical status from contractor data and translating into a risk summary the PM can use."}, {"time": "1200-1300", "activity": "Lunch. Sometimes at the desk. If you're smart, not at the desk."}, {"time": "1300-1430", "activity": "Requirements traceability review \u2014 checking that the new CDRLs submitted last week trace back to spec paragraphs in the CDRL list and flagging gaps for the lead systems engineer."}, {"time": "1430-1530", "activity": "OPR documentation \u2014 updating your personal impact record. If you closed an action today, write it down in a way you could put on a bullet in six months."}, {"time": "1530-1630", "activity": "Coordination with the Test and Evaluation division on upcoming test readiness criteria \u2014 the TRR is in eight weeks and the test-entry criteria package isn't fully drafted."}, {"time": "1630-1700", "activity": "Close out action items, check email, prepare tomorrow's reading. Program documentation doesn't read itself."}]
Weekly Cadence
Monday starts with the program-level standup — attendance is expected and preparation is required. The week's tempo varies by where the program sits in its schedule: if a milestone review is approaching (PDR, CDR, TRR), the entire week bends toward review preparation. Data packages, entrance criteria checklists, and briefing pre-reads consume the cycle. If the program is in steady-state execution, the week is driven by CDRL due dates and contractor performance tracking.
Mid-week is typically when contractor coordination happens — direct engineering exchanges, technical clarification meetings, and data product reviews. The 62E junior officer's job in these meetings is documentation: capturing what was agreed, what was deferred, and what the government's position is on open technical issues. The program office has no institutional memory beyond the action item register and the official contract file.
Friday afternoons are when OPR bullets either get written or get forgotten. The officers who document their work in near-real-time have dramatically stronger records than the ones who try to reconstruct a year of technical contributions from memory at mid-term OPR time. Keep a running impact log. It takes ten minutes a week.
Key Skills — How to Drill Each
[{"skill": "Read and analyze program technical documentation \u2014 SEPs, TEMPs, CDRLs, SOWs, and specs.", "how": "Start with the Systems Engineering Plan for your program and read it like a map \u2014 it tells you how the program is supposed to be managed technically and where the seams between government and contractor responsibility sit. Cross-reference every requirement in the spec against a test in the TEMP; if you can't find the test, you have found a verification gap the senior engineers need to know about."}, {"skill": "Support technical reviews (PDR, CDR, TRR) as a government evaluator.", "how": "Before any review, read the entrance criteria documented in the SEP \u2014 if the criteria aren't met, the review shouldn't proceed, and your job is to document that in writing before the meeting, not whisper it afterward. During the review, track action items in real time; the action item register you build becomes the program's technical accountability tool for the next 90 days."}, {"skill": "Translate contractor technical risk into plain language for the program manager.", "how": "Use the program's Risk Management Plan structure and the risk burning-down practice from DAU PM 101 \u2014 likelihood and consequence, not adjectives. A risk brief that says 'the propulsion integration risk is high probability, high consequence due to thermal margin shortfall on three test articles' is useful. A brief that says 'there are some thermal challenges' is not."}, {"skill": "Understand FAR/DFARS basics as they apply to technical evaluation.", "how": "You don't need to be a contracting officer, but you need to know enough to participate in Source Selection without creating protest exposure. Read FAR Part 15 (source selection) and the program's Source Selection Evaluation Plan before your first SSEB seat. Your job is to evaluate technical merit against documented criteria \u2014 not to rank companies or discuss price."}, {"skill": "Write technically clear and defensible staff packages, briefings, and evaluation reports.", "how": "At the program office, written products live forever \u2014 in the official contract file, in the congressional record, in a Government Accountability Office protest response. Write like someone is going to read it in court, because occasionally they will. Precision matters; 'meets requirements' with no elaboration fails legal scrutiny; 'meets requirements as demonstrated by [test reference]' does not."}]
Manuals & References — What Chapters Matter
[{"ref": "DAU ACQ 101 \u2014 Fundamentals of Systems Acquisition Management", "why": "Mandatory entry course for the acquisition workforce; covers the Defense Acquisition System framework, program phases, and decision authority structure. Take it before your first milestone review, not after."}, {"ref": "DODI 5000.02 \u2014 Operation of the Adaptive Acquisition Framework", "why": "The governing instruction for how defense programs are structured, managed, and overseen. Know the six acquisition pathways and which one your program uses \u2014 the oversight requirements differ substantially."}, {"ref": "MIL-HDBK-881 \u2014 Work Breakdown Structures for Defense Materiel Items", "why": "The WBS is how program cost, schedule, and technical progress are tracked. You will use WBS elements daily; understanding how they are constructed makes you faster in every reporting environment."}, {"ref": "AFMAN 63-144 \u2014 Air Force Acquisition Program Reporting and Status", "why": "Governs how AFLCMC programs report status through the chain \u2014 SAR, DAES, SFAR. The reporting architecture tells you what is visible to OSD, Congress, and the service secretary at any given milestone."}, {"ref": "IEEE 15288 \u2014 Systems and Software Engineering: System Life Cycle Processes", "why": "The technical process standard underneath most Air Force SEPs. When a contractor's Systems Engineering Plan references a systems analysis process, this is the document they're conforming to \u2014 knowing the standard lets you evaluate whether the conformance claim is real."}]
Standards — How to Hit Each
[{"standard": "APDP Engineering and Technical Management Level I certification within first 24 months.", "how": "The certification requires specific DAU courses and documented experience in acquisition engineering. Map your course requirements against your assignment start date and schedule aggressively \u2014 waiting until you're a Capt to start is a common mistake that creates pressure at O-4."}, {"standard": "OPR stratification in top third of the peer group by end of 1Lt window.", "how": "Acquisition community OPRs are scored on program contributions, not just execution of duties. Document your impact in numeric terms wherever possible \u2014 'identified 14 open requirements traceability gaps, closed 11 before CDR' is an OPR line; 'supported CDR preparation' is not."}, {"standard": "Complete at least one technical review milestone in a supporting-engineer or evaluator capacity.", "how": "Ask your supervisor to put you on the review team, even in a support role. The milestone review is where the program's technical discipline is tested; being in the room, reading the documentation, and tracking actions is the apprenticeship that classroom training cannot replicate."}]
Technical Mistakes — Concrete Consequences
[{"mistake": "Accepting contractor deliverable status reports at face value without independently verifying against contract data requirements.", "consequence": "The program enters a milestone review with a contractor's green-on-status report and a government technical evaluation that hasn't independently verified the claims \u2014 when the review board asks a technical detail question, the government team has no answer, and the program's credibility takes a hit that follows the PM for a year."}, {"mistake": "Writing technical evaluation documentation that references requirements without citing the specific specification paragraph.", "consequence": "A GAO protest counsel finds the evaluation record does not trace technical findings to the RFP \u2014 the protest is sustained, the award is re-evaluated, and the source selection timeline resets by 12-18 months. The evaluator's name is in the record."}, {"mistake": "Letting a critical open action from a technical review age past 90 days without a documented disposition.", "consequence": "The subsequent milestone review surfaces the undisposed action as a program risk; the milestone authority postpones the decision pending resolution, adding cost and schedule to a program that was on track."}, {"mistake": "Assuming the contractor's systems engineering process is compliant because the SEP says it is.", "consequence": "At CDR, the government discovers the contractor's interface control documentation is three revisions behind the current design \u2014 the review board finds CDR entrance criteria not met, the contractor requests additional schedule, and the cost-plus contract absorbs it at government expense."}]
Career Decisions at This Rank
[{"decision": "AFIT master's degree vs. civilian institution vs. stay in the program office.", "analysis": "AFIT gives you full pay and benefits while pursuing a technical or acquisition master's, and the curriculum is specifically designed for DoD application. The civilian institution route via fully-funded programs is also credible for top technical programs. The 'just stay in the program office' path is faster in the short term and materially weaker at O-5 and O-6 boards, where a graduate technical degree is near-universal among competitive peers. The right time to apply is during your 1Lt to O-3 transition window."}, {"decision": "AFLCMC program office vs. AFRL research assignment vs. operational unit engineering billet.", "analysis": "AFLCMC is the acquisition mainstream \u2014 program management, source selection, milestone oversight. AFRL is research-focused and technically deeper; officers who spend time at AFRL before returning to acquisition bring technology-maturation perspective that program offices value. Operational unit billets (wing engineering officer) give you operational credibility that acquisition-only careers lack, but they also slow your acquisition certification progression. Most strong 62E career paths have at least one operational-unit or joint tour before O-5."}, {"decision": "Stay in engineering track vs. move toward program management certification.", "analysis": "The 62E AFSC is an engineering designation, but the career progression toward O-5 and O-6 increasingly requires program management competency alongside technical depth. Officers who over-specialize in pure technical work without building PM experience are often passed over for PM jobs at O-5 that are where the visible command-equivalent positions sit. The dual-track approach \u2014 APDP Engineering Level II plus PM Level II certification \u2014 is the competitive standard."}]
How the Seat Varies by Unit Type
[{"unitType": "AFLCMC Program Office \u2014 major platform (F-35, B-21, C-17, F-22 sustainment)", "reality": "High-visibility, high-pressure, large contractor presence. The program has its own congressional interest and OSD oversight. Everything you write may end up in a SAR or a GAO protest record. The best development environment for acquisition fundamentals, but the pace is relentless and the learning curve is compressed."}, {"unitType": "AFLCMC Program Office \u2014 smaller program or pre-milestone technology program", "reality": "More latitude, more ownership, steeper individual accountability. A 2Lt who performs on a smaller program may brief the PM directly within months; the same officer in a large platform program may not brief above the division chief for years. Both develop different but complementary skills."}, {"unitType": "AFRL \u2014 Research Laboratory (Air Vehicles, Directed Energy, Materials, Munitions)", "reality": "Technical depth over process breadth. You are working earlier in the technology maturity curve, engaging with university researchers and small businesses in addition to major contractors. Less acquisition policy, more engineering judgment. The career risk is that AFRL experience can make you too technically specialized for the program management track \u2014 plan your return to acquisition programs deliberately."}, {"unitType": "Operational unit \u2014 Wing or Group Engineering Officer", "reality": "You are the engineering advisor to a flying wing, which means your job is to bridge the gap between the acquisition community's understanding of a system and the operators who fly it every day. Test and evaluation observations, field engineering support, and operational feedback to the program office are the core work. Operationally credible 62E officers at O-4 and above are a scarce resource; this tour pays compound interest."}, {"unitType": "Space Systems Command (SSC) \u2014 Space Acquisition", "reality": "Space acquisition is a separate tempo and a separate culture from air systems programs. You are likely working on satellite systems, launch vehicles, or ground-based space control capabilities. The acquisition frameworks are the same, but the technical domain, the contractor ecosystem (ULA, SpaceX, Northrop, L3Harris), and the operational context are completely different. The career value of a space acquisition tour is high and growing."}]
What Good Looks Like at This Rank
The strong 2Lt/1Lt 62E officer is the person in the program office who actually reads the documents. Not skims them — reads them. They know what the TEMP says the test sequence is, they know where the spec is ambiguous, and they know which contractor deliverable is three weeks late. The senior engineers trust them with pre-brief preparation because the data will be right.
They are also the officer who shows up to DAU resident courses having pre-read the case studies, and who comes back to the program office with something useful from the course, not just a completion certificate. Learning acquisition is a continuous job; the 2Lt who treats it as background noise is visible by O-3 when the policy questions start landing on their desk.
AFIT applications are not checked boxes — the strong junior 62E officer has a clear answer to 'why this program and what will you bring back' that the acquisition community finds credible. A master's degree in systems engineering or a technical discipline is a serious investment in a career that will eventually require you to evaluate programs worth more than most small countries' defense budgets.
Preview — The Next Rank
Captain is when the acquisition community starts evaluating you as a contributor rather than a student. The DAU coursework that was optional at 2Lt is mandatory by the time you pin O-3, and the APDP certifications are on your OPR. The program office expects you to run a piece of the program — a technical sub-discipline, a test series, a requirements review — without a senior engineer reviewing every output before it goes to the contractor.
The Captain's Career Course is a required professional military education gate, and at the 62E level it coincides with the window where AFIT assignment requests or civilian-institution graduate program applications are due. The officers who delay education past O-3 are not necessarily disadvantaged, but the ones who have a graduate degree in hand before their first senior assignment at O-4 are consistently the stronger candidates for the jobs that matter.
The other thing that changes at O-3 is source selection exposure. Captains run technical evaluation teams, chair working-level source selection coordination, and sign technical evaluation reports that become part of the permanent contract file. The legal and ethical standards are not jokes — the acquisition community has a long memory for officers whose source selection work created protest vulnerability, and a longer memory for the ones whose work held up under scrutiny.
FAQ
62E O1-O2 — Frequently Asked Questions
Q01What does a O1-O2 62E (Developmental Engineer) actually do?
The Developmental Engineer commission is one of the most cognitively demanding entry paths in the Air Force, and nothing about the first assignment tells you that clearly enough.
Q02What's the most important thing to know as a O1-O2 62E?
You are entering the acquisition workforce as a junior engineer, not a working engineer.
Q03What mistakes get O1-O2 62E soldiers fired or relieved?
["Treating DAU courses as checkbox items and ignoring the material \u2014 the officers who learn acquisition policy at 2Lt aren't cramming at O-4 when they're managing a $2B program.", "Letting the contractor drive the technical narrative \u2014 at every level, your job is to independently evaluate contractor claims, not accept them.", "Confusing a good working relationship with a contractor with an appropriate one \u2014 OGE financial disclosure exists for a reason,…
Q04What's next after O1-O2 for a 62E (Developmental Engineer) in the Air Force?
Captain is when the acquisition community starts evaluating you as a contributor rather than a student.
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