Applications Administrator IV (IT Systems)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Given text: Department: Location: Belknap Campus Time Type: Full time Worker Type: Regular Job Req ID: R109287 Minimum Requirements: Bachelor's degree in Business, Computer Science or a related field and six (6) years of relevant experience or an equivalent combination of education and experience. Grade 9 (Salaried). Position Description: The Application Administrator IV position, is a role based in Information Technology Services (ITS) that provides support for departmental software applications. (cloud or on-premise) With limited supervision, the Application Administrator IV provides specialized support for business-critical software applications to ensure systems are configured to align with the University of Louisville (UofL) enterprise technology environment. (Backups, DR, Authentication, Integrations, Security, etc.) Through collaboration with internal ITS Enterprise teams and the campus stakeholders, the Application Administrator IV will be responsible for the following: Essential Duties And Responsibilities Provide specialized support for business-critical departmental software applications including:Serving as a primary contact point for system support. Productive and timely communications with customers. Documentation of system configuration and operations. Ability to effectively communicate complex business processes and technical concepts to a non-technical audience. Ensuring that organizational and customer expectations are met. Promoting continuous process/system improvements. Change management. Ensure system implementation aligns with the overall enterprise technology environment (Backups, DR, Authentication, Integrations, Security, etc.) Daily support and accountability for:System maintenance and upgrade planning/execution. Monitoring and stability of system and integrations. System Administration: Configuration of system and functionality, Integration, Security, Programming/coding (planning, analysis, design, implementation, testing/integration, maintenance). Status reporting. End user training. Seek continuous professional development through training and self-education. Coach, mentor, and cross train with team members. Other duties as assigned. Preferred Qualifications Data integration experience (flat file data imports/exports, SQL, XML, API’s – REST/SOAP, IPaaS). COMPETENCIES Organizational Skills. Computer Programming and/or Software Application Administration. Communication Skills – Verbal and Written. Competency in Microsoft Office programs (Excel, Word, etc.). Compensation Will Be Commensurate To Candidate Experience. Equal Employment Opportunity ... (boilerplate) Assistance and Accommodations ... (boilerplate) We need to remove boilerplate: EEO, assistance, etc. We need to preserve all substantive info. We need sections: About the role (maybe from Position Description?), Responsibilities (Essential Duties And Responsibilities), Requirements (Minimum Requirements), Qualifications (Preferred Qualifications?), Skills (Competencies), Benefits (none? Not mentioned), Pay (Compensation Will Be Commensurate To Candidate Experience - that's vague "commensurate with experience" - we should NOT include Pay section if it's just "commensurate with experience" because that's placeholder/filler. The instruction: 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. So we should NOT include Pay section because it's just "commensurate with experience". Also no Benefits or Schedule mentioned. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills. We need to use

for each section heading. Inside sections: Use

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

  for prose. We need to preserve all substantive info; do not invent or summarize away detail. We need to format content appropriately. Let's extract: About the role: Could be the Position Description paragraph before responsibilities: "The Application Administrator IV position, is a role based in Information Technology Services (ITS) that provides support for departmental software applications. (cloud or on-premise) With limited supervision, the Application Administrator IV provides specialized support for business-critical software applications to ensure systems are configured to align with the University of Louisville (UofL) enterprise technology environment. (Backups, DR, Authentication, Integrations, Security, etc.) Through collaboration with internal ITS Enterprise teams and the campus stakeholders, the Application Administrator IV will be responsible for the following:" That's basically intro. We'll put that as prose

  . Responsibilities: The list after "Essential Duties And Responsibilities". It includes bullet-like sentences separated by periods. We need to turn each duty into

