AI Instructional Designer

We need to output HTML fragment with sections only if real content. 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 substantive info, remove boilerplate. We need to parse posting. Key sections: - About the role: maybe "Primary Purpose Of Organizational Unit" and "Position Summary". Could combine. - Responsibilities: "The AI Instructional Designer will develop, review, and maintain AI fluency content for faculty, staff, and students across the university. Working within the CAIO office and in close collaboration with the Center for Faculty Excellence, the designer will translate complex AI concepts into accessible, high-quality learning experiences tailored to diverse campus audiences." - Requirements: Minimum Education And Experience Requirements: "Master’s or Bachelor’s and 0-2 years’ experience; or will accept a combination of related education and experience in substitution." - Required Qualifications, Competencies, And Experience: list bullet points. - Preferred Qualifications, Competencies, And Experience: list bullet points. - Skills: maybe combine required/preferred? But we have separate sections for Qualifications and Skills. Could put required qualifications under Requirements? Actually we have separate sections: Requirements (maybe education/experience), Qualifications (maybe required qualifications), Skills (maybe competencies). But we can decide. Given instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. Thus we need to decide which sections have content. - About the role: we have description of unit and purpose. Yes. - Responsibilities: we have bullet about developing content. - Requirements: we have minimum education/experience. - Qualifications: we have required qualifications list. - Skills: maybe we could put required qualifications under Qualifications and preferred under Skills? But better to follow typical: Qualifications = required qualifications, Skills = preferred or competencies. However we have both required and preferred qualifications. Could put required under Qualifications, preferred under Skills. Or we could combine both under Qualifications and leave Skills empty (but then we shouldn't emit Skills heading if empty). So we need to decide. We have required qualifications list: Demonstrated experience designing and developing learning content for adult or professional audiences; Working knowledge of and genuine interest in AI tools, including hands-on experience with generative AI platforms; Proficiency with e-learning authoring tools (Articulate Storyline, Rise, Adobe Captivate, or equivalent); Experience developing content in a learning management system (Canvas preferred); Strong writing and editing skills with the ability to translate technical concepts into clear, accessible language; Demonstrated ability to manage multiple projects, meet deadlines, and iterate based on feedback. Preferred qualifications list: Master’s degree in Instructional Design, Educational Technology, Learning Sciences, or a related field; Experience in higher education or faculty development contexts; Knowledge of prompt engineering, AI ethics, data privacy, and responsible AI use sufficient to teach these topics; Experience designing role-based or tiered learning pathways for diverse organizational audiences; Knowledge of learning analytics, assessment design, and data-informed content iteration. We could put required under Qualifications, preferred under Skills. Or we could put both under Qualifications and not have Skills. Since we have both, better to split. Thus: - Qualifications (Required) -> list. - Skills (Preferred) -> list. - Benefits, Pay, Schedule: none provided. So omit those sections. Also we might include "About the role" with description of unit and purpose. Now we need to format: Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. We need to include the location? It's in posting: Position Location North Carolina, US. Could be considered substantive. Where to put? Could be part of About the role or maybe a separate meta but we are told not to put Job ID/requisition numbers as headings; fold minor metadata into a short

  or drop it. Location is minor metadata; we could include in a short

  under About the role or maybe separate paragraph. Since we need to preserve all substantive info, we should include location somewhere. Could add a paragraph after About the role heading:

  Position Location: North Carolina, US.

  Or incorporate into prose. Also we have "Full-time/Part-time FTE 1 Hours Per Week 40" - that's schedule info (40 hrs/week). That's schedule specifics. According to rule: include Schedule section ONLY if posting actually states them. It does state Hours Per Week 40. So we could create a Schedule section with that info. However we must not create Schedule section if content is just "varies", "TBD". Here it's specific: 40 hours per week, FTE 1. So we can include Schedule section with that. Similarly, we have "Proposed Start Date 10/12/2026" and "Estimated Duration of Appointment 8 months". That could be considered under Schedule? Or maybe under About the role? There's no specific heading for start date/duration. Could include in About the role paragraph or maybe a separate "Details" but not allowed headings. We could include in About the role as prose. Also "Hiring Range" not provided (blank). So we skip Pay. Benefits: not provided. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. Check if we need to include "Requirements" heading for minimum education/experience. Yes. Now we need to ensure we don't include boilerplate like "Be a Tar Heel!" etc. That's substantive? It's promotional but still part of posting. We should preserve all substantive information, but we can remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Be a Tar Heel!" is part of the university description; it's substantive? It's fluff but still part of posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that description. However we can condense? Not summarizing away detail; we can keep the prose as is. But we can remove duplicated lines. There's no duplication. Thus About the role section could include the paragraph about being a Tar Heel, the primary purpose, position summary, location, start date, duration, hours. We need to avoid putting job title as heading. Already not. Now format:

  About the role

  Be a Tar Heel! A global higher education leader in innovative teaching, research and public service, the University of North Carolina at Chapel Hill consistently ranks as one of the nation’s top public universities. Known for its beautiful campus, world-class medical care, commitment to the arts and top athletic programs, Carolina is an ideal place to teach, work and learn. One of the best college towns and best places to live in the United States, Chapel Hill has diverse social, cultural, recreation and professional opportunities that span the campus and community. University employees can choose from a wide range of professional training opportunities for career growth, skill development and lifelong learning and enjoy exclusive perks that include numerous retail and restaurant discounts, savings on local child care centers and special rates for performing arts events. As the University’s Chief Academic Officer, the Provost has broad responsibilities for advancing the education and research missions of the University. The Office of the Executive Vice Chancellor and Provost ( OEVCP ) provides the leadership for UNC‑CH’s strategic planning for academic programs. The Provost’s organization ensures the development and enhancement of high quality baccalaureate, masters and doctoral-level programs through ongoing program review and assessment, the raising of academic standards, and the expansion of research and other scholarship/creative activity. The Office of the Vice Provost for Artificial Intelligence leads Carolina’s institutional AI strategy and develops tools, programs, and infrastructure that advance responsible AI use across the university. The office works closely with campus partners including the Center for Faculty Excellence, the University Library, and schools and units across campus. The AI Instructional Designer will develop, review, and maintain AI fluency content for faculty, staff, and students across the university. Working within the CAIO office and in close collaboration with the Center for Faculty Excellence, the designer will translate complex AI concepts into accessible, high-quality learning experiences tailored to diverse campus audiences. Position Location: North Carolina, US. Proposed Start Date: 10/12/2026. Estimated Duration of Appointment: 8 months. Hours Per Week: 40 (FTE 1).

  But we have schedule section separate; maybe we should not duplicate hours in About the role if we have Schedule section. However we can keep location and start date/duration in About the role, and schedule in Schedule section. Thus About the role paragraph includes location, start date, duration maybe. Now Responsibilities: we have a sentence about developing content. Could be a
  • list? It's just one duty; but we can still use
    • for list of duties. Or we could use

      . The rule: Use

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

        for prose. If it's a single item, still could be

        • . But we can also use

          . Safer to use

          • for list. Thus:

            Responsibilities

            • Develop, review, and maintain AI fluency content for faculty, staff, and students across the university.
            • Work within the CAIO office and in close collaboration with the Center for Faculty Excellence to translate complex AI concepts into accessible, high-quality learning experiences tailored to diverse campus audiences.
            Now Requirements: Minimum education/experience. We could put as
            • Master’s or Bachelor’s degree and 0‑2 years’ experience; or equivalent combination of related education and experience.
            Now Qualifications (Required): list bullet points. Now Skills (Preferred): list bullet points. Now Schedule: we have Hours Per Week 40 (FTE 1). Could also include maybe "Full-time". We'll put as

            Full‑time, 40 hours per week (FTE 1).

            Now ensure we don't include any boilerplate like Equal Opportunity Employer Statement etc. Remove. Now output only HTML fragment. Check for any repeated content: We included "The AI Instructional Designer will develop, review, and maintain AI fluency content..." in About the role and also in Responsibilities. That's duplication; we should avoid duplicating lines. The instruction: remove duplicated lines. So we should not repeat the same sentence. In About the role we already included a summary of responsibilities; we should maybe not repeat that exact sentence in Responsibilities. Instead, Responsibilities could list the duties more specifically: develop, review, maintain AI fluency content; collaborate with Center for Faculty Excellence; translate concepts; maybe also "maintain content". We need to ensure we don't duplicate exactly same phrasing. Let's adjust. In About the role we already have a sentence: "The AI Instructional Designer will develop, review, and maintain AI fluency content for faculty, staff, and students across the university. Working within the CAIO office and in close collaboration with the Center for Faculty Excellence, the designer will translate complex AI concepts into accessible, high-quality learning experiences tailored to diverse campus audiences." That's essentially the responsibilities. So we could keep that in About the role and not repeat in Responsibilities. But Responsibilities section expects list of duties; we could still list them but maybe rephrase slightly to avoid duplication. However the instruction says remove duplicated lines, not necessarily avoid similar meaning. Safer to not repeat the exact same sentence. We can keep About the role with the unit description and purpose, but maybe shorten responsibilities to just a high-level statement, and then Responsibilities list the specific duties. Let's craft About the role to focus on unit description, purpose, location, start date