Data Center Technician (On-site)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Include only sections with real specific content. Must preserve all substantive info. We need to parse the posting. First part: "Who is Trace3?" description: It's about company. Probably not needed as a section? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The company description could be part of About the role? Actually "About the Role:" appears later. The earlier "Who is Trace3?" is company overview, not required to be a section. Could be omitted? The instruction: "Prefer a few substantive sections over many thin ones." We could include a brief intro as a

  before sections? Not required but we can include as a paragraph before sections. The output only HTML fragment; we can include a

  describing Trace3? Not required but could be considered substantive. However the instruction: "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 stick to those. The company description could be placed as a

  before the first heading. Now extract sections: About the Role: The text after "About the Role:" includes: "Under the general direction of the Lead, Data Center Services, the Data Center Technician will physically support and provide remote-hand services to customers.*** This is a position with a 100% Onsite requirement***" That's prose. Could be a

  . Responsibilities: The "What You’ll Do:" section with bullet points grouped by percentages. We need to list duties. Could break into

  • items. The percentages are not required but we can keep them as part of each bullet. We have categories: Data Center Infrastructure & Cabling: 30% then list of duties. Compute/Network/Storage support: 30% then list. Asset Management: 20% then list. Other: 20% then list. We can combine all duties into a single list or separate subheadings? The instruction: Use
    • for any list of duties/requirements/benefits. Could have multiple lists under subheadings? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No subheadings. So we can put all duties under Responsibilities as a
      • . That's fine. Requirements: Might be same as Qualifications? The posting has "Qualifications and Interests". That's a list of qualifications. Could treat as Requirements section? The instruction: Use headings for Requirements and Qualifications separately. But we have only one block that includes both qualifications and interests. We could split: Requirements: maybe the experience and skills needed? Qualifications: education/certification? However we need to avoid thin sections. Might combine into Qualifications section only, and omit Requirements if not distinct. But we need to preserve all substantive info. We could put all qualification-related content under Qualifications heading, and maybe Requirements heading empty? Not allowed: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we cannot have empty Requirements. So we need to decide whether to have Requirements or Qualifications. The posting includes "Qualifications and Interests". That's likely the Qualifications section. There's also a separate "Qualifications and Interests" heading. There's no separate "Requirements". So we will have a Qualifications section. Skills: Could be derived from qualifications list (proficiency in Microsoft Office, etc.). But we could also have a Skills section separate. However we have limited headings; we could put skills under Qualifications as well. But we need to follow instruction: Use headings for Skills if there is real specific content. The posting does not have a separate "Skills" heading, but we could extract skills from qualifications: "Good command of written and spoken English.", "Proficiency in Microsoft Office", "Strong attention to detail", "Some Travel is available." Those are skills. Could create a Skills section. But we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to have Qualifications include skills and education. We'll have Qualifications section containing both. Benefits: The "The Perks" section lists benefits. So we will have Benefits heading with a
        • list. Pay: The posting includes "Estimated Pay Range: $27 USD - $32 USD". Also mentions variable incentive compensation. So we have Pay section with that info. Schedule: The posting mentions "*** This is a position with a 100% Onsite requirement***". That's schedule/location. Could be considered Schedule. So we will have Schedule section with that note. Now we need to output HTML fragment: start with maybe a

          about Trace3? Could include as intro. Not required but could be included as a paragraph before sections. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can have multiple elements. Let's craft:

          Trace3 is a leading Transformative IT Authority, providing unique technology solutions and consulting services to our clients. Equipped with elite engineering and dynamic innovation, we empower IT executives and their organizations to achieve competitive advantage through a process of Integrate, Automate, Innovate. Our culture at Trace3 embodies the spirit of a startup with the advantage of a scalable business. Employees can grow their career and have fun while doing it! Trace3 is headquartered in Irvine, California. We employ more than 1,200 people all over the United States. Our major field office locations include Denver, Indianapolis, Grand Rapids, Lexington, Los Angeles, Louisville, Texas, San Francisco. Ready to discover the possibilities that live in technology? Come Join Us!

          Then sections:

          About the Role

          Under the general direction of the Lead, Data Center Services, the Data Center Technician will physically support and provide remote-hand services to customers. This is a position with a 100% Onsite requirement.

          Responsibilities

          • Data Center Infrastructure & Cabling (30%): Support day-to-day operations of data center and execute various projects; perform analysis and consulting of customers IT infrastructure hardware in production; perform walkthrough with customer to determine ability to deliver project; install and manage structured cabling infrastructure projects; elicit Data Center infrastructure requirements from clients; install, terminate, test, and label all cross connects (copper and fiber) in the data center according to standard operating procedures; perform preventative maintenance and repairs by troubleshooting cabling system issues; troubleshoot and address physical issues; create straight-through, crossover, and console cables; move/install shelves, power strips, rails, cable management, servers, switches, and other equipment with requirements.
          • Compute/Network/Storage support (30%): Identify and report problem devices; replace defective parts as directed; visually inspect equipment for errors or unusual noises; assist performing infrastructure readiness tests; configure OOB (out of band) management interfaces on various devices for remote access (compute, storage and networking); test and validate remote accessibility to the customer computer, server and/or network system; monitor and perform on-going maintenance on servers and network equipment; upgrade internal system components, including CPUs, memory, hard drives, and network cables; create and maintain service desk documentation.
          • Asset Management (20%): Provide a plan, unpack received items, identify parts, and dispose of all non-essential items; must report results and give recommendations; ensure that power tests and reports on all incoming products are conducted before they are moved to the data center floor, per practices; digitally scan all incoming paperwork, transmit results, and proactively provide recommendations on gaps; input all device locations and cable connections into a customer-defined database; record all received products into a customer-defined database (including asset tags information, product manufacturer, model, and serial number); consult and conduct inventory control; compare received products to the packing slip and report discrepancies; identify customer-defined spare parts and keep them in an inventory-controlled area; recommend changes.
          • Other (20%): Maintain a high level of customer satisfaction; review work orders proactively and as post-work quality assurance to ensure requests are handled appropriately; actively participate during the service transition phase to perform knowledge transfer and documentation; develop documentation to maintain accurate records of customer computer, server, and network systems; shipping/loading dock management (report new items received); accept, fulfill, and report status via the ticketing system, time reports, and email processes; escort vendors and repair technicians as requested by the customer; perform crisis management in critical situations or during major service outages; communicate with stakeholders according to SLAs (service level agreements); perform root cause analysis; follow the Company's best practices and Standard Operating Procedures; mentor lower-level Data Center Technicians; may perform other duties as assigned by supervisor.

          Qualifications

          • Minimum of two years’ experience in a technical or data center support role.
          • Independently research Internet technologies (firewall/router/switch/VPN/DNS/Proxy).
          • Good understanding of the OSI model.
          • Good command of written and spoken English.
          • Excellent customer service skills.
          • Proficiency in Microsoft Office (Word, Excel, PowerPoint, etc.).
          • Strong attention to detail.
          • Some travel is available.
          • Education/Certification: High School diploma/GED required.
          • CompTIA, A+, BICSI or similar certification is preferred.

          Benefits

          • Comprehensive medical, dental and vision plans for you and your dependents.
          • 401(k) Retirement Plan with Employer Match.
          • 529 College Savings Plan.
          • Health Savings Account.
          • Life Insurance.
          • Long-Term Disability.
          • Competitive Compensation.
          • Training and development programs.
          • Major offices stocked with snacks and beverages.
          • Collaborative and cool culture.
          • Work-life balance and generous paid time off.

          Pay

          Estimated Pay Range: $27 USD - $32 USD (actual salary based on location, experience, skill set, performance, licensure, certification, and business needs; certain positions may also be eligible for variable incentive compensation such as bonuses or commissions).

          Schedule

          100% Onsite requirement.

          Check for any boilerplate removed: We removed the "Street-Smart - Thriving in Dynamic Times", "Juice - The “Stuff” it takes to be a Needle Mover", "Teamwork - Humble, Hungry and Smart" sections (those are cultural values). Those could be considered part of company description but we omitted them. Are they substantive? They are cultural values; could be considered part of About the company but not required sections. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The cultural values are not boilerplate; they are substantive. However we have no heading for them. Could we include them as a

          under About the Role? Not appropriate. Could we add a section "Culture"? Not allowed headings list. The instruction says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills