Field Support Technician

We need to output HTML fragment with sections: About the role? Actually we have "About Us" then "The Role We Want You For" then "The Specifics of the Role" then "Requirements" then "Some Things You Should Know" then "Why Clayco?" then "Benefits" then "Compensation". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to appropriate headings. We have: - About Us: description of company. Could be "About the role"? Actually "About Us" is about company, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map sections accordingly. "About Us" could be considered "About the role"? Not exactly. But maybe we can treat "About Us" as "About the role"? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not limited to those. So we can use those headings if appropriate. We have content about company, role specifics, responsibilities, requirements, benefits, compensation. We'll create sections: - About the role: could combine "About Us" and "The Role We Want You For" maybe. But we need to avoid repeating job title as heading. We'll put a brief description. - Responsibilities: from "The Specifics of the Role" bullet list. - Requirements: from "Requirements" list. - Qualifications: maybe not separate; we could combine with Requirements? But we have no separate qualifications. Could skip. - Skills: maybe from requirements like "Ability to use hand and power tools", "Strong interpersonal and communication skills", etc. Could be separate. - Benefits: from "Benefits" section. - Pay: from "Compensation" section (salary range). - Schedule: maybe from travel requirement: "60% plus Travel". Could be schedule. We must not create sections with filler like "not specified". So only include sections where we have real content. Let's extract content: About Us: Clayco is a full-service, turnkey real estate development, master planning, architecture, engineering, and construction firm that safely delivers clients across North America the highest quality solutions on time, on budget, and above and beyond expectations. With $8.1 billion in revenue for 2025, Clayco specializes in the "art and science of building," providing fast track, efficient solutions for mission critical, industrial, life sciences, power & energy, aviation, commercial, institutional, residential and sports & entertainment related building projects. The Role We Want You For: If you are looking for fast paced technical work that provides the opportunity for travel across the United States, look no further than Clayco. This position assists and provides IT services to internal customers located at our jobsites around the country. Support includes installation, documentation, and testing of computer systems and peripherals, as well as establishing standards and guidelines for supporting local and remote sites. This position requires the ability to identify and organize tickets and requests according to priority. Travel is usually planned in advance, but issues can arise which could warrant immediate travel to one or more local or remote locations. The Specifics of the Role: bullet list of duties. Requirements: list. Some Things You Should Know: includes travel required, collaborative design-build approach, creative complex award-winning high-profile jobs, fast pace, safety-sensitive role, background check, drug testing. Why Clayco?: awards. Benefits: list. Compensation: salary range. We need to produce HTML fragment with

headings and appropriate

or

