Fargo Hiring Event - September 30, 2026

We need to output HTML fragment with sections: About Us? The instruction: 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. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. It includes: - About Us (company description) - Divcon is growing our team in Fargo, ND! We’re looking for talented professionals ready to build a career in the fast-growing mission-critical industry. Divcon builds the systems that keep data centers and critical facilities running. Our teams combine technology, craftsmanship, and expertise to deliver solutions that truly matter. We are looking for Controls Technicians, Senior/Lead Controls Technicians, Wiring Technicians and Project Managers who are driven, hands-on, and ready to take their careers to the next level. We are offering Sign-on bonuses!!! $5,000 for Controls Technician (all levels) $10,000 for Project Managers Then sections for each role: Controls Technicians, Senior/Lead Controls Technicians, Wiring Technicians, Project Managers. Each includes responsibilities and requirements. Then "Why Join Us?" with bullet list: Opportunities for Growth, Medical/Dental/Vision Insurance, 401K with Employer Match, Disability Coverage, Flexible PTO, Field-Based Employee Benefits. Then "Join Us In-Person to Meet Our Team and Explore a Career in Mission Critical Event Details" includes date, location, address, time. Then "Job Type: Full-time + Overtime Projected Total Compensation: $40,000.00 - $220,000.00 per year Work Location: Traveling and onsite in Fargo, ND The Pay Range For This Role Is 40,000 - 220,000 USD per year(Fargo)" We need to produce sections: maybe About Us, Responsibilities (maybe per role?), Requirements, Benefits, Pay, Schedule? But we must only include sections when there is real specific content. The posting includes "About Us" content. It includes responsibilities for each role (detailed). It includes requirements (experience). It includes benefits (Why Join Us). It includes Pay (range). It includes Schedule? Not explicit schedule besides "Full-time + Overtime". That could be schedule info. Also event details (date/time/location) maybe not needed as it's application instructions? It's an event to meet team; maybe we can include as a section? The instruction says remove application instructions. The event details might be considered application instructions? It's an invitation to an in-person event; not exactly application instructions but could be considered promotional. However, we might keep it as a short paragraph under maybe "Event" but not required. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include sections like About Us, Responsibilities, Requirements, Benefits, Pay, Schedule (if we have schedule content). For schedule we have "Full-time + Overtime". That's specific enough. We need to use

  for section headings. Use

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

    for prose. We need to 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 must not repeat the job title as a heading. The posting does not have a single job title; it's multiple roles. So we won't add a heading for job title. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: cookie/navigation/legal/EEO etc. None present. We need to avoid duplication. Let's extract content: About Us paragraph(s): "Headquartered in Dallas, Texas, Divcon delivers fully integrated automation solutions nationwide that optimize performance, energy efficiency, and reliability across HVAC, lighting, power monitoring, and mission-critical systems. Leveraging advanced technologies - including Allen-Bradley PLCs, Ignition SCADA, and Delta DDC systems - we combine deep technical expertise with field-tested execution to deliver precise, scalable, and high-performance solutions. Divcon is growing our team in Fargo, ND! We’re looking for talented professionals ready to build a career in the fast-growing mission-critical industry. Divcon builds the systems that keep data centers and critical facilities running. Our teams combine technology, craftsmanship, and expertise to deliver solutions that truly matter. We are looking for Controls Technicians, Senior/Lead Controls Technicians, Wiring Technicians and Project Managers who are driven, hands-on, and ready to take their careers to the next level. We are offering Sign-on bonuses!!! $5,000 for Controls Technician (all levels) $10,000 for Project Managers" We could keep that as About Us section. Then responsibilities for each role: Could combine under a single Responsibilities section with subheadings? But we only allowed

    for section headings; we could have multiple

    sections: Responsibilities, Requirements, Benefits, Pay, Schedule. However, we need to preserve all substantive information; we could list responsibilities per role under Responsibilities using

    • . Similarly requirements per role under Requirements. But we need to avoid making sections too thin; but we have enough content. Let's parse responsibilities: Controls Technicians: - Support DDC/BAS and PLC project work through installation verification, point-to-point checkout, startup, commissioning, documentation, and issue escalation. - Start up, commission, and re-commission customer systems utilizing DDC or PLC technology. - Verify field installation against drawings, point lists, network architecture, and project documentation. - Perform point-to-point checks and support L2-L5/IST commissioning activities on data center projects. Senior/Lead Controls Technicians: - Troubleshoot challenging systems, lead commissioning efforts, support your team, and help ensure projects are completed successfully from startup through turnover. - Lead and support controls startup, commissioning, testing, and troubleshooting across DDC/BAS and PLC systems. - Take ownership of field issues, identify solutions, and work through problems to ensure systems are operating as intended. - Lead and support technicians in the field by assigning work, providing guidance, and sharing your knowledge and experience. - Review project information and field conditions to help identify potential issues and ensure the team is prepared for successful commissioning. - Help ensure projects are completed with a strong focus on quality, functionality, customer satisfaction, and on-time turnover. - Support testing, system adjustments, documentation, and final project closeout. Wiring Technicians: - Build, assemble, wire, and test industrial control panels from electrical schematics and work instructions. - Assemble and wire UL508 control panels for commercial and mission-critical applications. - Perform panel layout, component mounting, wiring/termination, functional testing, and troubleshooting. - Read electrical schematics and wiring diagrams and maintain high standards for quality, safety, and workmanship. Project Managers: - Lead the successful execution of data center controls projects from installation and commissioning through handover, with responsibility for scope, schedule, budget, field coordination, and client communication. - Manage project scope, schedules, budgets, change orders, purchase orders, project expenses, billings, and financial reporting. - Oversee installation subcontractors and Controls Technicians during commissioning and assign field work. - Review engineering submittals, technical drawings, project documentation, and Bills of Materials. - Build strong client relationships, identify project risks, and coordinate cross-functional teams to keep projects moving. Now requirements: Controls Technicians: - 0–3 years of controls installer experience or 1–2 years in HVAC controls; equivalent electrical, HVAC, construction, automation, or technical training may be considered. Senior/Lead Controls Technicians: - Typically, 5+ years of hands-on controls experience in DDC/BAS, PLC, or industrial automation environments. Wiring Technicians: - 2+ years of control panel assembly or wiring experience preferred Project Managers: - 4+ years of construction project management experience with an understanding of BMS, HVAC controls, automation, commissioning, and electrical systems. Also sign-on bonus: $5,000 for Controls Technician (all levels) $10,000 for Project Managers. This could be part of Benefits or Pay? It's a bonus; could be included in Benefits or Pay. Since we have a Pay section for range, we could include bonus in Benefits or maybe in Pay as additional note. But we need to avoid duplication. We'll include sign-on bonus in Benefits section maybe. Benefits (Why Join Us?): - Opportunities for Growth: Hands-on training and career advancement in an exploding data-center industry. - Medical, Dental, and Vision Insurance: We cover 100% of individual medical premiums and help offset the cost of family coverage. - 401K with Employer Match: Eligible after 90 days, with company matching to help you invest in your future. - Disability Coverage: Both short- and long-term disability insurance provided at no cost to our employees. - Flexible PTO: Take time off when you need it, no accruing time necessary. - Field-Based Employee Benefits: For eligible field-based roles that require travel, Divcon covers all business travel expenses and provides a per diem, phone allowance, tools, and PPE at no cost. Eligible employees also receive paid training and additional reimbursable business expenses. - Sign-on bonuses: $5,000 for Controls Technician (all levels) $10,000 for Project Managers. Schedule: "Job Type: Full-time + Overtime". Also maybe "Work Location: Traveling and onsite in Fargo, ND". That's location not schedule. Could include location under About Us or separate? But we only need sections for which we have content. Could add a section "Work Location" but not in allowed headings list; but we could incorporate into About Us or maybe a separate section like "Details". However instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings but says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings; we can use those. So we should stick to those headings. So we can put location info maybe in About Us or Pay? Probably About Us includes location? Not exactly. Could add a short paragraph under About Us about location? The About Us already mentions Divcon is growing our team in Fargo, ND! So location is there. Schedule: we have Full-time + Overtime. That's schedule. Pay: we have range $40,000 - $220,000 per year. Now we need to ensure we don't create sections with filler. We'll have sections: About Us, Responsibilities, Requirements, Benefits, Pay, Schedule. We need to use

      for each