Engineering Program Manager II

We need to output HTML fragment with sections: About the role? The posting includes intro "Join Axon and be a Force for Good..." then description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse content. First, intro: "Join Axon and be a Force for Good..." That's about the role? Could be "About the role". We'll put that as

About the role

then

with that paragraph. Then "Your Impact:" then description about Dedrone etc. That seems like responsibilities? Actually "Your Impact:" is maybe about the role. But we already used About the role. Could treat "Your Impact:" as part of About the role or maybe separate? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have sections: - About the role: includes mission statement, description of Axon, Dedrone, role overview. - Responsibilities: "What You'll Do:" bullet list. - Requirements/Qualifications/Skills: "What You Bring:" includes education, experience, technical fluency, etc. Could split into Requirements (education, experience), Qualifications (certifications), Skills (technical fluency, communication). But we can combine if content is substantive. The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (combining education, experience, certifications), Skills (technical & soft skills), Benefits, Pay, Schedule. We need to check if Pay and Schedule are present: Yes, there is "Base Pay Range: $115,500 USD - $184,800 USD". Also "Work Location" includes hybrid schedule: Tues-Fri in office, remote Mondays. So we have Pay and Schedule sections. Benefits: there is a "Benefits that Benefit You" list. Thus we will include sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, legal, etc. At end there is lots of EEO, privacy, phishing alert. Remove those. Also remove duplicated lines. Now craft HTML. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics. Let's extract content. About the role: combine first paragraphs up to "Your Impact:"? Actually "Your Impact:" is a heading but we can incorporate into About the role. Text: "Join Axon and be a Force for Good.At Axon, we’re on a mission to Protect Life. We’re explorers, pursuing society’s most critical safety and justice issues with our ecosystem of devices and cloud software. Like our products, we work better together. We connect with candor and care, seeking out diverse perspectives from our customers, communities and each other. Life at Axon is fast-paced, challenging and meaningful. Here, you’ll take ownership and drive real change. Constantly grow as you work hard for a mission that matters at a company where you matter. Your Impact:Dedrone stands out as the global leader in airspace defense technology and counter-UAS solutions. Engineering at Dedrone is tasked with delivering innovative solutions and products to maintain our position on the cutting edge of innovation.Engineering Program Managers, Solutions at Dedrone own the delivery of next generation cUAS engineering solutions from requirements definition through deployment, driving programs that are highly visible to even the most senior executives. This role sits at the intersection of product, internal engineering, and external development partners: taking requirements from product management, aligning them with internal technical teams, and directing outside development partners (ODM/CM and technical solution providers) to design, develop, and deliver the resulting engineering solutions.This role emphasizes vendor and program management, requirements translation, partner alignment, and cross-functional execution across the full solutions development lifecycle. The ideal candidate combines strong hardware program management fundamentals with hands-on experience managing external development partners, ensuring that vendor-delivered work meets technical requirements, schedule, and quality bars." We need to keep that as prose. Could split into paragraphs but it's okay as one

. Now Responsibilities: "What You'll Do:" then bullet list. Let's extract bullet points: - Translate product requirements from Product Management into clear technical scopes, then align internal Systems, Electrical, and Mechanical Engineering teams and external development partners around a shared execution plan. - Own the master schedule for solutions programs delivered in partnership with outside development partners (ODM/CM and technical solution providers), driving milestones across all program phases (EVT, DVT, PVT). - Serve as the primary program interface to external development partners — managing scope, technical reviews, and deliverable acceptance to ensure vendor output meets Dedrone's requirements. - Identify, track, and proactively mitigate program risks from partner capability gaps and long-lead component constraints to supplier qualification gaps before they become schedule or cost impacts. - Own program budget management including NRE, tooling, and build costs, maintaining alignment between vendor commitments and business objectives. - Collaborate regularly with both domestic and international stakeholders, including ODM/CM and other development partners, to ensure manufacturing readiness and on-time production ramp. - Translate complex technical status, vendor tradeoffs, and program risk into clear, actionable communication for executive and cross-functional audiences. - Work autonomously and collaboratively in an empowering and fast-paced environment, driving clarity in ambiguous situations. - Hone your program and vendor management expertise in a dynamic learning environment focused on personal and professional development. We'll put each as

inside

