Assistant Project Manager (South Dakota Mines Career Fair)

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us", "About This Role", "What You'll Do", "What You'll Bring", "Benefits". Also Pay and Location/Travel Requirements. According to rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We must not repeat job title as heading. The page already shows it, so we don't output a heading for the title. We need to include sections only when posting has real specific content. We have: - About Us: description of company. Could be considered "About the role"? Actually "About Us" is company overview. Could be placed under a heading like "About the company" but not in list. The allowed headings list includes "About the role". There's no "About Us" but we could treat as "About the role"? Not exactly. However we could include a

for company overview without a heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should map content to those headings where appropriate. We have: - About This Role: description of role. That maps to "About the role". So we can use

About the role

and put that prose. - What You'll Do: responsibilities. That maps to "Responsibilities". Use

Responsibilities

with

• items. - What You'll Bring: qualifications. Could split into Required Qualifications and Preferred Qualifications. Could use "Requirements" or "Qualifications". The list includes Requirements, Qualifications, Skills. We could use

  Qualifications

  and include both required and preferred as list items, maybe separate subheadings? But we cannot add extra headings beyond those? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those. We could have

  Requirements

  for required qualifications, and

  Preferred Qualifications

  maybe not allowed. Could combine into Qualifications. We also have Benefits:

  Benefits

  with list. Pay: we have pay range. So

  Pay

  with prose. Location/Travel Requirements: could be under Schedule? Not exactly. There's no heading for location/travel. Could be under Schedule? Not appropriate. Could be under "Schedule"? Not really. Could be under "Pay"? No. Could be under "Requirements"? Not really. Could be under "About the role"? Not. Could be a separate heading like "Location" but not in list. The instruction says use those headings for section headings; but does not forbid other headings? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings when appropriate, but we could also use other headings if needed? The examples are just examples. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to include sections for content we have. If we don't have a matching heading, we could still use

  Location/Travel Requirements

  but that's not in the list. Might be okay but risk. Better to incorporate location/travel into "Schedule"? Not exactly. Could treat as "Schedule" (travel percentage). But schedule usually refers to work schedule (full-time, part-time, shift). Not ideal. Maybe we can include a

  Location/Travel Requirements

  as a heading, even if not in examples, as it's a section heading. The instruction didn't forbid other headings; it just gave examples. So it's likely acceptable. We also need to remove boilerplate: EEO, E-Verify, visa sponsorship, etc. Also remove "About Us" maybe? Actually "About Us" is substantive company overview; we could keep it as a section maybe under "About the role"? But we already have "About the role" for role description. Could we include company overview under "About the role"? Might be mixing. Better to have a separate section like "About the company". Not in list but could be okay. But the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but encourages those. I'd stick to those for clarity. Thus we need to map: - About Us: maybe we can omit because it's not required? But it's substantive info about company. Could be considered part of "About the role"? Not really. However we could include it as a

  without heading? The instruction says use

  for section headings, and

  for prose. So we could have a

  with company overview without a heading. That's allowed: we can have prose outside headings. 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." It doesn't say every prose must be under a heading. So we can have a leading

    for About Us. Thus structure:

    About Us Brink Constructors, Inc....

    Then

    About the role

    with prose from "About This Role". Then

    Responsibilities

    with
    • list from "What You'll Do". Then

      Qualifications

      with maybe two sublists? Could separate required and preferred but still under same heading. Could do

      Qualifications

      then

      Required Qualifications:

      ... then

      Preferred Qualifications:

      ... That's acceptable. Then

      Pay

      with prose. Then

      Location/Travel Requirements

      with prose. Then

      Benefits

      with
      • list. We must exclude boilerplate: EEO, E-Verify, visa sponsorship, etc. Also remove "Pre-screen: Upon offer..." maybe that's part of requirements? It's about pre-employment drug screen, background, MVR check. That is a requirement; we could include under Qualifications? It's a condition. Could be included as a list item under Qualifications (maybe under Required). But it's not exactly qualification; it's a condition. Could be included under Requirements. But we have Qualifications heading; we could add a list item: "Must pass pre-employment drug screen, background check, and MVR check." Also "This job requires a DOT physical and a current DOT Medical Examiner's Certificate." That's a requirement. We need to preserve all substantive information. So include those. Also note: "Brink Constructors, Inc. does not sponsor applicants for work visas. All applicants must be legally authorized to work in the United States." That's a requirement (legal authorization). Could include. Also "Brink Constructors, Inc. participates in E-Verify..." that's boilerplate about process; maybe we can drop as it's not substantive about job? It's a condition but could be considered boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. E-Verify is similar to legal compliance; might be considered boilerplate. Safer to drop. Also remove "Equal Opportunity Employer" etc. Thus final HTML:

        About Us Brink Constructors, Inc. is an electrical contractor with over 75 years of experience in high-voltage transmission line and substation erection. With a long and industrious history, our experienced team continues to help power the nation now and into the future. At Brink, our success stems from the skilled personnel that we employ and the philosophy we instill to follow and uphold our core fundamental ideals including Safety First. Becoming a member of the Brink team is more than “just a job” or satisfactory employment—at Brink, we build careers, and we invest in the future of our people. Bring your skills to light and power your future with our team.

        About the role

        The Assistant Construction Project Manager (APM) role is designed as a developmental position for individuals looking to grow their careers in construction project management within the power delivery industry. Working closely with an experienced Project Manager and project team, the APM gains hands-on exposure to planning, coordination, documentation, and execution of transmission and substation projects. This role emphasizes learning by doing, with structured support, mentorship, and increasing responsibility over time. The APM supports project activities across the full project lifecycle while developing the skills, knowledge, and experience needed to progress into a Project Manager role. Assignments may include supporting multiple projects concurrently and collaborating with field leadership and operational support teams.

        Responsibilities

        • Support the Project Manager with project setup activities including schedules, budgets, cost codes, and project documentation
        • Assist with tracking project controls such as production data, cost reports, forecasts, and progress metrics
        • Coordinate material management activities including submittals, RFIs, purchase orders, and change documentation
        • Maintain accurate project records such as job books, daily reports, field documentation, progress photos, and closeout records
        • Coordinate and communicate with field leadership, safety, project controls, procurement, and support teams
        • Support project-specific safety planning, reporting, and compliance efforts
        • Assist with preparing project updates, reports, and documentation for internal reviews
        • Support invoice processing, project closeout documentation, and participation in lessons learned
        • Learn and apply Brink’s standards, processes, and procedures while building core project management skills
        • Perform additional duties as assigned in support of the Project Manager

        Qualifications

        Required Qualifications:

        • Bachelor’s degree in Construction Management, Engineering, Business, or a related field, or equivalent experience
        • Foundational understanding of construction project management concepts, or a strong desire to learn them
        • Proficiency with Microsoft Office and ability to learn project management and scheduling systems
        • Strong organizational skills with attention to detail and ability to manage multiple priorities
        • Clear written and verbal communication skills and willingness to collaborate with field and office teams
        • Interest in professional development and career growth toward a Project Manager role
        • Valid driver’s license and ability to travel as required by project assignments
        • Must pass pre-employment drug screen, background check, and MVR check
        • This job requires a DOT physical and a current DOT Medical Examiner's Certificate
        • All applicants must be legally authorized to work in the United States

        Preferred Qualifications:

        • Familiarity with schedules, budgets, documentation, and contract-related processes
        • Exposure to power delivery construction environments (transmission, distribution, or substation)
        • Experience submitting utility locate requests through state or regional one-call systems

        Pay

        This is