IT Support Specialist

We need to output HTML fragment with sections: About the team? The posting includes "About The Team" and "About The Role". Also "Who you are" (qualifications). "Get to know us" maybe about company but could be considered boilerplate? It's about Zillow mission; maybe keep as a paragraph? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Get to know us" and "How we work" etc might be considered boilerplate? It's describing company culture; not strictly required but could be kept as it's substantive? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep those paragraphs as they are substantive about company. However they might be considered generic marketing; but they are part of posting. Likely keep them. We need headings: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map sections accordingly. We have: - About The Team (could be heading "About the team"? Not in list but we can use heading as per content. The list includes "About the role" etc. 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 we should follow that pattern. Probably we should use headings for the sections we have: About The Team, About The Role, Responsibilities (maybe embed within About The Role?), Requirements/Qualifications, Who you are (qualifications), Benefits, Pay, Schedule. However we need to only include sections when posting has real specific content. Let's extract content: About The Team: paragraph about Associate Specialist, Desktop Systems supports day-to-day end-user computing... About The Role: list of duties: Respond to and resolve routine desktop support requests..., Configure, deploy..., Perform basic troubleshooting..., Complete well-defined maintenance tasks..., Maintain accurate asset..., This role requires working Eastern Time (ET) hours. This role has been categorized as a Remote position. ... description of remote. Then after that: Pay info: In California, Connecticut... base pay range $28.70 - $45.90 hourly. In Colorado... $27.30 - $43.50 hourly. Also mention equity awards eligibility, etc. Also mention employees will not be paid below salary threshold for exempt employees. Then "Who you are": High school diploma or equivalent. - 0–2 years of experience... Or equivalent combination. Then "Get to know us": paragraph about Zillow mission. Then "How we work": paragraph about Cloud HQ etc. Then recognition: Zillow honored etc. Then EEO boilerplate: equal opportunity employer etc. That should be removed per instruction (EEO/equal-opportunity boilerplate). Also Los Angeles County applicants specifics: that's likely legal boilerplate; should be removed. Thus we need to output HTML with sections: -

About the Team

...

-

About the Role

maybe we split responsibilities into

