Outreach Coordinator

We need to output HTML fragment only, with sections for headings where there is real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not put Job ID etc as headings. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must include sections only when posting has real specific content for it. Must not emit heading followed by filler placeholder like "commensurate with experience", "not specified", etc. Also never create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes: Anticipated Hiring Range Commensurate with education and experience (anticipated hiring range $70,000 - $80,000). That's pay info. So we can include Pay section with that range. Work Schedule: Monday through Friday, 8 am to 5 pm (additional work outside of standard hours may be required due to business needs). So Schedule section. Benefits: The posting includes "Wolfpack Perks And Benefits" with list of benefits. So Benefits section. About the role: There's "About The Department" and description. Also there is description of role in "Essential Job Duties". Could combine as About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have content for About the role: The department description and role overview. Could put under About the role. Responsibilities: There's "Essential Job Duties" and "Key Responsibilities" and "Other Responsibilities". So we can put under Responsibilities. Requirements: Might be similar to Qualifications? The instruction lists Requirements and Qualifications separate. Usually Requirements could be minimum qualifications, while Qualifications could be preferred? But we have "Minimum Education and Experience" under Qualifications heading, and "Other Required Qualifications", "Preferred Qualifications". Also "Required License(s) Or Certification(s)". So we could treat Requirements as the mandatory qualifications (minimum education/experience, other required qualifications, required license). Qualifications as preferred qualifications. Or we could combine. But we need to follow instruction: Use headings as given. We'll include both Requirements and Qualifications sections if there is substantive content. Skills: Could be derived from "Effective communication skills", "Strong organizational and project coordination skills", etc. Might be part of Qualifications. But we could create Skills section if there is explicit skill list. The posting includes skills like communication, organizational, project coordination, relationship building, managing multiple programs, proficiency with office software and CRM, collecting metrics. Could be placed under Skills. However we already have Qualifications covering similar. To avoid duplication, maybe we just include Qualifications and Skills separate if there is distinct skill content. The instruction says prefer a few substantive sections over many thin ones. So maybe combine skills into Qualifications. But we have both Requirements and Qualifications headings; we could put minimum qualifications under Requirements, and preferred qualifications under Qualifications. Skills could be omitted or merged. We need to ensure we don't create sections with filler like "commensurate with experience". Pay section we have actual range, so okay. Schedule: we have actual schedule. Benefits: we have list. Now we need to strip boilerplate: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Disclaimer: Perks and Benefit eligibility..." maybe that's part of benefits but it's a disclaimer; could keep? It's not boilerplate? It's about eligibility; could keep as part of benefits but it's not a substantive benefit. Might keep but it's okay. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First, About the role: We have "About The Department" paragraph describing department's mission. Also there is description of role in "Essential Job Duties" first paragraph: "Help expand access to cutting-edge research while building meaningful connections across academia, industry, government, and education. Self-driving Platforms for Expedited Experimental co-Design ( SPEED ) is an NSF -funded national user facility at NC State University that provides remote access to self-driving laboratories, combining robotics and artificial intelligence to accelerate discovery in chemistry and materials science. As the Outreach and User Engagement Coordinator, you will play a vital role in growing SPEED’s user community by recruiting new users, coordinating engagement activities, and developing programs that connect researchers, students, and external partners with advanced scientific resources. Your work will help strengthen research collaborations, support workforce development, and contribute to the facility’s long-term success and sponsor objectives." We could combine department description and role overview into About the role. Now Responsibilities: We have "Key Responsibilities" with sub-bullets: User Engagement & Community Building, Programs, Events & Outreach, Program Operations & Assessment. Each has multiple sentences. Also "Other Responsibilities" list. We'll combine all responsibilities into a

