Project Manager Intern

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: EEO, equal opportunity, scam warning, navigation, cookie, legal, duplicated lines, application instructions. Also remove "Share Share Email Post Share" etc. Also remove "If you want to view the Know Your Rights..." etc. Also remove "View Company Information To see other positions, click here." Also remove "McConnell & Associates is proud to be a drug-free, equal opportunity employer..." (EEO). Also remove "Competitive Hourly WagePaid Holidays.Employee Stock Ownership Plan (ESOP).401K Savings Plan With a Company MatchCareer Growth: Direct pathway to full-time opportunities with MAC upon graduation." That's benefits and pay? It mentions Competitive Hourly Wage (pay) and benefits: Paid Holidays, ESOP, 401K with match, Career growth. So we can have a Benefits section and maybe Pay section? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide: Pay: "Competitive Hourly Wage" is specific enough? It's not a number but it's a statement. It's not placeholder like "commensurate with experience". It's a specific statement: Competitive Hourly Wage. So we can include Pay section with that line. Benefits: Paid Holidays, ESOP, 401K Savings Plan With a Company Match, Career Growth: Direct pathway to full-time opportunities with MAC upon graduation. Those are specific. So Benefits section. Schedule: The posting mentions "Ability to work 40–50 hours per week, including weekends as needed." That's schedule info. So we can include Schedule section. Responsibilities: The bullet list under "Key Responsibilities" includes two subheadings: Sales, Estimating & Client Relations and Project Execution & Management. We need to extract responsibilities as list items. Should we keep subheadings? Probably just list items. Could group but not required. We'll output