• ... but we also have schedule info (ET hours, Remote). Could be separate sections: Schedule and maybe Benefits? There's no explicit benefits besides equity awards eligibility. Could be a Benefits section. We have Pay info: we can make

  Pay

  with paragraphs about ranges. We have Schedule: mention working Eastern Time (ET) hours and Remote position. Could be

  Schedule

  with paragraph. We have Requirements/Qualifications: "Who you are" section: high school diploma, 0-2 years experience, or equivalent combination. Could be

  Qualifications

  with
  • ... maybe also include education. We have Responsibilities: the bullet list under About The Role before schedule. Could be

    Responsibilities

    with
    • ... each duty. We might also have a section "About the Team" as above. We need to avoid repeating job title as heading (page already shows it). So we don't add heading for job title. We need to not put Job ID/requisition numbers as headings (none present). We need to remove boilerplate: EEO, Los Angeles County specifics, etc. We need to preserve all substantive information: So keep the paragraphs about team, role responsibilities, schedule, pay, qualifications, equity awards, etc. Also keep "Get to know us", "How we work", recognition statements? Those are substantive about company; but they might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those paragraphs are not those categories; they are company description. Likely keep them. Thus we may have a section "About Zillow" or "Company Overview". But we don't have a heading for that in the list; we could just put

      after a heading like "About the Company". However the instruction says prefer a few substantive sections over many thin ones. Could combine "Get to know us", "How we work", recognition into a single section maybe "About Zillow". But we need to follow heading convention: maybe use

      About the Company

      . Not in the list but acceptable? The list gave examples; not exclusive. We'll include. But we must not create sections with filler like "commensurate with experience". We have real content. Thus final HTML:

      About the Team

      The Associate Specialist, Desktop Systems supports day-to-day end-user computing by maintaining workstations, peripherals, and standard software, resolving routine technical issues, and completing well-defined service requests under close supervision. This role focuses on delivering reliable, high-quality desktop support so Zillow employees can work productively and securely.

      About the Role

      Respond to and resolve routine desktop support requests for hardware, operating systems, and standard applications, escalating non-routine issues as needed. Configure, deploy, and decommission laptops, desktops, and peripherals by following established imaging, setup, and security procedures. Perform basic troubleshooting for network connectivity, printing, and account access issues, documenting steps taken and outcomes in the ticketing system. Complete well-defined maintenance tasks such as software installs, updates, and basic device checks in line with standard operating procedures. Maintain accurate asset and configuration information for end-user devices to support inventory tracking and lifecycle management.

      Responsibilities

      ... Actually we already put responsibilities in About the Role; maybe we should separate. But we could keep About the Role as intro and then Responsibilities list. However we already included duties in About the Role paragraph. To avoid duplication, we could keep About the Role as brief intro and then Responsibilities list. But the instruction says preserve ALL substantive information; we can keep both but ensure not duplicate. The About the Role paragraph currently includes the duties; if we also list them as
      , that duplicates. Better to have About the Role as a short summary and then Responsibilities list. However the original text didn't have a separate summary; it's just the list. So we could treat the list as Responsibilities and not have an About the Role section. But we need a heading for About the Role? The instruction says use

      for section headings (e.g. About the role...). So we should have an About the role heading. Under it we can put the responsibilities list. That seems fine. Thus:

      About the Role

      • Respond to and resolve routine desktop support requests for hardware, operating systems, and standard applications, escalating non-routine issues as needed.
      • Configure, deploy, and decommission laptops, desktops, and peripherals by following established imaging, setup, and security procedures.
      • Perform basic troubleshooting for network connectivity, printing, and account access issues, documenting steps taken and outcomes in the ticketing system.
      • Complete well-defined maintenance tasks such as software installs, updates, and basic device checks in line with standard operating procedures.
      • Maintain accurate asset and configuration information for end-user devices to support inventory tracking and lifecycle management.
      Then schedule:

      Schedule

      This role requires working Eastern Time (ET) hours. This role has been categorized as a Remote position. “Remote” employees do not have a permanent corporate office workplace and, instead, work from a physical location of their choice, which must be identified to the Company. U.S. employees may live in any of the 50 United States, with limited exceptions.

      Pay:

      Pay

      In California, Connecticut, Maryland, Massachusetts, New Jersey, New York, Washington state, and Washington DC the standard base pay range for this role is $28.70 - $45.90 hourly. This base pay range is specific to these locations and may not be applicable to other locations.

      In Colorado, Hawaii, Illinois, Maine, Minnesota, Nevada, Ohio, Rhode Island, Vermont, and Virginia the standard base pay range for this role is $27.30 - $43.50 hourly. The base pay range is specific to these locations and may not be applicable to other locations.

      In addition to a competitive base salary this position is also eligible for equity awards based on factors such as experience, performance and location. Actual amounts will vary depending on experience, performance and location.

      Employees in this role will not be paid below the salary threshold for exempt employees in the state where they reside.

      Qualifications:

      Qualifications

      • High school diploma or equivalent.
      • 0–2 years of experience in desktop support, end-user computing, or a related technical support role.
      • Or an equivalent combination of education and experience.
      Company overview: We could have

      About Zillow

      with paragraphs from "Get to know us", "How we work", recognition. Let's extract those paragraphs: Get to know us: "At Zillow, we’re reimagining how people move—through the real estate market and through their careers. As the most-visited real estate platform in the U.S., we help people navigate buying, selling, financing and renting with greater ease and confidence. Whether you're working in tech, sales, operations, or design, you’ll be part of a company reshaping an industry and helping more people make home a reality." How we work: "Through Cloud HQ, our strategic approach to distributed work, most employees have the flexibility to work from wherever they’re most productive—enabling us to move fast, stay connected and deliver on our people promise." Recognition: "Zillow is honored to be recognized among the best workplaces in the U.S. Zillow was named one of FORTUNE 100 Best Companies to Work For® in 2026, and included on TIME’s America’s Best Companies 2026 list, reflecting our commitment to creating an innovative, inclusive, and engaging culture where employees are empowered to grow." We could combine into one

      or multiple

      . We'll keep as separate paragraphs under the heading. Thus:

      About Zillow

      At Zillow, we’re reimagining how people move—through the real estate market and through their careers. As the most-visited real estate platform in the U.S., we help people navigate buying, selling, financing and renting with greater ease and confidence. Whether you're working in tech, sales, operations, or design, you’ll be part of a company reshaping an industry and helping more people make home a reality.

      Through Cloud HQ, our strategic approach to distributed work, most employees have the flexibility to work from wherever they’re most productive—enabling us to move