Tech Int Eng II

We need to output HTML fragment with sections: About the role? The posting includes description of duties, responsibilities, department, compensation, required qualifications, preferred qualifications, work location, etc. We must not repeat job title as heading. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have content for responsibilities (list of duties). We have required qualifications and preferred qualifications (these could be under Requirements or Qualifications). We have compensation (pay range). We have benefits info (mention benefits package but no specifics). The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits: posting says "Benefits Information Universities of Wisconsin employees receive an excellent benefits package. To learn more..." It's vague but states they receive benefits package. That's real content? It says they receive an excellent benefits package, but no specifics. The rule: 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. Benefits: they state they receive an excellent benefits package, but no specifics. Is that considered filler? It's vague but still states they receive benefits. Might be considered substantive enough? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but not details. Might be okay to include Benefits section with a short paragraph summarizing that they receive excellent benefits package and link to more info. However, we must not invent details. We can include a

that says they receive an excellent benefits package; refer to link for details. That's not inventing. Pay: they give a salary range $75,000 - $85,700. So we can include Pay section. Schedule: they mention full-time, salaried (exempt), academic staff position. Also mention Telecommuting or hybrid work options may be approved. That's schedule info (full-time, flexible work). So we can include Schedule section. We need to avoid boilerplate like EEO, accommodation request, criminal background check, etc. Remove those. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the duty list exactly as given, but we can format as

