Developmental Engineer

You're a newly commissioned Developmental Engineer embedded in an acquisition program office or AFRL lab, leaning hard on your technical degree while learning the machinery of defense acquisition. The Air Force paid for your education precisely so you'd know what you're looking at when a contractor hands you a system specification.

Your days alternate between technical deep-dives and acquisition paperwork, often simultaneously. In a program office you're a member of an Integrated Product Team (IPT), reviewing contractor deliverables, attending design reviews, and flagging technical risk you can actually justify with math. In AFRL you're supporting a research project, writing test plans, analyzing data, and learning what "transition to program of record" actually requires. You spend considerable time working through DAU courses — not optional, they're career checkboxes — while senior engineers and program managers teach you the gap between what specifications say and what contractors actually build. You'll write technical evaluations for source selections earlier than you expect, and the weight of that responsibility is real.

• 01Systems engineering fundamentals, technical documentation review, risk identification, DAU acquisition coursework, IPT participation, requirements traceability

• —AFI 63-101/20-101 (Integrated Life Cycle Management), DoDI 5000.02 (Operation of the Adaptive Acquisition Framework), DAU Acquisition Fundamentals (ACQ 101/201), Systems Engineering Guidebook (SEG)

• —DAU ACQ 101 (Fundamentals of Systems Acquisition Management) required early; AFIT short courses on systems engineering; Squadron Officer School (SOS) completion by O3 window; professional engineering licensure encouraged

• —Deferring entirely to the contractor on technical questions because you feel junior — you were hired to push back with engineering rigor, not rubber-stamp deliverables. Contractors are paid to deliver; you're paid to verify.

A 62E O2 at AFLCMC flags an inconsistency between a contractor's CDRl and the system specification during a Critical Design Review, traces it back to an ambiguous requirement from the original RFP, and brings a draft requirements change proposal to the IPT lead with three options and a cost-risk tradeoff — before the program manager has to ask. That's the job at this tier: find the technical problem before it becomes a contract modification.

You're a working engineer with real program experience, now trusted to lead a technical work stream, run an IPT, or represent the government on contractor technical performance. The DAU credentials are accumulating and you've seen at least one program stumble — which is the education that classroom courses can't replicate.

At O3 you own something: a subsystem, a test phase, a source selection technical evaluation team, or an AFRL project. You're no longer just supporting — you're accountable. In an AFLCMC product office you may be the lead systems engineer for a specific capability increment, coordinating between the contractor, the test community (typically AFOTEC or a DT&E org), and the requirements owner (usually an ACC or AFSPC functional). AFIT is realistic at this point — many 62Es pursue a fully-funded master's in systems engineering, computer science, or a related field, and it's the expected path for competitive promotion. You're also mentoring O1s and O2s, which forces you to articulate what you actually know. Staff assignments begin appearing: AFMC/A5, SAF/AQ, or an OSD AT&L billet will be on your developmental team's radar.

• 01IPT leadership, technical risk management, test and evaluation oversight, source selection technical evaluation, requirements management, contractor performance assessment, AFIT preparation

• —AFI 63-101/20-101, AFPAM 63-128 (Guide to Acquisition and Sustainment Life Cycle Management), DAU ACQ 202 (Intermediate Systems Acquisition), SEG Chapter 4 (Technical Planning)

• —DAU ACQ 202 completion; AFIT MS degree (common at this tier); Air Command and Staff College (ACSC) by correspondence or in-residence if selected; PE licensure pursuit encouraged for credibility with contractor engineering teams

• —Letting schedule pressure override technical judgment during test planning — accepting a truncated test matrix because the PM is behind schedule, then watching a deficiency surface post-fielding that your test would have caught. The program manager's schedule problem becomes your name on the test plan.

An O3 leading the T&E oversight for a major avionics upgrade identifies that the contractor's developmental test plan doesn't adequately stress the system at operational temperature extremes. She rewrites the government's test objectives, coordinates with the operational test agency six months before their test window, and the resulting DT catches a failure mode that would have required a field retrofit — saving an estimated $40M in post-fielding corrections. The PM is annoyed she slowed things down. The program is grateful eighteen months later.

You're a field-grade officer who's been through at least one full acquisition phase, has the AFIT degree or equivalent, and is now operating at the program level rather than the subsystem level. Your technical credibility is established; now the question is whether you can lead a larger organization and navigate the interagency acquisition bureaucracy.

