Network Automation Engineer

We need to output HTML fragment with sections: About the role? Actually description includes "Description Seeking a Cloud/Network Automation Engineer ...". We need to parse content: The posting includes description, skills, additional skills & qualifications, experience level, job type & location, pay and benefits, workplace type, application deadline, about TEKsystems (multiple paragraphs), etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "About TEKsystems" repeated? The instruction: remove EEO/equal-opportunity boilerplate. The "About TEKsystems" sections contain some EEO statements; we need to strip those. Also remove duplicated lines. Keep substantive info: role description, responsibilities? Not explicit responsibilities but description includes seeking candidate with experience etc. Could treat as "About the role" maybe. We need headings: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if posting has real specific content. We have: - About the role: description: "Seeking a Cloud/Network Automation Engineer with deep experience in Azure and AWS networking, strong expertise in routing, DNS, firewalls, and network segmentation, and demonstrated success implementing automation through Terraform, Ansible, Python, and Infrastructure-as-Code practices. The ideal candidate will have experience designing secure multi-cloud network architectures, troubleshooting complex hybrid-cloud environments, and driving operational efficiency through automation and standardization." That's substantive. - Responsibilities: Not explicitly listed; maybe we can infer from description? But we should not invent. So we should not create Responsibilities section if no explicit responsibilities listed. The description includes tasks but not as bullet list. Might be okay to treat as responsibilities? The instruction: "include a section ONLY when the posting has real, specific content for it". The description includes responsibilities implicitly but not as a list. Could we create a Responsibilities section with prose from that paragraph? Might be considered specific content. However they gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to put the description under About the role. Then maybe Skills section from "Skills Automation, Python, Cloud, Aws, Azure, network design, arista networks, palo alto firewalls, devops, arista". Also "Additional Skills & Qualifications None". So we can have Skills section with list. - Requirements/Qualifications: maybe from "Experience Level Intermediate Level". Also "Job Type & Location This is a Contract position based out of Buffalo, NY." Could be under Requirements? But better to have a section for Job Type & Location? Not in allowed headings. Could incorporate into About the role or maybe a separate section like "Details"? Not allowed. We could put location under About the role or maybe under a generic

. Since we cannot invent headings not listed, we should stick to allowed headings. So we can put location and job type in a

under About the role or maybe under a separate section like "Details" but not allowed. So we will include location and job type in About the role paragraph. - Pay and Benefits: we have pay range and benefits list. So we need Pay section and Benefits section. According to rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need separate Pay and Benefits headings if content exists. Pay: we have pay range. Benefits: list of benefits. - Schedule: Not mentioned; we have Workplace Type hybrid position. Not schedule. So we should not create Schedule section. - Requirements/Qualifications: we have Experience Level Intermediate Level. Could be under Requirements or Qualifications. We'll choose Requirements maybe. Also maybe "Additional Skills & Qualifications None" indicates none. So we can skip. Thus sections: About the role, Skills, Requirements, Pay, Benefits. We need to use

