Senior Network Engineer **UMC Employees Only**

We need to output HTML fragment with sections: Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to parse the posting. Content: - Position Summary: includes description about UMC, employer-paid pension plan, competitive salary & benefits, UMC employees only, not remote, onsite work. Also mention technical lead and subject matter expertise in hospital networking support, designing, developing, installing, testing, maintaining all hospital networks linking computers, peripherals, communication equipment and video equipment using cabling or wireless and software, including routers, switches, access devices and hospital email and active directory systems. - Job Requirement Education/Experience: Equivalent to Bachelor's degree in computer sciences or related field and four (4) increasingly responsible experience in network/internet administration. - Licensing/Certification Requirements: Certain positions may require certification in specific information systems technology programs. - Additional Position Requirements: At least 2 years' experience with Extreme Network gear; at least 2 years' experience support large scale network environment; Cisco / Extreme certifications; Experience installing and configuring network equipment; Ability to analyze and evaluate networks to identify issues; Comprehensive understanding of network design, services and protocols. - Preferred Requirements: Checkpoint Firewall Experience (Managing and/or configuring). - Knowledge Of: long list of knowledge, skills, abilities, physical requirements. - Skill In: list of skills. - Physical Requirements And Working Conditions: mobility, stamina, vision, hearing, speech, strength, agility, reasonable accommodations. - Also mention "EMPLOYER-PAID PENSION PLAN (NEVADA PERS) Competitive Salary & Benefits Package". That's benefits. - No explicit pay amount or schedule. Thus sections: - About the role: could include position summary description of role and organization. - Responsibilities: designing, developing, installing, testing, maintaining all hospital networks... etc. - Requirements: Education/Experience, Licensing/Certification, Additional Position Requirements (Extreme gear, large scale, Cisco/Extreme certifications, installing/configuring, analyzing networks, understanding design), Preferred Requirements (Checkpoint Firewall). Could combine. - Qualifications: maybe same as Requirements? But we need to avoid duplication. Could treat Requirements as education/experience, and Qualifications as certifications/preferred? But guidelines: Use headings only when posting has real specific content. We can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Pay and Schedule omitted because not specified. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include boilerplate like EEO, etc. There's none. We need to use

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

  for prose. Thus we need to decide what is list vs prose. For About the role: could be prose paragraph(s) summarizing role and organization. Responsibilities: list of duties: designing, developing, installing, testing, maintaining all hospital networks that link computers, peripherals, communication equipment and video equipment using cabling methods or wireless transmissions and software. To include; routers, switches, access devices and the hospitals email and active directory systems. We can make each bullet. Requirements: list: Bachelor's degree or equivalent, four years increasingly responsible experience in network/internet administration; licensing/certification may require certification in specific info systems tech programs; at least 2 years experience with Extreme Network gear; at least 2 years experience supporting large scale network environment; Cisco/Extreme certifications; experience installing and configuring network equipment; ability to analyze and evaluate networks to identify issues; comprehensive understanding of network design, services and protocols; preferred: Checkpoint Firewall experience (managing/configuring). Could separate required vs preferred but we can just list all. Qualifications: maybe we can treat as knowledge/skills/abilities? But we already have Skills section. The posting has "Knowledge Of:" and "Skill In:" and "Physical Requirements And Working Conditions:" which could go under Skills and maybe Qualifications? But we need to decide. We could have: - Requirements: education/experience, certifications, experience. - Qualifications: knowledge (list of knowledge areas), skills (list of skill abilities), physical requirements. But the instruction says use headings only when posting has real specific content. We have knowledge, skill, physical requirements sections. So we could have separate headings: Knowledge, Skills, Physical Requirements. However the allowed headings list includes Skills, but not Knowledge or Physical Requirements. But we can still use Skills heading for skill list, and maybe put knowledge under Skills? Or we could combine knowledge and skills under Skills heading. Physical requirements could go under a separate heading? Not in allowed list. Could we put physical requirements under Skills? Might be odd but allowed headings list is not exhaustive? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. It says use

  for section headings (e.g. ...). Likely we should stick to those headings. So we can only use those headings. So we need to map content to those headings. Thus we have: - About the role: description of role and organization. - Responsibilities: duties. - Requirements: education/experience, licensing/certification, additional position requirements (Extreme gear, large scale, Cisco/Extreme certifications, installing/configuring, analyzing networks, understanding design), preferred (Checkpoint Firewall). - Qualifications: maybe we can put knowledge and skill lists here? But we also have Skills heading. Could put knowledge under Qualifications, skills under Skills, physical requirements maybe under Qualifications? Or we could omit physical requirements if not covered? But we must preserve ALL substantive information. Physical requirements are substantive. We need to include them somewhere. Could put them under Skills? Not ideal but maybe acceptable. Or we could create a Qualifications section that includes knowledge, skills, and physical requirements. Then we could also have a Skills section? That would duplicate. Better to have one section for qualifications that includes knowledge, skills, physical requirements. But we also have Skills heading in allowed list; we could still use it but maybe we can omit Skills heading and put skill list under Qualifications. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid using other headings, but suggests these as examples. It says "Use

  for section headings (e.g. ...)". Likely they expect us to use those headings where appropriate. We can choose to not use Skills if we think it's redundant. But we need to preserve skill list. Could put skill list under Qualifications. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Benefits: employer-paid pension plan (Nevada PERS), competitive salary & benefits package. Also maybe mention UMC employees only? That's eligibility not benefit. But we can include benefits: employer-paid pension plan (Nevada PERS), competitive salary & benefits package. We must not include Pay or Schedule sections because not specified. Now we need to format. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • Knowledge: ...
  • Skills: ...
  • Physical requirements: ...

  Benefits

  • Employer-paid pension plan (Nevada PERS)
  • Competitive salary & benefits package
  We need to ensure we preserve all substantive information. Let's extract details. About the role: The posting includes: "Position Summary EMPLOYER-PAID PENSION PLAN (NEVADA PERS) Competitive Salary & Benefits Package UMC Employees Only** As an academic medical center with a rich history of providing life-saving treatment in Southern Nevada, UMC serves as the anchor hospital of the Las Vegas Medical District, offering Nevada’s highest level of care to promote successful medical outcomes for patients. UMC is home to Nevada's ONLY Nonprofit Level I Trauma Center, Verified Burn Center, and Multi-Organ Transplant Center. In 2026, we became the FIRST and ONLY Magnet®-Recognized hospital in the state, reflecting UMC's nursing professionalism, teamwork, and superiority in patient care. **This is not a remote position and will require onsite work.** Position Summary: Provide technical lead and subject matter expertise in hospital networking support. Responsible for designing, developing, installing, testing, and maintaining all hospital networks that link computers, peripherals, communication equipment and video equipment using cabling methods or wireless transmissions and software. To include; routers, switches, access devices and the hospitals email and active directory systems." We need to avoid repeating job title as heading. The "Position Summary" phrase appears but we can incorporate. We need to preserve all substantive info: mention employer-paid pension plan, competitive salary & benefits, UMC employees only, not remote, onsite work, academic medical center, rich history, anchor hospital, Las Vegas Medical District, highest level of care, nonprofit Level I Trauma Center, Verified Burn Center, Multi-Organ Transplant Center, FIRST and ONLY Magnet-recognized hospital in state, nursing professionalism, teamwork, superiority in patient care. Also technical lead and subject matter expertise in hospital networking support. We'll put that in About the role paragraph(s). Could be two paragraphs: one about UMC, one about role. Now Responsibilities: The responsibilities are essentially the same as the position summary: designing, developing, installing, testing, maintaining all hospital networks linking computers, peripherals, communication equipment and video equipment using cabling methods or wireless transmissions and software; to include routers, switches, access devices and the hospitals email and active directory systems. We can list each duty as bullet. Requirements: list: - Equivalent to a Bachelor's Degree in computer sciences or a closely related field and four (4) increasingly responsible experience in network/internet administration. - Licensing/Certification Requirements: Certain positions may require certification in specific information systems technology programs. - Additional Position Requirements: * At least 2 years' experience with Extreme Network gear * At least 2 years' experience support large scale network environment * Cisco / Extreme certifications * Experience installing and configuring network equipment * Ability to analyze and evaluate networks to identify issues * Comprehensive understanding of network design, services and protocols - Preferred Requirements: Checkpoint Firewall Experience (Managing and/or configuring). We'll combine into a list. Qualifications: Need to capture Knowledge Of, Skill In, Physical Requirements And Working Conditions. Knowledge Of list: (very long) includes: - Network protocols; interdependence of software and hardware operating in a multi-functioning, multi-user environment; principles, practices and techniques in the installation and maintenance of network hardware and software; concepts and capabilities of computer operations platforms; use of network management tools and problem analysis techniques; program and system documentation requirements; patient rights; department and hospital safety practice and procedures; patient rights; age specific patient care practices; infection control policies and practices; handling, storage, use and disposal of hazardous materials; department and hospital emergency response policies and procedures. Note patient rights appears twice. Skill In list: (also long) includes: - Troubleshooting and resolving complex system problems; organizing and scheduling installations and down time; conceptualizing, designing, and implementing new application software programs; training others in the use of application programs and in conveying technical information to non-technical audiences; writing procedure manuals and user guides; collecting, manipulating, retrieving and analyzing data; evaluating software programs; establishing and maintaining effective working relationships with all personnel