Customer Outreach Specialist

We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually the posting includes "Job Description Summary", "Roles And Responsibilities", "Qualifications", "Benefits", maybe "Pay" (salary range). Also "Schedule"? Not present. There's mention of "9/80 work schedule" in benefits. So schedule is part of benefits. We'll include Pay section with salary range. Benefits section with listed benefits. Also maybe "About AV" could be considered "About the role"? Actually "About AV" is company description; we could include as a section maybe "About the company"? But instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use those headings if content matches. We have: - About the role: maybe the Job Description Summary? Could be "About the role". We'll put that as h3. - Responsibilities: from "Roles And Responsibilities". We'll list bullet points. - Requirements: maybe "Qualifications". Could be "Requirements" or "Qualifications". We'll use "Qualifications" heading. - Skills: maybe not separate; qualifications include skills. Could combine. - Benefits: present. - Pay: salary range. - Schedule: not separate; but we have 9/80 work schedule inside benefits; we could still include Schedule heading if we want but instruction: include a section ONLY when posting has real, specific content for it. The posting mentions "9/80 work schedule" as part of benefits, not a separate schedule section. So we could either not create Schedule section, or we could include Schedule with that detail. But better to follow instruction: only create Schedule if posting actually states them as a separate schedule. It's inside benefits, but still states schedule. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule (9/80 work schedule) so we could create Schedule section. But we also have Benefits section; we could keep both. However they said prefer a few substantive sections over many thin ones. Might be better to incorporate schedule into Benefits. Since they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule, so we could create Schedule. But we also have Benefits; we could still have both. However to avoid thin sections, maybe combine schedule into Benefits. I'd choose to include Benefits only, and mention schedule within that list. Pay: we have salary range, so include Pay section. Thus sections: About the role (h3), Responsibilities (h3), Qualifications (h3), Pay (h3), Benefits (h3). Possibly also Skills? Not needed. Now we need to strip boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Principals only need apply. NO agencies please." That's application instruction; remove. Remove EEO statements. Remove ITAR requirement? That's substantive? It's about clearance and citizenship; maybe keep as part of Qualifications? It's a requirement. The posting includes "TS/SCI with polygraph Clearance Level Top Secret with Poly". Also "ITAR Requirement" and "ITAR U.S. Citizenship is required." That's substantive; we should keep. Also "Secret or Top Secret clearance, or the ability obtain a clearance is desired." That's also qualification. We need to preserve all substantive information. So include clearance and citizenship requirements within Qualifications. Now we need to format. Let's extract content: Job Description Summary: "At AV our Cyber experts operate at the mission's edge. Using advanced cyber techniques, our team of technologists and analysts employ capabilities spanning traditional computing environments to Internet of Things (IoT), including offensive and defensive cyber operations and analysis, signals intelligence (SIGINT) discovery, and data science. We are seeking a Customer Outreach Specialist/System Engineer. As a Customer Outreach Specialist within our Intel Division, you will serve as the primary bridge between operational end users, mission stakeholders, and our software engineering teams. You will drive tool adoption, advocate for mission needs, lead interactive user training, perform front-line technical troubleshooting, and support functional testing to ensure fielded capabilities directly accelerate customer operations." That's the summary. Roles And Responsibilities: list: - User Outreach & Training: Lead product demonstrations, facilitate formal user training, and coordinate Champion working groups to drive tool adoption and gather critical feedback. - Technical Problem-Solving & Support: Triage, investigate, and resolve user-reported technical issues, managing support tickets to closure while coordinating closely with developers and leadership. - Requirements Advocacy & Engineering Collaboration: Act as the voice of the customer, translating operational mission needs into clear technical requirements and participating in feature testing/validation. - Documentation: Author and maintain comprehensive user guides, release notes, standard operating procedures, and baseline system workflow diagrams to support onboarding and operational readiness. - Stakeholder Engagement: Assist in facilitating meetings and status reviews with government leadership and stakeholders. Qualifications: - Minimum of 2 -4 years of experience supporting the IC in an analyst, systems engineer, technical support, or mission outreach capacity. - Typically requires a Bachelor’s degree and a minimum of 2 years of related experience; or an advanced degree without experience; or equivalent work experience. - Strong problem-solving, critical thinking, and troubleshooting skills. - Excellent written, verbal, and interpersonal communication skills. - Strong writing and documentation skills. - TS/SCI with polygraph Clearance Level Top Secret with Poly. - ITAR Requirement: This position requires access to information that is subject to compliance with the International Traffic Arms Regulations (“ITAR”) and/or the Export Administration Regulations (“EAR”). In order to comply with the requirements of the ITAR and/or the EAR, applicants must qualify as a U.S. person under the ITAR and the EAR, or a person to be approved for an export license by the governing agency whose technology comes under its jurisdiction. Please understand that any job offer that requires approval of an export license will be conditional on AeroVironment’s determination that it will be able to obtain an export license in a time frame consistent with AeroVironment’s business requirements. A “U.S. person” according to the ITAR definition is a U.S. citizen, U.S. lawful permanent resident (green card holder), or protected individual such as a refugee or asylee. See 22 CFR 120.15. Some positions will require current U.S. Citizenship due to contract requirements. - ITAR U.S. Citizenship is required. Secret or Top Secret clearance, or the ability obtain a clearance is desired. We need to keep that but maybe condense? We must preserve all substantive information; we cannot invent or summarize away detail. However we can keep the text as is, but we need to format as list items. The ITAR paragraph is long; we can keep as a list item but it's okay. Pay: "The Salary Range For This Role Is $83,500 - $146,000 AeroVironment considers several factors when extending an offer, including but not limited to, the location, the role and associated responsibilities, a candidate’s work experience, education/training, and key skills." We should keep that sentence. Benefits: "Benefits: AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown. For more information about our company benefit offerings please visit: http://www.avinc.com/myavbenefits. We also encourage you to review our company website at http://www.avinc.com to learn more about us." We need to remove application instructions and links? The instruction says remove application instructions, but benefit links maybe not application instructions; they are informational. Could keep but maybe remove the URLs as they are not substantive? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The URLs are not application instructions; they are benefit info. Could keep but maybe we should keep the description but drop the URLs as they are navigation? Might be considered navigation. Safer to remove the URLs. Keep the description of benefits. Also "About AV" section: we could include as "About the role"? Actually we already have About the role from summary. The "About AV" is company description; could be omitted as not required heading. But we could include as a separate section maybe "About the company". However instructions only list certain headings; we could add a heading like "About AV" but not in list. Better to omit because not needed. Thus final HTML:

