Student Systems Tech Team Manager

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key sections: - About UofSC (description) maybe "About the role"? Actually "About UofSC" is about the organization, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Advertised Job Summary (description of role) -> could be "About the role". Should include summary paragraph. - Key Responsibilities list -> Responsibilities section. - What We're Looking For (list of qualifications/experience) -> could be Requirements or Qualifications. We need to decide: The posting includes "What We're Looking For" with bullet points: Bachelor's degree and 5+ years..., at least 2 years managing..., significant experience supporting a Student Information System..., strong technical knowledge..., experience with application development..., experience planning and executing..., demonstrated ability to troubleshoot..., leadership style..., strong customer-service orientation..., ability to communicate..., commitment to security... This is a mix of requirements and qualifications. We could split into Requirements (education/experience) and Qualifications (skills). But instruction says prefer few substantive sections over many thin ones. Could combine into one "Requirements" section containing all bullet points. Or we could have "Qualifications" for skills and "Requirements" for education/experience. But we need to avoid thin sections. Perhaps one "Requirements" covering all bullet points. - Why Join Us? (benefits/perks) -> could be Benefits section. It lists impact, lead, build team, solve problems, work closely, balance stability, join mission-driven organization. Those are more like selling points, not benefits. Then there is "Perks of the University of South Carolina" bullet list with specific benefits: Downtown COLA Location, Energetic Leadership, etc. Also later: "The University of South Carolina offers a valuable benefits package including but not limited to: - Health and Life Insurance - Retirement Programs - Paid Tuition - Dependent Scholarships - Annual Leave - Sick Leave - 13 Paid Holidays (including an extended December holiday) - Paid Parental Leave - Professional Development Opportunities". That's definitely benefits. Thus Benefits section should include both "Perks of the University of South Carolina" and the benefits package list. Pay: Not mentioned (Advertised Salary Range: Part/Full Time: Full Time but no salary range). So we should NOT include Pay section because no specific salary. Schedule: Not mentioned besides Full Time. Could we include Schedule? The posting says Part/Full Time: Full Time. That's schedule info (full-time). Should we include Schedule section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. "Full Time" is specific content. So we could include Schedule section with "Full Time". However we need to see if they want schedule details like hours, shift etc. "Full Time" is specific enough. We'll include Schedule. Also we have "Advertised Salary Range: Part/Full Time: Full Time". No salary range, so skip Pay. Now we need to output HTML with

headings and appropriate

