Distribution Engineer III

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About the role: The first paragraph(s) describing the role: "Distribution Designer Actalent Services, LLC connects passion with purpose..." etc. Should we include that as About the role? Probably yes. - Responsibilities: The list of duties: "Design and review overhead and underground distribution lines from 4 kV to 69 kV", "Develop overhead, URD, re-conductoring and asset replacement projects, and underground cable/conduit work packages", "Design complex overhead and underground distribution projects in urban and rural environments in compliance with client's engineering and construction specifications, field engineering of project requirements, identification of conflicting utilities, engineering and design calculations, and programming of protective line equipment.", "Coordinate small design teams as needed to develop budgets, prepare scoping documents, design criteria, and project deliverables.", "Provide clients with engineering assistance during construction, and be available to attend construction meetings, coordination efforts and community outreach as needed.", "Identify and initiate corrective action when project objectives are not being met", "Interpret codes and regulations and develop standards for construction projects", "Promote engineering professionalism and standards", "Develop, recommend, and implement plans by establishing goals, objectives, and requirements that include all scheduling, resources, and information for complex engineering". That's a lot; we can put as

• . - Requirements: Might be "Bachelors Degree in Electrical Engineering from an accredited institution", "Masters Degree in Electrical Engineering from an accredited institution will count towards years of experience", "Technical training, certifications, or coursework related to utility design, telecommunications, GIS, CAD, or electric utility infrastructure", "2+ years of utility, telecom, joint use, or make-ready design experience". Also maybe "Experience In One Or More Of The Following Pole Loading Analysis Telecom Attachment Design Joint use or make-ready projects supporting electric utilities or telecommunications providers JETS or DDS software experience AutoCAD, MicroStation, GIS, or utility design platforms". That could be Skills. - Qualifications: Might be overlapping with Requirements. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Usually Requirements = minimum qualifications; Qualifications = preferred? But we can split: Requirements: education, experience; Qualifications: maybe certifications, technical training; Skills: specific software, pole loading analysis, etc. However we must not create thin sections; prefer few substantive sections. Could combine Requirements and Qualifications into one? But headings are prescribed; we can include only those with content. We could have Requirements (education + experience) and Skills (technical skills). Qualifications maybe not needed if content overlaps. But we must not invent sections; we can omit Qualifications if no distinct content. Let's extract: Education: Bachelors Degree in Electrical Engineering from an accredited institution; Masters Degree in Electrical Engineering from an accredited institution will count towards years of experience. Experience: 2+ years of utility, telecom, joint use, or make-ready design experience. Technical training/certifications: Technical training, certifications, or coursework related to utility design, telecommunications, GIS, CAD, or electric utility infrastructure. Specific experience areas: Pole Loading Analysis, Telecom Attachment Design, Joint use or make-ready projects supporting electric utilities or telecommunications providers, JETS or DDS software experience, AutoCAD, MicroStation, GIS, or utility design platforms. Thus we could have: - Requirements: Education + Experience (maybe also technical training? but that's more skill). Could put education and experience under Requirements. - Skills: Technical training/certifications + specific experience areas (pole loading, telecom attachment, JETS/DDS, AutoCAD etc.) - Qualifications: maybe not needed. But we need to ensure we don't lose any substantive info. If we omit Qualifications heading, that's fine as long as we include the info elsewhere. Now Benefits and Pay: The posting includes Pay And Benefits section: pay range $35.00 - $50.00/hr. Benefits list: 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). Also note: "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:" This is a bit confusing: says temporary role but earlier says Permanent position. We'll keep the benefits list as given. Schedule: The posting includes "Workplace Type This is a fully remote position." That's not schedule but workplace type. There's no explicit schedule (e.g., full-time, part-time). There's "Job Type & Location This is a Permanent position based out of Atlanta, GA." That's job type and location. No schedule info. So we should not create a Schedule section because no specific schedule content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we can include Pay and Benefits (since they are stated). For Schedule, we omit. Also we have "Application Deadline This position is anticipated to close on Oct 9, 2026." That's metadata; we could fold into a short p or drop. 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 short paragraph for Application Deadline maybe under a generic paragraph? But we should not create a heading for it. We could include it in a

  after the About the role maybe. However we should avoid boilerplate; but this is substantive info (deadline). We can include it as a paragraph. Also "Job Type & Location This is a Permanent position based out of Atlanta, GA." That's also minor metadata; we can include as a paragraph. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include location, job type, deadline. We must not repeat the job title as a heading. The job title is "Distribution Designer". Not to be used as heading. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the long EEO statement, the accommodation request, San Francisco Fair Chance, Massachusetts Lie Detector, Use of AI, etc. Also the "About Actalent" paragraph describing the company; that's maybe boilerplate? It's about the company, not the role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Actalent" is not exactly legal boilerplate but it's company description; might be considered boilerplate? The instruction says preserve ALL substantive information; does company description count as substantive? It's not about the role; but could be considered generic. However the instruction about sections: About the role, Responsibilities, etc. The "About Actalent" is not about the role; it's about the company. Might be considered boilerplate to remove. The posting starts with "Distribution Designer Actalent Services, LLC connects passion with purpose. We are supporting critical engineering and sciences initiatives that advance how companies serve the world. With almost 40 years of experience, our scalable talent solutions and engineering and sciences services provide the expertise our customers need to achieve more. The position falls within the Distribution Department of the organization." That first paragraph is about the company and role context; maybe we keep as About the role? It includes description of the company and the role's department. That seems substantive to the role. The later "About Actalent" paragraph is more generic company description; could be considered boilerplate. We'll keep the first paragraph(s) up to "The position falls within the Distribution Department of the organization." as About the role. Then we can discard the later "About Actalent" paragraph. Now we need to output HTML fragment only, no /, no markdown fences. Structure:

  About the role

  ... (the description)

  Responsibilities

  • ... each duty

  Requirements

  • ... education
  • ... experience

  Skills

  • ... technical training/certifications
  • ... specific experience areas

  Pay

  The pay range for this position is $35.00 - $50.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.

  Benefits

  • 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)
  We might also include a paragraph for location and deadline after About the role or as separate

  without heading. The instruction: fold minor metadata into a short

  or drop it. So we can add a

  after About the role: "Job type: Permanent. Location: Atlanta, GA. Application deadline: Oct 9, 2026." Or similar. We must not include any heading for that. Now check for any duplicated lines: we need to ensure we didn't repeat. Let's extract the About the role text precisely: "Distribution Designer Actalent Services, LLC connects passion with purpose. We are supporting critical engineering and sciences initiatives that advance how companies serve the world. With almost 40 years of experience, our scalable talent solutions and engineering and sciences services provide the expertise our customers need to achieve more. The position falls within the Distribution Department of the organization." We should keep that as is. Now Responsibilities: list each duty as separate

• . Let's capture them: - Design and review overhead and underground distribution lines from 4 kV to 69 kV - Develop overhead, URD, re-conductoring and asset replacement projects, and underground cable/conduit work packages - Design complex overhead and underground distribution projects in urban and rural environments in compliance with client's engineering and construction specifications, field engineering of project requirements, identification of conflicting utilities, engineering and design calculations, and programming of protective line equipment. - Coordinate small design teams as needed to develop budgets, prepare scoping documents, design criteria, and project deliverables. - Provide clients with engineering assistance during construction, and be available to attend construction meetings, coordination efforts and community outreach as needed. - Identify and initiate corrective action when project objectives are not being met - Interpret codes and regulations and develop standards for construction projects - Promote engineering professionalism and standards - Develop, recommend, and implement plans by establishing goals, objectives, and requirements that include all scheduling, resources, and information for complex engineering Check for any trailing spaces. Now