Buyer II

We need to output HTML fragment with sections: About the role? Actually we have a lot of introductory text about transition. Should we include that as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - About Our Transition To Ondas Sentinel DZYNE Technologies... (intro paragraph) - Position Title: Buyer II - Location: Irvine, CA - Work Arrangement: On-Site - Position Summary (paragraph) - Required Duties And Responsibilities (list of bullet-like sentences) - Required Skills/Qualifications (list) - Preferred Skills/Qualifications (list) - Education (sentence) - Clearance Level Required: None - Export Control / ITAR Requirement (paragraph) - Work Authorization Requirement (sentence) - Travel Required: None - Working Conditions (sentence) - Physical Demands (sentence) - Salary: $75,000 – $85,000 annually (plus bonus note) - Benefits (paragraph) - Some Final Notes (paragraph) - EEO boilerplate (should be removed) We need to remove EEO boilerplate and any duplicated lines. Also remove navigation/legal etc. We need to decide sections: Possibly "About the role" could include the transition intro and position summary? Or we could have "About the role" for the transition description and position summary. Then "Responsibilities" for Required Duties And Responsibilities. Then "Qualifications" could combine Required Skills/Qualifications and Preferred Skills/Qualifications? Or separate "Requirements" and "Preferred Qualifications". The instruction list includes headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to use. We need to avoid filler sections. We have concrete content for: - About the role: transition description and position summary (maybe combine) - Responsibilities: list of duties - Requirements: Required Skills/Qualifications (maybe also Education, Clearance, Export Control, Work Authorization, Travel, etc.) Could be separate sections but we want few substantive sections. - Qualifications: maybe Preferred Skills/Qualifications? Or we could combine Required and Preferred under "Qualifications" with subheadings? But we only allowed

  headings, not subheadings. Could have separate sections: "Required Qualifications" and "Preferred Qualifications". But the instruction list includes "Requirements" and "Qualifications". Might map Requirements to required skills, Qualifications to preferred? Or we could have "Requirements" for required skills/qualifications, and "Qualifications" for education/clearance etc. However we need to avoid filler. We have Salary info: we can create a Pay section with the salary range and bonus note. We have Benefits: we have a Benefits paragraph. We have Schedule? Not given; Work Arrangement: On-Site (maybe schedule not given). No schedule details, so we should not create Schedule section. We have no explicit "About the role" but we have transition intro and position summary. That seems appropriate. We need to preserve all substantive information. So we must include details like location, work arrangement, etc. Those could be placed in a short

  under About the role or maybe a separate "Details" section but not in heading list. Since we cannot invent headings, we could include them as a paragraph within About the role. We must not repeat job title as heading. So we won't have

  Buyer II

  . We must not include duplicated lines: The Required Duties And Responsibilities list appears also repeated in Required Skills/Qualifications (they are identical). Indeed the Required Skills/Qualifications list is exactly same as duties list. We need to preserve all substantive information but not duplicate. We should deduplicate: include each piece of information once. Since the duties list and required skills list are identical, we should include only once. Probably under Responsibilities. Similarly, the Required Skills/Qualifications list includes many items that are similar to duties but also includes some extra like "Solid knowledge of procurement processes..." etc. Actually the Required Skills/Qualifications list is exactly same as duties list (I need to verify). Looking at the text: After "Required Duties And Responsibilities" there is a list of items each ending with a period. Then after that there is "Required Skills/Qualifications" and then a list that appears to be exactly the same sentences as the duties list. Yes it's duplicated. Then after that there is "Preferred Skills/Qualifications" with a different list. Thus we should include the duties list once under Responsibilities. Then we should include the Required Skills/Qualifications? Since it's duplicate, we can omit it to avoid duplication. But we need to preserve all substantive information; if we omit the duplicate, we are not losing information because it's same as duties. So it's okay. Now we need to include Preferred Skills/Qualifications list. Education: "Bachelor’s degree in Supply Chain, Business, Finance, Operations Management, or a related discipline preferred. Equivalent combination of education and professional experience may be considered." Clearance Level Required: None Export Control / ITAR Requirement: paragraph. Work Authorization Requirement: sentence. Travel Required: None Working Conditions: sentence. Physical Demands: sentence. Salary: $75,000 – $85,000 annually plus bonus note. Benefits: paragraph. Some Final Notes: paragraph. We need to remove EEO boilerplate. Now decide sections: - About the role: include transition intro paragraph(s) and position summary. Also could include location, work arrangement? Might be better to include location and work arrangement as a short paragraph under About the role. - Responsibilities: the duties list (unique). - Qualifications: could include Preferred Skills/Qualifications, Education, Clearance, Export Control, Work Authorization, Travel, Working Conditions, Physical Demands? That's a lot but maybe we can split into "Qualifications" (preferred skills + education) and "Requirements" (clearance, export, work auth, travel, working conditions, physical demands). However we need to avoid thin sections. But we have substantive content for each. Alternatively, we could have a single "Qualifications" section that includes all of those as a list (mix of preferred skills, education, clearance, etc.) But the instruction says use
  • for any list of duties/requirements/benefits. So we can have a list for qualifications. We need to decide headings: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Requirements? But we can incorporate requirements into Qualifications. We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits, so we can include those. We should not create Schedule section because not given. Thus final sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. We'll start with

    About the role

    then

    containing transition intro and position summary plus location and work arrangement. Transition intro: multiple paragraphs. We'll combine into one

    maybe with line breaks? But we can keep as multiple

    inside the section? The instruction: use

    for prose. Could have multiple

    under same heading. That's fine. Thus:

    About the role

    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.

    Position Summary Buyer II is responsible for performing intermediate-level procurement activities to support organizational operations. This role manages the purchasing of materials, equipment, supplies, and services in accordance with established policies, quality standards, budget requirements, and delivery schedules. The Buyer II conducts supplier sourcing, evaluates quotes, negotiates pricing and terms, and ensures timely and accurate orders. This position requires strong analytical skills, communication abilities, and purchasing experience. The Buyer II works cross-functionally with internal departments—such as operations, finance, inventory control, and engineering—to clarify requirements, resolve issues, and maintain supply continuity. The role also supports supplier relationship management, contributes to cost saving initiatives, and maintains purchasing records and data integrity.

    Location: Irvine, CA • Work Arrangement: On-Site

    Now Responsibilities:

    Responsibilities

    • Maintain accurate procurement records, purchase order data, and documentation within the ERP/MRP system.
    • Collaborate with cross functional teams—including operations, engineering, inventory control, finance, and quality—to clarify specifications, resolve issues, and maintain supply continuity.
    • Review inventory levels, production schedules, and planning reports to determine purchasing needs.
    • Evaluate supplier performance and escalate concerns when quality or delivery standards are not met.
    • Ensure all procurement activities comply with company policies, contractual requirements, and applicable regulations.
    • Assist in developing and implementing cost reduction initiatives and sourcing strategies.
    • Support process improvements to enhance procurement efficiency, accuracy, and lead time performance.
    • Provide purchasing support for projects, new product introductions, and special sourcing requirements.
    Now Qualifications: include Preferred Skills/Qualifications list, Education, Clearance Level, Export Control, Work Authorization, Travel, Working Conditions, Physical Demands. We could make a
    for Preferred Skills/Qualifications and then separate paragraphs for other items. Or we could combine all into one list but that would mix different types. Better to have separate headings? But we only have one Qualifications heading.