Intern - PM/Estimator - Bismark, ND

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the job description. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO etc. Also remove duplicated lines, navigation, legal, etc. Keep substantive info. We need to decide which sections to include. Let's extract content: Job Description paragraph: "The Civil Construction Internship provides students interested in pursuing a Project Manager/Estimator career track the opportunity to learn the role. Consideration for full-time employment is contingent on completion of the program, quality of work produced, the amount of interest displayed by the intern, and business need. The mentoring Project Manager/Estimator will provide direction, support, and encouragement for the Civil Construction Intern to develop an understanding of the responsibilities of the role. Civil Construction Internships are available within the following service groups: Earthwork, Utilities, Demolition, and Foundations." Then "A Day in the Life" bullet list of duties: many sentences. Then "What You’ll Need" list of requirements. Then "What Will Set You Apart" list. Then "Other" includes "Requires 8 to 10-hour hour workdays, Monday – Friday." That's schedule info. Then "Physical Demands" etc. Might be considered part of Requirements? Could be separate but we only have headings list; we could put under Requirements or Qualifications. Probably Requirements includes education, experience, etc. Physical Demands maybe part of Requirements but we could include under Requirements as a bullet. Work Environment also could be under Requirements or Qualifications. "Additional Job Description Who Are We?" is company description; could be About the role? Actually About the role could be the initial paragraph describing role. Could also include company description under About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About the role: maybe the introductory paragraph describing the internship and service groups. - Responsibilities: the "A Day in the Life" list. - Requirements: the "What You’ll Need" list (education, experience, etc.) plus maybe Physical Demands and Work Environment? But those could be under Requirements or Qualifications. Since we have both Requirements and Qualifications headings, we need to decide distribution. Usually Requirements are mandatory; Qualifications are preferred. In posting: "What You’ll Need" seems mandatory. "What Will Set You Apart" seems preferred qualifications/skills. So we can map: Requirements: What You’ll Need (education, experience, Office Suite, communication, etc.) Qualifications: What Will Set You Apart (prior experience with takeoff software, ability to read plans, etc.) Skills: maybe we could combine some but we have separate Skills heading; we could put software skills etc. But we already have Qualifications for preferred skills. Could also put Skills for abilities like communication, etc. However we already used Requirements for mandatory abilities. Might be better to follow typical pattern: Requirements = mandatory; Qualifications = preferred; Skills = specific technical skills. But we have limited headings; we can decide to put technical skills under Skills, and other abilities under Requirements. Let's parse: What You’ll Need: - Minimum of 1-year education working toward completion of bachelor’s degree (B.A. or B.S.) in Construction Management, Construction Engineering, Civil Engineering, or similar discipline. - At least 1 summer of construction work experience is strongly preferred. (Note: "strongly preferred" maybe not mandatory but it's in What You’ll Need) - Experience with Microsoft Office Suite. - Ability to communicate effectively with peers and supervisor. - Ability to read, comprehend and act on simple instructions. - Ability to respond to shifting priorities in a fast-paced environment with a can-do attitude. What Will Set You Apart: - Prior experience using Familiarity with construction takeoff, bidding, and/or estimating software is preferred. - Ability to read, analyze, and interpret project plans and specifications. Other: - Requires 8 to 10-hour hour workdays, Monday – Friday. (Schedule) - Physical Demands description. - Work Environment description. Benefits: none mentioned. Pay: none. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Schedule. We might not need Skills if we put technical skills under Qualifications. But we have a Skills heading; we could put software familiarity etc there. However Qualifications already covers that. To avoid thin sections, we could omit Skills if no distinct content. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills if we can fit its content elsewhere. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. Check if we have content for each: About the role: introductory paragraph + service groups. Responsibilities: A Day in the Life list. Requirements: What You’ll Need list (including education, experience, Office Suite, communication, reading instructions, shifting priorities). Possibly also include Physical Demands? But we could keep them under Requirements as they are mandatory aspects. However Physical Demands and Work Environment are more about job conditions; could be under Requirements as well. But we might also put them under Qualifications? They are not qualifications but job demands. I'd include them under Requirements as additional bullets. Qualifications: What Will Set You Apart list. Schedule: the 8-10 hour workdays Monday-Friday. We should not include Benefits, Pay as no info. Now we need to format as HTML: use

for each heading, then content: either

for prose,

