Cable Technician

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. Let's parse the description. First paragraph: "Description Candidate should bring a strong bkgrd in physically demanding construction-related environments and has demonstrated the reliability, work ethic, and positive attitude needed to succeed in a data center setting. While telecom experience is limited, the candidate has a proven ability to learn quickly, follow direction, and adapt to new job requirements. Accustomed to working long 10-hour shifts in challenging outdoor conditions, including extreme heat and cold, with a consistent record of dependability and attendance. Hiring manager is seeking a trainable individual with a strong work ethic, and this candidate aligns well with those priorities." That's basically about the role / candidate profile. Could go under "About the role" or maybe "Qualifications". We'll decide. Key Responsibilities bullet list: Pull and route cabling throughout the data center; Assemble, stack, and drill racks; Scan, label and port equipment; Support general installation tasks as directed by experienced technicians. Additional Required Attributes: Experience working in physically demanding environments (construction, trades, military, or similar); Strong work ethic and positive attitude; Reliable attendance history; Hands on electrical or military experience is highly valued; Must be able to work on ladders and lifts. Additional Skills & Qualifications: Ideal personality profile is a hard worker who wants to grow with an organization, who is honest, and reliable. There is a lot of growth opportunity and looking for people who want to be leaders. This will most likely be a long term contract with the ability to go direct as an FTE once headcount becomes available. Job Type & Location: This is a Contract to Hire position based out of Summerville, SC. Pay And Benefits: The pay range for this position is $20.00 - $20.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 fully onsite position in Summerville,SC. Application Deadline: This position is anticipated to close on Oct 2, 2026. About TEKsystems: paragraphs about company, equal opportunity, etc. Must remove boilerplate/legal/EEO etc. The instructions: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the About TEKsystems sections (they are boilerplate). Also remove Application Deadline? It's not a boilerplate but maybe considered application instruction? It's a date; but they said remove application instructions. The deadline is not an instruction but could be considered metadata. However they said "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Application deadline is minor metadata; we could fold into a short p or drop it. Probably better to drop it as it's not substantive about the role. The instructions: "Preserve ALL substantive information; do NOT invent or summarize away detail." The deadline is substantive? Might be considered minor metadata. I'd lean to drop it, as it's not about the role responsibilities etc. But we could include a short paragraph under maybe "About the role" or separate? The instruction says fold minor metadata into a short

