Network / System Engineer II

We need to output HTML fragment with sections: About the role? Actually we have sections: About BCforward (company description) maybe not needed? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. 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 have content: Job Title, Location, Duration, Pay Range, Job ID, About BCforward (company description), Job Description (intro paragraph), Responsibilities (list), Required Skills & Qualifications (list), Preferred Skills (list), Work Schedule & Onsite Expectations (text), Why BCforward? (benefits list), About Our Commitment (EEO boilerplate - remove), Interested? Apply Now! (application instructions - remove). Also we have "Pay Range: $60.28/hr (W2)" - that's pay info, so we can include a Pay section. Schedule: "Work Schedule & Onsite Expectations: Second shift coverage with participation in an 8x7 shift rotation, including weekends as scheduled. Onsite 4 days per week for the first 6 months, then onsite 3 days per week per workplace guidelines." That's schedule info, so we can include a Schedule section. Benefits: "Why BCforward? At BCforward, we believe in advancing lives and careers. When you join our team, you gain access to: Competitive compensation and benefits Opportunities for growth with global clients A supportive, inclusive culture that values innovation and people Exposure to cutting-edge technologies and projects". That's benefits list. We also have "About BCforward" description - could be "About the role"? Actually "About the role" is a generic heading but we have a job description paragraph: "We are seeking a Network / System Engineer II to join our dynamic team. The ideal candidate will have strong experience in Linux infrastructure, automation, and observability and a proven ability to support and enhance large-scale, mission-critical environments." That's a prose description. Could be placed under a heading like "About the role". The instructions say use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Required Skills & Qualifications (maybe combine Requirements and Qualifications?), Preferred Skills (maybe under Skills), Pay, Schedule, Benefits (Why BCforward?). We need to decide what sections to include based on content. We have Required Skills & Qualifications (list). That's both requirements and qualifications. Could split into Requirements and Qualifications but we can just have one section "Requirements" or "Required Skills & Qualifications". The instruction list includes Requirements and Qualifications as separate possible headings, but we can combine if we want fewer sections. They said prefer a few substantive sections over many thin ones. So maybe we combine Required Skills & Qualifications into one section titled "Required Skills & Qualifications". Preferred Skills could be a separate "Preferred Skills" section. We have Pay: we have Pay Range. Schedule: we have Work Schedule & Onsite Expectations. Benefits: we have Why BCforward? list. We also have company description About BCforward - could be included under "About the role"? Actually "About the role" is about the job, not the company. The company description is not strictly required but it's substantive info about the employer. Could be included as a paragraph under "About the role" or maybe a separate "About BCforward" but not in the list of 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 suggests those as examples. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. So we could have "About the role" containing the job description paragraph and maybe also the company description? But the company description is about BCforward, not the role. However it's still relevant. Could include it as a paragraph under "About the role" or maybe we could add a section "About BCforward" but that's not in the examples; but it's not prohibited. However they said prefer a few substantive sections over many thin ones. Adding another section may be thin. Better to incorporate company description into "About the role" or maybe into a brief paragraph before responsibilities. We need to preserve ALL substantive information. So we must include the company description somewhere. Let's plan sections: -

About the role

: includes the job description paragraph (We are seeking...). Could also include the company description as a separate paragraph? Might be okay. -

Responsibilities

: list of duties. -

Required Skills & Qualifications

: list of required skills. -

Preferred Skills

: list of preferred skills. -

Pay

: paragraph with pay range. -

Schedule

: paragraph with work schedule. -

Benefits

: list of benefits from Why BCforward?. We must not include sections like "About BCforward" separately if we incorporate into About the role. We must remove boilerplate: EEO, Apply Now, etc. We must not include Job ID etc. Could fold minor metadata into a short

or drop it. The location, duration, pay range are already covered; we could include location and duration in a short paragraph maybe under About the role? But we have separate Pay and Schedule sections; location and duration could be placed in a short

after the heading? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include location and duration in a short paragraph maybe under About the role or as a separate