. Now Requirements: from "What You Bring:" we need to separate education/experience/certifications maybe. Text after "What You Bring:": "Bachelor's or Master's degree in Mechanical Engineering, Electrical Engineering, Systems Engineering, or a related technical field; MBA or MS in Engineering Management a plus.PMP certification a plus.Proven experience managing hardware or technical solutions programs delivered through external development partners, preferably in industries involving advanced electromechanical systems.Strong technical fluency across mechanical, electrical, and firmware disciplines sufficient to translate product requirements, evaluate vendor tradeoffs, and engage meaningfully with internal engineering teams.Demonstrated experience managing ODM/CM or outside development partner relationships, including scoping, technical reviews, deliverable acceptance, and coordinating manufacturing readiness activities such as yield, regulatory certification, and factory acceptance.Familiarity with hardware build phases (EVT/DVT/PVT), design freeze processes, and the tradeoffs inherent in transitioning from development to production.Proficiency with program management tools for scheduling, risk tracking, and cross-functional coordination.Knowledge of regulatory and compliance requirements (e.g., FCC, CE, UL, MIL-STD) and experience driving vendor-delivered products through certification processes.Strong analytical and problem-solving abilities to identify critical path risks — including those originating with external partners — and drive resolution across competing organizational priorities.Excellent communication skills to effectively align product managers, internal engineering teams, and external development partners, surface tradeoffs to leadership, and present program status with clarity and confidence.Ability to thrive in a fast-paced, dynamic environment with high levels of ambiguity and evolving requirements." We could split into Requirements (education, experience, certifications) and Skills (technical fluency, communication, problem-solving, etc.). But we have also a Skills section heading allowed. Let's decide: Requirements: education, experience, certifications. Skills: technical fluency, communication, problem-solving, ability to thrive, etc. Thus: Requirements (

Requirements

)
with: - Bachelor's or Master's degree in Mechanical Engineering, Electrical Engineering, Systems Engineering, or a related technical field; MBA or MS in Engineering Management a plus. - PMP certification a plus. - Proven experience managing hardware or technical solutions programs delivered through external development partners, preferably in industries involving advanced electromechanical systems. Now Skills (

Skills

)
with: - Strong technical fluency across mechanical, electrical, and firmware disciplines sufficient to translate product requirements, evaluate vendor tradeoffs, and engage meaningfully with internal engineering teams. - Demonstrated experience managing ODM/CM or outside development partner relationships, including scoping, technical reviews, deliverable acceptance, and coordinating manufacturing readiness activities such as yield, regulatory certification, and factory acceptance. - Familiarity with hardware build phases (EVT/DVT/PVT), design freeze processes, and the tradeoffs inherent in transitioning from development to production. - Proficiency with program management tools for scheduling, risk tracking, and cross-functional coordination. - Knowledge of regulatory and compliance requirements (e.g., FCC, CE, UL, MIL-STD) and experience driving vendor-delivered products through certification processes. - Strong analytical and problem-solving abilities to identify critical path risks — including those originating with external partners — and drive resolution across competing organizational priorities. - Excellent communication skills to effectively align product managers, internal engineering teams, and external development partners, surface tradeoffs to leadership, and present program status with clarity and confidence. - Ability to thrive in a fast-paced, dynamic environment with high levels of ambiguity and evolving requirements. Now Benefits: from "Benefits that Benefit You" list. List: - Competitive salary and 401k with employer match - Discretionary paid time off - Paid parental leave for all - Medical, Dental, Vision plans - Fitness Programs - Emotional & Mental Wellness support - Learning & Development programs - And yes, we have snacks in our offices Also note: "Benefits listed herein may vary depending on the nature of your employment and the location where you work". That's a qualifier but we can keep as part of benefits description maybe as a note. But instruction: do not include filler like "may vary". However it's substantive? It's a note about variability. Might be considered boilerplate? It's not a benefit itself. Could include as a

after list. But we should avoid filler. Might be okay to include as a short note. However the instruction: "Prefer a few substantive sections over many thin ones." Including a note about variability is not a benefit but a qualifier. Might be considered boilerplate? I'd include it as a

after the list, but it's not a heading. It's okay. Now Pay: Base Pay Range: $115,500 USD - $184,800 USD. Also note about total compensation: base pay, bonus, stock awards. That's substantive. We'll include as

. Now Schedule: Work location and hybrid schedule: "This role is based out of our Sterling, VA office and follows a hybrid schedule. We rely on in-person collaboration and ask that team members work onsite Tuesdays through Fridays, with the flexibility to work remotely on Mondays, unless there is an approved workplace accommodation. We believe that connection fuels innovation, and our in-office culture is designed to foster meaningful teamwork, mentorship, and shared success." We'll put as

. Now ensure we removed boilerplate: EEO, legal, privacy, phishing alert, etc. Also remove "Don’t meet every single requirement? That's ok..." etc. That's motivational but maybe considered boilerplate? It's not a standard boilerplate but it's encouraging to apply. Might be considered part of the posting but not a section. Could be included in About the role? It's after the qualifications. It's a note encouraging applicants. Could be included as a

under About the role or separate? The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those. It's a motivational note. I'd keep it as part of About the role maybe as a separate paragraph. But we already used About the role for the initial description. Could add another paragraph after that about encouraging to apply. Let's incorporate: after the initial About the role paragraph, add a

with that note. Now ensure we don't repeat any content. Now produce HTML fragment. Structure: