IT Desktop Administrator

We need to output only HTML fragment, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. Let's parse. Job description content: - Intro: "The IT Desktop Administrator will be responsible for diagnosing and troubleshooting PC systems, software/hardware updates, maintaining backups, diagnostics of failing components, and imaging/deployment of new systems. The desktop administrator supports end users remotely to resolve their PC problems along with arranging for systems to be shipped to the administrator for resolution. This position relies on instructions and pre-established guidelines to perform the functions of the job" That's about role. Could be "About the role" section. - Functions/Responsibilities list: Provide subject matter expertise in resolving incidents and problems. Execution of service requests. Contributes to the planning and organization of the deployment of new systems. Participates in departmental and cross-departmental IT projects. Lead and train fellow desktop administrators in organizational procedures. Assists in organizational training Contributor of the knowledge store used by the desktop support team. Monitor activities performed by the desktop support team and ensure that execution is compliant with procedures. Ensure that asset management library is accurate. Follows best practices and standards for the desktop support team. Execute the asset management procedure. Contributes to the project planning of hardware and software procurement process. That's responsibilities. - Top Skills' Details: "3-5+ years experience with: Developing images for deployments Windows and/or macOS environment (an absolute need) IT Desktop support experience Any server related experience is a bonus and will highly favor mac experience Skills Preferred Desktop, Building Images, SCCM, Azure, Imaging, Deployment, server support Additional Skills & Qualifications Candidates with high level MAC experience will be highly favorable/preferred" That's skills/requirements. - Pay And Benefits: Pay range $25.00 - $30.00/hr. Benefits listed: 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 note eligibility etc. - Workplace Type: This is a fully onsite position in Grand Rapids, MI. - Application Deadline: This position is anticipated to close on Oct 9, 2026. (We should drop application instructions? The instruction says remove application instructions. Deadline maybe considered metadata; but we could include as short p? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Deadline is metadata; we could include in a short p maybe under a generic section? But we have no section for metadata. Probably we can drop it. - About TEKsystems: boilerplate about company, equal opportunity, etc. Should be removed as boilerplate/legal/EEO. So we drop that. Thus sections we have: About the role (intro), Responsibilities (list), Skills (maybe Requirements/Qualifications combined), Benefits, Pay, Schedule? Schedule not given. Workplace type maybe could be considered Schedule? Not exactly. There's no schedule info (like full-time, part-time, shift). So we should not create Schedule section. We need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine Requirements and Qualifications maybe but we need to decide which to include. The posting has skills and experience requirements; we could put them under Requirements or Skills. Since we have both Requirements and Qualifications headings available, we could put experience under Requirements and skills under Skills. But we must not create empty sections. So we need to decide if we have content for each. We have content for: About the role (intro). Responsibilities (list). Requirements (experience: 3-5+ years experience with developing images for deployments Windows/macOS, IT Desktop support experience, server related experience bonus). Qualifications maybe could be "Additional Skills & Qualifications" but that's similar to skills. Could treat that as Qualifications. Skills: list of preferred skills: Desktop, Building Images, SCCM, Azure, Imaging, Deployment, server support, high level MAC experience. We could split: Requirements: experience (years, etc). Qualifications: maybe "Candidates with high level MAC experience will be highly favorable/preferred" plus maybe "Any server related experience is a bonus". But that seems overlapping. Better: Use Requirements for the experience bullet list, Qualifications for the "Additional Skills & Qualifications" line (Candidates with high level MAC experience will be highly favorable/preferred). Skills for the list of preferred skills (Desktop, Building Images, SCCM, Azure, Imaging, Deployment, server support). That seems reasonable. Benefits: we have benefits list. Pay: we have pay range. Schedule: not present, so we should NOT include Schedule heading. We must not include empty sections. Thus output HTML with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Each heading

. Then content: For prose use

. For lists use

