Senior Autonomy Engineer

We need to output HTML fragment with sections: About the role? The posting includes Position Summary, Essential Duties And Responsibilities, Required Qualifications, Additional Desired Qualifications, Physical Requirements And Working Conditions, Background Check, EEO and ITAR/EAR Work Authorization Disclosure, E-Verify, Compensation (partial). We need to remove boilerplate: EEO, ITAR/EAR, E-Verify, background check maybe? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop EEO, ITAR/EAR, E-Verify, background check? The background check is not exactly boilerplate but maybe considered legal? It says "Background Check This position will require successfully completing a post-offer background check." That's somewhat legal but maybe we keep? The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. Background check is legal but not EEO. Might be okay to keep? However they said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So legal includes background check? Probably drop it. Also "Compensation: Salary plus generous annual equity package and poten" is incomplete; we should not include if incomplete. The compensation line is cut off; we should not create Pay section unless posting actually states them. It says "Compensation: Salary plus generous annual equity package and poten" incomplete, so we should not include Pay section. Benefits? Not mentioned. Schedule? Not mentioned. So we will have sections: About the role (maybe from Position Summary), Responsibilities (Essential Duties And Responsibilities), Qualifications (Required Qualifications), Additional Desired Qualifications (maybe as Skills? but we can have a section "Additional Desired Qualifications" or "Preferred Qualifications". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use others if appropriate? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when applicable. So we should map content to those headings. Let's decide: - About the role: from Position Summary. - Responsibilities: Essential Duties And Responsibilities. - Requirements: Required Qualifications (maybe also include Additional Desired Qualifications under Skills? But they have Skills heading. Could put Additional Desired Qualifications under Skills. - Qualifications: maybe we could combine Required and Additional? But they said prefer few substantive sections over many thin ones. Could have About the role, Responsibilities, Requirements (including both required and desired), and maybe Skills? But we have separate headings for Qualifications and Skills. Could do: About the role, Responsibilities, Requirements (Required Qualifications), Skills (Additional Desired Qualifications). Physical Requirements And Working Conditions could be part of Requirements? But maybe we can include under Requirements as a bullet? However they said only include section when posting has real specific content. Physical requirements are present; we could include a section "Requirements" that includes both qualifications and physical? But they'd be mixed. Better to have separate sections: Requirements (for qualifications) and maybe "Working Conditions" not in list. Not in allowed headings. Could we create a custom heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples but not exclusive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we must map content to those headings. If a section doesn't fit exactly, we may need to omit or combine. Thus we have: - About the role: Position Summary. - Responsibilities: Essential Duties And Responsibilities. - Qualifications: Required Qualifications. - Skills: Additional Desired Qualifications (maybe also include proficiency in C++, Python etc but those are in Required). Additional Desired includes many items; we can treat as Skills. - Possibly we could also include Physical Requirements under Qualifications? But maybe we can add a separate section "Requirements" for physical? But we already used Qualifications. Could we use Requirements for physical and Qualifications for education/experience? The list includes both Requirements and Qualifications as separate headings. So we can assign: - Requirements: Physical Requirements And Working Conditions (maybe also include ability to travel, etc). But travel is in Required Qualifications. Hmm. Better: Use: - About the role: Position Summary. - Responsibilities: Essential Duties And Responsibilities. - Requirements: Required Qualifications (education, experience, citizenship, etc). - Skills: Additional Desired Qualifications. - (Optional) Benefits: none. - Pay: none. - Schedule: none. We could also include a short paragraph for metadata like Job ID? Not needed. We must preserve all substantive information. So we need to include all bullets from Responsibilities, Required Qualifications, Additional Desired Qualifications, Physical Requirements. We must not repeat job title as heading. We must output only HTML fragment. Let's craft:

About the role

Blue Ops is seeking a highly skilled Senior USV Autonomy Engineer (USA) to lead the design, integration, deployment, and evolution of autonomy capabilities for Uncrewed Surface Vessels (USVs). Oversee autonomy software and hardware integration, sensor fusion, mission planning, control, and field testing. Mentor junior engineers and contribute to team development. Collaborate with cross-functional teams to deliver reliable, scalable, and safe autonomy systems supporting maritime, defense, and commercial programs. Support the roadmap toward AI-enabled, fully autonomous maritime operations. Leverage artificial intelligence and machine learning to advance situational awareness, navigation, and decision-making.

Responsibilities

• Design, implement, and validate autonomous behaviors for USV platforms.
• Develop and integrate sensor-driven situational awareness capabilities for real-time perception, obstacle avoidance, and decision-making.
• Adapt and optimize autonomy stacks for U.S. regulatory, environmental, and safety requirements.
• Lead installation, calibration, and testing of autonomy systems on production and demonstration vessels.
• Support simulation-based development, software architecture design, and scalability across multiple platforms.
• Serve as the technical liaison between autonomy developers, marine engineering teams, systems integrators, and field operations.
• Provide mentorship and training to engineering teams on installation, operation, and troubleshooting.
• Advance development of COLREG-compliant navigation and collision-avoidance behaviors.
• Ensure compliance with ITAR/EAR, cybersecurity, and U.S. defense technology transfer regulations.

Requirements

• U.S. citizenship is required.
• Bachelor’s degree in Robotics, Computer Science, Electrical, Mechanical, or Marine Engineering from an ABET-accredited university.
• Minimum of 10 years of relevant experience in autonomy, robotics, or intelligent systems engineering.
• Strong understanding of marine platforms, navigation systems, control architectures, and sensor fusion.
• Proficiency in C++, Python, and robotics simulation environments such as ROS, Gazebo, and SIL/HIL.
• Excellent written and verbal communication skills.
• Ability to travel domestically and internationally for integration, sea trials, and customer support.

Skills

• Active Secret (or higher) security clearance preferred.
• Master’s or PhD with at least 7 years of related experience.
• Direct experience with Uncrewed Surface Vessels (USV) or autonomous maritime systems.
• Experience developing or validating COLREG-compliant navigation systems.
• Familiarity with integration and operations aboard military host vessels.
• Experience with AI/ML algorithms, mission planning, and data-driven decision frameworks.
• Experience implementing DevSecOps or CI/CD pipelines for mission-critical autonomy software.
• Experience in ITAR-controlled or defense environments.
• Experience with SWARM autonomy or multi-vehicle coordination technologies.
• Proven success transitioning autonomy research into deployed field systems.

We might also include Physical Requirements And Working Conditions. Where to put? Could be under Requirements as additional bullet? But we already used Requirements for qualifications. Could add another section "Requirements" for physical? But we already used that heading. Could we add a second

Requirements? That would duplicate heading; not ideal. Maybe we can incorporate physical requirements into Responsibilities? Not appropriate. Could create a section "Requirements" that includes both qualifications and physical? But we already split. Perhaps we should rename: Use "Requirements" for physical and "Qualifications" for education/experience. Let's re-evaluate. The instruction list includes both Requirements and Qualifications as examples. So we can have both sections. Let's assign: - Requirements: Physical Requirements And Working Conditions (maybe also include ability to travel? but travel is in qualifications). However travel is more a qualification. But we can keep travel under Qualifications. - Qualifications: Required Qualifications (education, experience, citizenship, etc). - Skills: Additional Desired Qualifications. Thus we need to output sections: About the role, Responsibilities, Requirements, Qualifications, Skills. Let's do that. Requirements section bullets: - Must be able to walk, stand, and navigate large indoor and outdoor facilities for extended periods of time. - Ability to lift, carry, and move materials and equipment weighing up to 25 lbs on a regular basis. - Use of personal protective equipment (PPE) may be required in designated areas or when performing specific tasks, in accordance with safety protocols and company policy. - May be required to climb ladders, stoop, kneel, or crouch during inspections, maintenance walk-throughs, or emergency response situations. - Regular exposure to facility operations including noise, dust, temperature fluctuations, and industrial equipment. - Occasional off-hours or weekend work required for emergency facility responses or projects as needed. - Requires frequent use of a computer and other standard office equipment for documentation, communication, and coordination tasks. Qualifications section bullets: U.S. citizenship, Bachelor's degree, 10 years experience, strong understanding, proficiency in C++, Python, ROS etc, excellent communication, ability to travel. Skills section bullets: Additional Desired Qualifications list. Now we need to ensure we preserve all substantive information. Did we miss anything? The posting also mentions "Support the roadmap toward AI-enabled, fully autonomous maritime operations." Already in About the role. "Leverage artificial intelligence and machine learning to advance situational awareness, navigation, and decision-making." Included. Also "Oversee autonomy software and hardware integration, sensor fusion, mission planning, control, and field testing." In responsibilities. "Mentor junior engineers and contribute to team development." In responsibilities. "Collaborate with cross-functional teams to deliver reliable, scalable, and safe autonomy systems supporting maritime, defense, and commercial programs." In responsibilities. "Support the roadmap toward AI-enabled, fully autonomous maritime operations." Already. "Leverage artificial intelligence and machine learning to advance situational awareness, navigation, and decision-making." Already. "Essential Duties And Responsibilities" we captured. "Required Qualifications" we captured. "Additional Desired Qualifications" we captured. "Physical Requirements And Working Conditions" we captured. "Background Check" we dropped (legal). "EEO and ITAR/EAR Work Authorization Disclosure" dropped. "E-Verify" dropped. "Compensation: Salary plus generous annual equity package and poten" incomplete, we drop. Now output HTML fragment. Make sure