Lead C-UAS Systems Integration & Operational Analysis Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes Position Overview, Key Responsibilities, Required Qualifications, Preferred Qualifications, Technical Skills of Interest, Candidate Profile, Clearance Level, Salary Range, Benefits. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map sections accordingly. We must not repeat job title as heading. No Job ID etc. Remove boilerplate (cookie/navigation/legal/EEO etc). Preserve all substantive info. We need sections only when posting has real specific content. So we can include sections: About the role (Position Overview), Responsibilities (Key Responsibilities), Requirements (Required Qualifications), Qualifications (Preferred Qualifications maybe combine?), Skills (Technical Skills of Interest), Benefits, Pay (Salary Range). Schedule maybe not present (no schedule details). So omit Schedule. We must use

• for any list of duties/requirements/benefits. So for responsibilities list, qualifications list, skills list, benefits list. We need to preserve all substantive info; do not invent or summarize away detail. So we need to include details like location, work arrangement, clearance, citizenship etc. Those could be placed in a short

  maybe under About the role or separate meta? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include location, work arrangement, clearance, citizenship in a paragraph after the heading maybe. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

  About the role

  Location: Huntsville, Alabama. Work arrangement: Primarily on-site, with travel to test ranges and operational locations. Clearance: Active Secret security clearance preferred; ability to obtain and maintain a clearance required. Citizenship: U.S. citizenship required.

  Position Overview: We are seeking an experienced C-UAS Systems Integration and Operational Analysis Engineer to support the development, integration, testing, and fielding of a next-generation C-UAS missile system. This position will lead integration of the missile into command-and-control systems and the broader C-UAS architecture. The engineer will support system testing, evaluate operational performance, and translate test and theater data into actionable recommendations for system improvement and warfighter employment. The successful candidate will work across interceptor, launcher, command-and-control, radar, sensor, and communications interfaces to ensure the weapon system performs effectively as part of an end-to-end kill chain. This role requires a combination of systems engineering, quantitative analysis, test support, operational analysis, and customer-facing technical communication.

  Then Responsibilities:

  Responsibilities

  • Lead integration of the Next Generation C-UAS Missile into command-and-control and battle-management systems.
  • Support end-to-end integration across the interceptor, launcher, canister, command-and-control system, radar, sensor, communications network, and external system interfaces.
  • Develop and maintain system-integration plans, interface requirements, verification methods, and test objectives.
  • Coordinate integration activities among missile developers, launcher teams, command-and-control providers, sensor developers, government customers, test organizations, and operational users.
  • Support laboratory, ground, system-integration, flight, and live-fire testing at government and contractor facilities.
  • Provide on-site engineering and analytical support at test ranges such as Yuma Proving Ground, White Sands Missile Range, Eglin Air Force Base, and other locations.
  • Monitor test execution, evaluate system performance, identify anomalies, and provide timely recommendations during active test events.
  • Analyze system performance across the complete engagement sequence, from target detection and tracking through weapon assignment, launch, interceptor flyout, and target defeat.
  • Evaluate command-and-control behavior, engagement logic, system timing, sensor-to-shooter connectivity, and end-to-end kill-chain performance.
  • Support development of test plans, test cards, data-management plans, test-readiness reviews, technical reports, and final test findings.
  • Formulate recommendations for improvements to missile performance, system integration, operator interfaces, software behavior, and system employment.
  • Conduct quantitative analysis to assess system effectiveness against representative UAS threats and operational scenarios.
  • Analyze operational and theater data to validate system effectiveness in real-world environments.
  • Identify performance gaps, integration deficiencies, environmental limitations, and opportunities to improve the effectiveness of fielded C-UAS capabilities.
  • Develop forensic reports following operational events, reconstructing the engagement timeline and evaluating how the system and operators performed.
  • Provide clear narrative responses to operational units describing findings, recommended corrective actions, and potential improvements to tactics, techniques, and procedures.
  • Support site-survey and emplacement analysis for radars, launchers, sensors, and command-and-control systems.
  • Recommend system placement and employment concepts based on terrain, threat approaches, sensor coverage, interceptor performance, infrastructure, and operational constraints.
  • Develop analytical tools, models, visualizations, and decision-support products using Python, MATLAB, Excel, Minitab, or similar tools.
  • Apply optimization, operations-research, and process-improvement methods to system performance, test planning, production readiness, and fielding challenges.
  • Brief technical findings, program risks, and recommended actions to engineering teams, program leadership, government customers, and operational users.
  • Mentor junior engineers and help establish repeatable processes for integration, testing, operational analysis, and technical reporting.
  Then Requirements (Required Qualifications):

  Requirements

  • Bachelor's degree in aerospace engineering, systems engineering, operations research, applied mathematics, industrial engineering, mechanical engineering, electrical engineering, or a closely related technical field.
  • Minimum of 8 years of relevant experience in C-UAS, missile defense, air defense, weapons integration, operational analysis, test and evaluation, or another complex defense-system environment.
  • Demonstrated experience integrating interceptors or other effectors into command-and-control systems.
  • Experience supporting engineering, integration, flight, or live-fire test events at Department of Defense test ranges.
  • Experience analyzing the performance of complex systems using test, operational, or simulation data.
  • Understanding of end-to-end C-UAS or air-defense engagement processes.
  • Experience developing technical reports and evidence-based recommendations for system-performance improvements.
  • Ability to evaluate complex technical and operational problems from a system-of-systems perspective.
  • Strong quantitative, analytical, and problem-solving skills.
  • Proficiency with Microsoft Excel, PowerPoint, Word, and Visio.
  • Experience with Python, MATLAB, Minitab, or comparable analytical tools.
  • Strong written and verbal communication skills, including the ability to brief technical findings to program leaders, government customers, and operational users.
  • Ability to work effectively with multidisciplinary government and industry teams.
  • Willingness to travel regularly to test ranges, integration facilities, suppliers, and operational locations.
  • U.S. citizenship and ability to obtain and maintain the required security clearance.
  Then Qualifications (Preferred Qualifications):

  Qualifications

  • Master's degree in operations research, operations management, systems engineering, applied mathematics, engineering management, or a related field.
  • Direct experience with C-UAS interceptors, launchers, command-and-control systems, and sensor architectures.
  • Experience supporting the Joint Analysis Team or a comparable government systems-engineering and operational-analysis organization.
  • Experience integrating missile or interceptor systems with FAAD C2, IBCS-M, or comparable battle-management systems.
  • Experience supporting tests at Yuma Proving Ground, White Sands Missile Range, Eglin Air Force Base, or similar Department of Defense ranges.
  • Experience conducting operational or theater analysis of deployed C-UAS systems.
  • Experience preparing forensic analyses following real-world UAS engagements.
  • Knowledge of radar coverage, sensor placement, interceptor envelopes, site-emplacement planning, and layered-defense design.
  • Experience developing or improving warfighter tactics, techniques, and procedures.
  • Familiarity with test and evaluation processes, requirements verification, test-readiness reviews, deficiency reporting, and corrective-action tracking.
  • Experience with optimization, operations research, statistical analysis, or simulation.
  • Experience with manufacturing-capacity analysis, production planning, material flow, manpower planning, or process improvement.
  • Familiarity with Lean, value-stream mapping, industrial engineering, or continuous-improvement methods.
  • Experience leading multidisciplinary technical teams or major system-integration activities.
  • Active Secret or higher-level U.S. security clearance.
  Then Skills (Technical Skills of Interest):

  Skills

  • C-UAS system-of-systems integration
  • Missile and interceptor integration
  • Command-and-control integration
  • Launcher and canister integration
  • Sensor-to-shooter connectivity
  • End-to-end kill-chain analysis
  • Flight-test and live-fire test support
  • Operational and theater analysis
  • Forensic event reconstruction
  • System-effectiveness assessment
  • Site-emplacement and coverage analysis
  • Requirements verification
  • Test planning and technical reporting
  • Python and MATLAB
  • Excel, Visio and Minitab
  • Optimization and operations research
  • Statistical and quantitative analysis
  • Process and production-capacity improvement
  Then Benefits:

  Benefits

  • Medical, dental, vision
  • 401K with company matching
  • 9/80 work schedule
  • Paid holiday shutdown
  Then Pay:

  Pay

  The Salary Range For This Role Is $111,500 - $170,000

  We should also include Candidate Profile? Could be part of About the role or separate section maybe "Overview". But we have limited headings list; we could add a section "Profile" but not in list. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can add other headings if needed, but better to stick to those. Candidate Profile could be merged into About the role or Responsibilities. We'll incorporate into About the role paragraph. We must not include duplicated lines. Ensure we didn't repeat location etc elsewhere. Check for any boilerplate: "Principals only need apply. NO agencies please." That's application instruction; we should remove. Also "About AV" section is boilerplate; remove. Also "ITAR Requirement" maybe considered legal; but it's substantive? It's about compliance; maybe we can keep as a short paragraph under About the role? It's not a heading; we could fold into a paragraph. However it's legal/export control; might be considered boilerplate but it's a requirement. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. ITAR requirement is legal; but it's a specific requirement for the role. Might be considered necessary. However it's more legal compliance; but it's a requirement for applicants. Could be included as a short paragraph under About the role or Requirements. I'd include it as a brief note under Requirements maybe. But to be safe, we could include