Preconstruction Project Intern

We need to output HTML fragment with sections: About us? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They say 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. The posting includes: - ABOUT US: description of company, values, onboarding, safety, etc. This could be "About the role"? Actually "About us" is about company, not role. The instructions list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About us" but we could use "About the role" maybe? However they said do NOT repeat the job title as a heading. The job title is Preconstruction Intern. So we could have a section "About the role" describing the internship summary. The "SUMMARY:" section provides description of role. That could go under "About the role". The "ABOUT US:" could be considered company overview; maybe we could include as a paragraph under "About the role" or separate? The instructions only list those headings; but they didn't forbid other headings? They said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we could include sections: About the role, Responsibilities, Requirements (or Qualifications), Skills maybe combined. The posting includes "MINIMUM REQUIREMENTS:" which includes education, skills, etc. Could split into Requirements and Qualifications? Usually Requirements are mandatory, Qualifications are preferred. The posting includes "Preferred but not required:" items. So we could have a Requirements section for mandatory items, and a Qualifications (or Skills) for preferred. But they said prefer few sections; maybe combine Requirements and Qualifications into one "Requirements" section that includes both mandatory and preferred? However they differentiate. But we can still include both as subpoints. We also have "ESSENTIAL DUTIES & RESPONSIBILITIES:" which is clearly Responsibilities. We have no explicit Pay, Schedule, Benefits mentioned. So we should NOT create those sections. Thus we will output sections: -

About the role

with content from SUMMARY and maybe ABOUT US? The ABOUT US is about company; could be included as part of About the role? Might be better to have a separate "About the company" but not in list. However instructions didn't forbid other headings; they just gave examples. But they said "Prefer a few substantive sections over many thin ones." Adding an extra section for About US may be okay if it's substantive. But we need to decide. Given the examples, they likely expect sections: About the role, Responsibilities, Requirements (or Qualifications), Skills maybe. But we can combine Skills into Requirements. Let's think: The posting includes: - ABOUT US: company description. - SUMMARY: role description. - ESSENTIAL DUTIES & RESPONSIBILITIES: list of duties. - MINIMUM REQUIREMENTS: list of mandatory and preferred. Thus we could have:

About the role

(summary)

Responsibilities

(duties)

Requirements

(minimum requirements, including preferred) We could also include a brief "About the company" paragraph inside About the role or as a separate

before sections? 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 can include a short

for metadata like company overview? Not exactly metadata. But we could include the ABOUT US as a

before the sections, not as a heading. That would preserve info without extra heading. Thus output:

ABOUT US: ...

(but we need to remove boilerplate? The ABOUT US is substantive; we keep it.) Then

About the role

with the SUMMARY paragraph. Then

Responsibilities

with

