Associate Registrar

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as 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 parse the posting and decide which sections to include. The posting includes: - Position Information: Position/Classification Title, Working Title, Position Number, FLSA Exempt, Appointment Type, Tenure Track No, FTE, Department Hiring Range, salary competitive determined based on candidate's background, etc. This includes salary info: "The salary is competitive and will be determined based on the candidate’s educational background, relevant experience, qualifications, and demonstrated expertise." That's not a specific number, but it's a statement about salary. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary is competitive and will be determined based on... That's a statement about pay. So we could include a Pay section with that statement. However, we must avoid filler like "commensurate with experience". This is similar but not exactly filler; it's a statement that salary is competitive and will be determined based on... That's substantive enough? It's not a specific number but it's a statement. The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "The salary is competitive and will be determined based on the candidate’s educational background, relevant experience, qualifications, and demonstrated expertise." is somewhat generic but not exactly placeholder like "commensurate with experience". It's still vague but maybe acceptable. However, they said "Prefer a few substantive sections over many thin ones." Might be better to combine Pay into a Benefits section? But Benefits section is separate. We have Employee Benefits listed: Accrued Vacation and Sick Leave, Community Service Leave, NC State – Health Benefits, NCFlex – Vision, Dental, Flexible Spending Account, Life Insurance and more, 11-12 Paid Holidays, Teachers and State Employees Retirement System (TSERS), Optional Supplemental Plans – 401k, 403b, 457b and 457, Employee Assistance Program (EAP), Campus Recreation Center Discount, University Bookstore Discount and more. That's substantive. We have Primary Function of Organizational Unit, Primary Purpose of Position, Required Knowledge, Skills, And Abilities, Minimum Education/Experience, Licenses or Certification required by Statute or Regulation (n/a), Pre-Employment Requirement (but we should remove application instructions). Also Primary Responsibilities And Duties broken into functions: Planning and Organizing, Project Management, Technical Knowledge, Technical Support. Those are duties. We need to decide sections: About the role (maybe overview), Responsibilities (duties), Requirements (minimum education/experience, knowledge/skills), Qualifications (maybe same as requirements?), Skills (maybe separate), Benefits, Pay, Schedule. We need to avoid duplication. The posting includes "Position Overview" (the Eagle etc). That's about the role. So we can have About the role section with that prose. Responsibilities: we have Primary Responsibilities And Duties with subfunctions. We can combine into a

  list of duties. Requirements: Minimum Education/Experience, Required Knowledge, Skills, And Abilities (these are skills/abilities). Could be Requirements section. Qualifications: maybe same as Requirements; but we could combine. Skills: maybe separate list of skills from Required Knowledge, Skills, And Abilities. Benefits: we have Employee Benefits list. Pay: we have salary statement. Schedule: we have FTE 1 = 40 hours/week, 12 months. That's schedule info: full-time, 40 hours/week, 12 months. So we can include Schedule section. We must not include boilerplate like EEO, Pre-Employment Requirement (application instructions), Licenses or Certification required by Statute or Regulation (n/a) - we can drop n/a. Also remove duplicated lines. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the specifics: e.g., "Working knowledge of the Banner Student Module, including functional processes and activities related to student registration, records, and other Registrar operations." etc. We need to keep those as list items. We need to avoid repeating job title as heading. The title is "465016: IT Systems Support Professional, Systems Administrator Working Title Associate Registrar". We should not repeat that as heading. We need to not put Job ID / requisition numbers as headings; we can fold minor metadata into a short

  or drop it. The posting includes Position Number 601810, etc. We could drop them or include in a short paragraph at top maybe. But we should not create a heading for them. We could include a

  with metadata like "Position Number: 601810; FTE: 1 (40 hours/week, 12 months); FLSA: Exempt; Appointment: Permanent - Full Time". But we need to avoid duplication with Schedule section. Maybe we can include a short paragraph at top with Position Number and FTE, but we also have Schedule section later. Might be okay. But we need to preserve ALL substantive information. So we need to keep Position Number, FLSA, Appointment Type, Tenure Track No, FTE, Department Hiring Range (maybe not given). The Department Hiring Range is mentioned but no value. Actually "Department Hiring Range" line appears but no value after. Might be placeholder; we could drop if no substantive content. We need to remove boilerplate like EEO, equal-opportunity, scam-warning, etc. Also remove "Pre-Employment Requirement" details about application instructions (must complete electronic application, resumes not accepted, veteran's preference forms, background check, E-Verify). Those are application instructions; we should remove them. Also remove "Equal Opportunity Employer" block. Also remove "Work Location Fully On-site (dedicated office at Duty Station)" maybe we can keep as part of schedule or a note? It's substantive about work location. Could be included in Schedule or a separate section? There's no heading for Work Location; we could include in Schedule section or a short paragraph. We need to output only HTML fragment, no /, no markdown. Let's structure:

  About the role

  ... (the Position Overview paragraph)

  Responsibilities

  • ... each duty from Primary Responsibilities And Duties (maybe combine subfunctions into list items)

  Requirements

  • ... Minimum Education/Experience items
  • ... Required Knowledge, Skills, And Abilities items (maybe split into skills)
  Alternatively separate Skills section. But we need to avoid too many thin sections. Could combine Requirements and Skills into one Requirements section that includes both education/experience and skills. But the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require all; we can pick those that have content. We have content for About the role, Responsibilities, Requirements (education/experience), Skills (knowledge/abilities), Benefits, Pay, Schedule. Qualifications maybe same as Requirements; we could omit Qualifications to avoid thin. Let's decide sections: - About the role - Responsibilities - Requirements (includes Minimum Education/Experience and Required Knowledge, Skills, And Abilities) - Benefits - Pay - Schedule We could also include a short metadata paragraph at top (Position Number, FTE, etc.) but maybe we can fold into Schedule or About. Better to include a short

  with Position Number and FTE before sections. But we must not repeat job title as heading; we can include a

  with the position number and classification title? The classification title is part of job title; we might avoid repeating it. But we can include "Position Number: 601810" etc. Let's extract substantive content: Position Overview paragraph: "Be an Eagle - Where Purpose Takes Flight! Are you ready to make an impact? At North Carolina Central University (NCCU), we are more than an institution—we are a community rooted in a legacy of excellence and transformation. A historically Black university located in Durham, North Carolina, also known as ‘The City of Medicine,’ NCCU has been a cornerstone of education since 1910, fostering innovation and progress. Join our team and enjoy a comprehensive benefits package and exclusive perks designed to support your work-life balance. At NCCU, your professional growth will be nurtured, and your contributions will help shape the future for our students and the community we serve. Become part of a legacy that drives change and achievement. An opportunity awaits you at NCCU, where your purpose can take flight. Visit NCCU.edu." We need to keep that. Responsibilities: from Primary Responsibilities And Duties: Function Planning and Organizing: - Provide strategic leadership and operational oversight of the Office of the Registrar including the administration, integrity, security, and maintenance of student academic records and related services. - Direct and coordinate all functions associated with registration, grading, transcripts, degree conferral, academic standing, records retention, classroom scheduling, enrollment reporting, and graduation processing. - Establish divisional priorities, operational goals, and service standards aligned with institutional strategic objectives and student success initiatives. - Regularly assists management in establishing work standards, standard processes and references. - Provide leadership for staff development, succession planning, cross-training, organizational effectiveness, and continuous process improvement initiatives to ensure high-quality service delivery and operational continuity. Function Project Management: - Maintain institutional compliance associated with FERPA, NCAA, VA certification, state authorization, financial aid enrollment reporting, academic calendar structures, curriculum coding, instructional modalities, and other regulatory requirements affecting student records and academic operations. - Manages complex projects. - Develops project plans, manages milestones and drives project forward. - Accountable for keeping projects on track. Function Technical Knowledge: - Serve as the institutional authority for the operationalization of approved curricular actions, including the creation of new academic programs, certificates, concentrations, and courses; modifications to existing curriculum; program deactivations and discontinuations; modality changes; and implementation of academic policy updates. - Ensure curricular changes are accurately translated into institutional systems, student-facing materials, degree audit structures, reporting frameworks, and compliance documentation. - Collaborate with Academic Affairs, academic colleges, admissions, marketing, advising, and other campus stakeholders to support timely and coordinated implementation of curricular and programmatic changes. - Serves as an experienced technical resource to technicians and analysts. - Uses detailed understanding of technical issues to design architecture for stable technologies and provides direction for technicians and other analysts. Function Technical Support: - Serve as the functional lead for student systems within the Registrar’s operational scope, including system enhancements, workflow improvements, data governance, reporting structures, integrations, and process automation initiatives. - Provide leadership for implementation and ongoing support of technologies related to registration, degree audit, curriculum management, catalog management, scheduling, and academic records. - Serves as a key resource in