• . Must not repeat job title as heading. We need to decide sections: About the role (maybe a brief overview), Responsibilities, Requirements (or Qualifications), Skills (maybe combine required/preferred?), Pay, Benefits, Schedule. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Required and Preferred qualifications into a "Qualifications" section with subpoints? But we must use

  for section headings only; inside we can have

  or

  . We could have a Qualifications section with two subheadings? Not allowed because only

  for section headings; we could still have or

  but not extra headings. Better to have separate sections: Requirements (maybe required qualifications) and Preferred Qualifications? But that adds many sections. Could combine into one "Qualifications" section with both required and preferred listed, maybe marking required vs preferred in text. That would be fewer sections. We also have Department description (OLITS). Could be part of About the role. Thus sections: About the role (includes department overview and role description), Responsibilities, Qualifications (required and preferred), Pay, Benefits, Schedule. Check each for real content. About the role: we have description: "Designs, implements, and maintains technical integrations across multiple systems..." plus department description. That's substantive. Responsibilities: list of key activities. Qualifications: required and preferred qualifications. Pay: salary range. Benefits: statement about excellent benefits package and link. Schedule: full-time, salaried (exempt), telecommuting/hybrid options. We must not include Job ID etc. Now produce HTML fragment. We need to use

  for each section heading. Inside sections, use

  for prose,

  • for lists. We must not include markdown code fences. Let's craft. About the role: combine initial duties and department description. Paragraph: "Designs, implements, and maintains technical integrations across multiple systems, including in-house systems, acquired commercial, and external such as Cloud hosted Software as a Service (SaaS) applications. Provides day-to-day maintenance and long-term assistance to ensure subsystems and infrastructure function together, and business needs are met." Then department paragraph: "The Office of Learning & Information Technology Services (OLITS) is dedicated to supporting the use of technology to enhance the teaching and learning mission of the UW System universities. OLITS staff have responsibility for systemwide collaboration and enhancement of six major areas of Information Technology: overall systemwide IT planning; technology for teaching and learning; development of major administrative systems; wide area networking issues; library automation and collections enhancement; and research and development in emerging technologies. In addition, OLITS develops and supports information technology systems and services that allow UW System Administration staff to effectively and efficiently perform their responsibilities." That's fine. Responsibilities: list the bullet points from "Key Job Responsibilities Responsibilities include the following key activities:" then each item. We need to ensure we keep all items exactly as given. List: - Integrates, identifies, troubleshoots, monitors, and resolves moderately complex, routine, and varied supported services, systems, network, and application problems according to established processes and procedures - Develops, programs, tests, and maintains automation solutions and scripts to improve system functionality, efficiency, and reliability - Serves as a point of contact for internal and external stakeholders, identifies needs, provides solution options, and communicates issue updates and resolutions - Participates in the evaluation of new vendor software releases and impacts. - Documents and communicates system enhancements or changes - Assists with the planning and coordination of system resources, upgrades, security, implementations, and integrations - Configures, maintains, upgrades, develops, and tests IT systems and services in alignment with industry best practices - Runs, maintains, and operates technical systems and infrastructure - Plans and directs staff implementation of small to medium technical projects as needed Make each as
  • . Qualifications: we need required and preferred. We could have a

    stating "Required Qualifications:" then a

    for required, then another

    for "Preferred Qualifications:" then

    for preferred. That's okay inside same section. Required Qualifications: - Bachelor's degree in computer science, information technology, related field, or 2+ years of experience supporting IT services and systems in a complex organization. - Proficiency with automation of tasks utilizing API’s - Experience with scripting/languages (Python, PowerShell, Perl, etc.) Preferred Qualifications: - One or more years in DevOps or related role - AWS/Azure/GCP experience - Proficiency in Python/Bash - CI/CD tooling (Jenkins/GitLab) - Docker/Kubernetes - IaC tools - Strong collaboration skills - Experience with AI development, Copilot Studio or AWS Bedrock - Experience with cloud applications, M365, Okta We must keep exact phrasing. Pay: "Well-qualified candidates can expect a starting annual salary within a range of $75,000 - $85,700 commensurate with the candidate’s education, related experience, and qualifications." We should not include filler like "commensurate with experience"? That phrase is present but it's part of the sentence. The rule says 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 phrase "commensurate with experience" is considered filler? It's a typical phrase but it's part of the actual sentence. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", ...). That suggests we should not include a section where the only content is that phrase. But we have actual numbers, so it's okay. We can keep the sentence as is. Benefits: "Universities of Wisconsin employees receive an excellent benefits package. To learn more about the benefits package, review the Faculty, Academic Staff & Limited Appointees or University Staff Please see this link for total compensation information: Universities of Wisconsin Health & Retirement Contributions Estimator to provide you with total compensation information." That's a bit messy but we can keep as a paragraph. Schedule: "The Technical Integration Engineer II is a full-time, salaried (exempt), academic staff position. Well-qualified candidates can expect a starting annual salary within a range of $75,000 - $85,700 commensurate with the candidate’s education, related experience, and qualifications." Wait that's pay again. Actually schedule: we have "full-time, salaried (exempt), academic staff position." Also "Work Location: Telecommuting or hybrid work options may be approved. The office location is at 780 Regent Street, Madison, WI. Preference will be given to candidates that reside within the state of Wisconsin. Flexible Work/Telecommuting agreements are subject to change at any time." So schedule section can include full-time, salaried (exempt), and telecommuting/hybrid options. We must not repeat pay info in schedule. Thus schedule paragraph: "This is a full-time, salaried (exempt) academic staff position. Telecommuting or hybrid work options may be approved; the office is located at 780 Regent Street, Madison, WI. Preference is given to candidates residing within the state of Wisconsin, and flexible work/telecommuting agreements are subject to change." Now produce HTML. Check for any boilerplate we must remove: "Current Employees: If you are currently employed at any of the Universities of Wisconsin, log in to Workday to apply through the internal application process." That's internal instruction; we should remove as it's application instructions? It's about internal process; maybe considered application instruction. Remove. "Position Title Tech Int Eng II Job Category Academic Staff Employment Type Regular Job Profile Technical Integration Engineer II" - we should not repeat job title as heading; but we can drop these metadata lines. "Job Duties" heading we already covered in About the role. "Department" we included. "Compensation" we used for Pay. "Required Qualifications" and "Preferred Qualifications" we used. "Work Location" we used in Schedule. "How To Apply", "Contact Information", "Accommodation Request", "Criminal Background Check and Reference Check Policy", "Employment Authorization", "Confidentiality", "Benefits Information", "Clery Act information", "UW is an Equal Opportunity Employer" - all boilerplate to remove. We must preserve all substantive information; we have kept duties, responsibilities, qualifications, pay, benefits, schedule, department description. Now output HTML. Let's craft:

    About the role

    Designs, implements, and maintains technical integrations across multiple systems, including in-house systems, acquired commercial, and external such as Cloud hosted Software as a Service (SaaS) applications. Provides day-to-day maintenance and long-term assistance to ensure subsystems and infrastructure function together, and business needs are met.

    The Office of Learning & Information Technology Services (OLITS) is dedicated to supporting the use of technology to enhance the teaching and learning mission of the UW System universities. OLITS staff have responsibility for systemwide collaboration and enhancement of six major areas of Information Technology: overall systemwide IT planning; technology for teaching and learning; development of major administrative systems; wide area networking issues; library automation and collections enhancement; and research and development in emerging technologies. In addition, OLITS develops and supports information technology systems and services that allow UW System Administration staff to effectively and efficiently perform their responsibilities.

    Res