• . We must not include boilerplate like EEO etc. Not present. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must preserve all substantive information. We need to decide which sections to include. Potential sections: - About the role (combining About Us and The Role We Want You For). Could be two paragraphs. - Responsibilities (The Specifics of the Role bullet list). - Requirements (Requirements list). - Skills (maybe extract from Requirements: "Ability to use hand and power tools", "Lift and move heavy objects (50+ lbs)", "Service industry experience", "Strong interpersonal and communication skills", "Basic MS Office Suite/iOS support", "Experience using enterprise ticketing system (ServiceNow)", "Knowledge of AV solutions", "Experience with cellular technologies (cradlepoints, hotspots)". Could be a skills section. - Benefits (Benefits list). - Pay (Compensation salary range). - Schedule (Travel requirement: "60% plus Travel" and travel details). Could be schedule. - Additional info: "Some Things You Should Know" and "Why Clayco?" maybe could be combined into "About the company" or "Additional details". But we only have headings list; we could add a section like "About Clayco" but not in list. The instruction says use h3 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 stick to those. We could incorporate "Some Things You Should Know" into About the role or Responsibilities? It includes safety-sensitive role, background check, drug testing, fast pace, etc. Could be part of About the role. "Why Clayco?" could be part of Benefits? Not exactly. Could be omitted? But we must preserve ALL substantive information. So we need to include that info somewhere. Could add a section "Why Clayco?" as its own heading, though not in the example list but maybe allowed. The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we could use a heading like "Why Clayco?" as it's substantive. Similarly "Some Things You Should Know" could be a heading. But the instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections, but we could also use others if needed. However to be safe, we could map that info into existing sections: "Some Things You Should Know" includes travel required (already in schedule), safety-sensitive role, background check, drug testing (could be part of Responsibilities? maybe not). Could be part of About the role. "Why Clayco?" includes awards and recognitions; could be part of Benefits? Not really. Could be a separate section "Why Clayco?" as heading. Given the instruction to prefer a few substantive sections over many thin ones, we might combine. Let's think: we could have sections: - About the role (company description + role overview) - Responsibilities (duties) - Requirements (experience, tools, etc.) - Skills (maybe merge with Requirements) - Benefits - Pay - Schedule (travel) - Additional info (safety, background check, awards) maybe as "About Clayco" or "Company highlights". But we need to avoid too many thin sections. Maybe we can have:

  About the role

  (contains About Us + The Role We Want You For + Some Things You Should Know + Why Clayco?)

  Responsibilities

  (The Specifics of the Role)

  Requirements

  (Requirements list)

  Benefits

  (Benefits)

  Pay

  (Compensation)

  Schedule

  (Travel requirement) That seems reasonable and covers all info. We need to ensure we don't repeat content. Let's extract each piece. About Us paragraph: "Clayco is a full-service, turnkey real estate development, master planning, architecture, engineering, and construction firm that safely delivers clients across North America the highest quality solutions on time, on budget, and above and beyond expectations. With $8.1 billion in revenue for 2025, Clayco specializes in the "art and science of building," providing fast track, efficient solutions for mission critical, industrial, life sciences, power & energy, aviation, commercial, institutional, residential and sports & entertainment related building projects." The Role We Want You For paragraph: "If you are looking for fast paced technical work that provides the opportunity for travel across the United States, look no further than Clayco. This position assists and provides IT services to internal customers located at our jobsites around the country. Support includes installation, documentation, and testing of computer systems and peripherals, as well as establishing standards and guidelines for supporting local and remote sites. This position requires the ability to identify and organize tickets and requests according to priority. Travel is usually planned in advance, but issues can arise which could warrant immediate travel to one or more local or remote locations." Some Things You Should Know bullet-ish sentences: "Our clients and projects are nationwide – Travel will be required.No other builder can offer the collaborative design-build approach that Clayco does.We work on creative, complex, award-winning, high-profile jobs.The pace is fast!This position is classified as a safety-sensitive role in accordance with applicable state and federal laws. Candidates selected for this position will be subject to a comprehensive background check, which includes mandatory drug testing." Why Clayco? bullet list: "2025 Best Places to Work – St. Louis Business Journal, Los Angeles Business Journal, and Phoenix Business Journal.2025 ENR Top 400 – Top Data Center Contractor (Top 3).2025 ENR Top 100 Design-Build Firms – Design-Build Contractor (Top 5).2025 ENR Top 100 Green Contractors – Green Contractor (Top 3)." We can combine these into About the role section as paragraphs. Now Responsibilities: The Specifics of the Role bullet list: - Provide day to day support to our remote Jobsites - Prioritize problems and incidents and escalate to internal teams - Basic knowledge of Microsoft products (Windows, Office) - Physical Installation of Meraki networks - Physical Installation of full site Mesh networks - Satellite communication installation - Basic Knowledge of Cisco AV Room kits (Webex) - Basic understanding of Design and Construction delivery process - Create and document training materials and knowledge articles - Provide training on software, hardware, and systems to Clayco Team Members - Preventative maintenance, including checking and cleaning of workstations, printers, and peripherals - Perform post-resolution follow-ups to requests and incidents - Manage printer hardware and software throughout our jobsites - Provide feedback on recurring incidents to engineering and development teams - First line of troubleshooting for remote networks - Adaptive and willing to learn business processes - Self-starter with the ability to work without direct supervision - Effective communication skills and deductive reasoning ability - Work with the Service Desk, Device Support, Engineering, VDC, and Development teams to determine and resolve problems received from clients local and remote. - Work with ISP vendors and managed services support partners to resolve technical problems - Perform regular health checks on equipment at remote sites. - Use diagnostic utilities, knowledge bases, and internet resources to document and create troubleshooting processes that can be utilized by others. - Provide technical assistance for project planning and support. - Identify and inform Leadership of recurring Incidents. - Contribute to company vision and direction by helping improve technical practices. We need to output as
  • items. Requirements list: - 1 to 4 years of experience in IT - 60% plus Travel - Ability to use hand and power tools - Lift and move heavy objects (50+ lbs) - Service industry experience - Strong interpersonal and communication skills - Basic MS Office Suite/iOS support - Experience using enterprise ticketing system (ServiceNow) - Knowledge