Onsite Support Engineer II
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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 need to extract content:
- Location: Horsham, PA (metadata). Could be in a short
.
- About The Role: paragraph.
- What You’ll Support: list of duties (troubleshoot network, server, endpoint issues; handle escalations; maintain and document IT environments in IT Glue; remotely access systems; manage and resolve Microsoft 365, AzureAD, DHCP/DNS, and Active Directory-related issues; work with vendors to help restore service during outages). That's responsibilities.
- Requirements: bullet list: Ability to document work and progress in a ticketing system as tasks are completed; Strong communication skills for both remote and in-person support; Willingness to work entirely onsite and travel between client buildings as needed.
- Recommended Skills: bullet list: Proficiency in VMware or Hyper-V environments; Knowledge of Microsoft Windows Server environments, patching, and print server drivers; Familiarity with networking concepts such as VLANs, ISP troubleshooting, and firewall equipment; Experience using centralized documentation systems (e.g., IT Glue); Comfortable working in support escalation and on-call rotations.
- Schedule & Benefits: includes Location: 100% onsite at assigned client sites (travel between buildings required); Hours: Full-time; must be available for on-call weeks and emergency outages; Benefits: Standard benefits package available (details provided during interview process). So we have schedule and benefits. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule and benefits, albeit generic. So we can include a Schedule section and a Benefits section? The instruction says prefer a few substantive sections over many thin ones. Could combine schedule and benefits into one section? But headings allowed: Schedule, Benefits. We could have both if they have content. The schedule: "Location: 100% onsite at assigned client sites (travel between buildings required); Hours: Full-time; must be available for on-call weeks and emergency outages". Benefits: "Standard benefits package available (details provided during interview process)". That's somewhat vague but still specific enough? It says standard benefits package available (details provided during interview process). That's not placeholder like "not specified"? It's somewhat generic but still states there is a standard benefits package. Might be okay. However we might combine into a single "Schedule & Benefits" section as the posting used that heading. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid using a combined heading. But they gave examples; we can use "Schedule & Benefits" as a heading if we want. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't say we cannot use other headings, but we should follow the examples. Probably better to separate: Schedule
and Benefits
. But the benefits description is vague; maybe we should not create a Benefits section if it's just "Standard benefits package available (details provided during interview process)" which is not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits, albeit generic. But also they say prefer a few substantive sections over many thin ones. The benefits section would be thin. Might be better to incorporate benefits into Schedule section or omit. However the posting explicitly has a "Schedule & Benefits" subsection. We could keep that as a combined section: Schedule & Benefits
with
containing both schedule and benefits details. That seems reasonable and follows the posting's structure.
Thus sections:
- About the role (paragraph)
- Responsibilities (What You’ll Support) (list)
- Requirements (list)
- Skills (Recommended Skills) (list)
- Schedule & Benefits (paragraph with schedule and benefits details)
Also include location metadata maybe as a short
before sections.
We must not include application instructions, EEO, etc. Remove duplicated lines.
Let's craft HTML.
We'll output:
Location: Horsham, PA
About the role
As an Onsite Support Engineer II, you’ll be the front line of support for our clients, working 100% onsite at assigned customer locations. Your job is to resolve technical issues that come in through our ticketing system or phone queue, often escalating from our Level I team. You’ll handle everything from system and network troubleshooting to vendor coordination and customer walk-throughs, bringing both tech skill and a friendly, professional presence. Your days will be a mix of hands-on fixes, remote diagnostics, and documentation. You’ll manage support tickets, uphold service level agreements (SLAs), and ensure clients receive timely, effective solutions. This role relies on your ability to work independently while staying tightly aligned with internal procedures and escalation paths. Your success helps ensure business continuity for our clients and builds long-term trust in our IT services.
Responsibilities
- Troubleshoot network, server, and endpoint issues (virtual or physical environments)
- Handle escalations from Level I engineers and follow escalation paths as defined in documentation
- Maintain and document IT environments in IT Glue, updating or creating new articles
- Remotely access systems to push scripts or run actions as needed
- Manage and resolve Microsoft 365, AzureAD, DHCP/DNS, and Active Directory-related issues
- Work with vendors to help restore service during outages
Requirements
- Ability to document work and progress in a ticketing system as tasks are completed
- Strong communication skills for both remote and in-person support
- Willingness to work entirely onsite and travel between client buildings as needed
Skills
- Proficiency in VMware or Hyper-V environments
- Knowledge of Microsoft Windows Server environments, patching, and print server drivers
- Familiarity with networking concepts such as VLANs, ISP troubleshooting, and firewall equipment
- Experience using centralized documentation systems (e.g., IT Glue)
- Comfortable working in support escalation and on-call rotations
Schedule & Benefits
Location: 100% onsite at assigned client sites (travel between buildings required). Hours: Full-time; must be available for on-call weeks and emergency outages. Benefits: Standard benefits package available (details provided during interview process).
That should satisfy.
Check for any duplicated lines: none.
No mention of Pay, Qualifications etc.
We didn't include "Why Join Path Forward IT?" etc. That's extra content but could be considered boilerplate? It's descriptive about company; maybe we could include as a section? The instruction says include a section ONLY when the posting has real, specific content for it. That content is real and specific about company culture. However they didn't list a heading for that; but we could include as a section like "About the company" but not in the allowed headings list. 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 are typical. Safer to stick to those. The company description could be considered "About the role"? No. It's extra but maybe we should include as a paragraph under About the role? But it's not about the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that company description somewhere. Where to put? Could add a section About Path Forward IT
but not in the list. Might be okay but risk deviating from instruction. However instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exclusive. So we can add other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." Adding another section may be okay if it's substantive.
But the company description includes many details: Path Forward IT, a Blue Alliance company, nationally recognized MSP, etc. That's substantive. Should we preserve? Yes.
We could incorporate it into a section About the Company
. That seems reasonable.
But we already have About the role. Could we merge company description into About the role? That would mix role description with company info, but still preserve all info. Might be acceptable. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding other headings.
I'll add a section About Path Forward IT
with the company description paragraphs.
Let's extract that content:
"Path Forward IT, a Blue Alliance company, is a nationally recognized managed services provider (MSP) that exclusively supports the healthcare industry. Ranked among the top 15% of MSPs nationwide, we deliver world-class IT services that ensure technology never stands in the way of patients receiving the care they need. Our work is driven by urgency, empathy, and a patient-centered mindset. We understand the critical nature of healthcare operations and prioritize our work to empower providers to focus on what matters most: delivering exceptional care. Founded in 2002, Path Forward IT has grown to a team of over 100 professionals located across 40+ states. We foster a collaborative, career-focused culture where team members thrive. Many of our employees have been with us for years, and we regularly celebrate 5- and 10-year milestones. A Team Environment Built for Growth Joining Path Forward IT means working alongside IT specialists supporting complex, enterprise environments. As part of the Blue Alliance network, you gain access to a community of hundreds of peers and experts across the country. This means more opportunities for learning, professional development, and career advancement without losing the close-knit feel of a smaller team. You’ll Enjoy The Best Of Both Worlds The autonomy and client engagement typical of a local MSP The resources, support, and structure of a leading national IT services organization A Unique Opportunity Through Blue Alliance As a Blue Alliance partner company, Path Forward IT provides team members with unmatched opportunities to learn, lead, and succeed. Each company in the network maintains its unique identity while working toward shared goals. If you’re looking to make
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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 need to extract content: - Location: Horsham, PA (metadata). Could be in a short
. - About The Role: paragraph. - What You’ll Support: list of duties (troubleshoot network, server, endpoint issues; handle escalations; maintain and document IT environments in IT Glue; remotely access systems; manage and resolve Microsoft 365, AzureAD, DHCP/DNS, and Active Directory-related issues; work with vendors to help restore service during outages). That's responsibilities. - Requirements: bullet list: Ability to document work and progress in a ticketing system as tasks are completed; Strong communication skills for both remote and in-person support; Willingness to work entirely onsite and travel between client buildings as needed. - Recommended Skills: bullet list: Proficiency in VMware or Hyper-V environments; Knowledge of Microsoft Windows Server environments, patching, and print server drivers; Familiarity with networking concepts such as VLANs, ISP troubleshooting, and firewall equipment; Experience using centralized documentation systems (e.g., IT Glue); Comfortable working in support escalation and on-call rotations. - Schedule & Benefits: includes Location: 100% onsite at assigned client sites (travel between buildings required); Hours: Full-time; must be available for on-call weeks and emergency outages; Benefits: Standard benefits package available (details provided during interview process). So we have schedule and benefits. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule and benefits, albeit generic. So we can include a Schedule section and a Benefits section? The instruction says prefer a few substantive sections over many thin ones. Could combine schedule and benefits into one section? But headings allowed: Schedule, Benefits. We could have both if they have content. The schedule: "Location: 100% onsite at assigned client sites (travel between buildings required); Hours: Full-time; must be available for on-call weeks and emergency outages". Benefits: "Standard benefits package available (details provided during interview process)". That's somewhat vague but still specific enough? It says standard benefits package available (details provided during interview process). That's not placeholder like "not specified"? It's somewhat generic but still states there is a standard benefits package. Might be okay. However we might combine into a single "Schedule & Benefits" section as the posting used that heading. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid using a combined heading. But they gave examples; we can use "Schedule & Benefits" as a heading if we want. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't say we cannot use other headings, but we should follow the examples. Probably better to separate: Schedule
and Benefits
. But the benefits description is vague; maybe we should not create a Benefits section if it's just "Standard benefits package available (details provided during interview process)" which is not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits, albeit generic. But also they say prefer a few substantive sections over many thin ones. The benefits section would be thin. Might be better to incorporate benefits into Schedule section or omit. However the posting explicitly has a "Schedule & Benefits" subsection. We could keep that as a combined section: Schedule & Benefits
with
containing both schedule and benefits details. That seems reasonable and follows the posting's structure. Thus sections: - About the role (paragraph) - Responsibilities (What You’ll Support) (list) - Requirements (list) - Skills (Recommended Skills) (list) - Schedule & Benefits (paragraph with schedule and benefits details) Also include location metadata maybe as a short
before sections. We must not include application instructions, EEO, etc. Remove duplicated lines. Let's craft HTML. We'll output:
Location: Horsham, PA
About the role
As an Onsite Support Engineer II, you’ll be the front line of support for our clients, working 100% onsite at assigned customer locations. Your job is to resolve technical issues that come in through our ticketing system or phone queue, often escalating from our Level I team. You’ll handle everything from system and network troubleshooting to vendor coordination and customer walk-throughs, bringing both tech skill and a friendly, professional presence. Your days will be a mix of hands-on fixes, remote diagnostics, and documentation. You’ll manage support tickets, uphold service level agreements (SLAs), and ensure clients receive timely, effective solutions. This role relies on your ability to work independently while staying tightly aligned with internal procedures and escalation paths. Your success helps ensure business continuity for our clients and builds long-term trust in our IT services.
Responsibilities
- Troubleshoot network, server, and endpoint issues (virtual or physical environments)
- Handle escalations from Level I engineers and follow escalation paths as defined in documentation
- Maintain and document IT environments in IT Glue, updating or creating new articles
- Remotely access systems to push scripts or run actions as needed
- Manage and resolve Microsoft 365, AzureAD, DHCP/DNS, and Active Directory-related issues
- Work with vendors to help restore service during outages
Requirements
- Ability to document work and progress in a ticketing system as tasks are completed
- Strong communication skills for both remote and in-person support
- Willingness to work entirely onsite and travel between client buildings as needed
Skills
- Proficiency in VMware or Hyper-V environments
- Knowledge of Microsoft Windows Server environments, patching, and print server drivers
- Familiarity with networking concepts such as VLANs, ISP troubleshooting, and firewall equipment
- Experience using centralized documentation systems (e.g., IT Glue)
- Comfortable working in support escalation and on-call rotations
Schedule & Benefits
Location: 100% onsite at assigned client sites (travel between buildings required). Hours: Full-time; must be available for on-call weeks and emergency outages. Benefits: Standard benefits package available (details provided during interview process).
That should satisfy. Check for any duplicated lines: none. No mention of Pay, Qualifications etc. We didn't include "Why Join Path Forward IT?" etc. That's extra content but could be considered boilerplate? It's descriptive about company; maybe we could include as a section? The instruction says include a section ONLY when the posting has real, specific content for it. That content is real and specific about company culture. However they didn't list a heading for that; but we could include as a section like "About the company" but not in the allowed headings list. The instruction says use