Engineer Information Systems Architecture

We need to output HTML fragment with sections for headings where content exists. Must not repeat job title. No markdown fences. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Remove boilerplate like EEO, navigation, etc. Preserve all substantive info. Do not invent or summarize away detail. Include a section only when posting has real specific content for it; never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Number of Positions In Requisition 1 (metadata) - minor metadata, fold into short

  or drop. Probably include as a short paragraph. - Job Details: description repeated twice (Summary Job Description). We'll need to include description content once. - Job Duties: list of duties (multiple bullet-like sentences). Should be

  • . - Minimum Qualifications: list of qualifications (some sentences). Could be
    • . - Preferred Qualifications: list. - Additional Qualifications: Physical Demands (maybe include as bullet). Also includes disclaimer text (Job Description Disclaimer) - maybe treat as prose. - Work Shift: "Workday Day (United States of America)" - schedule info. So we can have a Schedule section. - Worker Sub Type: Regular Employee - maybe minor metadata. - Entity: Thomas Jefferson University - metadata. - Primary Location Address: address. - Then description about Jefferson (organization description) - maybe treat as About the role? Actually "About the role" could be the summary description. But we have a separate "Job Description" repeated. Could treat that as About the role. - Benefits: paragraph describing benefits. We need to avoid boilerplate: EEO statement, etc. Remove that. Also remove "Job Description Disclaimer" maybe keep as prose? It's not boilerplate? It's a disclaimer about position description; could be considered boilerplate but it's specific to the role. Might keep as a paragraph under maybe "Additional Information". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add other headings? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those categories. Likely we should stick to those. So we need to map content to these sections. - About the role: could be the summary job description (the paragraph about designing and implementing enterprise-wide solutions). That's substantive. - Responsibilities: the Job Duties list. - Requirements: could combine Minimum Qualifications and maybe Additional Qualifications? But we have Qualifications heading separate. Actually we have both Requirements and Qualifications as possible headings. The instruction list includes Requirements and Qualifications separately. We need to decide what goes where. Typically Requirements = minimum qualifications, Qualifications = preferred qualifications. But we also have Skills heading maybe for specific skills. However we can keep simple: Use Requirements for Minimum Qualifications, Qualifications for Preferred Qualifications, Skills for maybe technical skills extracted? But we could also put all under Qualifications. But we need to avoid thin sections. Perhaps combine Minimum and Preferred into Qualifications? But then we lose distinction. However we can still have both headings if content exists. We have also Physical Demands under Additional Qualifications - could be part of Requirements or Qualifications? Might be better to put under Requirements as a bullet. We have Benefits section. We have Schedule: Workday Day (United States of America). That's schedule info. We have Pay: not mentioned, so omit. We have About the role: we have summary. We have Responsibilities: job duties. We have Requirements: Minimum Qualifications. We have Qualifications: Preferred Qualifications. We have Skills: maybe we could list specific skills like routing protocols, firewall, automation tools, etc. But those are already in qualifications. Could create Skills section pulling out specific technical skills from qualifications. But risk of duplication/inventing. Better to not create Skills if not explicitly listed as skills. The posting does not have a separate "Skills" heading; it's embedded in qualifications. So we may omit Skills section to avoid thin. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Also we might include a short paragraph for metadata like Number of Positions, Entity, Location. Could fold into a short

      under maybe About the role? But better to create a small paragraph before sections? The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

      or drop it. So we can include a

      at start with metadata: "Number of Positions: 1. Entity: Thomas Jefferson University. Primary Location: 1100 Virginia Drive, Fort Washington, Pennsylvania, USA." That's minor metadata. Now we need to ensure we preserve all substantive information. Let's extract. From posting: - Number of Positions In Requisition 1 - Job Details: (the description repeated) We'll capture the description: "Designs and implements enterprise-wide solutions for small to medium projects in alignment with organizational standards, developing configurations, test plans, and performance validations while resolving deployment issues. This role builds and maintains core routing, switching, wireless, and connectivity solutions across the enterprise, troubleshooting moderate technical issues and supporting project-driven deployments. By coordinating operational handoffs and executing structured changes with rigorous validation and configuration management, the engineer ensures reliability and contributes to technology evaluations that influence enterprise network strategy." That's the summary. - Job Duties (list): 1. Translate high-level requirements and constraints into detailed low-level designs, including drafting solution diagrams for on-premises and cloud-integrated network architectures. 2. Implement routing structures, NAT, ACLs, and network access control policies according to security baselines, while deploying firewalls and policy objects through approved change control procedures across both on-premises and cloud environments. 3. Perform migration tasks and onboarding workflows, coordinating with supporting teams to ensure seamless integration and minimal service disruption, including SD‑WAN/SASE policy cutovers where applicable. 4. Develop and maintain automation scripts to standardize and accelerate repeatable tasks, improving operational efficiency and reducing manual errors. 5. Diagnose and resolve moderate technical issues across enterprise network environments, liaising with cross-functional teams to restore service and maintain reliability. - Minimum Qualifications: - Associate’s Degree or High School Diploma/GED with preferred work experience. - 2 years related work experience. - Demonstrated competency with routing protocols such as OSPF/EIGRP and working knowledge of BGP and IPv6, with the ability to apply and validate switch and router configurations in complex network environments. - Strong understanding of firewall rule design, network access control (NAC) concepts, and experience implementing secure connectivity solutions, including VPN tunnel configuration and performance validation for both on-premises and cloud environments. - Familiarity with cloud networking constructs (AWS VPC, Azure VNets, or GCP equivalents), hybrid connectivity solutions, and foundational knowledge of SD-WAN or emerging secure edge technologies. - Preferred Qualifications: - Bachelor’s Degree - 4 years related work experience. - Ability to conduct and interpret wireless assessments and early experience with automation workflows for network provisioning and optimization. - Hands-on experience with tools such as Ansible or Terraform for infrastructure automation across on-premises and cloud environments, familiarity with Git-based version control for maintaining configuration integrity, and exposure to Kubernetes CNI/service networking. - Additional Qualifications: - Physical Demands: Lift and carry 25 lbs. frequent sitting/standing, frequent keyboard use, *patient care providers may be required to perform activities specific to their role including kneeling, bending, squatting and performing CPR. - Job Description Disclaimer: (we may keep as prose but it's boilerplate-ish; maybe we can drop as it's generic). The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This disclaimer is legal-ish; maybe drop. We'll drop. - Work Shift: Workday Day (United States of America) - Worker Sub Type: Regular Employee (metadata) - Entity: Thomas Jefferson University (metadata) - Primary Location Address: 1100 Virginia Drive, Fort Washington, Pennsylvania, United States of America - Then description about Jefferson (organization description). This is substantive but not about the role; it's about employer. Could be considered "About the role"? Actually "About the role" is about the job, not employer. But we could include employer description under maybe a separate section? Not allowed headings. Could fold into About the role as extra context? Might be considered boilerplate? It's describing the organization; could be kept as part of About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that description somewhere. Since we don't have a heading for "About the company", we could include it as a paragraph under About the role? But that might misrepresent. However we could add a section heading "About the role" and include both the job summary and the employer description? That would be mixing. Better to create a section "About the role" for job summary, and then maybe add a paragraph after sections for employer info without a heading? The instruction says output ONLY the HTML fragment; we can include

      elements anywhere. So we can add a

      for employer description after sections, without a heading. That's acceptable. - Benefits paragraph: "Jefferson offers a comprehensive package of benefits for full-time and part-time colleagues, including medical (including prescription), supplemental insurance, dental, vision, life and AD&D insurance, short- and long-term disability, flexible spending accounts, retirement plans, tuition assistance, as well as voluntary benefits, which provide colleagues with access to group rates on insurance and discounts. Colleagues have access to tuition discounts at Thomas Jefferson University after one year of full time service or two years of part time service. All colleagues, including those who work less than part-time (including per diem colleagues, adjunct faculty, and Jeff Temps), have access to medical (including prescription) insurance. For more benefits information, please click here" We need to remove the "For more benefits information, please click here" as it's an application instruction/link? It's a link instruction; maybe drop as it's application instruction. The instruction says remove application instructions. So drop that sentence. Thus benefits paragraph ends before that. Now schedule: "Workday Day (United States of America)" - we can phrase as "Workday schedule (United States of America)". Keep as is. Now we need to ensure we don't repeat content. The summary appears twice; we will include once. Now construct HTML. Start with a

      for metadata: maybe "Number of Positions: 1. Entity: Thomas Jefferson University. Location: 1100 Virginia Drive, Fort Washington, Pennsylvania, USA." Then

      About the role

      then

      with the summary. Then

      Responsibilities

      then
      • each duty. Then

        Requirements

        then
        • each minimum qualification. Then

          Qualifications

          then
          • each preferred qualification. Then

            Benefits

            then

            benefits paragraph (without the click here). Then

            Schedule

            then

            Workday Day (United States of America). After that, maybe add a

            for employer description. Check for any other substantive info: The "Additional Qualifications Physical Demands" we haven't included. We should include that somewhere. Could be under Requirements as an additional bullet. So add a bullet under Requirements: "Physical Demands: Lift and carry 25 lbs. frequent sitting/standing, frequent keyboard use;