• for lists,

  for prose. We must not repeat job title as heading. The job title is "Student Systems Tech Team Manager". Not to be used. We need to preserve all substantive information: that includes the About UofSC paragraph, the job summary, responsibilities, what we're looking for, why join us, perks, benefits package, schedule (full time). Also maybe include "Advertised Job Summary" as part of About the role. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. At end there is EEO Statement and a link etc. Remove those. Also remove "Job Close Date", "Special Instructions to Applicant", etc. Those are application instructions/boilerplate. Remove. Also remove "Minimum And Additional Requirements Knowledge/Skills/Abilities - Banner student system, Higher Education, Development Life Cycle." That seems like a heading but not substantive? It's a line: "Minimum And Additional Requirements Knowledge/Skills/Abilities - Banner student system, Higher Education, Development Life Cycle." Might be considered part of requirements but it's vague. Could include as part of Requirements? It says "Minimum And Additional Requirements Knowledge/Skills/Abilities - Banner student system, Higher Education, Development Life Cycle." That's somewhat redundant with other bullets. Might be considered boilerplate? It's not a list, just a phrase. Might be safe to include as a sentence in Requirements? But it's not a bullet; it's a line. Could treat as part of Requirements prose. But we need to preserve ALL substantive information. So we should include that line somewhere. However it's not clear if it's substantive. It mentions "Banner student system, Higher Education, Development Life Cycle." That's somewhat covered elsewhere. But to be safe, we can include it as a sentence in Requirements. Also "Preferred Qualifications Preferred Qualifications - Minimum of 2 years managerial experience. - Experience with Student Information Systems (e.g., Banner, PeopleSoft or similar). - Strong knowledge of databases (SQL), system integrations, and data management. - 5+ years Banner Student Systems experience." This duplicates some of What We're Looking For. It's a separate section but similar. We should include those bullets as part of Requirements/Qualifications but avoid duplication? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines. So we need to deduplicate identical content. The Preferred Qualifications list overlaps with What We're Looking For. We need to keep only one instance of each distinct bullet. Let's extract distinct bullets: From What We're Looking For: - Bachelor's degree and 5+ years of relevant professional experience, or an equivalent combination of education, certification, training, and experience. - At least 2 years of experience managing or supervising technical professionals. - Significant experience supporting a Student Information System, with 5+ years of Ellucian Banner Student experience strongly preferred. - Strong technical knowledge of databases, SQL, system integrations, APIs/interfaces, data management, and enterprise application architecture. - Experience with application development and the full software development lifecycle, including design, testing, deployment, maintenance, and change management. - Experience planning and executing enterprise application upgrades, patches, configuration changes, and production deployments. - Demonstrated ability to troubleshoot complex production application and integration problems and lead effective root-cause analysis. - A leadership style that develops people, encourages collaboration, builds technical depth, and holds teams accountable for results. - Strong customer-service orientation and the ability to build trusted relationships with both technical and nontechnical partners. - Ability to communicate complex technology issues clearly to audiences ranging from developers to functional leaders and senior management. - Commitment to security, documentation, operational discipline, continuous improvement, and reliable production support. From Preferred Qualifications: - Minimum of 2 years managerial experience. (similar to at least 2 years managing) - Experience with Student Information Systems (e.g., Banner, PeopleSoft or similar). (similar to significant experience supporting a SIS) - Strong knowledge of databases (SQL), system integrations, and data management. (subset of strong technical knowledge) - 5+ years Banner Student Systems experience. (similar to 5+ years Banner Student experience) Thus many duplicates. We should keep the more detailed bullets from What We're Looking For and discard the Preferred Qualifications duplicates. Also keep any unique info: maybe "Minimum of 2 years managerial experience" is same as at least 2 years managing. So duplicate. Thus we will keep the What We're Looking For list as the requirements. Now "Minimum And Additional Requirements Knowledge/Skills/Abilities - Banner student system, Higher Education, Development Life Cycle." This is a short phrase; could be considered a requirement but it's vague. Might be considered boilerplate? It's not a list, just a phrase. Might be safe to include as a sentence in Requirements. Now "Why Join Us?" bullet list: we can treat as Benefits? Actually it's more about role benefits. Could be part of Benefits section. But we also have explicit "Perks of the University of South Carolina" and benefits package. We could combine all under Benefits. Thus Benefits section will contain: - Make an impact that matters. The systems you lead directly support students and some of the university's most important academic and administrative processes. - Lead, don't just maintain. This role has the opportunity to improve technical practices, modernize processes, strengthen integrations, and influence the future direction of USC's Student Systems environment. - Build a great team. You'll lead six technical professionals and have the opportunity to develop talent, expand knowledge across the team, and create a strong engineering and customer-service culture. - Solve interesting problems at enterprise scale. Banner and its surrounding ecosystem touch numerous applications, integrations, business processes, and university organizations. - Work closely with the people who use what you build. You'll partner directly with Admissions, Registrar, Financial Aid, academic organizations, and other university stakeholders. - Balance stability with modernization. You'll be responsible for keeping critical systems dependable today while helping USC improve and modernize them for tomorrow. - Join a mission-driven organization. Your technical leadership ultimately supports education, research, faculty, staff, and student success rather than simply delivering technology for its own sake. - Perks of the University of South Carolina: - Downtown COLA Location. Enjoy working in the heart of Columbia, SC, with easy access to vibrant city life, dining, and cultural events. - Energetic Leadership. Thrive under the guidance of an energetic and innovative leadership team dedicated to transforming IT at USC, making your role impactful and exciting. - The University of South Carolina offers a valuable benefits package including but not limited to: - Health and Life Insurance - Retirement Programs - Paid Tuition - Dependent Scholarships - Annual Leave - Sick Leave - 13 Paid Holidays (including an extended December holiday) - Paid Parental Leave - Professional Development Opportunities We need to format as

  • . For each bullet we can have
  • containing the text. For sub-bullets (like under Perks) we could nest
    but not required; we could just treat each as separate
    • . However the instruction: Use
      • for any list of duties/requirements/benefits. So we can have nested lists if needed but not required. Simpler: each bullet as
      • . For the "Perks of the University of South Carolina" heading we could treat as a

        then a

        . Similarly for benefits package. Thus Benefits section will have a mix of

        prose and

        lists. Now Schedule section: we have "Part/Full Time: Full Time". So we can output

        Full Time

        under Schedule heading. Now About the role: we need to include the Advertised Job Summary paragraph(s) and maybe the About UofSC description? The About UofSC is about the institution, not role. But we could include it under About the role? The instruction says use headings like About the role, Responsibilities, etc. About UofSC could be considered "About the role" context? Might be better to include it as a paragraph under About the role. However the About UofSC is generic about the university, not specific to role. But it's substantive info about the employer. Could we create a separate section like "About the University"? Not in allowed headings. So we must fit into allowed headings. The allowed headings are limited; we could put the About UofSC paragraph under About the role as a description of the organization. That seems acceptable. Thus About the role section will contain: - The About UofSC paragraph (multiple sentences).