Fall Co-Op - Kansas City

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. We need to parse the posting. Given the posting: Division: Kansas City Project Location(s): Kansas City, MO 64105 USA Minimum Years Experience: Travel Involved: Job Type: Seasonal Job Classification: Intern Education: Degree in Progress Job Family: Construction Compensation: Intern Non-Exempt Position Description: Assist in day-to-day supervised activities related to the development of a construction project to build foundational knowledge in construction management, business and project financial management, project safety protocols, subcontractor relationships, quality control, and project coordination and lifecycle. Essential Duties & Key Responsibilities: (list) Qualifications: (list) Physical Demands: (list) Work Environment: (list) We need to map to sections. "About the role": could be the Position Description paragraph. "Responsibilities": Essential Duties & Key Responsibilities. "Requirements": maybe Minimum Years Experience? But they have Minimum Years Experience field blank? Actually "Minimum Years Experience:" appears but no value. Travel Involved: maybe blank. Job Type: Seasonal. Job Classification: Intern. Education: Degree in Progress. Job Family: Construction. Compensation: Intern Non-Exempt. Could treat these as metadata but we shouldn't put Job ID etc. We can include a short

for metadata like location, job type, classification, etc. But 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 with location, job type, classification, etc. Not as a heading. "Qualifications": we have Qualifications section. "Skills": maybe from Qualifications list includes interpersonal skills, communication, etc. Could treat as Skills section. "Benefits": none given. "Pay": none given. "Schedule": maybe Job Type: Seasonal indicates schedule? Could include schedule if stated. It says Job Type: Seasonal. That's schedule info. So we could include a Schedule section with "Seasonal". But we must not create sections unless posting has real specific content. It does have Job Type: Seasonal, which is schedule. So we can include Schedule. "Pay": Compensation: Intern Non-Exempt. That is not a pay amount. It's classification. Not pay. So we should not create Pay section because no specific pay. "Benefits": none. Thus sections: About the role (position description), Responsibilities (essential duties), Qualifications, Skills (maybe derived from qualifications), Schedule (job type). Could also include Requirements? There's Minimum Years Experience blank, Travel Involved blank, Education: Degree in Progress, etc. Could treat as Requirements section? But we have Qualifications already covering education etc. Might be redundant. Better to follow instruction: Prefer a few substantive sections over many thin ones. So we can combine education etc into Qualifications. So we may not need separate Requirements. Thus produce:

About the role

Assist in day-to-day supervised activities related to the development of a construction project to build foundational knowledge in construction management, business and project financial management, project safety protocols, subcontractor relationships, quality control, and project coordination and lifecycle.

Responsibilities

• Depending on business need and location, the Intern/Co-Op will be supervised and assigned to work at an active construction project site in one of our many specialties, in a department located at a main office working in Preconstruction/Estimating, or Business Development, or in a division such as Special Projects (SPD) or Self Perform Operations (SPO).
• Support project team with meeting coordination, material tracking, file management, document control, and progress reporting.
• Provide progress reports to supervisor and be receptive to learning about construction management.
• Relate and apply knowledge acquired in the academic setting to company/project setting.
• Maintain professional relationships with employees, customers, clients, and subcontractors.
• Participate in training, meetings, and orientation.
• Other activities, duties, and responsibilities as assigned.
• Based on the assignment, the following activities may be performed:
• Assist with project start-up activities and provide support to Project Engineer, Project Superintendent, and/or Project Manager.
• Assist with collection and review of information and approvals for processing shop drawings, submittals, and Requests for Information (RFIs).
• Assist with preparation and distribution of information for contract requirements to appropriate parties.
• Assist with preparation of estimates for changes in work from subcontractors.
• Attend project site visits to observe and document construction field activities.
• Assist with preparation of and conduct correspondence and communication as directed to Architects, Engineers, vendors, and subcontractors in connection with performing their assigned trades.
• Assist with communication to Trades and subcontractors to understand and track job schedules.
• Assist with monitoring contractor compliance with Turner’s safety program, as directed.
• Assist with preparation of quantity take-offs and studies for project items using either traditional or computer-aided programs, learning and discussing details necessary to complete project.
• Request and distribute subcontractor proposals relative to their scope of work to assemble proposals for delivery system.
• Assist with project close out preparations.

But note we have nested lists; we need proper HTML. The "Based on the assignment..." could be a list item with sublist. We'll keep as

with inner