• for each duty. Then

  Requirements

  with
  • for each requirement (mandatory) and maybe separate
    for preferred? Could combine. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet exactly as in posting? We can keep the substance but maybe rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not omit any details. We can keep them as list items, maybe slightly trimmed but not lose meaning. Probably okay to keep the bullet points as they are. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement at end: "CSM Group is an Equal Opportunity Employer (EOE). ..." That's boilerplate; we should remove it. Also the "Physical Demands & Work Environment – Jobsite" is substantive? It describes physical demands; that is part of requirements? It's not in the MINIMUM REQUIREMENTS but it's a description of physical demands. Should we keep it? It's substantive info about job. The instructions: preserve ALL substantive information; do not invent or summarize away detail. So we should keep that as part of Requirements maybe. It's not a duplicate. It's not boilerplate. So we need to include that info. Thus the Requirements section should include both the MINIMUM REQUIREMENTS bullets and the Physical Demands & Work Environment description. We need to format as
    • for any list of duties/requirements/benefits. For prose, use

      . The Physical Demands description is a paragraph (multiple sentences). Could be a

      . Or we could break into list items? It's not a list; it's a description. So we'll use

      . Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML fragment. Let's extract the ABOUT US text: "ABOUT US: We are a nationally ranked, safety-focused, and talent-driven organization focused on delivering project management services through tailored delivery models. Our strength is our ability to match a delivery model to specific project needs, making the construction process feel easy. Our foundation is built on our people, culture, and values. Our teammates come first. We support each other through successes and failures and respect each other's ideas and opinions. We are a people-first company. We know there is always a way to do it better, so we seek and nurture curious minds with a desire to solve problems and move forward by being creative and curious together. We celebrate each other's successes and acknowledge hard work because we know our people are the backbone of our success. #StrongerTogether! Leading with safety is our No. 1 priority. We believe it is a fundamental human right to have a safe workplace, so we dedicate ourselves to creating safe environments for our people and everyone we do business with. In addition to a positive atmosphere, a happy, healthy, and supportive work environment is especially important. Upon joining CSM Group, we will provide you with a robust onboarding program to expose you to broad aspects of the organization by meeting with operations, business leaders, and peers to better understand how we operate." We need to keep that as a paragraph. Possibly remove the "#StrongerTogether!"? It's part of the text; it's substantive? It's a hashtag; maybe keep. Now SUMMARY: "SUMMARY: CSM Group is seeking a motivated and detail-oriented Preconstruction Intern to support our Preconstruction team. This internship provides valuable hands-on experience in estimating, budgeting, scheduling, value analysis, subcontractor coordination, and project planning. The intern will work alongside experienced estimators and project professionals to gain exposure to the full preconstruction process and contribute to meaningful project pursuits. This position is ideal for students interested in construction management, engineering, architecture, or related fields who are eager to build a foundation for a career in the construction industry." We'll put that as a paragraph under About the role. Now ESSENTIAL DUTIES & RESPONSIBILITIES: list of duties. We need to capture each bullet. Let's extract: - Estimating & Cost Analysis Assist with quantity takeoffs using plans, specifications, and digital estimating tools. Support the preparation of conceptual, schematic, design development, and detailed construction estimates. Help gather pricing information from subcontractors, suppliers, and vendors. Participate in bid analysis and cost comparison exercises. Assist in maintaining historical cost databases and estimating records. - Project Planning & Preconstruction Support Review drawings, specifications, and project documents for completeness and constructability. Support the development of project budgets and cost models. Assist with value engineering evaluations and cost-saving recommendations. Participate in project planning meetings and preconstruction team discussions. - Scheduling & Logistics Support the development and updating of preliminary project schedules. Assist with project phasing, site logistics, and sequencing reviews. Help identify potential risks and opportunities during project planning. - Proposal & Presentation Support Assist in preparing client presentations, proposals, and project pursuit materials. Compile project information, project narratives, and supporting documentation. Support the preparation of preconstruction reports and meeting materials. - Coordination & Communication Collaborate with estimators, project managers, architects, engineers, and trade partners. Participate in subcontractor outreach and bid solicitation activities. Attend project meetings and document meeting notes and action items. Assist with maintaining project files and ensuring document accuracy. - Special Projects Conduct market research on construction materials, labor trends, and industry best practices. Support process improvement initiatives within the Preconstruction department. Assist with data analysis and reporting related to project costs and performance metrics. We need to output each as

    • . Should we keep the subheadings like "Estimating & Cost Analysis" as part of the list item text? Probably yes; we can include them as part of the
    • text. Or we could make them separate headings but not needed. We'll just include them as part of the li. Now MINIMUM REQUIREMENTS: "MINIMUM REQUIREMENTS: Currently pursuing a Bachelor's degree in Construction Management, Civil Engineering, Architecture, Engineering Technology, Building Science, or a related field. Strong analytical and problem-solving skills. Ability to read and interpret construction drawings and specifications (preferred). Excellent organizational skills and attention to detail. Strong written and verbal communication skills. Proficiency in Microsoft Office Suite, including Excel, Word, and PowerPoint. Ability to work both independently and collaboratively in a team environment. Preferred but not required: Prior internship, co-op, construction experience, or related coursework. Familiarity with estimating software such as Bluebeam, On-Screen Takeoff, Sage Estimating, or similar platforms. Knowledge of scheduling tools such as Microsoft Project or Primavera P6. Interest in commercial, industrial, healthcare, education,