• . We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from each section. Let's extract precise text. About the role: The first paragraph: "The IT Desktop Administrator will be responsible for diagnosing and troubleshooting PC systems, software/hardware updates, maintaining backups, diagnostics of failing components, and imaging/deployment of new systems. The desktop administrator supports end users remotely to resolve their PC problems along with arranging for systems to be shipped to the administrator for resolution. This position relies on instructions and pre-established guidelines to perform the functions of the job" We'll put that in a

  . Responsibilities: list items as given. Need to ensure we keep each bullet exactly as in posting. Let's list: - Provide subject matter expertise in resolving incidents and problems. - Execution of service requests. - Contributes to the planning and organization of the deployment of new systems. - Participates in departmental and cross-departmental IT projects. - Lead and train fellow desktop administrators in organizational procedures. - Assists in organizational training - Contributor of the knowledge store used by the desktop support team. - Monitor activities performed by the desktop support team and ensure that execution is compliant with procedures. - Ensure that asset management library is accurate. - Follows best practices and standards for the desktop support team. - Execute the asset management procedure. - Contributes to the project planning of hardware and software procurement process. Note there is a line "Assists in organizational training" then next line "Contributor of the knowledge store used by the desktop support team." It seems missing a period after training but we keep as is. We'll output each as

• . Requirements: experience details: "3-5+ years experience with: Developing images for deployments Windows and/or macOS environment (an absolute need) IT Desktop support experience Any server related experience is a bonus and will highly favor mac experience" We need to preserve that exactly. Could break into
  items? The posting uses colon and list. We could treat as a

  preserving the text. But instruction: Use

  • for any list of duties/requirements/benefits. This is a list of requirements, so we should use
    • . However the text is not clearly separated items; we could split by commas? Better to keep as a

      to avoid misrepresenting. But instruction says use

      • for any list of duties/requirements/benefits. The requirements are a list; we can make each item separate: "Developing images for deployments Windows and/or macOS environment (an absolute need)", "IT Desktop support experience", "Any server related experience is a bonus and will highly favor mac experience". Also the "3-5+ years experience with:" prefix. Could incorporate as leading text. Might be okay to keep as

        with the full sentence. But to follow instruction, we could do

        3-5+ years experience with:

        then
        • Developing images for deployments Windows and/or macOS environment (an absolute need)
        ... etc. That seems acceptable. Qualifications: "Candidates with high level MAC experience will be highly favorable/preferred". Also maybe "Additional Skills & Qualifications" heading but we treat as qualifications. We'll put that in

        . Skills: list: "Desktop, Building Images, SCCM, Azure, Imaging, Deployment, server support". Also maybe "high level MAC experience" but that's already in qualifications. We'll keep skills list as those. We'll output as

        • Desktop
        etc. Benefits: list as given. We'll make
        • each. Pay: "$25.00 - $30.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:" then list benefits. Actually the benefits list appears after that sentence. We'll keep the introductory sentence as

          then

          for benefits. We must not include boilerplate like "Eligibility requirements apply..."? That's part of pay/benefits description, we keep. Now ensure we don't include any application instructions, EEO, etc. We also need to drop the line about "Please apply if you're interested..." etc. Also drop "We are looking to set up interviews as early as next week". Also drop email, job type location? Actually job type and location: "This is a Contract to Hire position based out of Grand Rapids, MI." That's substantive? Could be considered metadata but maybe we should keep as part of About the role? The instruction says fold minor metadata into a short

          or drop it. Job type and location maybe minor metadata; we could include in a short p under About the role or separate? But we already have About the role with intro; we could add another p about job type and location. However the instruction says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

          or drop it." So we can include a short p for job type and location. Also Workplace Type: "This is a fully onsite position in Grand Rapids,MI." That's similar; we could combine. We also have "Application Deadline This position is anticipated to close on Oct 9, 2026." That's metadata; we could drop or include as short p. The instruction says remove application instructions; deadline maybe not instruction but still metadata. Safer to drop it. Thus we may add a short p under About the role: "This is a Contract to Hire position based out of Grand Rapids, MI. This is a fully onsite position." Could combine. But we must not repeat job title as heading; fine. Now ensure we don't include any duplicated lines. Let's craft HTML. We'll start with

          About the role

          then

          The IT Desktop Administrator will be responsible for diagnosing and troubleshooting PC systems, software/hardware updates, maintaining backups, diagnostics of failing components, and imaging/deployment of new systems. The desktop administrator supports end users remotely to resolve their PC problems along with arranging for systems to be shipped to the administrator for resolution. This position relies on instructions and pre-established guidelines to perform the functions of the job.

          Then maybe another

          This is a Contract to Hire position based out of Grand Rapids, MI. This is a fully onsite position.

          Then