. Now Qualifications:

Qualifications

• Enrolled and actively pursuing college or university accredited degree program; recommended majors include and not limited to Engineering, Architecture, Construction Management, or other related field of study, and at minimum 1 year of completed education, and/or equivalent combination of education, training, and experience
• Desire to work in construction management and to learn about construction industry
• Flexible to work standard business hours and overtime as determined by assignment
• Demonstrate interpersonal skills including student leadership, volunteerism, or other community involvement
• Professional and clear verbal and written communication skills
• Assume personal and professional accountability for own actions and activities
• Proactive, curious, and eager to learn and participate
• Able to work independently, with direction and supervision, and in team environment
• Exceptional organizational skills with attention to detail
• Able to take direction, learn and process information quickly, follow tasks through to completion
• Basic computer and data entry skills and familiar with Microsoft Office suite of applications
• Some travel may be required, access to reliable transportation required
Skills: Could extract from qualifications: interpersonal skills, communication, organizational, etc. But we might combine into Qualifications and not create Skills to avoid thin section. However we have a Skills heading possible if we have specific skills list. The qualifications already include skills. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe we omit Skills. Schedule: Job Type: Seasonal. So:

Schedule

Seasonal

We also need to include location etc as short paragraph maybe before sections. Could include a short

with location and job classification. Eg:

Location: Kansas City, MO 64105 USA • Job Type: Seasonal • Job Classification: Intern • Division: Kansas City Project • Job Family: Construction

But we must not repeat job title as heading. That's fine. We must not include boilerplate like EEO etc. We removed. Now ensure we only output HTML fragment, no markdown fences. Let's craft final HTML. Check for any duplicated lines: we have "Based on the assignment, the following activities may be performed:" as a list item; we included sublist. Good. Check for any placeholders like "commensurate with experience": none. Check for any missing info: Physical Demands and Work Environment sections were omitted because we didn't create a section for them. But we must preserve ALL substantive information; we cannot drop them. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include Physical Demands and Work Environment somewhere. They are substantive. We could include them under a section like "Working Conditions" but we only have allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put Physical Demands and Work Environment under Requirements or Qualifications? They are not exactly qualifications but could be considered Requirements (physical demands). The instruction says we can use those headings only if posting has real specific content for it. We have content for Physical Demands and Work Environment. So we could create a section for them, but not in the allowed list? The allowed list includes those specific headings; we can use any of them. We could use "Requirements" to include physical demands and work environment. Or we could create a new heading not in list? The instruction says: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; not that we cannot use others, but likely we should stick to those. So we can put Physical Demands and Work Environment under Requirements. That seems appropriate. Thus we need a Requirements section with content: Minimum Years Experience (blank?), Travel Involved (blank?), Education: Degree in Progress, etc plus Physical Demands and Work Environment. But Minimum Years Experience and Travel Involved have no values; we should not include placeholder text like blank. We should omit those lines if they have no value. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not include lines that are empty or just labels without values. So we can skip Minimum Years Experience and Travel Involved if they have no value. Thus Requirements section will include: Education: Degree in Progress, Job Type: Seasonal maybe? Actually Job Type is schedule. But we already have Schedule section. Could keep schedule separate. We could put Education under Requirements, and Physical Demands and Work Environment also under Requirements. But we also have Qualifications separate. Might be overlapping. However we can keep Qualifications for personal/skill requirements, and Requirements for logistical/educational/physical. Let's decide: - About the role: position description. - Responsibilities: essential duties. - Requirements: Education, Physical Demands, Work Environment. - Qualifications: enrollment, desire, flexibility, interpersonal skills, communication, accountability, proactive, teamwork, organizational, ability to learn, computer skills, travel requirement. - Schedule: Seasonal. We must not repeat info. Ensure we don't duplicate education etc. Education appears in Qualifications as "Enrolled and actively pursuing college or university accredited degree program; recommended majors include and not limited to Engineering, Architecture, Construction Management, or other related field of study, and at minimum 1 year of completed education, and/or equivalent combination of education, training, and experience". That's education requirement. So we could put education under Qualifications, not Requirements. Then Requirements could be just Physical Demands and Work Environment. But we need a heading only if we have real specific content. We have Physical Demands and Work Environment, so we could make a section called "Requirements" for those. Or we could make a section "Working Conditions" but not in list. Better to use Requirements. Thus Requirements will contain Physical Demands and Work Environment