or drop it. So we could include a short p with the deadline. However they also said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Application deadline could be considered application instruction? It's not instruction but it's about application. Safer to drop it. Workplace Type: fully onsite position in Summerville,SC. That's substantive about schedule/location. Could be under Schedule or maybe a separate section? We have Schedule heading; we could put location there. But schedule is about hours/shift? Not given. Could include location under Schedule or maybe under About the role. Since we have Schedule heading, we could include "Fully onsite in Summerville, SC". But schedule also could include shift length? Not given. We'll include location under Schedule. Pay And Benefits: we have pay range and benefits list. So we need Pay and Benefits sections. According to rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need separate headings for Pay and Benefits. However we could combine if content is thin? They said prefer a few substantive sections over many thin ones. But we have both pay and benefits substantive. So we will include both. We also need Requirements, Qualifications, Skills sections. We have Required Attributes, Additional Skills & Qualifications. Could map Required Attributes to Requirements, Additional Skills & Qualifications to Qualifications or Skills. We need to decide. We have "Key Responsibilities" -> Responsibilities. We have "Additional Required Attributes" -> Requirements. We have "Additional Skills & Qualifications" -> could be Qualifications and Skills. But we have both Qualifications and Skills headings available. We could split: Qualifications: Ideal personality profile is a hard worker who wants to grow with an organization, who is honest, and reliable. There is a lot of growth opportunity and looking for people who want to be leaders. This will most likely be a long term contract with the ability to go direct as an FTE once headcount becomes available. Skills: maybe none else? Could include "Hands on electrical or military experience is highly valued" but that's already in Required Attributes. Could also include "Ability to work on ladders and lifts". That's also Required Attributes. Maybe we treat Required Attributes as Requirements, Additional Skills & Qualifications as Skills (or Qualifications). Let's map: - About the role: initial description paragraph (Candidate should bring...). - Responsibilities: bullet list. - Requirements: Additional Required Attributes bullet list. - Qualifications: maybe we could include "Ideal personality profile is a hard worker who wants to grow with an organization, who is honest, and reliable. There is a lot of growth opportunity and looking for people who want to be leaders. This will most likely be a long term contract with the ability to go direct as an FTE once headcount becomes available." That's more about qualifications. - Skills: maybe we could include "Hands on electrical or military experience is highly valued; Must be able to work on ladders and lifts." But those are already in Requirements. Could also include "Ability to learn quickly, follow direction, adapt to new job requirements" from description. But that's more about qualifications. We need to avoid duplication. Let's think: The posting includes: - Description (first paragraph) about candidate background. - Key Responsibilities (list). - Additional Required Attributes (list). - Additional Skills & Qualifications (paragraph). - Job Type & Location (Contract to Hire, Summerville SC). - Pay And Benefits (pay range, benefits list). - Workplace Type (fully onsite). - Application Deadline (date). - About TEKsystems (boilerplate). We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Benefits and Pay separate. We have Schedule: we could include shift length? Not given. Could include "long 10-hour shifts" from description. That's schedule info. Also "fully onsite". So Schedule section could include "Long 10-hour shifts; Fully onsite in Summerville, SC". That seems appropriate. Thus we can use Schedule heading for shift and location. Now we need to decide what goes into About the role: maybe the initial description paragraph. Responsibilities: bullet list. Requirements: Additional Required Attributes bullet list. Qualifications: Additional Skills & Qualifications paragraph (maybe also include "Contract to Hire position based out of Summerville, SC"? That's job type/location but we already used location in Schedule. Could also include "Contract to Hire" under Qualifications? Might be better to put Job Type under About the role? But we already used About the role for candidate background. Could add job type there. But we must not repeat job title. Job type is not title. We could include "Contract to Hire position based out of Summerville, SC" under About the role or Schedule. Since we already used location in Schedule, we could mention contract type there. But Schedule heading is for schedule; contract type is not schedule. Maybe better to put Job Type under About the role as a short sentence. Let's think: The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have those headings. We need to include only those with real content. Thus we will produce:

About the role

Candidate should bring a strong background in physically demanding construction-related environments and has demonstrated the reliability, work ethic, and positive attitude needed to succeed in a data center setting. While telecom experience is limited, the candidate has a proven ability to learn quickly, follow direction, and adapt to new job requirements. Accustomed to working long 10-hour shifts in challenging outdoor conditions, including extreme heat and cold, with a consistent record of dependability and attendance. Hiring manager is seeking a trainable individual with a strong work ethic, and this candidate aligns well with those priorities. This is a Contract to Hire position based out of Summerville, SC.

Responsibilities

• Pull and route cabling throughout the data center
• Assemble, stack, and drill racks
• Scan, label and port equipment
• Support general installation tasks as directed by experienced technicians

Requirements

• Experience working in physically demanding environments (construction, trades, military, or similar)
• Strong work ethic and positive attitude
• Reliable attendance history
• Hands on electrical or military experience is highly valued
• Must be able to work on ladders and lifts

Qualifications

Ideal personality profile is a hard worker who wants to grow with an organization, who is honest, and reliable. There is a lot of growth opportunity and looking for people who want to be leaders. This will most likely be a long term contract with the ability to go direct as an FTE once headcount becomes available.

Skills

Ability to learn quickly, follow direction, and adapt to new job requirements; comfortable working in extreme heat and cold; dependable attendance.

But we already used some of those in About the role and Requirements. Might be duplication. Better to keep Skills minimal but not duplicate. Perhaps we can omit Skills section if content is thin. The instruction: prefer a few substantive sections over many thin ones. So we could drop Skills if not enough distinct content. Let's see if we have any distinct skill not covered elsewhere: "Ability to learn quickly, follow direction,