Network & UC Administrator

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key sections: - Position Summary: description of responsibilities, etc. - Essential Functions Job Duties Knowledge Skills And Abilities: basically a list of skills/abilities. - Required Education: Associates Degree or at least 60 college hours. Note about experience substitution. - Required Work Experience: list of relevant experience items. - Preferred Qualifications: list. - Required Certifications, Licenses Or Registrations: driver's license, military clearance. - Work Hours: typical work week M-F 8AM to 5PM with flexibility extended hours. - Physical Demands: list. - Posting Number, Job Type, Job Category, Desired Start Date, Position End Date (if Temporary) Reports To, Salary, Open Date, Close Date, Special Instructions to Applicant (duplicate of military clearance), etc. We need to remove boilerplate: EEO, copyright, posted by, etc. We need to keep substantive info: position summary, duties, skills, education, experience, preferred qualifications, certifications, work hours, physical demands, salary, reporting line, maybe start date. We need to decide sections: About the role (maybe summary), Responsibilities (essential functions), Requirements (required education + required work experience?), Qualifications (preferred qualifications?), Skills (maybe combine with responsibilities?), Benefits (none mentioned), Pay (salary given), Schedule (work hours). Also maybe "Physical Demands" could be part of Requirements? But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also include other headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. We shouldn't invent other headings. So we need to map content to these sections. We have: - About the role: could be the Position Summary paragraph. - Responsibilities: Essential Functions Job Duties Knowledge Skills And Abilities (list of duties/skills). Could be responsibilities. - Requirements: Required Education + Required Work Experience (maybe also Required Certifications? but certifications maybe part of Requirements). Could include driver's license, military clearance. - Qualifications: Preferred Qualifications. - Skills: maybe we could separate technical skills from responsibilities? But we already used responsibilities for duties. Could put technical skills under Skills. However we need to avoid duplication. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine responsibilities and skills into one section? But we need to follow headings if we have content. We could have About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. That's six sections. Skills maybe not needed if covered in Responsibilities. Benefits none, so omit. We need to ensure we don't create sections with placeholder text. So we will only include sections where we have substantive content. Let's extract content: About the role (Position Summary): "The Network & UC Administrator is responsible for providing technical assistance, support, and advice to users, as well as day-to-day administration, maintenance, and support of the UIW network across multiple locations on multiple UIW campuses. This position communicates technical information to technical support entities and non-technical network users, students, and other personnel with a strong customer service focus. The Network & UC Administrator reports to the Network and Unified Communications Manager. This position requires the ability to successfully acquire military clearance to access UIW systems/employees located at the local military bases of Ft. Sam Houston JBSA, Lackland AFB, and Randolph AFB." That's the summary. Responsibilities (Essential Functions Job Duties Knowledge Skills And Abilities): List items: - Well-versed in core networking concepts, network monitoring, and troubleshooting LANs, WANs, VPN solutions, routers, switches, virtualized and physical appliances. - Good understanding of information security rules and regulations related to data confidentiality (e.g., FERPA, HIPAA, and PCI). - Skilled in designing, implementing, and maintaining a wired and wireless local area network, including access point installation/ configuration and use of management platform interfaces. - Skilled in using network monitoring tools to proactively monitor a variety of network conditions. - Proficient in IP addressing/subnetting, protocol analysis tools, and monitoring tools. - Ability to work successfully independently and in a team environment, prioritizing the needs of the team. - Ability to actively pursue and continue professional development and training related to networking and information technology. - Ability to take on new technology, utilizing available learning resources, attend classes/seminars/workshops, and other professional development opportunities. - Advanced critical thinking, troubleshooting, and problem-solving skills. - Ability to maintain confidentiality and professionalism in all aspects of the job. - Ability to manage multiple tasks with frequent interruptions. - Ability to manage multiple priorities. - Ability to diffuse and manage volatile and stressful situations. - Ability to communicate in non-technical terms to community members with a customer service focus. - Ability to work effectively with individuals from diverse communities and cultures. - Employee shall adhere to all applicable rules and regulations of the University, the Conference, and the NCAA. We could format as

  • each. Requirements: - Required Education: Associates Degree or at least 60 college hours. Note that up to two years of additional relevant experience in areas identified below will be considered in lieu of listed education. - Required Work Experience: list: - Relevant experience with Multiprotocol Wireless Networks in a managed environment, including wireless LAN controllers. - Relevant experience with Multiprotocol Local Area Networks. - Relevant experience with Network Security appliances or Network Access Control software. - Relevant experience with managed switches using CLI and GUI to configure switches. - Relevant experience with network security tools, procedures, and best practices. - Required Certifications, Licenses Or Registrations: - Must have a valid drivers license, driving record that is insurable by UIW insurance carrier, and be at least 21 years of age, as required to drive for UIW. - Ability to successfully acquire military clearance to access UIW systems/employees located at the local military bases of Ft. Sam Houston JBSA, Lackland AFB, and Randolph AFB. We could combine education, experience, certifications under Requirements. Qualifications (Preferred Qualifications): - Associates Degree in Computer Science or in a related field. - Experience in System Administration, specifically for higher education. - One (1) year of experience with Multiprotocol Wireless Networks in a managed environment including wireless LAN controllers (local and cloud-based). - One (1) year of experience with Multiprotocol Local Area Networks including routing and switching. - One (1) year of experience with Network Security appliances or Network Access Control software, and/or Authorization / Access Control systems. - Relevant certification (CCNA, CWNA, Network+, or similar). - Experience in networking in virtual environments, as well as network security tools, procedures, and best practices. Pay: - Salary: $67,000 Annualized. Schedule: - Work Hours: Typical work week is M-F 8AM to 5PM with flexibility with extended hours as needed to meet departmental goals. Extended hours may include some evening hours, weekend work, and occasional over-night hours as needed to execute upgrades an/or meet departmental goals. Physical Demands: Not a allowed heading, but we could maybe include under Requirements? But it's not education/experience. Could be part of Requirements? Might be okay to add a separate section? The instruction only gave examples but didn't forbid other headings? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings; we should not create others. So we need to fit Physical Demands somewhere, maybe under Requirements as a bullet? Or under Responsibilities? Probably under Requirements as a bullet about physical ability. But it's not a requirement per se, but we can include. We could also add a section "Skills" if we want to separate technical skills from responsibilities. But we already have responsibilities list includes many skills. Could create Skills section for technical skills: core networking concepts, network monitoring, troubleshooting LANs/WANs/VPN, routers, switches, virtualized/physical appliances, information security rules, designing/wireless LAN, network monitoring tools, IP addressing/subnetting, protocol analysis, monitoring tools. Then Responsibilities could be more about duties like providing assistance, communicating, etc. But the original list mixes both. To avoid duplication, maybe we keep Responsibilities as the list of duties (including skills) and not create Skills section. Since we have many sections already, we can omit Skills. Benefits: none mentioned, so omit. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive information. Let's verify we didn't drop any important bits: - Position Summary: included. - Essential Functions list: included under Responsibilities. - Required Education: included under Requirements. - Required Work Experience: included under Requirements. - Required Certifications, Licenses Or Registrations: included under Requirements (driver's license, military clearance). - Preferred Qualifications: included under Qualifications. - Salary: included under Pay. - Work Hours: included under Schedule. - Physical Demands: we haven't included yet. Need to include somewhere. Could add under Requirements as a bullet: "Physical Demands: Ability to lift up to 30lbs of computer equipment; ability to reach overhead, bend, squat to retrieve and install computer and related equipment; ability to push/pull equipment carts holding up to 100lbs; ability to actively engage in troubleshooting and installation activities for extended periods of time; ability to regularly move about main campus and local satellite campuses to provide customer install/troubleshooting services as needed throughout the day; ability to move about campus and event venues to provide IT support as needed during assigned events; ability to regularly move about campus actively engage faculty, staff, and potential/current students, as well as attend meetings on and off campus." We need to ensure we don't duplicate. It's not duplicated elsewhere. - Posting Number, Job Type, Job Category, Desired Start Date, Position End Date, Reports To, Open Date, Close Date, Special Instructions to Applicant (duplicate military clearance), etc. Are these substantive? Possibly we should include Reports To (already in summary). Desired Start Date maybe relevant. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include Desired Start Date, Reports To (though already in summary but we can keep), Job Type (Full Time), Job Category (Administrator (exempt)), maybe Posting Number? It said do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we could include a short paragraph at the end with metadata like Posting Number,