• for any list of duties/requirements/benefits. So Skills list as
  • . Benefits list as
    • . Requirements maybe as
      • if we list items (Experience Level Intermediate Level, Job Type Contract, Location Buffalo, NY). Could be list. We must preserve all substantive information, not invent or summarize away detail. So we need to include all specifics: pay range $46.64 - $77.74/hr. Benefits list exactly as given: Medical, dental & vision; Critical Illness, Accident, and Hospital; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available; Life Insurance (Voluntary Life & AD&D for the employee and dependents); Short and long-term disability; Health Spending Account (HSA); Transportation benefits; Employee Assistance Program; Time Off/Leave (PTO, Vacation or Sick Leave). Also maybe mention eligibility requirements apply etc. We should keep that? The instruction: remove boilerplate, duplicated lines, and application instructions. The benefits paragraph includes "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms." That seems like boilerplate but still part of benefits description. Might be considered boilerplate but it's about benefits. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those, but could be considered generic benefits disclaimer. Might be okay to keep? Safer to keep substantive benefit items; the disclaimer may be considered boilerplate but not explicitly listed to remove. I'd keep it as a

        after the list maybe. Also we have "Workplace Type This is a hybrid position in Buffalo,NY." That's substantive; we should include location and workplace type. Could be under About the role or Requirements. We'll include in About the role paragraph. Also "Application Deadline This position is anticipated to close on Sep 4, 2026." That's substantive; we could include under About the role or maybe a separate section like "Details". Not in allowed headings; we could put in About the role paragraph. Also "About TEKsystems" paragraphs: we need to remove EEO boilerplate but keep descriptive content about TEKsystems. The paragraphs about TEKsystems contain some EEO statements repeated. We need to strip those. Keep the descriptive content: "We're partners in transformation. We help clients activate ideas and solutions to take advantage of a new world of opportunity. We are a team of 80,000 strong, working with over 6,000 clients, including 80% of the Fortune 500, across North America, Europe and Asia. As an industry leader in Full-Stack Technology Services, Talent Services, and real-world application, we work with progressive leaders to drive change. That's the power of true partnership. TEKsystems is an Allegis Group company." Then second paragraph: "We’re a leading provider of business and technology services. We accelerate business transformation for our customers. Our expertise in strategy, design, execution and operations unlocks business value through a range of solutions. We’re a team of 80,000 strong, working with over 6,000 customers, including 80% of the Fortune 500 across North America, Europe and Asia, who partner with us for our scale, full-stack capabilities and speed. We’re strategic thinkers, hands-on collaborators, helping customers capitalize on change and master the momentum of technology. We’re building tomorrow by delivering business outcomes and making positive impacts in our global communities. TEKsystems and TEKsystems Global Services are Allegis Group companies. Learn more at TEKsystems.com." We need to remove the EEO lines: "The company is an equal opportunity employer and will consider all applications without regards to race, sex, age, color, religion, national origin, veteran status, disability, sexual orientation, gender identity, genetic information or any characteristic protected by law." Also repeated later. Also "San Francisco Fair Chance Ordinance..." etc. Those are legal boilerplate; remove them. Also "Massachusetts Lie Detector:" etc. Also "Use of Artificial Intelligence (AI):" etc. Those are also legal boilerplate; remove. Thus we keep only the descriptive paragraphs about TEKsystems. Now, where to put About TEKsystems? Could be a section like "About the company"? Not in allowed headings. But we could incorporate into About the role? Might be odd. However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings but better to stick to those. However the About TEKsystems content is substantive; we could put it under a section like "About the company" but not in list. Might be considered creating a heading not in examples; risk. Perhaps we can incorporate it into About the role as a paragraph describing the employer. That seems acceptable: About the role can include company description. Thus About the role paragraph will include: seeking Cloud/Network Automation Engineer ... plus job type, location, deadline, plus company description. We must not repeat the job title as a heading. So we won't have

        Cloud/Network Automation Engineer

        . Good. Now produce HTML fragment. Structure:

        About the role

        Seeking a Cloud/Network Automation Engineer with deep experience in Azure and AWS networking, strong expertise in routing, DNS, firewalls, and network segmentation, and demonstrated success implementing automation through Terraform, Ansible, Python, and Infrastructure-as-Code practices. The ideal candidate will have experience designing secure multi-cloud network architectures, troubleshooting complex hybrid-cloud environments, and driving operational efficiency through automation and standardization. This is a Contract position based out of Buffalo, NY. The position is anticipated to close on Sep 4, 2026. TEKsystems is a partner in transformation, helping clients activate ideas and solutions to take advantage of a new world of opportunity. They are a team of 80,000+ working with over 6,000 clients, including 80% of the Fortune 500 across North America, Europe and Asia. As an industry leader in Full-Stack Technology Services, Talent Services, and real-world application, they work with progressive leaders to drive change. TEKsystems is an Allegis Group company. They also provide business and technology services, accelerating business transformation for customers through expertise in strategy, design, execution and operations, partnering with over 6,000 customers, including 80% of the Fortune 500, for scale, full-stack capabilities and speed. They are strategic thinkers, hands-on collaborators, helping customers capitalize on change and master the momentum of technology, building tomorrow by delivering business outcomes and making positive impacts in global communities. TEKsystems and TEKsystems Global Services are Allegis Group companies. Learn more at TEKsystems.com.

        Then Skills:

        Skills

        • Automation
        • Python
        • Cloud
        • AWS
        • Azure
        • network design
        • Arista networks
        • Palo Alto firewalls
        • DevOps
        Note: "arista" appears twice; we list once. Requirements:

        Requirements

        • Experience Level: Intermediate
        • Job Type: Contract
        • Location: Buffalo, NY
        Pay:

        Pay

        The pay range for this position is $46.64 - $77.74/hr. Individual compensation offered