• for lists. We must preserve all substantive information, not invent or summarize away detail. So we need to keep exact phrasing? We should preserve the meaning but not necessarily exact wording? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the details, but we can rephrase slightly as long as we keep all info. Safer to copy sentences. We need to remove boilerplate: EEO etc. Also remove duplicated lines, navigation, legal, etc. Also remove "Additional Job Description Who Are We?" maybe we can incorporate company description into About the role? The "Who Are We?" paragraph is about Veit company. That is substantive info about employer; could be included under About the role as additional paragraph. It's not boilerplate; it's company overview. So we should include it. Thus About the role will have two paragraphs: the internship description and service groups, plus the company overview. Let's extract company overview: "Who Are We? Veit is one of the country’s leading specialty contractors, with nearly a century of experience and the best people in the industry. We specialize in foundations, earthwork, utilities, marine services, industrial cleaning, cured‑in‑place pipelining, and waste disposal. We pride ourselves on our relentless pursuit to push the construction industry forward and deliver for our customers. Our modern fleet of iron, diverse expertise, and unmatched determination allow us to successfully tackle some of the largest and most complex projects across every sector while also living out our values every day. Our company culture is one where everyone pitches in to get the job done, regardless of job title or seniority. We do everything we can to maintain an atmosphere where family comes first. We want every one of our employees to look forward to each day at work and make it home safe and happy at the end of the day. Never settle, dig deeper Our Core Values Deliberately Safe We believe all safety incidents are avoidable when everyone operates with a deliberate mindset. We are deliberately proactive and thorough in training and job planning. We are deliberately safe in our everyday operations and decision-making.Build with Intention We build with intention. Whether in the office or the field, we work with grit and determination toward a better future for everyone involved. We leave things better than we found them, and never leave a job until we’re proud to put the Veit name on it.Leaders Dig First Egos have no place at Veit. We expect everyone on our team to dig in with a leadership mentality. That means being willing to jump in, take ownership, and get mud on our boots — especially when times get challenging.Real Relationships Like our work, we approach relationships authentically, with a long-term mindset. Whether you’re a client partner, vendor, or team member, we make an effort to build a more meaningful connection with you by communicating with respect and honesty.Integrity in Everything As part of the Veit family, everything we do and say reflects on this entire company. We act with integrity, which means treating others just as we want to be treated, doing the right thing, and holding ourselves accountable." That is a lot. We need to keep all substantive information. It's okay to include as prose paragraphs. We must not include the EEO line at end: "VEIT IS AN EQUAL OPPORTUNITY AFFIRMATIVE ACTION EMPLOYER, INCLUDING VET/DISABILITY". That's boilerplate; remove. Now we need to format lists. Responsibilities list: The "A Day in the Life" sentences each start with a verb. We'll make each as
• . Let's extract them: - Reviews plans and specifications to determine the scope of the work required for the project. - Reviews jobsites before bidding to make appropriate estimates. - Completes accurate takeoffs utilizing software. - Also performs hand takeoff quantities for various aspects of each project. - Calculates quantities (square yard, linear feet, cubic yard, each, etc) for each project to factor materials needed and material movement. - Solicits quotes from subcontractors for bid preparation and final numbers. - Keeps DBE/MBE requirements in mind with subcontractor invitations to bid. - Constructs bids by adding activities (work to be completed), crews and equipment, adjusting production rates. - Prints out bid proposals and create proposal. - Reviews bid with estimator or project manager. - Observes the change order process. - Attends project meetings. Note: "Prints out bid proposals and create proposal." maybe grammar but keep. Now Requirements list: from "What You’ll Need": - Minimum of 1-year education working toward completion of bachelor’s degree (B.A. or B.S.) in Construction Management, Construction Engineering, Civil Engineering, or similar discipline. - At least 1 summer of construction work experience is strongly preferred. - Experience with Microsoft Office Suite. - Ability to communicate effectively with peers and supervisor. - Ability to read, comprehend and act on simple instructions. - Ability to respond to shifting priorities in a fast-paced environment with a can-do attitude. Add Physical Demands and Work Environment as bullets under Requirements? Could be separate but we have no heading for them; we could include under Requirements as additional bullets. Physical Demands bullet points: The description is a paragraph; we could break into multiple bullets but maybe keep as a single

  under Requirements after the list. However instruction: Use

  • for any list of duties/requirements/benefits. Physical Demands is not a list but a description; we can use

    . Similarly Work Environment. Thus Requirements section will have a

    for the mandatory requirements, then

    for Physical Demands, then

    for Work Environment. Qualifications section: from "What Will Set You Apart": - Prior experience using Familiarity with construction takeoff, bidding, and/or estimating software is preferred. - Ability to read, analyze, and interpret project plans and specifications. Note the first bullet wording is awkward: "Prior experience using Familiarity with construction takeoff, bidding, and/or estimating software is preferred." Probably means "Prior experience using construction takeoff, bidding, and/or estimating software is preferred." We'll keep as is but maybe fix grammar? We should not invent or summarize away detail; but we can correct obvious typo? The instruction says do not invent or summarize away detail. Changing wording could be considered altering detail. Safer to keep exactly as written: "Prior experience using Familiarity with construction takeoff, bidding, and/or estimating software is preferred." That's weird