Help Desk Support

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. Let's parse the description: - Title: Tier I + II Service Desk Technician within government sector in Oregon. Supporting roughly 1800 users. Part of support will be for government leadership and other stakeholders. Candidate must have strong customer service. Need to be able to take calls, triage, and process. Ideal candidate will have experience with Window environment, M365 platform, Ivanti. Similar experience to Bomgar (BeyondTrust Remote Support also a plus). Skills microsoft office, windows, remote support, Help desk, Service desk, Customer service, Office 365, ivanti, beyondtrust - Additional Skills & Qualifications: A person who can handle remote support and walk-ins as they arise. - Experience Level: Intermediate Level - Job Type & Location: This is a Contract position based out of Salem, OR. - Pay And Benefits: The pay range for this position is $25.00 - $28.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. 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. If eligible, the benefits available for this temporary role may include the following: 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) - Workplace Type: This is a hybrid position in Salem,OR. - Application Deadline: This position is anticipated to close on Oct 2, 2026. - About TEKsystems: (company description) - we need to remove boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TEKsystems" is not necessarily boilerplate but could be considered company description. Should we keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The "About TEKsystems" is substantive about the employer. However, the instruction also says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "About TEKsystems" is not those. It might be okay to keep. However, we need to decide if we include a section for it. The allowed sections are limited: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company" section. So we likely should not include a separate heading for company description; we could incorporate relevant info into other sections? But the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can use those headings only. It does not forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. Thus we need to extract: - About the role: description of role, supporting 1800 users, government leadership, taking calls, triage, process, customer service, remote support, walk-ins, hybrid, contract, location Salem OR, etc. - Responsibilities: likely taking calls, triage, process, remote support, walk-ins, supporting users, government leadership. - Requirements: experience with Windows environment, M365, Ivanti, Bomgar/BeyondTrust, strong customer service, intermediate level, contract, etc. - Qualifications: maybe similar to requirements? Could combine. - Skills: list of skills: Microsoft Office, Windows, remote support, Help desk, Service desk, Customer service, Office 365, Ivanti, BeyondTrust (Bomgar). - Benefits: list benefits as given. - Pay: pay range $25.00 - $28.00/hr. - Schedule: maybe hybrid position? Workplace type hybrid. Could be schedule info: hybrid position in Salem, OR. Could also include application deadline? Not schedule. But schedule maybe not given; we could omit if not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay and Benefits stated. Schedule not explicitly stated; we have workplace type hybrid but not schedule (e.g., full-time, part-time, shift). Might be considered schedule? Could treat hybrid as schedule? Probably better to omit Schedule section if not explicit. However, we could include "Workplace Type" under Schedule? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So Schedule is allowed if we have schedule info. We have "This is a hybrid position in Salem,OR." That's about workplace type, not schedule (hours). Might be considered schedule? Not sure. Safer to omit Schedule if not explicit about hours/days. We'll omit. We must not include boilerplate like EEO, legal, etc. So we strip the TEKsystems description and equal opportunity statements, AI usage, etc. We must preserve all substantive information: the role details, responsibilities, requirements, qualifications, skills, benefits, pay, workplace type (maybe as part of About the role or Responsibilities). Also contract position, location Salem OR, experience level intermediate. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

...

Responsibilities

• ...

Requirements

• ...

Qualifications

... maybe combine with requirements? But we can keep short.

Skills

• ...

Benefits

• ...

Pay

...

We must not repeat job title as heading. Good. We need to ensure we don't include filler like "commensurate with experience". Not present. Let's craft content. About the role: Provide description: Tier I + II Service Desk Technician supporting roughly 1,800 users in Oregon government sector, providing support to government leadership and other stakeholders, handling calls, triage, processing tickets, remote support and walk-ins, hybrid contract position based in Salem, OR, intermediate level. Responsibilities: Taking incoming calls, triaging issues, processing service requests, providing remote support via tools (Ivanti, BeyondTrust/Bomgar), handling walk-in support, assisting government leadership and stakeholders, maintaining customer service standards, documenting tickets, escalating as needed. Requirements: Experience with Windows environment, Microsoft 365 (M365) platform, Ivanti ticketing/remote support, familiarity with Bomgar/BeyondTrust Remote Support, strong customer service skills, ability to handle remote support and walk-ins, intermediate experience level, contract position. Qualifications: Intermediate level experience, contract role, ability to work hybrid in Salem, OR. Skills: Microsoft Office, Windows, remote support, Help desk, Service desk, Customer service, Office 365, Ivanti, BeyondTrust (Bomgar). Benefits: List: Medical, dental & vision; Critical Illness, Accident, and Hospital coverage; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions; Life Insurance (Voluntary Life & AD&D for 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). Pay: Pay range $25.00 - $28.00 per hour; compensation based on qualifications, skills, experience, etc. We should not include the sentence about eligibility requirements etc. That's part of benefits description but we can keep as part of benefits description? The instruction: preserve ALL substantive information. So we need to keep the eligibility details? It says "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's substantive about benefits. We could include that as a paragraph under Benefits. Similarly, we should include the note about Application Deadline? That's not in allowed sections; maybe we could put under About the role? But it's not role. Could we add a separate heading like "Application Deadline"? Not allowed per instruction? It 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 using those. Safer to not add extra headings. Could we embed the deadline in a paragraph under About the role? Might be okay but it's not about role. Might be considered boilerplate? It's substantive info about the posting. The instruction says remove application instructions. The deadline is not an instruction but a date. Might be considered part of posting metadata. Could be omitted? The instruction says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can fold minor metadata into a short

or drop it. So we could include a short paragraph with the deadline maybe under About the role? Or we could just drop it. The instruction says "fold minor metadata into a short

or drop it." So we could include a short

somewhere (maybe after the sections) containing the deadline. But they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other

tags. So we could add a

for minor metadata like deadline. However, they also said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The deadline is not an instruction, it's a date. Might be okay to keep. But to be safe, we could include a short

after sections: "

Application deadline: October 2, 2026.

" That's minor metadata. We also need to include workplace type hybrid location Salem OR. Could be in About the role. Now ensure we don't repeat content. Let's craft HTML. We'll need to escape any special characters? Not needed. We'll produce:

About the role

Tier I + II Service Desk Technician supporting approximately 1,800 users in an Oregon government environment, providing support to government leadership and other stakeholders. The role involves taking calls, triaging issues, processing tickets, delivering remote support and handling walk‑in requests in a hybrid contract position based in Salem, OR.

Responsibilities

• Answer incoming service desk calls and triage incidents
• Process service requests and maintain accurate ticket documentation
• Provide remote support using