Principal Extension Specialist for Outreach and Strategic Initiatives

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: navigation, EEO, equal opportunity, scam warning, application instructions, etc. Also remove "Click here for more information about equivalencies" link? That's maybe considered metadata but not boilerplate; but it's a link; we might keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to equivalencies might be considered part of required education info; but it's a link; we could keep as part of required education? Might be considered not boilerplate. However we can keep the text "Click here for more information about equivalencies: https://hr.uky.edu/employment/working-uk/equivalencies" maybe as part of required education. But it's a link; we could keep as plain text. We need to parse posting details. Let's extract sections: Job Title: Principal Extension Specialist for Outreach and Strategic Initiatives (not heading) Requisition Number: RE55835 (drop) Working Title: (maybe blank) ignore Department Name: 81170:Program and Staff Development (maybe metadata; could be included in a short paragraph about department? Not required but we could include as part of About the role? The instruction: fold minor metadata into a short

or drop it. So we could include department and location in a short paragraph under About the role. Work Location: Lexington, KY Grade Level: 49 (metadata) Salary Range: $73,861-121,888/year (Pay section) Type of Position: Staff Position Time Status: Full-Time Required Education: PhD Link for equivalencies Required Related Experience: 5 yrs Required License/Registration/Certification: Driver’s License required Physical Requirements: Lifting, pushing or pulling objects up to 50 lbs. Shift: Primarily days, some possible evening and weekend activities. Job Summary: paragraph. Why Join Us: paragraph with benefits list. Skills / Knowledge / Abilities: includes supervisory responsibilities? No Preferred Education/Experience: Doctoral degree. Deadline to Apply: 09/29/2026 (application instruction? maybe drop as it's application instruction; but it's a deadline; could be considered metadata; but instruction says remove application instructions. Deadline is part of application instructions; we should drop. Our University Community: includes EEO etc; we should remove boilerplate like equal opportunity, tobacco free, nondiscrimination, etc. Also remove "Any candidate offered a position may be required to pass pre-employment screenings..." that's legal/boilerplate; drop. Also "#CampusGrade" drop. Thus we need to keep substantive info: Job Summary, Why Join Us (benefits), Skills/Knowledge/Abilities (supervisory responsibilities? No), Preferred Education/Experience, Required Education, Required Experience, License, Physical Requirements, Shift, Pay, maybe Department/Location. We need to decide sections. We have Pay: Salary Range. Schedule: Shift info (Primarily days, some possible evening and weekend activities.) That's schedule. Benefits: Why Join Us list. Responsibilities: Job Summary maybe includes responsibilities; but we could treat Job Summary as About the role? Actually About the role could be Job Summary. Responsibilities could be derived from Job Summary? The Job Summary includes leading initiatives, developing solutions, building consensus, representing. That's responsibilities. Could put under Responsibilities. Requirements: Required Education, Required Experience, License, Physical Requirements maybe. Qualifications: Preferred Education/Experience, maybe also Required Education? But we already have Required Education under Requirements. Qualifications could be Preferred Education/Experience. Skills: Supervisory responsibilities? No; maybe also Skills/Knowledge/Abilities section includes supervisory responsibilities? No. Could be empty; we should not create Skills section if no specific content. The posting says "Skills / Knowledge / Abilities Does this position have supervisory responsibilities? No". That's basically a statement that there are no supervisory responsibilities. That's not a skill. Could we treat as Skills section with that line? It's not a skill but it's content. Might be considered Skills section. However instruction: 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. The Skills section content is "Does this position have supervisory responsibilities? No". That's specific content (though it's a negative). It's not filler. So we could include Skills heading with that line as a

. But maybe better to put under Requirements? However the heading Skills is allowed. We'll include Skills with that statement. Now Benefits: The Why Join Us paragraph includes list: Exceptional benefits package. A formal mentoring program to support your professional development Access to a staff development fund for continued learning and skill building Dedicated staff recognition programs that celebrate your contributions A shared commitment to making the University of Kentucky the University of, for, and with Kentucky. Join us in shaping the future of teaching and learning—where innovation meets impact. Also a link "Click Here". That's maybe boilerplate? It's a link to more info; could be considered application instruction? Might be considered part of benefits? It's a link to find out more about Martin-Gatton CAFE. Could be considered extra info but not boilerplate. We'll keep the text but maybe drop the link? The instruction: remove application instructions. This link is not exactly application instruction; it's informational. Might keep as part of benefits paragraph. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the benefits list exactly as given. Let's extract the benefits paragraph exactly: "Why Join Us At the Martin-Gatton College of Agriculture, Food and Environment, you’ll find a community that values collaboration, growth, and recognition. Benefits of joining our team include: Exceptional benefits package. A formal mentoring program to support your professional developmentAccess to a staff development fund for continued learning and skill buildingDedicated staff recognition programs that celebrate your contributions A shared commitment to making the University of Kentucky the University of, for, and with Kentucky. Join us in shaping the future of teaching and learning—where innovation meets impact. To find out more about Martin-Gatton CAFE and how the college supports the mission of this being the University of, for, and with Kentucky, Click Here ." We need to keep that exactly, but we can format as

and maybe

• for the list after "Benefits of joining our team include:" The list items are: Exceptional benefits package. A formal mentoring program to support your professional development Access to a staff development fund for continued learning and skill building Dedicated staff recognition programs that celebrate your contributions A shared commitment to making the University of Kentucky the University of, for, and with Kentucky. Join us in shaping the future of teaching and learning—where innovation meets impact. But note the original text lacks punctuation between items; it's a bit messy. We should preserve the exact wording? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should not change the wording, but we can format as list items; that might be considered summarizing? However converting a sentence list into
  • is acceptable as it's still preserving the content, not changing meaning. It's typical to reformat. We'll keep the content same but split into items. We need to decide where to split. The phrase: "Benefits of joining our team include: Exceptional benefits package. A formal mentoring program to support your professional developmentAccess to a staff development fund for continued learning and skill buildingDedicated staff recognition programs that celebrate your contributions A shared commitment to making the University of Kentucky the University of, for, and with Kentucky. Join us in shaping the future of teaching and learning—where innovation meets impact." We could make each sentence as an item: - Exceptional benefits package. - A formal mentoring program to support your professional development - Access to a staff development fund for continued learning and skill building - Dedicated staff recognition programs that celebrate your contributions - A shared commitment to making the University of Kentucky the University of, for, and with Kentucky. - Join us in shaping the future of teaching and learning—where innovation meets impact. But note there is missing space between "developmentAccess". In original: "professional developmentAccess". That's likely a typo; we should preserve exactly? If we split, we might lose that typo. Safer to keep as a single paragraph without list? But instruction says use
    • for any list of duties/requirements/benefits. So we should make a list. We could keep the exact string as one list item? That would be weird. Better to preserve the content but we can keep the typo as is within an item: "A formal mentoring program to support your professional developmentAccess to a staff development fund for continued learning and skill building". That preserves the typo. Then next item: "Dedicated staff recognition programs that celebrate your contributions". Next: "A shared commitment to making the University of Kentucky the University of, for, and with Kentucky." Next: "Join us in shaping the future of teaching and learning—where innovation meets impact." plus the first item "Exceptional benefits package." Thus list items: - Exceptional benefits package. - A formal mentoring program to support your professional developmentAccess to a staff development fund for continued learning and skill building - Dedicated staff recognition programs that celebrate your contributions - A shared commitment to making the University of Kentucky the University of, for, and with Kentucky. - Join us in shaping the future of teaching and learning—where innovation meets impact. We also need to keep the introductory sentence: "Why Join Us At the Martin-Gatton College of Agriculture, Food and Environment, you’ll find a community that values collaboration, growth, and recognition." That's separate paragraph before list. Now Responsibilities: Job Summary paragraph: "The Principal Extension Specialist serves as a senior Extension leader providing statewide leadership in outreach, strategic partnerships, organizational development, and advisory system support. The position leads complex, high-visibility initiatives that advance the Cooperative Extension mission. The individual develops innovative solutions to organizational challenges, builds consensus among stakeholder groups, and represents Cooperative Extension in statewide and national forums." We'll put that as

      under Responsibilities. Requirements: Required Education PhD, Required Related Experience 5 yrs, Required License/Registration/Certification Driver’s License required, Physical Requirements Lifting, pushing or pulling objects up to 50 lbs. We'll make a list. Qualifications: Preferred Education/Experience Doctoral degree. (Note: Required Education already PhD; Preferred Education/Experience Doctoral degree is similar but we keep.) Skills: "Does this position have supervisory responsibilities? No". We'll put as

      . Pay: Salary Range $73,861-121,888/year. Schedule: Shift Primarily days, some possible evening and weekend activities. We might also include Work Location and Department as part of About the role? But we have no About the role heading; we could use About the role for a short paragraph containing department and location. However we already have Responsibilities covering job summary; we could add About the role as a brief intro: "Department: 81170:Program and Staff Development. Location: Lexington, KY." But we must not repeat job title. It's okay. But we need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for all except maybe About the role. We could put department and location there. That's minor metadata but we can include as short paragraph. Now ensure we don't include boilerplate: remove EEO etc. Also remove "