• each responsibility. Requirements/Qualifications/Skills: The posting has "Skills & Qualifications" with Education, Leadership & Work Ethic, Licensing & Driving Record, Communication, Availability. Those could be considered Qualifications or Skills. We need to decide which sections to output. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to avoid duplication. We can map: About the role: from "Position Overview" paragraph. Responsibilities: list of duties. Requirements: maybe education and licensing? Qualifications: maybe leadership & work ethic, communication? Skills: maybe specific skills? But we have overlapping. Better to follow typical: Requirements = education, licensing, etc. Qualifications = leadership, work ethic, communication. Skills = maybe specific skills like estimating, scheduling? But we don't have explicit skills list besides those. Could combine. However instruction: Prefer a few substantive sections over many thin ones. So we could combine into Qualifications and Skills maybe. But we need to follow headings allowed. We could output About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. That's 6 sections. Or we could output About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Let's see content: Education, Licensing & Driving Record, Availability are requirements. Leadership & Work Ethic, Communication are qualifications. There's no separate skills list beyond those. So we could have Requirements (education, licensing, availability) and Qualifications (leadership, work ethic, communication). That seems reasonable. We'll not output Skills section. Thus sections: About the role (from Position Overview), Responsibilities (list), Requirements (Education, Licensing & Driving Record, Availability), Qualifications (Leadership & Work Ethic, Communication), Benefits (Paid Holidays, ESOP, 401K Savings Plan With a Company Match, Career Growth), Pay (Competitive Hourly Wage), Schedule (Ability to work 40–50 hours per week, including weekends as needed). We must not include headings with empty content. All have content. Now format: Use

  for each heading. Then content: For About the role: a

  with the paragraph. For Responsibilities:

  • each responsibility. For Requirements: maybe
    • each. For Qualifications:
      • each. For Benefits:
        • each. For Pay:

          with statement. For Schedule:

          with statement. We must preserve all substantive information, not invent or summarize away detail. So we need to include each bullet exactly as in posting. Let's extract: About Us paragraph: "McConnell & Associates is a leading employee-owned civil and sports construction company serving clients throughout the Midwest. We build and maintain durable, high-performance infrastructure and athletic facilities while maintaining a strong commitment to safety, reliability, and quality. As a 100% employee-owned company (ESOP), our employee-owners share directly in the success they help create." That's About Us, but we need About the role? The instruction says use

          for section headings (e.g. About the role, Responsibilities...). The posting has "About Us" and "Position Overview". We should combine? The About the role likely corresponds to Position Overview: "The Project Manager Intern offers students a unique, immersive opportunity to learn the full lifecycle of construction management, sales, and operations. Working alongside experienced Project Managers and Estimators, this role bridges business development, estimating, and project execution across our St. Louis office." That's the role description. We'll use that as About the role. We'll not include About Us because it's company description, not role. But we could include it as part of About the role? The instruction says About the role heading. So we should put the Position Overview paragraph there. We'll not duplicate About Us. Now Responsibilities: Under "Key Responsibilities" there are two bold headings: Sales, Estimating & Client Relations and Project Execution & Management. Under each, sentences. Let's list each sentence as a separate

          ? The instruction: Use

          • for any list of duties/requirements/benefits. So we can treat each sentence as a list item. We'll keep the content exactly. Sentences: - Assist with building customer relationships and delivering tailored solutions for project needs. - Support bid follow-ups, contract negotiations, and sales efforts. - Participate in pre-construction site visits, project scope development, and specification writing. - Gain hands-on experience in project estimating and budgeting. - Help manage project schedules, material procurement, submittals, and comprehensive project documentation. - Assist with obtaining subcontractor proposals, issuing subcontracts, and managing material orders. - Provide regular project status updates to clients and project stakeholders. - Work with field teams to observe site layout, material staging, and safety enforcement. Now Requirements: Education: Currently pursuing a degree in Construction Management, Civil Engineering, or a related field. Licensing & Driving Record: Valid driver’s license required. Relatively clean motor vehicle report (applicants with drug or alcohol driving offenses in the last three years will not be considered; other violations evaluated per insurance standards). Availability: Ability to work 40–50 hours per week, including weekends as needed. We could split into list items. Now Qualifications: Leadership & Work Ethic: Strong work ethic with a demonstrated ability to lead people and support project management tasks. Communication: Strong verbal and written communication skills. Now Benefits: Paid Holidays. Employee Stock Ownership Plan (ESOP). 401K Savings Plan With a Company Match. Career Growth: Direct pathway to full-time opportunities with MAC upon graduation. We need to keep exactly as posted: "Paid Holidays." "Employee Stock Ownership Plan (ESOP)." "401K Savings Plan With a Company Match". "Career Growth: Direct pathway to full-time opportunities with MAC upon graduation." Now Pay: Competitive Hourly Wage. Now Schedule: Already captured in Availability but we also have Schedule section. However Availability is also a requirement. But we have both Requirements and Schedule; we might duplicate. The instruction: do not repeat content? It didn't forbid duplication but we should preserve all substantive information. If we put Availability under Requirements and also under Schedule, that's duplication. Better to put Availability under Schedule only, and not under Requirements. But Requirements also includes Education and Licensing. So we can move Availability to Schedule section. Then Requirements only have Education and Licensing & Driving Record. Let's do that. Thus: Requirements: - Currently pursuing a degree in Construction Management, Civil Engineering, or a related field. - Valid driver’s license required. - Relatively clean motor vehicle report (applicants with drug or alcohol driving offenses in the last three years will not be considered; other violations evaluated per insurance standards). Qualifications: - Strong work ethic with a demonstrated ability to lead people and support project management tasks. - Strong verbal and written communication skills. Benefits as above. Pay: Competitive Hourly Wage. Schedule: Ability to work 40–50 hours per week, including weekends as needed. Now About the role: Position Overview paragraph. Now we need to ensure we didn't include any boilerplate: Remove EEO lines, etc. Also remove "McConnell & Associates is proud to be a drug-free, equal opportunity employer..." etc. Also remove "If you want to view the Know Your Rights..." etc. Also remove "View Company Information To see other positions, click here." Also remove "Share Share Email Post Share". Also remove "Location: St. Louis, MO Employment Type: Internship (Full-Time / Seasonal)"? That's metadata; we could drop it as per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

            or drop it. So we can drop location and employment type entirely, or we could include in a short p. But we already have About the role etc. The instruction: "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." So we could include location and employment type in a short p maybe under About the role? But we already have About the role paragraph; we could add a short p after it? However that might be considered extra content not in the posting? It's actually in the posting. We could include it as a short p under About the role or as a separate section like "Job Details". But we only allowed headings list; we could add a

            after the heading for minor metadata. But we must not create new headings not in list. So we could add a

            after About the role that includes location and employment type. However the instruction says "fold minor metadata into a short

            or drop it." So we can either drop it or include as a short p. I'd include it as a short p after About the role maybe before Responsibilities. But we need to ensure we don't create a heading for it. So we can just add a

            containing "Location: St. Louis, MO. Employment Type: Internship (Full-Time / Seasonal)." That's minor metadata. Now check for any other boilerplate: "McConnell & Associates is a leading employee-owned civil and sports construction company..." That's About Us, we omitted. That's okay because it's not role-specific. The instruction says preserve ALL substantive information; but About Us is substantive but not about the role. However we might consider it part of About the role? The heading "About the role" is for role description; About Us is company description. Should we include it? The instruction says "Preserve ALL substantive information". It doesn't restrict to role-only