AMD MISSION COMMAND PROGRAM INTEGRATOR

Igniters operate in the world’s most demanding environment.

Igniters are self-motivated, mission-driven, and relentless in solving the Warfighters’ hardest problems.

We move fast, think differently, and execute with precision to tackle high-stakes challenges across AI/ML, space and missile defense intelligence, EMSO, advanced analytics, and programmatic domains.

As an employee-owned SDVOSB headquartered in Huntsville, AL, our team delivers mission-critical impact for the Army, Air Force, Space Force, MDA, NASA, DIA, and FBI.

Ignite exists to outpace the threat and deliver results that matter in the moments that count.

Ignite is currently seeking a AMD Mission Command Program Integrator to join our team supporting the Portfolio Acquisition Executive (PAE) Fires, Integrated Fires Mission Command (IFMC) Project Office, Air and Missile Defense Mission Command Product Office (AMD MC PdO) to assist and coordinate Army Air and Missile Defense Command and Control System software product requirements. The requirements focus on the Army Integrated Air Missile Defense (AIAMD) system portfolio to include the Integrated Battle Command System (IBCS) and Patriot, as well as integration of Sensor and Weapon Platforms such as Sentinel, Lower Tier Air and Missile Defense Sensor (LTAMDS), and Indirect Fire Protection Capability (IFPC). This position is located at Redstone Arsenal, Alabama.

include, but are not limited to:

• Working with Subject Matter Experts (SMEs) to better understand the scope of an Initiative/Capability.
• Developing concepts utilizing a Model-Based System Engineering (MBSE) approach in an Agile SW workflow and environment.
• Assembling Artifacts and other information into Solutions Initiative Documents (SIDs) as well as Solutions Engineering Documents (SEDs) and refining Jira tickets as necessary.
• Modeling Capability behavior (SV-1, SV-4) using the MagicDraw MBSE tool.
• Creating/modifying existing behavior to include Functions and Data Exchanges/Signals.
• Defining Acceptance Criteria for a Capability and tracing the Acceptance Criteria to behavior in the model.
• Determining the current Capabilities Description Document (CDD) and System Spec requirements being satisfied by the capability and establishing those links in the model.