Product Configuration Specialist (Autonomous Systems)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have content: About the role (the "About Our Transition To Ondas Sentinel ..." plus maybe Position Summary). Responsibilities: list of duties. Requirements: maybe required skills/qualifications? Qualifications: maybe education? Skills: maybe preferred skills? Benefits: benefits described. Pay: salary range given. Schedule: maybe work arrangement? There's "Work Arrangement: On-site". Also "Travel Required: Less Than 10%". Could be schedule? Not exactly schedule but maybe we can include schedule as work arrangement and travel. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create those headings if content exists.
We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the EEO statement, etc.
We need to preserve all substantive information. So we need to include the transition description, position summary, duties list, required skills/qualifications, preferred skills/qualifications, education, clearance, export control, work authorization, travel, working conditions, physical demands, salary, benefits, etc.
We must not include placeholders like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which sections to include.
Let's parse content:
- Intro: "About Our Transition To Ondas Sentinel DZYNE Technologies was recently acquired..." This is about the company. Could be considered "About the role"? Actually "About the role" maybe includes position summary and company description. We'll put that under About the role.
- Position Summary: after "Position Summary". That's prose.
- Required Duties And Responsibilities: list of duties.
- Required Skills/Qualifications: list.
- Preferred Skills/Qualifications: list.
- Education: paragraph.
- Clearance Level Required: None
- Export Control / ITAR Requirement: paragraph.
- Work Authorization Requirement: paragraph.
- Travel Required: Less Than 10%.
- Working Conditions: paragraph.
- Physical Demands: paragraph.
- Salary: $90,000 – $108,000 annually plus bonus note.
- Benefits: paragraph describing benefits.
- Some Final Notes: paragraph about description not exhaustive, flexibility, etc. Might be considered part of About the role? Could be separate but we can include as part of About the role or maybe as a note. Since it's not a standard heading, we could incorporate into About the role as prose.
- EEO statement: remove.
We need to avoid duplication: there may be duplicated lines? Not seeing.
Now decide sections:
- About the role: include company transition description, position summary, maybe final notes.
- Responsibilities: list of duties.
- Requirements: maybe required skills/qualifications? Or we could split Requirements (required) and Qualifications (education/clearance etc). But we have both Required Skills/Qualifications and Preferred Skills/Qualifications. Could treat Required Skills/Qualifications as Requirements, Preferred as Skills? Or we could have Requirements (required), Qualifications (education/clearance etc), Skills (preferred). However the instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- Required Skills/Qualifications: could go under Requirements.
- Preferred Skills/Qualifications: could go under Skills.
- Education: could go under Qualifications (maybe also include clearance etc). But Qualifications heading could contain education, clearance, export control, work auth, travel, working conditions, physical demands? Might be too much. But we can split: Qualifications for education and clearance etc; Skills for preferred skills; Requirements for required skills.
- Benefits: benefits paragraph.
- Pay: salary and bonus.
- Schedule: work arrangement (On-site) and travel (About the role
- for any list of duties/requirements/benefits. Use
for prose. We need to decide which sections to include. Let's parse content: - Intro: "About Our Transition To Ondas Sentinel DZYNE Technologies was recently acquired..." This is about the company. Could be considered "About the role"? Actually "About the role" maybe includes position summary and company description. We'll put that under About the role. - Position Summary: after "Position Summary". That's prose. - Required Duties And Responsibilities: list of duties. - Required Skills/Qualifications: list. - Preferred Skills/Qualifications: list. - Education: paragraph. - Clearance Level Required: None - Export Control / ITAR Requirement: paragraph. - Work Authorization Requirement: paragraph. - Travel Required: Less Than 10%. - Working Conditions: paragraph. - Physical Demands: paragraph. - Salary: $90,000 – $108,000 annually plus bonus note. - Benefits: paragraph describing benefits. - Some Final Notes: paragraph about description not exhaustive, flexibility, etc. Might be considered part of About the role? Could be separate but we can include as part of About the role or maybe as a note. Since it's not a standard heading, we could incorporate into About the role as prose. - EEO statement: remove. We need to avoid duplication: there may be duplicated lines? Not seeing. Now decide sections: - About the role: include company transition description, position summary, maybe final notes. - Responsibilities: list of duties. - Requirements: maybe required skills/qualifications? Or we could split Requirements (required) and Qualifications (education/clearance etc). But we have both Required Skills/Qualifications and Preferred Skills/Qualifications. Could treat Required Skills/Qualifications as Requirements, Preferred as Skills? Or we could have Requirements (required), Qualifications (education/clearance etc), Skills (preferred). However the instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Required Skills/Qualifications: could go under Requirements. - Preferred Skills/Qualifications: could go under Skills. - Education: could go under Qualifications (maybe also include clearance etc). But Qualifications heading could contain education, clearance, export control, work auth, travel, working conditions, physical demands? Might be too much. But we can split: Qualifications for education and clearance etc; Skills for preferred skills; Requirements for required skills. - Benefits: benefits paragraph. - Pay: salary and bonus. - Schedule: work arrangement (On-site) and travel (About the role
... transition description ...
Position Summary: ...
Some Final Notes: ...
But we need to avoid repeating "Position Summary:" as heading; just include as prose. We need to preserve all substantive info; we can include the transition description as is. Let's extract transition description: "About Our Transition To Ondas Sentinel DZYNE Technologies was recently acquired by Ondas Inc. (NASDAQ: ONDS) and, together with World View, has joined forces to create Ondas Sentinel. Ondas Sentinel is a next‑generation U.S. defense platform integrating long‑endurance ISR, autonomous systems, counter‑UAS technologies, and mission intelligence. While DZYNE is now part of Ondas Sentinel, we are still legally operating as DZYNE as we complete the formal integration of our systems and processes. As a result, you may see roles cross‑posted across DZYNE and World View, during this transition. All positions represent opportunities within the same combined organization. What does this mean for candidates? You’re joining a team that is accelerating the future of autonomous defense.You’ll be part of a company backed by significant investment, strong growth, and mission‑proven technology.You’ll work alongside world‑class engineers and innovators who have already delivered thousands of operational flight hours, high‑impact ISR capabilities, leading counter‑UAS systems, and breakthrough autonomous effects.You’ll help shape a unified platform that enables operators to see more, decide faster, and act with confidence across the modern battlespace. Together, Ondas Sentinel is building something bigger than any one company, a scalable, integrated defense organization designed to meet emerging mission needs with speed, precision, and purpose. If you’re energized by ambitious missions, rapid innovation, and a chance to help define the future of autonomous defense, we’d love to have you on the team." We need to keep that as is. Now Position Summary: "The Product Configuration Specialist (Autonomous Systems) is responsible for the day-to-day maintenance, accuracy, and integrity of configuration data across hardware, software, and documentation for unmanned aircraft systems (UAS). This role focuses on executing established configuration management (CM) processes, ensuring that released designs, builds, and deployed systems remain aligned with approved baselines. The Product Configuration Specialist (Autonomous Systems) works closely with Engineering, Manufacturing, Supply Chain, and Operations to support controlled change and traceability throughout the product lifecycle." Now Some Final Notes: "The description gives you a sense of what the position involves but is not an exhaustive list. We are a growing and evolving team, which means your responsibilities may shift or expand overtime as new opportunities arise. Flexibility and curiosity are part of what makes our work exciting!" Now Responsibilities list: we need to convert each duty into