O4 is where 62Es split between the deep technical track and the program management track. On the technical side you might be a chief systems engineer on a major program, setting technical standards for the entire engineering team and serving as the government's primary technical authority in contractor negotiations. On the PM track you're running an IPT with significant budget responsibility, acting as an assistant program manager, or holding a staff position at AFMC/A5 or SAF/AQ where you're shaping acquisition policy rather than executing it. AFIT PhD candidates exist at this tier, though they're competing hard for slots. Joint assignments (OSD, combatant command staff) become relevant to promotion competitiveness — a 62E who's only ever worked acquisition programs looks narrow at the major board. You're likely supervising a mixed team of officers, civilians, and contractors, and the ability to lead that constellation is as important as any technical credential.

• 01Program-level technical leadership, acquisition strategy development, contractor performance management, multi-directorate staff coordination, budget defense, joint staff navigation, senior mentorship

• —DAU PMT 352 (Program Manager's Course) or equivalent; AFPAM 63-128; DoDI 5000.85 (Major Capability Acquisition); DoD Systems Engineering Plan (SEP) guidance; JCIDS Manual

• —DAU PMT 352 if tracking toward PM; ACSC completion (in-residence selection is competitive and career-enhancing); Level III DAWIA certification in Systems Engineering or Program Management; joint duty assignment credit

• —Becoming a PowerPoint program manager who can no longer engage technically with the contractor — losing the ability to read a system spec and know when something's wrong. At O4 you're leading engineers; if you can't keep up technically, they'll route around you.

An O4 program chief engineer on a next-generation sensor program identifies during a systems requirements review that the contractor's proposed architecture creates a single-point failure mode that wasn't in the original requirements. Rather than issuing a corrective action that extends schedule six months, he negotiates a risk-reduction prototype effort with a fixed cost cap and a six-week demonstration — the result folds into the baseline design with zero schedule impact. That's field-grade engineering leadership: solve the problem before it becomes a contract action.

You're a senior field-grade officer who's proven you can run a major program technical baseline or lead a significant staff directorate. The promotion board is evaluating whether you have the breadth — joint experience, command, cross-functional credibility — to be a colonel, not just whether you can engineer.

O5 62Es are typically running division-level operations: a product division chief at AFLCMC (responsible for a portfolio of programs, not just one), a squadron commander in a contracting or test wing (some 62Es command), an OSD or joint staff assignment, or a senior position at an AFRL technology directorate. The work is less about individual technical contributions and more about establishing the technical direction for an organization and making sure the people under you have what they need. You're also a key player in source selections at the major system level — the technical evaluation authority whose sign-off carries real weight in contract award decisions. Congressional budget justifications, milestone decision authority briefings, and JROC engagements are in your calendar. You're accountable for engineer development across your organization, which means PRFs, developmental team conversations, and being honest with junior officers about their trajectory.

• 01Organizational technical leadership, portfolio management, source selection authority, senior stakeholder engagement, Congressional budget process, engineer workforce development, major milestone decision support

• —DoDI 5000.02, AFI 63-101/20-101, Under Secretary of Defense (R&E) directives, SAF/AQ policy memoranda, NDAA provisions affecting acquisition authority

• —War College equivalent (SSS, ICAF, or equivalent credit) for promotion competitiveness; senior DAWIA Level III certifications maintained; joint duty assignment completed or in progress; command tour if available in specialty

• —Allowing your organization's technical rigor to erode under schedule and cost pressure from above — accepting contractor self-assessments instead of independent technical verification because it's faster. Program failures at Milestone C trace back to decisions made at this level.

An O5 division chief at AFLCMC inherits a portfolio of three programs, two of which are in Nunn-McCurdy breach territory. Rather than defending the programs to the milestone decision authority with optimistic contractor projections, she commissions an independent technical assessment, presents the MDA with an honest options analysis including a restructure recommendation, and takes the programmatic hit that saves the Air Force from a $2B sunk-cost spiral. She makes O6 despite the "failed" programs because the MDA saw exactly what kind of officer she is.

You're a colonel — selected from a thin cut of O5s — and you're running something significant: a major program office, an AFRL directorate, an AFLCMC product center division, or a senior staff position that shapes Air Force acquisition policy. Your job is institutional leadership as much as technical oversight.

O6 62Es hold the most consequential engineering leadership positions in the Air Force acquisition enterprise. As a program director at AFLCMC you're the senior military officer responsible for a major defense acquisition program — accountable to the PEO, to Congress (through budget oversight), to the operational community (who need the system to work), and to your workforce (who need your leadership to do their jobs). At AFRL you might direct a technology directorate with hundreds of scientists, engineers, and contractors developing the capabilities that will become programs of record in ten years. Staff colonels at SAF/AQ or OSD shape the acquisition regulations and policies that every program office executes. The rhythm is: milestone briefings, Congressional budget justifications, SECAF/CSAF program reviews, industry days, and workforce development — interspersed with technical deep-dives when something's actually broken. Your personal technical engagement is selective and high-leverage; you can't be in the weeds of every system, so you maintain enough fluency to know when your team is giving you the real picture versus the polished one.

• 01Major program direction, PEO/SECAF-level engagement, Congressional liaison, enterprise technical strategy, senior industry relationship management, acquisition workforce leadership, cross-MAJCOM coordination

• —USD(R&E) directives, SAF/AQ policy framework, NDAA acquisition authorities, DoD 5000-series policy suite, GAO and DOT&E oversight report management

• —Senior Developmental Education (War College) completed; senior acquisition position requirements (SAP certification per DoDI 5000.66 for program executive officers and above); continued engagement with DAU senior acquisition leadership programs

• —Surrounding yourself with optimists who tell you what you want to hear about program health — losing touch with the independent technical assessors, the test community's candid read, and the honest voice of your mid-grade engineers who know where the bodies are buried.

An O6 program director takes over a troubled hypersonic weapons program eighteen months before a major operational test. She immediately commissions an independent technical review, restructures the test matrix based on the results, renegotiates the contractor's incentive fee structure to weight technical performance over schedule, and personally briefs the SECAF with a recovery plan that includes a twelve-month delay and a $300M cost increase. The test succeeds. The program reaches IOC. Her candor at the SECAF briefing — the part where most colonels soften the numbers — is what earns her the star consideration.

You're a general officer in the acquisition and technology enterprise — a rare breed of technically credentialed flag officer who shapes what the Air Force and Space Force will be able to do a decade from now. The technical identity that got you here is still relevant; the strategic leadership demands are the whole job.

General officer 62Es hold positions like Program Executive Officer (PEO) for major capability portfolios, Deputy Assistant Secretary of the Air Force for acquisition roles (political-military interface), Director of AFRL, Commander of AFLCMC or SSC, and ultimately AFMC commander. At this level you're shaping the acquisition enterprise itself: testifying to Congress, negotiating with OSD on budget and authority questions, setting strategy for the Air Force's science and technology investment, and deciding which programs live and which get restructured or killed. The technical work is strategic — you're not reviewing individual CDRls, you're deciding what the Air Force's acquisition enterprise is capable of and what it needs to become. You're also a key voice in joint and interagency processes: JROC, CAPE, OMB, and the Congressional defense committees are your stakeholders. The 62E background gives you credibility that pure operational generals don't have in these forums — use it.

• 01Enterprise acquisition strategy, PEO portfolio governance, Congressional engagement, interagency coordination, defense industrial base management, PPBE senior leadership, science and technology investment strategy, joint acquisition policy

• —Title 10 USC acquisition authorities, NDAA provisions (annual), USD(R&E) and USD(A&S) policy framework, DoD 5000-series, OMB A-11 (budget process), GAO technology readiness assessment standards

• —Senior acquisition position (SAP) certification required for PEO and above; all PME completed; interagency and joint duty experience essential; Senate confirmation required for positions designated by statute

• —Allowing the acquisition enterprise under your command to optimize for program survival over honest reporting — creating a culture where red programs get green-washed before they reach you, and you lose the institutional capacity for candor that makes the oversight system function.

An AFLCMC commander redesigns the command's program health reporting system after a series of programs reached Nunn-McCurdy breach without adequate warning. The new system requires independent technical assessors to brief program status directly to the commander's council — bypassing program office filters — and creates a formal "early warning" process that flags technical risk indicators before they become budget crises. Congress notices. The next NDAA includes a provision directing DoD to study the model for enterprise adoption. That's what flag-officer-level acquisition leadership looks like: changing the system, not just running it.