About the role

At AV our Cyber experts operate at the mission's edge. Using advanced cyber techniques, our team of technologists and analysts employ capabilities spanning traditional computing environments to Internet of Things (IoT), including offensive and defensive cyber operations and analysis, signals intelligence (SIGINT) discovery, and data science. We are seeking a Customer Outreach Specialist/System Engineer. As a Customer Outreach Specialist within our Intel Division, you will serve as the primary bridge between operational end users, mission stakeholders, and our software engineering teams. You will drive tool adoption, advocate for mission needs, lead interactive user training, perform front-line technical troubleshooting, and support functional testing to ensure fielded capabilities directly accelerate customer operations.

Responsibilities

• User Outreach & Training: Lead product demonstrations, facilitate formal user training, and coordinate Champion working groups to drive tool adoption and gather critical feedback.
• Technical Problem-Solving & Support: Triage, investigate, and resolve user-reported technical issues, managing support tickets to closure while coordinating closely with developers and leadership.
• Requirements Advocacy & Engineering Collaboration: Act as the voice of the customer, translating operational mission needs into clear technical requirements and participating in feature testing/validation.
• Documentation: Author and maintain comprehensive user guides, release notes, standard operating procedures, and baseline system workflow diagrams to support onboarding and operational readiness.
• Stakeholder Engagement: Assist in facilitating meetings and status reviews with government leadership and stakeholders.

Qualifications

• Minimum of 2 -4 years of experience supporting the IC in an analyst, systems engineer, technical support, or mission outreach capacity.
• Typically requires a Bachelor’s degree and a minimum of 2 years of related experience; or an advanced degree without experience; or equivalent work experience.
• Strong problem-solving, critical thinking, and troubleshooting skills.
• Excellent written, verbal, and interpersonal communication skills.
• Strong writing and documentation skills.
• TS/SCI with polygraph Clearance Level Top Secret with Poly.
• ITAR Requirement: This position requires access to information that is subject to compliance with the International Traffic Arms Regulations (“ITAR”) and/or the Export Administration Regulations (“EAR”). In order to comply with the requirements of the ITAR and/or the EAR, applicants must qualify as a U.S. person under the ITAR and the EAR, or a person to be approved for an export license by the governing agency whose technology comes under its jurisdiction. Please understand that any job offer that requires approval of an export license will be conditional on AeroVironment’s determination that it will be able to obtain an export license in a time frame consistent with AeroVironment’s business requirements. A “U.S. person” according to the ITAR definition is a U.S. citizen, U.S. lawful permanent resident (green card holder), or protected individual such as a refugee or asylee. See 22 CFR 120.15. Some positions will require current U.S. Citizenship due to contract requirements.
• ITAR U.S. Citizenship is required. Secret or Top Secret clearance, or the ability obtain a clearance is desired.

Pay

The Salary Range For This Role Is $83,500