<div class="content-intro">Headquartered in Silicon Valley, California, Archer is a leader in the next-gen aerospace sector building an end-to-end advanced air mobility platform that delivers air taxis, unmanned aircraft systems (“UAS”), aviation-related physical artificial intelligence (“AI”) solutions, and other technologies to customers worldwide across the commercial aerospace and defense sectors. Our sights are set high and our problems are hard, and we believe that diversity in the workplace is what makes us smarter, drives better insights, and will ultimately lift us all to success. We are dedicated to cultivating an equitable and inclusive environment that embraces our differences, and supports and celebrates all of our team members.</div> What You’ll Do: Archer is seeking a Software Engineering Program Manager to drive aircraft-level software integration for the Midnight program. Working alongside the Software Integration (SWINT) team, you will own the integration schedule that combines Powertrain Software and Vehicle Management Software deliverables into a single aircraft software release, and keep the two domains sequenced against one another so that neither becomes the other’s surprise. This is a hands-on, execution-focused program management role at the seam between engineering domains: you will spend your time tracking cross-domain dependencies, coordinating integration test logistics, and surfacing interface and timing risks before they reach a release gate. You will partner closely with the Senior EPMs who own each software domain, the Integrated Test Group (ITG), Flight Test, Systems Engineering, and Certification. The role is scoped with a deliberate growth path toward release governance ownership and, ultimately, domain ownership. <ul> <li>Partner with SWINT to own the aircraft-level software integration schedule, combining Powertrain SW and Vehicle Management SW deliverables into a single Aircraft Integrated Release (AIR)</li> <li>Maintain the integrated view across engineering, blue label, and red label milestones; keep domain subschedules aligned to the aircraft software schedule and the program IMS</li> <li>Decompose release scope into trackable tasks with named owners and due dates; keep Jira as the source of truth and treat sheets and slides as renderings</li> <li>Track scope maturity, rework, and closure velocity to give an evidence-based read on release readiness rather than a status-by-assertion one</li> <li>Map and track dependencies and sequencing between Powertrain SW and Vehicle Management SW, including shared interfaces, data flows, and delivery order</li> <li>Flag early and explicitly when a slip in one domain threatens the other’s integration readiness, with the downstream impact quantified in schedule terms</li> <li>Drive dependency resolution to closure through disciplined follow-up; escalate jointly with both domain EPMs only after peer-level alignment has been attempted</li> <li>Keep change impact analysis (CIA) and problem-report scope current as release content shifts, so integration planning does not drift from the actual build</li> <li>Support all domain SW EPMs by consolidating domain release status into a single, unified aircraft-level view for program review</li> <li>Prepare and present integration status for software CCB, program reviews, readiness checkpoints, and executive forums; own agendas, minutes, and action tracking</li> <li>Translate domain-level technical detail into clear, decision-ready status and risk narratives for program leadership</li> <li>Maintain release dashboards and supporting pages, driving named owners to keep their sections c

Software Integration EPM

Job Description