• list. We need to preserve all substantive info; we should not lose any details. So we need to extract each duty as list items. Let's list them: From Key Responsibilities: - User Engagement & Community Building: * Recruit and engage prospective users through targeted outreach, conferences, meetings, partnerships, and networking activities to expand participation across academic, industry, government, and educational communities. * Coordinate user onboarding, orientation, facility access, and project start-up activities to ensure a seamless experience for new and returning users. * Build and maintain productive relationships with researchers, external partners, and stakeholders while serving as a key point of contact for user engagement initiatives. - Programs, Events & Outreach: * Plan and coordinate workshops, bootcamps, webinars, demonstrations, facility tours, advisory board meetings, sponsor visits, and workforce development programs. * Develop and distribute outreach materials, newsletters, announcements, and other user-facing communications that promote facility capabilities, opportunities, and accomplishments. * Manage event logistics, registration, speaker coordination, and post-event communications to deliver high-quality engagement experiences. - Program Operations & Assessment: * Maintain user and stakeholder databases, outreach calendars, and participation records to support ongoing engagement efforts. * Collect user feedback, testimonials, and success stories while tracking participation, demographics, outcomes, and other program metrics to support reporting requirements and continuous improvement. * Collaborate with SPEED leadership and communications staff to develop and implement outreach strategies that enhance user engagement and strengthen the facility’s impact. Other Responsibilities (list): - Support sponsor visits, advisory-board meetings, and facility tours. - Maintain user/contact databases and outreach calendars. - Coordinate event logistics, registration, speakers, and follow-up. - Collect user testimonials, success stories, and program feedback. - Collaborate with SPEED leadership and communications staff on engagement strategy. Note some overlap with earlier items; but we must preserve all. Could combine duplicates but better to keep as is? Might be duplication but instruction says remove duplicated lines. So we should deduplicate. Let's see duplicates: "Maintain user/contact databases and outreach calendars." appears both in Program Operations & Assessment (maintain user and stakeholder databases, outreach calendars, participation records) and Other Responsibilities (maintain user/contact databases and outreach calendars). Slightly different but similar. Also "Coordinate event logistics, registration, speaker coordination, and post-event communications" appears in Programs, Events & Outreach and also in Other Responsibilities (coordinate event logistics, registration, speakers, and follow-up). Slight differences. We could keep both but maybe they are considered duplicated lines? Safer to keep unique items; but we risk losing some nuance. However instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. We'll need to identify exact duplicate strings. Let's list each line exactly as appears. From Key Responsibilities: User Engagement & Community Building: 1. Recruit and engage prospective users through targeted outreach, conferences, meetings, partnerships, and networking activities to expand participation across academic, industry, government, and educational communities. 2. Coordinate user onboarding, orientation, facility access, and project start-up activities to ensure a seamless experience for new and returning users. 3. Build and maintain productive relationships with researchers, external partners, and stakeholders while serving as a key point of contact for user engagement initiatives. Programs, Events & Outreach: 4. Plan and coordinate workshops, bootcamps, webinars, demonstrations, facility tours, advisory board meetings, sponsor visits, and workforce development programs. 5. Develop and distribute outreach materials, newsletters, announcements, and other user-facing communications that promote facility capabilities, opportunities, and accomplishments. 6. Manage event logistics, registration, speaker coordination, and post-event communications to deliver high-quality engagement experiences. Program Operations & Assessment: 7. Maintain user and stakeholder databases, outreach calendars, and participation records to support ongoing engagement efforts. 8. Collect user feedback, testimonials, and success stories while tracking participation, demographics, outcomes, and other program metrics to support reporting requirements and continuous improvement. 9. Collaborate with SPEED leadership and communications staff to develop and implement outreach strategies that enhance user engagement and strengthen the facility’s impact. Other Responsibilities: 10. Support sponsor visits, advisory-board meetings, and facility tours. 11. Maintain user/contact databases and outreach calendars. 12. Coordinate event logistics, registration, speakers, and follow-up. 13. Collect user testimonials, success stories, and program feedback. 14. Collaborate with SPEED leadership and communications staff on engagement strategy. Now duplicates: Compare line 2 vs line 12? line2: "Coordinate user onboarding, orientation, facility access, and project start-up activities to ensure a seamless experience for new and returning users." line12: "Coordinate event logistics, registration, speakers, and follow-up." Not same. Line6: "Manage event logistics, registration, speaker coordination, and post-event communications to deliver high-quality engagement experiences." line12: "Coordinate event logistics, registration, speakers, and follow-up." Not same but similar. Line7: "Maintain user and stakeholder databases, outreach calendars, and participation records to support ongoing engagement efforts." line11: "Maintain user/contact databases and outreach calendars." Not same but similar. Line8: "Collect user feedback, testimonials, and success stories while tracking participation, demographics, outcomes, and other program metrics to support reporting requirements and continuous improvement." line13: "Collect user testimonials, success stories, and program feedback." Not same but similar. Line9: "Collaborate with SPEED leadership and communications staff to develop and implement outreach strategies that enhance user engagement and strengthen the facility’s impact." line14: "Collaborate with SPEED leadership and communications staff on engagement strategy." Similar but not identical. Given instruction to remove duplicated lines, we might keep only one version of each similar concept? Might be safer to keep all as they are not exact duplicates. The instruction likely refers to exact duplicated lines (like repeated sentences). We don't see exact duplicates. So we keep all. Now Requirements: Minimum Education and Experience: Bachelor’s degree in science, engineering, education, communications, or related field. Three or more years of relevant outreach, program, or stakeholder-engagement experience. Equivalent combinations of relevant education and applied experience considered. Other Required Qualifications: list: - Experience coordinating events, workshops, training programs, or community engagement activities. - Effective communication skills with both technical and nontechnical audiences through written, verbal, and presentation-based communications. - Strong organizational and project coordination skills, including scheduling activities, coordinating logistics, and following projects through to completion. - Demonstrated success building and maintaining professional relationships with scientists, students, industry representatives, and other external stakeholders. - Experience managing multiple programs, projects, or competing deadlines simultaneously. - Proficiency with standard office software and customer