before sections. But we already have Pay and Schedule sections; location and duration are not covered elsewhere. We could add a

after the About the role heading that includes location and duration. Or we could incorporate them into About the role paragraph. Let's include location and duration in a short

after the About the role heading, before the responsibilities. Thus:

About the role

Network / System Engineer II position located in Pennington, New Jersey. Contract duration: 10 months.

We are seeking a Network / System Engineer II to join our dynamic team. The ideal candidate will have strong experience in Linux infrastructure, automation, and observability and a proven ability to support and enhance large-scale, mission-critical environments.

BCforward is a leading global IT consulting and workforce solutions firm providing services and support to Fortune 500 and government clients. Founded in 1998, BCforward has grown with our customers needs into a full-service business solutions provider. With delivery centers and offices across North America and India, we take pride in building long-term relationships and delivering excellence through innovation, collaboration, and integrity.

That preserves location, duration, job description, company description. Then Responsibilities

• ... etc. Then Required Skills & Qualifications
  • ... etc. Then Preferred Skills
    • ... etc. Then Pay

      Pay

      Pay Range: $60.28/hr (W2)

      Then Schedule

      Schedule

      Work Schedule & Onsite Expectations: Second shift coverage with participation in an 8x7 shift rotation, including weekends as scheduled. Onsite 4 days per week for the first 6 months, then onsite 3 days per week per workplace guidelines.

      Then Benefits

      Benefits

      • Competitive compensation and benefits
      • Opportunities for growth with global clients
      • A supportive, inclusive culture that values innovation and people
      • Exposure to cutting-edge technologies and projects
      We must not include any other sections like "About Our Commitment" (EEO) or "Interested? Apply Now!" etc. Check for any duplicated lines: we have not duplicated. Check for any filler: none. Check that we didn't create Pay/Schedule/Benefits sections unless posting actually states them: yes we have those. Check that we didn't create sections with filler like "commensurate with experience": none. Check that we didn't repeat job title as heading: we didn't. Check that we didn't put Job ID as heading: we didn't. Check that we removed cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions: we removed EEO and Apply Now. Check that we preserved ALL substantive information: we have location, duration, pay, responsibilities, required skills, preferred skills, schedule, benefits, company description, job description. Did we miss anything? The job description also includes "About BCforward" which we included. The "Why BCforward?" we turned into benefits. The "Work Schedule & Onsite Expectations" we turned into schedule. The "Pay Range" we turned into pay. The "Required Skills & Qualifications" we turned into required skills. The "Preferred Skills" we turned into preferred skills. The "Responsibilities" we turned into responsibilities. The "Job Title" we didn't repeat as heading (good). The "Location" and "Duration" we included in a short paragraph. The "Job ID" we dropped (minor metadata). All good. Now ensure we output only HTML fragment, no /, no markdown fences. Let's craft final HTML. We'll need to wrap each section in appropriate tags. Use

      for headings. Use

      • for lists. Use

        for prose. We'll output:

        About the role

        Network / System Engineer II position located in Pennington, New Jersey. Contract duration: 10 months.

        We are seeking a Network / System Engineer II to join our dynamic team. The ideal candidate will have strong experience in Linux infrastructure, automation, and observability and a proven ability to support and enhance large-scale, mission-critical environments.

        BCforward is a leading global IT consulting and workforce solutions firm providing services and support to Fortune 500 and government clients. Founded in 1998, BCforward has grown with our customers needs into a full-service business solutions provider. With delivery centers and offices across North America and India, we take pride in building long-term relationships and delivering excellence through innovation, collaboration, and integrity.

        Responsibilities

        • Provide L3 support for a global risk management platform, including 2nd shift hours and rotational weekend coverage.
        • Monitor and support Quartz Core environment components and dependent technologies.
        • Design, implement, and manage end-to-end Linux-based infrastructure hosting databases, grid computing, job schedulers, and messaging platforms.
        • Develop tools and automation to improve resiliency, scalability, and operational efficiency.
        • Troubleshoot infrastructure and application issues proactively to prevent user impact.