Low Voltage Engineer

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. The posting includes: "The Opportunity" paragraph describing role. Could map to About the role. Responsibilities: bullet list of duties (the "What you will do?" list). Requirements: maybe "Required Qualifications". Qualifications: maybe "Preferred Qualifications". Skills: maybe combine some skill statements? Could include "Strong communication, documentation, problem-solving, and field-coordination skills." etc. Benefits: there is "How We Support You" with bullet list of benefits. Pay: not explicitly stated; only "Competitive pay with incentive opportunities". That's vague but mentions pay. The rule: never create Pay/Schedule sections unless posting actually states them. It says "Competitive pay with incentive opportunities". That's a statement about pay, albeit not specific numbers. Is that enough? It says "Competitive pay with incentive opportunities". That's a mention of pay. Might be considered specific enough? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive pay with incentive opportunities". So we can include Pay section with that sentence. Schedule: not mentioned. So omit Schedule. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We need to remove boilerplate: Equal Opportunity Statement, etc. Also remove "Location: Dallas, TX Department: DEPTEC" maybe? That's metadata; we can fold minor metadata into a short

  or drop it. Probably we can include a short paragraph with location and department. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a

  with location and department. We need to output only HTML fragment. Let's structure:

  Location: Dallas, TX | Department: DEPTEC

  About the role

  The Low Voltage Engineer is responsible for the design, coordination, and technical delivery of structured cabling, fiber-optic, and telecommunications infrastructure supporting modular data centers, full-scale construction projects, and mission-critical facilities. This role develops reliable and scalable connectivity solutions from early design through installation, testing, commissioning, and turnover. Working closely with design, BIM and VDC, manufacturing, construction, commissioning, operations, and client teams, the Low Voltage Engineer ensures that pathways, spaces, cabling systems, and technology interfaces are coordinated, constructible, testable, and ready for operation.

  Responsibilities

  • Design and coordinate low-voltage and telecommunications infrastructure for large-scale data centers and other mission-critical environments.
  • Develop fiber-optic backbone and horizontal cabling designs, including single-mode and multimode fiber, copper cabling, connectivity, racks, cabinets, patching, and equipment-room layouts.
  • Plan and document outside-plant and inside-plant pathways, entrances, maintenance holes, conduits, cable tray, ladder rack, sleeves, telecommunications rooms, meet-me rooms, MDFs, and IDFs.
  • Prepare and review drawings, specifications, bills of materials, riser diagrams, schedules, details, narratives, and installation requirements from concept through issued-for-construction documents.
  • Coordinate carrier demarcation, diverse pathways, campus connectivity, building entrances, and redundant telecommunications routes appropriate for mission-critical operations.
  • Ensure designs align with applicable BICSI and TIA standards, NEC requirements, client criteria, manufacturer requirements, and authority-having-jurisdiction expectations.
  • Coordinate low-voltage infrastructure with electrical, mechanical, structural, controls, security, fire alarm, BIM and VDC, network, manufacturing, and construction teams.
  • Review submittals, shop drawings, RFIs, substitutions, change orders, installation methods, and field conditions for compliance, constructability, maintainability, and schedule impact.
  • Support fiber splicing, labeling, inspection, OTDR and OLTS testing, loss-budget validation, commissioning, troubleshooting, punch-list resolution, and turnover documentation.
  • Evaluate technical and schedule risks, resolve system-integration issues, and recommend practical solutions that protect reliability, quality, and client requirements.
  • Provide technical guidance to engineers, designers, technicians, installers, and project teams.
  • Contribute to the continued development of low-voltage design standards, processes, and best practices.
  • Other duties may be assigned to support departmental and organizational objectives.

  Required Qualifications

  • Bachelor’s degree in Electrical Engineering, Telecommunications Engineering, Information and Communications Technology, or a related discipline; an equivalent combination of technical education and directly relevant experience may be considered.
  • Minimum of five years of progressive low-voltage, telecommunications, structured-cabling, or fiber-optic design experience in data centers, mission-critical facilities, industrial projects, or similarly complex environments.
  • Strong knowledge of fiber-optic and copper cabling systems, telecommunications pathways and spaces, grounding and bonding, labeling, testing, and closeout requirements.
  • Experience producing and reviewing construction documents, technical specifications, riser diagrams, pathway plans, details, bills of materials, submittals, and RFIs.
  • Working knowledge of applicable BICSI and TIA standards, NEC requirements, and industry installation and testing practices.
  • Ability to coordinate technical requirements across design, construction, vendor, commissioning, operations, and client stakeholders.
  • Strong communication, documentation, problem-solving, and field-coordination skills.
  • Willingness to travel based on project needs.

  Preferred Qualifications

  • Registered Communications Distribution Designer certification preferred but not required.
  • Direct experience supporting hyperscale, colocation, enterprise, or AI-focused data centers preferred.
  • Experience with outside-plant and inside-plant fiber, diverse carrier entrances, campus backbone systems, meet-me rooms, MDF and IDF design, and high-density network environments preferred.
  • Knowledge of fiber loss budgets, OTDR and OLTS testing, fusion splicing, polarity, MPO and MTP connectivity, acceptance testing, and turnover documentation preferred.
  • Familiarity with access control, video surveillance, distributed antenna systems, fire alarm, building controls, EPMS, BMS, or related technology-system interfaces is a plus.
  • Proficiency with Revit, AutoCAD, Bluebeam, BIM coordination tools, and Procore or comparable project platforms preferred.
  • BICSI, ETA International, FOA, manufacturer, safety, or commissioning credentials in addition to or in place of RCDD certification are a plus.

  Benefits

  • Performance-driven rewards – Competitive pay with incentive opportunities that recognize your results and contributions.
  • Comprehensive healthcare – Medical, dental, and vision coverage that supports you and your family’s total well-being.
  • Security and peace of mind – Life and disability insurance programs that provide protection when it matters most.
  • Flexible benefits options – A variety of voluntary benefits so you can personalize coverage to fit your needs.
  • Time to recharge – Generous paid time off to relax, travel, and maintain a healthy work-life balance.
  • Investing in your growth – Education assistance and tuition support to help you build skills and advance your career.
  • Planning for the future – Retirement and savings programs that help you achieve long-term financial confidence.

  Pay

  Competitive pay with incentive opportunities that recognize your results and contributions.

  We might also include a section "About Integra" maybe? Not required headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Skills not explicitly separate; we could embed skills in Required Qualifications or maybe create a Skills section from skill statements. But we already have communication etc in Required Qualifications. Could create a Skills section pulling out skill-related bullet points: Strong communication, documentation, problem-solving, field-coordination skills; Ability to coordinate technical requirements; etc. However we must not create thin sections; better to keep skills within Required Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills section. We have included About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Benefits, Pay. That's six sections. Check we didn't miss any substantive info: The "How We Support You" paragraph includes benefits list; we captured that. The "Come build with us" paragraph about Integra vision etc. That's substantive but not covered by any heading. Should we include it? It's about company culture, maybe could go under About the role? But it's not about the role; it's about company. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include that info somewhere. Could add a section "About the company" but not in allowed headings list. However we are allowed to use only those headings? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive list. But we should prefer those headings. However we could add another heading like "About Integra" if needed. But maybe we can incorporate that paragraph into About the role or Benefits? It's about company vision, culture. Could be placed under a heading "About Integra". Since not in the list, but the instruction says use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. However the company description is substantive; maybe we can incorporate it into a paragraph after Benefits but without a heading? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but to follow the pattern. Safer to include a heading "About Integra" as h3. But that might deviate from expected output. However the instruction says "Prefer a few substantive sections over many thin ones." Adding another section may be okay. Alternatively we could fold the company description into the Benefits section? Not appropriate. Could add a paragraph after Benefits without heading, but then it's not under a heading; still part of fragment. The instruction about headings is for sections; we can have prose outside sections? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose." It doesn't forbid prose outside sections. So we can add a

    after Benefits describing company vision. That would preserve info without extra heading. Thus after Benefits and Pay sections, we can add a

    with the "Come build with us" paragraph. Let's extract that paragraph: "Come build with us At Integra, we’re driven by a vision to transform the data center industry. We specialize in delivering optimized