Lead Network Engineer

We need to output HTML fragment with sections: About the role (maybe "Who We Are" and "Job Summary"? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We need to preserve all substantive info, remove boilerplate like Apply Now, How to Apply, cookie/navigation/legal/EEO, duplicated lines, application instructions. Also remove "Apply Now" repeated. Also remove "Job Detail" etc. We need to decide sections: "About the role" could combine Who We Are and Job Summary. "Responsibilities" from Responsibilities* bullet list. "Requirements" maybe combine Required Qualifications and Desired Qualifications? Or separate "Qualifications". The instruction list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "Qualifications" for required and desired. "Skills" maybe not needed if covered. "Benefits" from Why Work at Michigan? Benefits list. "Pay" from salary range and also salary figure later. There's also "Underfill Statement" with salary range for senior level $87,338 - $97,043, and later "Salary $103,040.00 - $114,488.00". Which is correct? The posting includes both: Underfill Statement says salary range for senior level is $87,338 - $97,043. Additional Information includes Must meet... Work is primarily remote... Then later "Salary $103,040.00 - $114,488.00". Likely the actual salary range is the latter. We need to preserve ALL substantive information, so include both? Might be contradictory but we must keep both as they appear. Could combine into Pay section with both ranges noted. However we should not invent or summarize away detail. So we include both statements. Schedule: The posting mentions hybrid with occasional in person days in Ann Arbor, Work is primarily remote currently, but there are times when on site work is necessary sometimes with short notice, May require working during non-business hours and on weekends, Modes of Work Hybrid Full/Part Time Full-Time. So we can include Schedule section with hybrid/remote details. We must not include sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /. Use

for headings,

• for lists,

  for prose. We need to avoid repeating job title as heading. So no heading for Lead Network Engineer etc. We need to drop Job ID etc. So we can include a short

  for metadata like Job Opening ID etc? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph with Job Opening ID etc maybe but it's minor. Could drop it entirely. Safer to drop. We need to remove duplicated lines, boilerplate like EEO, application instructions, "Apply Now", "How to Apply", "Learn more about the work modes", "Underfill Statement" maybe keep as it's substantive? It includes salary range. Keep. We need to keep "Who We Are" content, "Job Summary". We'll combine into About the role. Let's extract content: Who We Are paragraph(s): "Information and Technology Services (ITS) supports U-M faculty, researchers, staff, and students in their use of technology to teach, learn, research, and work, and be leaders in their fields. We are dedicated to creating cohesive digital experiences and promoting university wide innovations. ITS's mission is to be trusted enablers of technology for the U-M community. ITS works together to provide cohesive digital experiences and seamless support to the U-M community. The Network Engineering and Architecture team is responsible for the design of all computer networks at the University of Michigan. For more information about ITS, visit: https://its.umich.edu/about." Job Summary paragraph: "Information and Technology Services (ITS) is looking for a Network Engineer Lead for the Network Engineering and Architecture Team. In this role you will provide leadership to the WI-FI group within the team. You will also lead complex projects that require expert technical proficiency in Wi-Fi network technology. You will collaborate with team members and provide consultation to other technical teams to develop and implement new network systems. You are expected to assist the Network Operations Team in resolving problems, which may be at an end user level or on the network side. As part of project work you will develop instructions for the installation and upgrades of systems and may actually implement the work. You will report to the Network Planning Manager. This job is hybrid with occasional in person days in Ann Arbor." Responsibilities bullet list (under Responsibilities*): - Technical Leadership Guide the design, support and operational implementation for new technology and product deployments for the UM campus Provide a lead technical consulting role to project managers and customers to ensure optimal network design and deployment strategies Collaborate with multiple IT teams and advise on new products/technologies, conduct research to support recommendations Represent the team on university committees and hold seminars with appropriate audiences to support knowledge sharing Participate in Higher Education Networking groups, such as the BTAA Network Group Participate in strategic planning and setting of technical direction - Project Implementation/Problem Resolution Design networks using established guidelines and customer requirements. Review the design, bill-of-material, project costs, drawings, documentation, and configuration specifications for implementations created/proposed by the engineering team Prepare and publish detailed documents for completed network designs including RF design, wired network design, and associated CAD details Develop and present procedural documentation for the team and other technical staff Develop RFPs (requests for proposal), reviews bids and consult on bidder selection Guide lower level engineers through root-cause analysis of network infrastructure failures Provide accurate estimates for budget, time, and tasks; identifies impacted teams; and notifies management of potential risks and issues Required Qualifications* bullet list: - Bachelor degree in electrical engineering, computer engineering, or a related field and/or equivalent combination of education, certification and experience - Minimum of 6 years of related experience with HPE/Aruba Wi-Fi, specifically the administration of the system with AOS 8 or newer - Minimum of four years experience in a related role requiring confidentiality, timeliness, customer service, organization, prioritization, troubleshooting, and working independently to successfully assist customers in their utilization of computer and network hardware and software - Demonstrated knowledge of applicable: computer operating systems; Python programming; computer networking; and radio frequency fundamentals - Demonstrated experience determining project objectives and requirements, anticipating and solving problems, and developing standards and guidelines for wireless activities - Proficient with word processing, spreadsheet, and collaboration applications - Knowledge of TIA/EIA (Telecommunication Industry Association/Electronic Industries Alliance) standards and practices - Experience in the design of twisted pair, fiber optic, wireless, and coaxial systems related to customer premise wiring and networking - Proven ability to lead project teams to meet customer expectations - Demonstrated successful performance with coordinating and completing multiple tasks within and across departments to meet changing deadlines - Demonstrated knowledge and skills in negotiation, and conflict resolution - Ability to meet the requirements of driving a U-M vehicle and have a valid driver license with less than 7 points Desired Qualifications* bullet list: - HPE/ Aruba Professional level certification for Campus Access - Aruba Certified Expert, Campus Access Mobility Why Work at Michigan? Benefits paragraph: "In addition to a career filled with purpose and opportunity, The University of Michigan offers a comprehensive benefits package to help you stay well, protect yourself and your family and plan for a secure future. Benefits include: Generous time offA retirement plan that provides two-for-one matching contributions with immediate vestingMany choices for comprehensive health insuranceLife insuranceLong-term disability coverageFlexible spending accounts for healthcare and dependent care expensesDental and Vision InsuranceParental and Maternity Leave" Note there are no spaces between items; we should keep as is but maybe we can split into list items for readability. The instruction: use

  • for any list of duties/requirements/benefits. So we should turn benefits into list items. The benefits string currently is concatenated without spaces; we need to parse: "Generous time offA retirement plan that provides two-for-one matching contributions with immediate vestingMany choices for comprehensive health insuranceLife insuranceLong-term disability coverageFlexible spending accounts for healthcare and dependent care expensesDental and Vision InsuranceParental and Maternity Leave". We need to separate logically: Generous time off; A retirement plan that provides two-for-one matching contributions with immediate vesting; Many choices for comprehensive health insurance; Life insurance; Long-term disability coverage; Flexible spending accounts for healthcare and dependent care expenses; Dental and Vision Insurance; Parental and Maternity Leave. We'll create list items accordingly. Modes of Work section: "Positions that are eligible for hybrid or mobile/remote work mode are at the discretion of the hiring department. Work agreements are reviewed annually at a minimum and are subject to change at any time, and for any reason, throughout the course of employment. Learn more about the work modes." This is somewhat boilerplate but still substantive about work mode. We could include in Schedule section. Underfill Statement: "UM- ITS welcomes a healthy applicant pool so we encourage all interested applicants to apply. We may underfill this position at a lower classification depending on the qualifications of the selected candidate. The salary range for the senior level is $87,338 - $97,043." Additional Information: "Must meet the requirements of driving a U-M vehicle and have a valid driver license with less than 7 pointsWork is primarily remote currently, but there are times when on site work is necessary sometimes with short noticeMay require working during non-business hours and on weekends" Application Deadline etc: boilerplate, can drop. Job Detail etc: drop. We need to include Pay section: we have salary ranges from Underfill Statement and Additional Information? Actually Additional Information includes Must meet... Work is primarily remote... May require... No salary. The salary appears later: "Salary $103,040.00 - $114,488.00". Also Underfill Statement includes senior level salary range $87,338 - $97,043. We'll include both. Schedule section: hybrid with occasional in person days in Ann Arbor; Work is primarily remote currently, but there are times when on site work is necessary sometimes with short notice; May require working during non-business hours and on weekends; Positions eligible for hybrid or mobile/remote work mode at discretion; Work agreements reviewed annually. We'll create Schedule
    • items. Now produce HTML. Structure:

      About the role

      Who We Are content + Job Summary content combined maybe two paragraphs.

      Responsibilities

      • ... each bullet as
      • containing the subpoints? The responsibility list has two main categories with sub-bullets. We could flatten: each line as
      • . Might be okay. We'll list each bullet point as
      • with the text. Similarly for Required Qualifications and Desired Qualifications under

        Qualifications

        maybe separate Required and Desired? Could have two subheadings but not allowed? We can just list all qualifications under Qualifications. But we could also have

        Required Qualifications

        and

        Desired Qualifications

        . The instruction list includes Qualifications as a possible heading; we can use that. We'll do:

        Qualifications

        Required

        maybe not allowed because only h3 headings specified. Better to keep under Qualifications and separate with

        Required:

        etc. But that adds extra markup not prohibited. Safer to just list all qualifications under Qualifications with

        Required:

        then
        etc. But that adds

        not