Construction Internship
The Beck Group · Austin, CO · 1 mo ago
ManagementFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Who We Are: description of company. Could be "About the role"? Actually "Who We Are" is about company, not role. But we can treat as "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" heading and put description of role (maybe from "What you bring to the table" and "As an Intern...").
We need to preserve all substantive info, not invent.
We need to remove boilerplate: EEO, legal, etc. Also remove duplicated lines.
We need to not repeat job title as heading (the page already shows it). No Job ID.
We need to include sections only when posting has real specific content.
Let's extract:
- About the role: description of internship: entry-level internship in Project Management, Superintendent, Preconstruction; responsibilities: helping project team with administration, field engineering, field supervision, documentation; procurement of materials, identifying subcontract scope gaps, quality management, punch list maintenance; paid, expectation 40 hrs/week; also list of responsibilities (interpret drawings, assist submittal logs, etc). So we can put that under About the role or Responsibilities? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" heading and put description of role (maybe from "What you bring to the table" and "As an Intern...").
We need to preserve all substantive info, not invent.
We need to remove boilerplate: EEO, legal, etc. Also remove duplicated lines.
We need to not repeat job title as heading (the page already shows it). No Job ID.
We need to include sections only when posting has real specific content.
Let's extract:
- About the role: description of internship: entry-level internship in Project Management, Superintendent, Preconstruction; responsibilities: helping project team with administration, field engineering, field supervision, documentation; procurement of materials, identifying subcontract scope gaps, quality management, punch list maintenance; paid, expectation 40 hrs/week; also list of responsibilities (interpret drawings, assist submittal logs, etc). So we can put that under About the role or Responsibilities? The instruction: Use - for any list of duties/requirements/benefits. So we can have a Responsibilities section with list.
Thus:
About the role
... description ...
Then Responsibilities
- ... each duty ...
Then Requirements: "Who we think will be a great fit" includes willingness to learn, authenticity, integrity, time management, passion, interest in integrated project delivery, innovation, process improvement, technology. Also "You Also Meet The Following Requirements": College student pursuing a Construction or other relevant degree preferred; High school student with Construction interest may be considered; Past internships within architectural, engineering, or commercial construction company preferred but not required; Fundamental understanding of project documents; Experience using Excel, Bluebeam, and Revit or comparable construction technologies is a plus.
We can put those under Requirements (maybe also Qualifications). The instruction includes both Requirements and Qualifications headings. We need to decide which to use. Could combine? But we should not create thin sections. Perhaps we can have Requirements covering the "Who we think will be a great fit" (soft skills) and Qualifications covering education/experience/technical skills. Or we could just have Requirements and skip Qualifications if content thin. But we have enough for both.
Let's extract:
Requirements (soft skills): willingness to learn and be mentored, ability to proactively identify and solve problems, uncompromising authenticity and integrity, effective time management skills, passion to get things done, interest in integrated project delivery method, interest in being innovative in process improvement and technology.
Qualifications (education/experience): College student pursuing a Construction or other relevant degree preferred; High school student with Construction interest may be considered; Past internships within architectural, engineering, or commercial construction company preferred but not required; Fundamental understanding of project documents; Experience using Excel, Bluebeam, and Revit or comparable construction technologies is a plus.
Skills: maybe list of specific skills: Interpret, coordinate, maintain, and gain understanding of construction drawings, specifications, and other project documents; Assist in developing and maintaining Submittal Logs, Specification Logs, RFI logs and responses, meeting minutes, and as-built drawings; Learn to effectively review and expedite shop drawings and submittals; Assist in updating the project schedule; Utilize Project Management software; Coordinate with subcontractors and vendors; Assist in acquiring project closeout documentation; Enforce OSHA and Beck safety standards and policies, including conducting site-specific safety orientations to subcontractor workforce and regular safety inspections; Follow direction, collaborate with all team members, and complete assigned tasks. Also physical requirements: Frequently operates a computer and other office productivity equipment; Frequently ascends/descends ladders and stairs to multiple levels; Access all levels of the building as it ascends, which typically includes many elevations; Constantly works in outdoor weather conditions; Frequently moves equipment up to 50 lbs to various locations on site; Must have ability to constantly move around job site and walk on uneven surfaces such as rebar; Constantly communicates with subcontractors, vendors, and other members of project team; Must adhere to consistent and timely attendance.
These could be under Skills or Responsibilities. But we already have Responsibilities list of duties. The physical requirements could be under Skills? Might be better to put them under Skills (technical and physical abilities). However the instruction says use - for any list of duties/requirements/benefits. So we can have multiple lists.
We need to avoid duplication: The responsibilities list we already have includes many of those items. The physical requirements are not duties but essential functions. Could be under Requirements? Might be better to have a section "Essential Functions" but not in allowed headings. Could fold into Skills or Responsibilities. Since we have to use only those headings, we can put physical requirements under Skills (as they are skills/abilities). Or we could put them under Requirements (as they are requirements). Let's decide: We'll have:
- About the role (overview)
- Responsibilities (list of duties)
- Requirements (soft skills + education/experience)
- Skills (technical/physical abilities)
- Benefits (list from Beck’s Benefits)
- Pay (we have: "Our internship positions are paid, with the expectation of working 40 hours/week." That's pay info? It says paid but no amount. We cannot create Pay section if not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says paid but no amount; is that enough? It states they are paid, but not a specific number. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Paid" is not a specific amount; could be considered placeholder? It's not a number but it's a statement that it's paid. Might be okay to include Pay section with statement that it's paid (maybe with hourly rate not given). But risk of being considered placeholder. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state they are paid, so we can include Pay section with that statement. However also we have Schedule: "expectation of working 40 hours/week." That's a schedule. So we can include Schedule section with that.
Thus we will have Pay and Schedule sections.
Benefits: we have a list under "Beck’s Benefits". We'll include Benefits section.
Now we need to ensure we don't include boilerplate like EEO, etc.
Now produce HTML fragment:
About the role
...
Responsibilities
- Interpret, coordinate, maintain, and gain an understanding of construction drawings, specifications, and other project documents
- Assist in developing and maintaining Submittal Logs, Specification Logs, RFI logs and responses, meeting minutes, and as-built drawings
- Learn to effectively review and expedite shop drawings and submittals
- Assist in updating the project schedule
- Utilize Project Management software
- Coordinate with subcontractors and vendors
- Assist in acquiring project closeout documentation
- Enforce OSHA and Beck safety standards and policies, including conducting site-specific safety orientations to subcontractor workforce and regular safety inspections
- Follow direction, collaborate with all team members, and complete assigned tasks
Requirements
- Willingness to learn and be mentored under talented Project Management and Field Supervision staff
- Ability to proactively identify and solve problems
- Uncompromising authenticity and integrity
- Effective time management skills
- Passion to get things done
- Interest in the integrated project delivery method
- Interest in being innovative in process improvement and technology
- College student pursuing a Construction or other relevant degree preferred
- High school student with Construction interest may be considered
- Past internships within architectural, engineering, or commercial construction company preferred but not required
- Fundamental understanding of project documents
- Experience using Excel, Bluebeam, and Revit or comparable construction technologies is a plus
Skills
- Frequently operates a computer and other office productivity equipment
- Frequently ascends/descends ladders and stairs to multiple levels
- Access all levels of the building as it ascends, which typically includes many elevations
- Constantly works in outdoor weather conditions
- Frequently moves equipment up to 50 lbs to various locations on site
- Must have ability to constantly move around job site and walk on uneven surfaces such as rebar
- Constantly communicates with subcontractors, vendors, and other members of project team
- Must adhere to consistent and timely attendance
Benefits
- Robust coverage for medical, dental, vision, life & disability benefits
- 401k match and free SmartDollar program for financial wellness
- Free dedicated financial coach
- Personal health & fitness program for tracking activities & earning rewards
- Paid family leave
- Health discounts on medical premiums
- Free comprehensive health screenings
- Free health coach program for weight-loss & hypertension management
- Financial & behavioral support for family forming journeys (e.g., Fertility, adoption, pregnancy, and parenthood)
- Free Life Coach
- Pet insurance discount
- Organized projects and events to support our communities
Pay
Internship positions are paid.
Schedule
Expectation of working 40 hours per week.
Check for any duplicated lines: we have "Fundamental understanding of project documents" appears both in Requirements and maybe elsewhere; it's okay.
We must not include any markdown fences. Just raw HTML.
Check for any boilerplate: we removed EEO, legal, etc.
Check for any placeholder text: Pay section says "Internship positions are paid." That's not placeholder like "commensurate with experience". It's a statement. Acceptable.
Schedule section: "Expectation of working 40 hours per week." That's specific.
Now ensure we didn't miss any substantive info: The "Who We Are" description about company: we didn't include that. Should we include as About the role? The About the role section we used for overview of internship. The company description could be considered "About the role"? Might be better to include a short paragraph about company under About the role? But the instruction says use headings like About the role, Responsibilities, etc. The "Who We Are" is about the company, not the role. However we could incorporate it into About the role as context. 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." It didn't forbid including company
About the role
... description ...
ThenResponsibilities
- ... each duty ...
- for any list of duties/requirements/benefits. So we can have multiple lists.
We need to avoid duplication: The responsibilities list we already have includes many of those items. The physical requirements are not duties but essential functions. Could be under Requirements? Might be better to have a section "Essential Functions" but not in allowed headings. Could fold into Skills or Responsibilities. Since we have to use only those headings, we can put physical requirements under Skills (as they are skills/abilities). Or we could put them under Requirements (as they are requirements). Let's decide: We'll have:
- About the role (overview)
- Responsibilities (list of duties)
- Requirements (soft skills + education/experience)
- Skills (technical/physical abilities)
- Benefits (list from Beck’s Benefits)
- Pay (we have: "Our internship positions are paid, with the expectation of working 40 hours/week." That's pay info? It says paid but no amount. We cannot create Pay section if not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says paid but no amount; is that enough? It states they are paid, but not a specific number. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Paid" is not a specific amount; could be considered placeholder? It's not a number but it's a statement that it's paid. Might be okay to include Pay section with statement that it's paid (maybe with hourly rate not given). But risk of being considered placeholder. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state they are paid, so we can include Pay section with that statement. However also we have Schedule: "expectation of working 40 hours/week." That's a schedule. So we can include Schedule section with that.
Thus we will have Pay and Schedule sections.
Benefits: we have a list under "Beck’s Benefits". We'll include Benefits section.
Now we need to ensure we don't include boilerplate like EEO, etc.
Now produce HTML fragment:
About the role
...
Responsibilities
- Interpret, coordinate, maintain, and gain an understanding of construction drawings, specifications, and other project documents
- Assist in developing and maintaining Submittal Logs, Specification Logs, RFI logs and responses, meeting minutes, and as-built drawings
- Learn to effectively review and expedite shop drawings and submittals
- Assist in updating the project schedule
- Utilize Project Management software
- Coordinate with subcontractors and vendors
- Assist in acquiring project closeout documentation
- Enforce OSHA and Beck safety standards and policies, including conducting site-specific safety orientations to subcontractor workforce and regular safety inspections
- Follow direction, collaborate with all team members, and complete assigned tasks
Requirements
- Willingness to learn and be mentored under talented Project Management and Field Supervision staff
- Ability to proactively identify and solve problems
- Uncompromising authenticity and integrity
- Effective time management skills
- Passion to get things done
- Interest in the integrated project delivery method
- Interest in being innovative in process improvement and technology
- College student pursuing a Construction or other relevant degree preferred
- High school student with Construction interest may be considered
- Past internships within architectural, engineering, or commercial construction company preferred but not required
- Fundamental understanding of project documents
- Experience using Excel, Bluebeam, and Revit or comparable construction technologies is a plus
Skills
- Frequently operates a computer and other office productivity equipment
- Frequently ascends/descends ladders and stairs to multiple levels
- Access all levels of the building as it ascends, which typically includes many elevations
- Constantly works in outdoor weather conditions
- Frequently moves equipment up to 50 lbs to various locations on site
- Must have ability to constantly move around job site and walk on uneven surfaces such as rebar
- Constantly communicates with subcontractors, vendors, and other members of project team
- Must adhere to consistent and timely attendance
Benefits
- Robust coverage for medical, dental, vision, life & disability benefits
- 401k match and free SmartDollar program for financial wellness
- Free dedicated financial coach
- Personal health & fitness program for tracking activities & earning rewards
- Paid family leave
- Health discounts on medical premiums
- Free comprehensive health screenings
- Free health coach program for weight-loss & hypertension management
- Financial & behavioral support for family forming journeys (e.g., Fertility, adoption, pregnancy, and parenthood)
- Free Life Coach
- Pet insurance discount
- Organized projects and events to support our communities
Pay
Internship positions are paid.
Schedule
Expectation of working 40 hours per week.
Check for any duplicated lines: we have "Fundamental understanding of project documents" appears both in Requirements and maybe elsewhere; it's okay. We must not include any markdown fences. Just raw HTML. Check for any boilerplate: we removed EEO, legal, etc. Check for any placeholder text: Pay section says "Internship positions are paid." That's not placeholder like "commensurate with experience". It's a statement. Acceptable. Schedule section: "Expectation of working 40 hours per week." That's specific. Now ensure we didn't miss any substantive info: The "Who We Are" description about company: we didn't include that. Should we include as About the role? The About the role section we used for overview of internship. The company description could be considered "About the role"? Might be better to include a short paragraph about company under About the role? But the instruction says use headings like About the role, Responsibilities, etc. The "Who We Are" is about the company, not the role. However we could incorporate it into About the role as context. 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 shortor drop it." It didn't forbid including company