Junior Network / Systems Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content about the university (About The University). That could be "About the role"? Actually "About The University" is about the employer, not role. But we can still use heading "About the role"? The instruction says use headings like About the role, Responsibilities, etc. It doesn't forbid using other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those standard headings. We have content that fits: About the role could be the Position Description paragraph. Responsibilities: list of duties. Requirements: bullet list. Qualifications? Could be supplemental info? Skills? Could be supplemental info. Benefits, Pay, Schedule: not present, so omit.
We need to preserve all substantive information, not invent. Remove boilerplate: EEO, E-Verify, mission statement, etc. Also remove duplicated lines, application instructions. Also remove cookie/navigation/legal etc. The posting includes a lot of mission and EEO at end; we should drop those.
We need to keep: About The University description (first paragraph). Position Description paragraph. Job Responsibilities (with subheadings? but we can just list responsibilities). Requirements (including bullet list). Supplemental Information (Preferred). That could go under Qualifications or Skills. We'll decide.
We need to use - for any list of duties/requirements/benefits. So responsibilities list should be
- . Requirements list also
- . Supplemental info maybe also list.
We need to use
for prose.
We must not include headings with filler text. So we will include headings only for sections we have content: About the role (maybe using Position Description), Responsibilities, Requirements, Qualifications (or Skills). We'll decide.
Let's extract content:
About The University paragraph:
"Manhattan University is nestled in the historic neighborhood or Riverdale , close to dozens of restaurants and shops as well as Van Cortlandt Park , and is only 35 minutes from midtown Manhattan. Manhattan University is nationally ranked and offers degree programs in the arts, business, education, engineering, and science. The University has approximately 2,900 full and part-time undergraduate and graduate students enrolled in over 50 fields of study. It is committed to excellence in teaching a diverse student body and preparing students for successful careers and fulfilling lives. We are committed to creating an inclusive environment where all employees and faculty members can thrive personally and professionally."
We need to fix typo "or Riverdale" maybe keep as is? It's part of content; we should preserve.
Position Description paragraph:
"The Junior Network / Systems Engineer supports the design, implementation, administration, and continuous availability of Manhattan University's enterprise network and server infrastructure. This position ensures that wired and wireless connectivity, data center systems, and network-attached services remain secure, reliable, and performant across all campus buildings, classrooms, laboratories, offices, residence halls, and event spaces. Working under the direction of the Director of Network Systems, the Junior Network / Systems Engineer installs and maintains network hardware from multiple vendors, troubleshoots complex connectivity issues, administers Windows and Linux server environments, and supports virtualized and cloud-hosted platforms. The position serves as a hands-on technical resource for incident resolution, infrastructure projects, and campus technology deployments. This role also partners closely with the Information Security team on cybersecurity and compliance initiatives, contributes to business continuity and disaster recovery planning, and maintains accurate technical documentation, network diagrams, and asset records that support the long-term stability of the University's technology environment."
Responsibilities: They have headings: Network & Infrastructure Administration, Systems & Data Center Administration, User Support, Documentation & Collaboration. Under each there are bullet-like sentences. We'll combine into a single list? Probably better to keep as list items each responsibility. We'll extract each sentence as list item.
List items:
- Ensure the continuous, uninterrupted availability, security, and functionality of the network.
- Troubleshoot and resolve wired and wireless network issues, sometimes under duress.
- Install and maintain network equipment — including access points, switches, routers, and firewalls — from various vendors such as HPE Aruba, HP ProCurve, Juniper, Dell, and pfSense.
- Design and implement networks and wiring for network-reliant spaces, including classrooms, offices, labs, network closets, and event spaces.
- Create, test, and deploy network automation scripts and monitoring solutions.
- Maintain physical data center infrastructure, including racked server hardware, power and cooling considerations, and cable management.
- Maintain, monitor, and manage both Windows and Linux servers.
- Build, maintain, and deploy standardized system images and software packages for classroom and computer lab workstations.
- Manage virtualized and containerized environments both on-premises and in the cloud.
- Resolve network and server incidents and manage issues through the University's ticketing system.
- Support network connectivity and configuration for network-attached devices, including IP cameras, printers, and VoIP phones.
- Collaborate with the Information Security team to enforce cybersecurity and compliance initiatives.
- Participate in business continuity, backup management, and disaster recovery planning for network and server operations.
- Maintain technical documentation, network diagrams, configuration standards, and asset management records.
- Partner on ITS initiatives, evaluate new technology, and support system deployment testing and post-launch validation.
- Perform other duties as assigned.
Requirements: bullet list:
- Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field, or equivalent practical experience.
- Minimum of two (2) years of hands-on experience supporting enterprise/campus network infrastructure and system operations.
- Demonstrated understanding of the following:
- Network fundamentals, such as the TCP/IP model, OSI model, and subnetting.
- Network protocols, such as DNS, HTTP/HTTPS, FTP, SMTP, SNMP, and DHCP.
- Network architectures, such as WAN, LAN, VLAN, and WLAN.
- Routing protocols, such as OSPF, BGP, RIP, and EIGRP.
- Security standards, such as SSL/TLS, SSH, and WPA.
- Solid understanding of ethernet and fiber-optic cabling standards.
- Strong analytical, troubleshooting, organizational, and customer service skills, with effective communication across technical and non-technical audiences.
We need to format as list items; nested lists okay? Probably we can flatten: each bullet as
- . For sub-bullets we can also
- inside
. We'll keep simple: each line as - . Might be okay.
Supplemental Information (Preferred):
- Familiarity with data center operations, racking server hardware, and virtualization platforms such as VMware, Hyper-V, and KVM.
- Prior experience supporting higher education institutions or large-scale, multi-building campus environments.
- Hands-on experience with enterprise networking platforms such as HPE Aruba, HPE ProCurve, Juniper, Dell, and pfSense.
- Familiarity with administering, patching, and troubleshooting Windows Server environments alongside both Red Hat-based and Debian-based Linux systems.
- Experience managing network peripherals such as IP security cameras, printers, and VoIP telephony.
- Relevant industry certifications such as CompTIA Network+, Linux+, or Server+; CCNA; or vendor-specific credentials.
We could put this under "Qualifications" or "Skills". Since we have Requirements already, we can add a "Preferred Qualifications" section. But instruction only lists certain headings; we could use "Qualifications" for this. Or "Skills". Let's use "Qualifications" for supplemental preferred info.
We must not include headings with filler text. We have content for About the role (Position Description), Responsibilities, Requirements, Qualifications (preferred). Good.
Now produce HTML fragment:
About the role
... (Position Description)
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
We need to ensure we don't include any extra text like "About The University" heading; we used About the role. That's okay.
Check for any boilerplate left: we removed EEO, mission, E-Verify, etc. Also removed "Manhattan University is an E-Verify employer." etc. Also removed "Founded in 1853..." etc. Also removed "Please note that this job description is not designed..." etc.
Check for any duplicated lines: we have not duplicated.
Now produce final HTML.
Let's craft the About the role paragraph exactly as given (maybe fix spacing). We'll keep as is.
Position Description paragraph: we need to ensure we keep the content exactly.
Let's copy:
"The Junior Network / Systems Engineer supports the design, implementation, administration, and continuous availability of Manhattan University's enterprise network and server infrastructure. This position ensures that wired and wireless connectivity, data center systems, and network-attached services remain secure, reliable, and performant across all campus buildings, classrooms, laboratories, offices, residence halls, and event spaces. Working under the direction of the Director of Network Systems, the Junior Network / Systems Engineer installs and maintains network hardware from multiple vendors, troubleshoots complex connectivity issues, administers Windows and Linux server environments, and supports virtualized and cloud-hosted platforms. The position serves as a hands-on technical resource for incident resolution, infrastructure projects, and campus technology deployments. This role also partners closely with the Information Security team on cybersecurity and compliance initiatives, contributes to business continuity and disaster recovery planning, and maintains accurate technical documentation, network diagrams, and asset records that support the long-term stability of the University's technology environment."
Now Responsibilities list items as above.
Requirements list items: we need to include the sub-bullets under Demonstrated understanding. We'll flatten:
- Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field, or equivalent practical experience.
- Minimum of two (2) years of hands-on experience supporting enterprise/campus network infrastructure and system operations.
- Demonstrated understanding of the following: Network fundamentals, such as the TCP/IP model, OSI model, and subnetting.
- Demonstrated understanding of the following: Network protocols, such as DNS, HTTP/HTTPS, FTP, SMTP, SNMP, and DHCP.
- Demonstrated understanding of the following: Network architectures, such as WAN, LAN, VLAN, and WLAN.
- Demonstrated understanding of the following: Routing protocols, such as OSPF, BGP, RIP, and EIGRP.
- Demonstrated understanding of the following: Security standards, such as SSL/TLS, SSH, and WPA.
- Demonstrated understanding of the following: Solid understanding of ethernet and fiber-optic cabling standards.
- Strong analytical, troubleshooting, organizational, and customer service skills, with effective communication across technical and non-technical audiences.
But that repeats "Demonstrated understanding of the following:" many times; maybe better to keep as a single - with a nested list. However instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We can do:
- Demonstrated understanding of the following:
- Network fundamentals, such as the TCP/IP model, OSI model, and subnetting.
- Network protocols, such as DNS, HTTP/HTTPS, FTP, SMTP, SNMP, and DHCP.
- Network architectures, such as WAN, LAN, VLAN, and WLAN.
- Routing protocols, such as OSPF, BGP, RIP, and EIGRP.
- for any list of duties/requirements/benefits. So responsibilities list should be
- . Requirements list also
- . Supplemental info maybe also list.
We need to use
for prose. We must not include headings with filler text. So we will include headings only for sections we have content: About the role (maybe using Position Description), Responsibilities, Requirements, Qualifications (or Skills). We'll decide. Let's extract content: About The University paragraph: "Manhattan University is nestled in the historic neighborhood or Riverdale , close to dozens of restaurants and shops as well as Van Cortlandt Park , and is only 35 minutes from midtown Manhattan. Manhattan University is nationally ranked and offers degree programs in the arts, business, education, engineering, and science. The University has approximately 2,900 full and part-time undergraduate and graduate students enrolled in over 50 fields of study. It is committed to excellence in teaching a diverse student body and preparing students for successful careers and fulfilling lives. We are committed to creating an inclusive environment where all employees and faculty members can thrive personally and professionally." We need to fix typo "or Riverdale" maybe keep as is? It's part of content; we should preserve. Position Description paragraph: "The Junior Network / Systems Engineer supports the design, implementation, administration, and continuous availability of Manhattan University's enterprise network and server infrastructure. This position ensures that wired and wireless connectivity, data center systems, and network-attached services remain secure, reliable, and performant across all campus buildings, classrooms, laboratories, offices, residence halls, and event spaces. Working under the direction of the Director of Network Systems, the Junior Network / Systems Engineer installs and maintains network hardware from multiple vendors, troubleshoots complex connectivity issues, administers Windows and Linux server environments, and supports virtualized and cloud-hosted platforms. The position serves as a hands-on technical resource for incident resolution, infrastructure projects, and campus technology deployments. This role also partners closely with the Information Security team on cybersecurity and compliance initiatives, contributes to business continuity and disaster recovery planning, and maintains accurate technical documentation, network diagrams, and asset records that support the long-term stability of the University's technology environment." Responsibilities: They have headings: Network & Infrastructure Administration, Systems & Data Center Administration, User Support, Documentation & Collaboration. Under each there are bullet-like sentences. We'll combine into a single list? Probably better to keep as list items each responsibility. We'll extract each sentence as list item. List items: - Ensure the continuous, uninterrupted availability, security, and functionality of the network. - Troubleshoot and resolve wired and wireless network issues, sometimes under duress. - Install and maintain network equipment — including access points, switches, routers, and firewalls — from various vendors such as HPE Aruba, HP ProCurve, Juniper, Dell, and pfSense. - Design and implement networks and wiring for network-reliant spaces, including classrooms, offices, labs, network closets, and event spaces. - Create, test, and deploy network automation scripts and monitoring solutions. - Maintain physical data center infrastructure, including racked server hardware, power and cooling considerations, and cable management. - Maintain, monitor, and manage both Windows and Linux servers. - Build, maintain, and deploy standardized system images and software packages for classroom and computer lab workstations. - Manage virtualized and containerized environments both on-premises and in the cloud. - Resolve network and server incidents and manage issues through the University's ticketing system. - Support network connectivity and configuration for network-attached devices, including IP cameras, printers, and VoIP phones. - Collaborate with the Information Security team to enforce cybersecurity and compliance initiatives. - Participate in business continuity, backup management, and disaster recovery planning for network and server operations. - Maintain technical documentation, network diagrams, configuration standards, and asset management records. - Partner on ITS initiatives, evaluate new technology, and support system deployment testing and post-launch validation. - Perform other duties as assigned. Requirements: bullet list: - Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field, or equivalent practical experience. - Minimum of two (2) years of hands-on experience supporting enterprise/campus network infrastructure and system operations. - Demonstrated understanding of the following: - Network fundamentals, such as the TCP/IP model, OSI model, and subnetting. - Network protocols, such as DNS, HTTP/HTTPS, FTP, SMTP, SNMP, and DHCP. - Network architectures, such as WAN, LAN, VLAN, and WLAN. - Routing protocols, such as OSPF, BGP, RIP, and EIGRP. - Security standards, such as SSL/TLS, SSH, and WPA. - Solid understanding of ethernet and fiber-optic cabling standards. - Strong analytical, troubleshooting, organizational, and customer service skills, with effective communication across technical and non-technical audiences. We need to format as list items; nested lists okay? Probably we can flatten: each bullet as
- . For sub-bullets we can also
- inside
- . We'll keep simple: each line as
- . Might be okay.
Supplemental Information (Preferred):
- Familiarity with data center operations, racking server hardware, and virtualization platforms such as VMware, Hyper-V, and KVM.
- Prior experience supporting higher education institutions or large-scale, multi-building campus environments.
- Hands-on experience with enterprise networking platforms such as HPE Aruba, HPE ProCurve, Juniper, Dell, and pfSense.
- Familiarity with administering, patching, and troubleshooting Windows Server environments alongside both Red Hat-based and Debian-based Linux systems.
- Experience managing network peripherals such as IP security cameras, printers, and VoIP telephony.
- Relevant industry certifications such as CompTIA Network+, Linux+, or Server+; CCNA; or vendor-specific credentials.
We could put this under "Qualifications" or "Skills". Since we have Requirements already, we can add a "Preferred Qualifications" section. But instruction only lists certain headings; we could use "Qualifications" for this. Or "Skills". Let's use "Qualifications" for supplemental preferred info.
We must not include headings with filler text. We have content for About the role (Position Description), Responsibilities, Requirements, Qualifications (preferred). Good.
Now produce HTML fragment:
About the role
... (Position Description)
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
- with a nested list. However instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We can do:
- Demonstrated understanding of the following:
- Network fundamentals, such as the TCP/IP model, OSI model, and subnetting.
- Network protocols, such as DNS, HTTP/HTTPS, FTP, SMTP, SNMP, and DHCP.
- Network architectures, such as WAN, LAN, VLAN, and WLAN.
- Routing protocols, such as OSPF, BGP, RIP, and EIGRP.
- . Might be okay.
Supplemental Information (Preferred):
- Familiarity with data center operations, racking server hardware, and virtualization platforms such as VMware, Hyper-V, and KVM.
- Prior experience supporting higher education institutions or large-scale, multi-building campus environments.
- Hands-on experience with enterprise networking platforms such as HPE Aruba, HPE ProCurve, Juniper, Dell, and pfSense.
- Familiarity with administering, patching, and troubleshooting Windows Server environments alongside both Red Hat-based and Debian-based Linux systems.
- Experience managing network peripherals such as IP security cameras, printers, and VoIP telephony.
- Relevant industry certifications such as CompTIA Network+, Linux+, or Server+; CCNA; or vendor-specific credentials.
We could put this under "Qualifications" or "Skills". Since we have Requirements already, we can add a "Preferred Qualifications" section. But instruction only lists certain headings; we could use "Qualifications" for this. Or "Skills". Let's use "Qualifications" for supplemental preferred info.
We must not include headings with filler text. We have content for About the role (Position Description), Responsibilities, Requirements, Qualifications (preferred). Good.
Now produce HTML fragment:
- . Supplemental info maybe also list.
We need to use
- . Requirements list also