Data Center Cabling Foreman

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, etc. Also remove application instructions (none). Must not create sections with filler like "commensurate with experience" etc. For Pay, we have salary range $90,000-$115,000 (commensurate with experience) full benefits, project bonuses, paid travel, advanced training. The phrase "commensurate with experience" is filler? It's part of pay description but we should not include placeholder text like "commensurate with experience". The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. So we can include Pay section but must avoid filler text. We could phrase as "$90,000-$115,000 salary range, full benefits, project bonuses, paid travel, advanced training." That removes the filler phrase. That's acceptable. Schedule: The posting says "This position requires 75% travel to project sites nationwide, including AI build locations." Also earlier: "Willingness to travel 75% and work extended hours during active builds". So schedule includes travel 75% and possibly extended hours. We can include Schedule section with that info. Avoid filler like "varies". It's specific. Benefits: There's a "Tier 2 Benefits and Perks:" list with many items. So we include Benefits section with that list. About the role: The initial paragraph about Align, culture, etc. Could be About the role or maybe About the company. The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have "Position Overview" describing role. That could be About the role. We'll put that in

About the role

with paragraphs. Responsibilities: list under Key Responsibilities. Requirements: maybe Required Qualifications. Qualifications: maybe Preferred Qualifications. Skills: maybe we can extract skills like Excel, fiber testing tools, reading drawings, etc. Could be under Skills. But we must not create thin sections. We need to decide which sections to include based on content. We have: - About the role: Position Overview paragraph(s). Also maybe the introductory marketing about Align could be considered About the role? But we can keep it as About the role. - Responsibilities: bullet list. - Requirements: Required Qualifications (list). - Qualifications: Preferred Qualifications (list). - Skills: maybe we can combine some skill statements from Required Qualifications (Ability to read cabling drawings, Experience using fiber testing tools, Strong Excel skills, Comfortable working in live data center environments). Could be separate Skills section. - Benefits: list. - Pay: salary range and benefits (but benefits already separate). Pay section could just contain salary range and maybe project bonuses, paid travel, advanced training. - Schedule: travel 75% and extended hours. We must avoid duplication. Ensure we preserve all substantive info. Let's extract details. About the role: The Position Overview paragraph: "As a Data Center Cabling Foreman, you will support large-scale cabling installations for major AI and hyperscale data centers across the U.S. This hybrid role blends field leadership with hands-on work, ideal for someone who has grown beyond a Foreman role but is not yet a full Superintendent. You’ll assist the Superintendent with planning, standards enforcement, and on-site execution while working directly with technicians, contractors, and vendors. This role is heavily field-facing and requires strong technical skills, attention to detail, and the ability to help keep teams aligned with project timelines and quality expectations." Also earlier marketing paragraph about Align: "Join the Team! Is technology your passion? Do you want to work with smart, forward-thinking individuals? Do you want to grow in a career you love? At Align, our professionals are the key to our success. We don’t just hire talent, we invest in exceptional people who are forward-thinking, results-driven, and passionate about what they do. We’re a group of tech-savvy professionals who are motivated by making an impact. Our culture is one of unbounded opportunity that celebrates the passions, skills and ideas of our team—work hard, play hard, be smart! We believe great communities lead to great companies. That’s why we offer a dynamic workplace where you feel inspired, engaged and innovative. We offer professionals opportunities to train in the leading technologies, make an impact within the industry and acquire valuable new skills whether on client sites or in one of our regional offices." That seems like About the company/culture. Could be part of About the role or maybe we could omit as it's fluff? But it's substantive info about company. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Could be placed under About the role as well. Thus About the role section will contain two paragraphs: the marketing/intro and the position overview. Responsibilities: list items: - Support structured cabling installations in new data center white space and help coordinate daily work for cabling crews under the Superintendent. - Perform on-site QA checks for fiber/copper terminations, labeling, routing, and test results while reinforcing jobsite safety. - Assist with cabling standards, tracking sheets, patch schedules, port maps, and drawing reviews to ensure work meets TIA/BICSI specifications. - Communicate field progress, schedule risks, and material needs to project leadership. - Support documentation, RFIs, change orders, daily reports, and QA/QC corrective actions. Requirements (Required Qualifications): - 2-4+ years experience in structured cabling, low-voltage, or fiber optic systems (data center or mission-critical preferred). - Experience leading small cabling crews (foreman or lead technician level). - Ability to read cabling drawings, rack elevations, and labeling standards. - Experience using fiber testing tools (OLTS, OTDR, VFL). - Strong Excel skills for port mapping, tracking, and documentation. - Comfortable working in live data center environments with fast-paced schedules. - Willingness to travel 75% and work extended hours during active builds. Note: The last two items about travel and extended hours could also go to Schedule, but they are in Required Qualifications. We'll keep them in Requirements but also maybe schedule section. To avoid duplication, we could move travel and extended hours to Schedule section and remove from Requirements. However we must preserve all substantive info; we can keep them in both places? Duplication might be okay but better to avoid redundancy. The instruction: do not repeat job title as heading, but doesn't forbid repeating content. However better to keep each piece once. Let's allocate travel and extended hours to Schedule section, and keep other qualifications in Requirements. Thus Requirements list: - 2-4+ years experience in structured cabling, low-voltage, or fiber optic systems (data center or mission-critical preferred). - Experience leading small cabling crews (foreman or lead technician level). - Ability to read cabling drawings, rack elevations, and labeling standards. - Experience using fiber testing tools (OLTS, OTDR, VFL). - Strong Excel skills for port mapping, tracking, and documentation. - Comfortable working in live data center environments with fast-paced schedules. Qualifications (Preferred Qualifications): - Experience supporting data center cabling deployments. - Understanding of racks, containment systems, and cable pathways. - Familiarity with TIA/EIA or BICSI standards. - Certifications such as BICSI Technician or Installer II. Skills: Could we extract skill statements not already covered? Many are in Requirements. Could combine some like "strong technical skills, attention to detail, ability to help keep teams aligned with project timelines and quality expectations" from About the role. Also "ability to read cabling drawings" etc. Might be redundant. Perhaps we can omit Skills section if it would be thin. But we have some skill statements not captured: "strong technical skills, attention to detail, ability to help keep teams aligned with project timelines and quality expectations" (from About the role). Also "ability to communicate field progress, schedule risks, and material needs". That's more responsibility. Could be considered skill. Given we already have Requirements and Qualifications covering technical skills, maybe we can skip Skills section to avoid thin content. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills if it would be thin. Benefits: list from Tier 2 Benefits and Perks: - Comprehensive Medical, Dental, and Vision coverage - Health Savings Account (HSA) and Flexible Spending Account (FSA) options - 401(k) plan with a dollar-for-dollar company match at 3% up to an annual maximum of $5k. - Complimentary ClassPass membership to support your health and wellness goals - Generous Paid Time Off (PTO) - Company-paid holidays - Cellphone Reimbursement Program - Floating Holiday to celebrate a day that is meaningful to you - Pre-tax commuter benefits, where applicable - Employee wellness programs, events, and team-building activities - Employee referral program Pay: salary range $90,000-$115,000, full benefits, project bonuses, paid travel, advanced training. But we already have Benefits section covering benefits; we should not duplicate benefits in Pay. Pay section should contain salary range and maybe project bonuses, paid travel, advanced training. However paid travel is also schedule? It's a benefit? It's mentioned as part of compensation. We'll include in Pay: "$90,000-$115,000 salary range, project bonuses, paid travel, advanced training." Avoid filler "commensurate with experience". Also "full benefits" is duplicate; we can omit. Schedule: travel 75% and work extended hours during active builds. Also maybe mention hybrid role? But schedule is about travel and hours. We'll put: "Requires 75% travel to project sites nationwide, including AI build locations; may require extended hours during active builds." Now ensure we don't include any boilerplate like EEO, etc. There's a paragraph about interview recordings: "To support a fair, consistent, and high-quality hiring experience, some interviews may be recorded..." That's not boilerplate? It's about hiring process. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The interview recording notice is not exactly those categories, but could be considered part of hiring process. It's substantive? It's about the interview process. Might be considered application instructions? It's not exactly instructions to apply, but it's about interview process. The instruction says remove application instructions. This is about interview recording, not application. Might be okay to keep? However it's not directly about the job role. It's about hiring process. Could be considered boilerplate? Not sure. Safer to remove it as it's not about the job itself. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's about interview process. I'd lean to keep it? But it's not about the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The interview recording notice is substantive about hiring process. However many job postings include such statements; they might be considered boilerplate. The instruction didn't explicitly mention interview recording as boilerplate. I'd keep it maybe under a separate section? But we don't have a heading for that. Could add a

after sections? But we only allowed headings list; we could just include a paragraph without heading? The instruction says use

for section