VMware/Windows Infrastructure Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Content: - W2/1099/Own Corp Looking for an Infrastructure Engineer that can be local to Northborough, MA. The role requires being onsite 5 days a week. The contract is initially 6 months but will extend longer. this is a more senior position. Target at least 5-8 years minimum. ONSITE Northborough, MA - As an Infrastructure Engineer, you ll play a key role in building, maintaining, and optimizing the core technologies that power our organization. From platforms and servers to networks, storage, backups, and security tools, you ll ensure our estate is highly available, high performing, resilient, and secure. This is a hands-on engineering position where you ll combine strong technical expertise with smart automation, problem solving, and a proactive approach to improvement. You ll help integrate, support, and enhance the underlying infrastructure that enables our business-critical applications and services to operate seamlessly - 24/7. If you re driven by meaningful work, thrive in a technically diverse environment, and want to make a real impact on systems that matter, this is the role for you. - What You'll Do (list of duties) - How You Will Do It (list of tasks) - About You (some prose) - Here s What You Ll Bring To The Team (list of qualifications/experience) We need to map to sections: About the role (maybe the introductory description), Responsibilities (What You'll Do), Requirements (maybe the "About You" and "Here's What You'll Bring"? Actually requirements could be the experience needed: 5-8 years, senior, etc. Qualifications maybe the list of tools and experience. Skills maybe the specific technical skills. Benefits, Pay, Schedule: we have schedule: onsite 5 days a week. Pay: not given. Benefits: not given. So we should include Schedule section (since we have specific content: onsite 5 days a week). Pay and Benefits should be omitted because no specific content. We need to avoid repeating job title as heading. Also no Job ID. We need to use

for each section heading. We need to use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate etc. Let's extract sections: About the role: The introductory paragraph(s) describing role: "As an Infrastructure Engineer, you ll play a key role..." plus maybe the first sentence about W2/1099/Own Corp etc. But that includes location and contract details. Could be part of About the role. We'll include that. Responsibilities: The "What You'll Do" list. Requirements: Could be the experience requirement: "Target at least 5-8 years minimum." plus "more senior position." plus "ONSITE Northborough, MA" and "role requires being onsite 5 days a week." but schedule is separate. However we could put location and onsite requirement under Requirements or maybe under About the role. But we have a Schedule section for onsite 5 days a week. So we can put location and contract length maybe in About the role. Requirements could be the experience: 5-8 years, senior, etc. Also maybe "W2/1099/Own Corp" is employment type. Could be included in About the role. Qualifications: The list of experience and knowledge: "deep understanding of enterprise IT and OT infrastructure...", "Experience in critical infrastructure and/or utility environments.", "Working knowledge of TSA requirements...", "Experience supporting and securing segmented networks.", "Familiarity With Tools Such As ..." That's qualifications. Skills: Could be the specific technical skills enumerated in responsibilities? But we already have responsibilities list. Perhaps we can separate skills as the tools list. However the instructions: Use sections only when posting has real specific content. We have a list of tools under "Familiarity With Tools Such As". That could be Skills. Or we could put that under Qualifications. But we need to decide. We have "How You Will Do It" list which is more about methods; could be considered Responsibilities as well. But we already have Responsibilities from "What You'll Do". The "How You Will Do It" is more about approach; could be considered Responsibilities too. Might combine them into one Responsibilities section with both lists. But we need to avoid duplication. Let's think: The posting has two lists: "What You'll Do" and "How You Will Do It". Both are duties/responsibilities. We can combine them into a single Responsibilities section with two sub-lists? But we need to output only

  • for any list. Could we have two separate
    under same section? Yes, we can have multiple
    inside the section. Thus Responsibilities section will contain two
    lists: one for What You'll Do, another for How You Will Do It. Now Requirements: Could be the experience requirement: "Target at least 5-8 years minimum." plus "more senior position." plus maybe "W2/1099/Own Corp" (employment type). Also "ONSITE Northborough, MA" maybe location but we have schedule for onsite 5 days a week. Location could be in About the role. Qualifications: The list of experience and knowledge: deep understanding, experience in critical infrastructure, TSA requirements, supporting segmented networks, familiarity with tools. Skills: Could be the specific technical skills like VMware, Hyper-V, SCCM, MECM, SolarWinds, NetVault, Nessus, RSA, Active Directory/DNS/CA Logging, etc. But those are already in the qualifications list. Might be redundant. Better to treat Qualifications as the list of experience/knowledge, and Skills as the list of specific tools/technologies. However the qualifications list already includes "Familiarity With Tools Such As MECM NetVault/Qorestor SolarWinds Nessus VMware Active Directory/DNS/C A Logging Hyper-V". That's essentially skills. Thus we could have Qualifications include the experience and knowledge, and Skills include the tools list. But the tools list is already part of qualifications. To avoid duplication, we could put the tools list under Skills and keep qualifications as the experience/knowledge statements. Let's parse the "Here s What You Ll Bring To The Team" bullet points: - A deep understanding of enterprise IT and OT infrastructure - from compute and storage to backups, networks, operating systems (Windows/Linux), and OT integration - Experience in critical infrastructure and/or utility environments. - Working knowledge of TSA requirements and their application in a regulated environment. - Experience supporting and securing segmented networks. - Familiarity With Tools Such As MECM NetVault/Qorestor SolarWinds Nessus VMware Active Directory/DNS/C A Logging Hyper-V Thus we can split: first four bullets as Qualifications (experience/knowledge). The last bullet as Skills (tools familiarity). That seems reasonable. Now About the role: Should include the initial description: "W2/1099/Own Corp Looking for an Infrastructure Engineer that can be local to Northborough, MA. The role requires being onsite 5 days a week. The contract is initially 6 months but will extend longer. this is a more senior position. Target at least 5-8 years minimum. ONSITE Northborough, MA As an Infrastructure Engineer, you ll play a key role in building, maintaining, and optimizing the core technologies that power our organization. From platforms and servers to networks, storage, backups, and security tools, you ll ensure our estate is highly available, high performing, resilient, and secure. This is a hands-on engineering position where you ll combine strong technical expertise with smart automation, problem solving, and a proactive approach to improvement. You ll help integrate, support, and enhance the underlying infrastructure that enables our business-critical applications and services to operate seamlessly - 24/7. If you re driven by meaningful work, thrive in a technically diverse environment, and want to make a real impact on systems that matter, this is the role for you." We need to avoid repeating job title as heading; we are not using it. We need to ensure we don't include boilerplate like EEO etc. Not present. Now Schedule: we have "The role requires being onsite 5 days a week." Also "ONSITE Northborough, MA". So schedule section: Onsite 5 days a week, location Northborough, MA. Pay: not present, omit. Benefits: not present, omit. Now we need to output HTML fragment only. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...
    • ...
    ...

    Requirements

    ... maybe combine bullet points? Could be a list as well. Requirements: "Target at least 5-8 years minimum." "more senior position." "W2/1099/Own Corp" maybe. Could be a list. But we have also "ONSITE Northborough, MA" maybe location but we put in Schedule. So Requirements list: - Target at least 5-8 years minimum. - More senior position. - W2/1099/Own Corp (employment type). Could also include "local to Northborough, MA" but that's location; we already have schedule location. Might be okay to include location in About the role. We'll make Requirements as a

    with those items.

    Qualifications

    • ...
    ...
    (first four bullets)

    Skills

    • ...
    ...
    (tools list)

    Schedule

    Onsite 5 days a week in Northborough, MA.

    Check that we haven't missed any substantive info: The "About You" paragraph: "You re someone who thrives in complex technical environments and loves getting under the hood of enterprise infrastructure. You bring a blend of solid engineering fundamentals, problem solving instincts, and a curiosity to keep learning." This is descriptive; could be part of About the role or maybe a separate section like "About You". But we don't have a heading for About You in our list; we could incorporate into About the role as prose. It's substantive; we should include it. So add to About the role paragraph. Also "How You Will Do It" list we already included under Responsibilities. Now ensure we preserve all details: Let's extract each piece. About the role prose: - "W2/1099/Own Corp Looking for an Infrastructure Engineer that can be local to Northborough, MA. The role requires being onsite 5 days a week. The contract is initially 6 months but will extend longer. this is a more senior position. Target at least 5-8 years minimum. ONSITE Northborough, MA" - "As an Infrastructure Engineer, you ll play a key role in building, maintaining, and optimizing the core technologies that power our organization. From platforms and servers to networks, storage, backups, and security tools, you ll ensure our estate is highly available, high performing, resilient, and secure." - "This is a hands-on engineering position where you ll combine strong technical expertise with smart automation, problem solving, and a proactive approach to improvement. You ll help integrate, support, and enhance the underlying infrastructure that enables our business-critical applications and services to operate seamlessly - 24/7." - "If you re driven by meaningful work, thrive in a technically diverse environment, and want to make a real impact on systems that matter, this is the role for you." - "You re someone who thrives in complex technical environments and loves getting under the hood of enterprise infrastructure. You bring a blend of solid engineering fundamentals, problem solving instincts, and a curiosity to keep learning." Combine into one