• . Let's extract each duty: - Provide specialized support for business-critical departmental software applications including: Actually that's a heading then list? The text: "Provide specialized support for business-critical departmental software applications including:Serving as a primary contact point for system support. Productive and timely communications with customers. Documentation of system configuration and operations. Ability to effectively communicate complex business processes and technical concepts to a non-technical audience. Ensuring that organizational and customer expectations are met. Promoting continuous process/system improvements. Change management. Ensure system implementation aligns with the overall enterprise technology environment (Backups, DR, Authentication, Integrations, Security, etc.) Daily support and accountability for:System maintenance and upgrade planning/execution. Monitoring and stability of system and integrations. System Administration: Configuration of system and functionality, Integration, Security, Programming/coding (planning, analysis, design, implementation, testing/integration, maintenance). Status reporting. End user training. Seek continuous professional development through training and self-education. Coach, mentor, and cross train with team members. Other duties as assigned." We need to split into items. The text includes colon after "including:" then list separated by periods. Also after "Daily support and accountability for:" then list. We'll treat each sentence as a duty item. Let's list them: 1. Serving as a primary contact point for system support. 2. Productive and timely communications with customers. 3. Documentation of system configuration and operations. 4. Ability to effectively communicate complex business processes and technical concepts to a non-technical audience. 5. Ensuring that organizational and customer expectations are met. 6. Promoting continuous process/system improvements. 7. Change management. 8. Ensure system implementation aligns with the overall enterprise technology environment (Backups, DR, Authentication, Integrations, Security, etc.) 9. System maintenance and upgrade planning/execution. 10. Monitoring and stability of system and integrations. 11. System Administration: Configuration of system and functionality, Integration, Security, Programming/coding (planning, analysis, design, implementation, testing/integration, maintenance). 12. Status reporting. 13. End user training. 14. Seek continuous professional development through training and self-education. 15. Coach, mentor, and cross train with team members. 16. Other duties as assigned. We could also include "Provide specialized support for business-critical departmental software applications" as a duty but it's covered by the list. We'll output as
  • items. Requirements: Minimum Requirements: "Bachelor's degree in Business, Computer Science or a related field and six (6) years of relevant experience or an equivalent combination of education and experience. Grade 9 (Salaried)." That's the requirement. We'll put as

    maybe with bullet? It's not a list but we can put as

    . Could also split into two sentences: Bachelor's degree... and six years... or equivalent combination. Grade 9 (Salaried). We'll keep as

    . Qualifications: Preferred Qualifications: "Data integration experience (flat file data imports/exports, SQL, XML, API’s – REST/SOAP, IPaaS)." That's a qualification. We'll put as

    or maybe as

    • if list. It's a single sentence; we can put as

      . Skills: COMPETENCIES: "Organizational Skills. Computer Programming and/or Software Application Administration. Communication Skills – Verbal and Written. Competency in Microsoft Office programs (Excel, Word, etc.)." These are separate items separated by periods. We'll make

      • each. Thus sections:

        About the role

        ... (the intro paragraph)

        Responsibilities

        • ... each duty

        Requirements

        Bachelor's degree in Business, Computer Science or a related field and six (6) years of relevant experience or an equivalent combination of education and experience. Grade 9 (Salaried).

        Qualifications

        Data integration experience (flat file data imports/exports, SQL, XML, API’s – REST/SOAP, IPaaS).

        Skills

        • Organizational Skills
        • Computer Programming and/or Software Application Administration
        • Communication Skills – Verbal and Written
        • Competency in Microsoft Office programs (Excel, Word, etc.)
        We must not include Benefits, Pay, Schedule. Check for any other sections: maybe "About the role" could be named "About the role" as per instruction. Good. We need to ensure we don't repeat job title as heading; we aren't. We need to drop metadata like Department, Location, Time Type, Worker Type, Job Req ID. Those are minor metadata; we can drop them or fold into short

        . The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." We can drop them entirely; they are not substantive. So we omit. We need to preserve all substantive information: we have captured the description, responsibilities, requirements, qualifications, competencies. Did we miss anything like "Grade 9 (Salaried)"? Included in Requirements. Check if any other substantive: maybe "Position Description:" we used. Check if any other details like "cloud or on-premise" included in intro. Check if any other details like "Backups, DR, Authentication, Integrations, Security, etc." included in duties. Check if any other details like "End user training" included. Check if any other details like "Seek continuous professional development through training and self-education." included. Check if any other details like "Coach, mentor, and cross train with team members." included. Check if any other details like "Other duties as assigned." included. All good. Now output only HTML fragment. Make sure to properly escape any special characters like apostrophes? It's fine. We'll output:

        About the role

        The Application Administrator IV position, is a role based in Information Technology Services (ITS) that provides support for departmental software applications. (cloud or on-premise) With limited supervision, the Application Administrator IV provides specialized support for business-critical software applications to ensure systems are configured to align with the University of Louisville (UofL) enterprise technology environment. (Backups, DR, Authentication, Integrations, Security, etc.) Through collaboration with internal ITS Enterprise teams and the campus stakeholders, the Application Administrator IV will be responsible for the following:

        Responsibilities

        • Serving as a primary contact point for system support.
        • Productive and timely communications with customers.
        • Documentation of system configuration and operations.
        • Ability to effectively communicate complex business processes and technical concepts to a non-technical audience.
        • Ensuring that organizational and customer expectations are met.
        • Promoting continuous process/system improvements.
        • Change management.
        • Ensure system implementation aligns with the overall enterprise technology environment (Backups, DR, Authentication, Integrations, Security, etc.)
        • System maintenance and upgrade planning/execution.
        • Monitoring and stability of system and integrations.
        • System Administration: Configuration of system and functionality, Integration, Security