Jobs · West Virginia

Summer Internship Program

Brayman Construction Corporation · Hinton, WV · 1 mo ago
On-siteFull-time
We need to output only HTML fragment with sections for headings where content exists. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info. We need to identify sections: About the role? The posting includes description: "Are you ready to gain hands-on experience..." etc. Could be "About the role" or "About the internship program". There's a heading "About The Internship Program". Also "WHY JOIN BRAYMAN?" with bullet points. There's "Intern Qualifications". There's "About Brayman Construction". There's "SAFETY". There's "CONFIDENTIALITY". There's "APPLYING FOR BRAYMAN'S INTERNSHIP PROGRAM" includes college fair dates etc. However we must remove application instructions? The instruction says: Remove application instructions. The "APPLYING FOR BRAYMAN'S INTERNSHIP PROGRAM" includes college fair dates and applying online optional. That's application instructions. Should we remove that entire section? Likely yes, as it's application instructions. Also "Apply now using our initial 3-minute..." is application instruction. Remove. Also "Job Posted by ApplicantPro" is metadata, drop. We must keep substantive info: description of internship, why join, internship program details (divisions, tasks), qualifications, about company, safety, confidentiality. Also maybe schedule: "12-week paid summer internship from May 2027 to August 2027 (flexible dates)". That's schedule info. Should we create a Schedule section? The rule: only create Pay/Schedule/Benefits sections if posting actually states them. It does state schedule: 12-week paid summer internship from May 2027 to August 2027 (flexible dates). So we can include a Schedule section. Pay: It says paid internship but no amount. "paid Summer Internship positions" but no specific pay. The rule says do NOT create Pay section unless posting actually states them. It mentions paid but no amount; "paid" is generic. Likely we should not create Pay section because no specific pay figure. Benefits: Not mentioned. So skip Benefits. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat job title as heading. So headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content. We have content: "About The Internship Program" could map to "About the role" or maybe "About the Internship Program". Use heading "About the role"? The rule says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict; we can use those exact headings if appropriate. We have "About The Internship Program" which is similar to About the role. Could use

    About the role

    . Or we could keep "About the Internship Program" as heading? The rule says use

    for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests using those. Safer to use the given examples. So we will map: - About the role: description of internship, what you'll do, locations, etc. - Responsibilities: list of duties (Coordinating projects..., Preparing project reports..., etc.) - Requirements/Qualifications: qualifications (must be pursuing Bachelor's..., Business Management..., willingness to work..., proficient in MS Office, interest in working hard, willing to travel) - Skills: maybe not needed; we could combine with qualifications. But we have a list of skills in responsibilities; maybe we can have a Skills section for things like Microsoft Office proficiency, etc. However we already have qualifications includes MS Office. Could create Skills section for "Microsoft Office proficiency". But we might avoid duplication. The rule: prefer a few substantive sections over many thin ones. So maybe combine qualifications and skills into one Qualifications section. - Schedule: 12-week paid summer internship from May 2027 to August 2027 (flexible dates). Also mention locations: corporate office in Saxonburg, PA and field across Western PA, NW VA, WV. - Why Join Brayman? Could be a section like "About the company" or "Benefits"? Actually "WHY JOIN BRAYMAN?" is like benefits/value proposition. Could be a section "Benefits"? But we don't have explicit benefits like health etc. It's more about reasons to join. Could be a section "About the company"? But we have separate About Brayman Construction. So maybe we create a section "Why Join Brayman?" as a heading? Not in examples but could be okay. However rule says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests using those. Might be safer to map "WHY JOIN BRAYMAN?" to a Benefits section? But benefits are not listed; it's more about reasons. Could treat as "About the company"? Actually we have About Brayman Construction separate. So maybe we create a section "Why Join Brayman?" as a heading, but risk violating instruction. However instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, just gives examples. I think it's okay to use other headings as long as they are

    . But to be safe, we could use "Benefits" for the WHY JOIN BRAYMAN? content, as it's about benefits of joining. Even though not typical benefits, it's still benefits. We'll use

    Benefits

    . - About Brayman Construction: we can use

    About the company

    or maybe

    About Brayman Construction

    . The examples include About the role, not About the company. But we can still use About the company as heading? Might be okay. However we could map to "About the role"? No. Better to use a heading like "About Brayman Construction". The rule didn't forbid; it's just examples. I'll use that. - Safety: we can use

    Safety

    (not in examples but okay). Could map to Requirements? No. We'll keep Safety heading. - Confidentiality: similarly. We must not include duplicated lines. Need to extract substantive content. Let's parse the posting. First paragraph: "Are you ready to gain hands-on experience, learn from industry experts, and explore the exciting world of construction? Brayman Construction is looking to fill paid Summer Internship positions for a 12-week paid summer internship from May 2027 to August 2027 (flexible dates). This is your chance to be part of an innovative team and work on real-world projects, both in our corporate office in Saxonburg, PA (suburban Pittsburgh), and in the field across Western Pennsylvania, Northwest Virginia, and West Virginia. Whether you're passionate about fieldwork or enjoy the intricacies of corporate operations, we have opportunities for you!" That's description. Then "WHY JOIN BRAYMAN?" with bullet points: Real-World Experience: Interns will work on key construction projects in Western Pennsylvania, Northwest Virginia, and West Virginia. Corporate Insight: You'll also have the chance to work at our Saxonburg, PA corporate office, or a satellite office, while gaining exposure to the business side of construction. Mentorship & Networking: Work alongside experienced professionals who will guide you and help you develop your skills. Then "About The Internship Program Our program offers internships in various divisions including Heavy Civil, Foundations, and Estimating, and Safety. As an intern, you'll have the chance to dive into construction project management, gain on-site experience, and learn valuable skills like: Coordinating projects and activities Preparing project reports Cost computation and preparing estimates Analyzing blueprints, proposals, and labor estimates Following safety procedures and standards Performing general labor duties" Note: there is a missing comma after Estimating, and Safety. We'll keep as is. Then "APPLYING FOR BRAYMAN'S INTERNSHIP PROGRAM ..." we will remove. Then "Intern Qualifications Must be pursuing a Bachelor's Degree in either Civil Engineering, Construction Management, Mechanical Engineering, Safety or a similar field Business Management students interested in Project Management within the construction industry are encouraged to apply Willingness to work in both office and field environments Proficient in Microsoft Office Must have an interest in working hard and being challenged daily Must be willing to travel (per diem/lodging provided per company policy)" Then "For a complete job description and list of responsibilities, please visit our career page at https://www.brayman.com/careers#internships-and-co-ops" - this is application instruction, remove. Then "About Brayman Construction We are a leading heavy civil and geotechnical contractor with office headquarters in suburban Pittsburgh, Pennsylvania, along with various project field offices in the Mid-Atlantic and Northeast Regions. Incorporated in 1947 as a family-owned business, Brayman has grown, diversified and evolved its construction services from a small bridge and concrete company to a large, nationally recognized provider of complex, heavy civil and geotechnical construction projects servicing both public and private sector clients. Brayman has expertise in a wide variety of projects including large scale complex bridges, deep foundations, marine and dam construction and rehabilitation, complex and heavy steel erection and rehabilitation, and demolition services." Then "ARE YOU READY TO KICKSTART YOUR CAREER?! Apply now using our initial 3-minute, mobile-friendly application and be sure to visit us at any of the locations above! Join a company where your skills, ambition, and ideas will be valued. Brayman is the place to build your future. Apply Today and start your summer with an experience that will shape your career in construction!" - application instruction, remove. Then "SAFETY This is a Safety Sensitive Position requiring work on project sites, including federal projects. Project sites contain various safety hazards associated with heavy construction. This position may require working at heights, in confined spaces, around heavy equipment, and under constantly changing circumstances. This position may also entail project site work at night and on weekends on an as needed basis." Then "CONFIDENTIALITY Some positions with the company will have access to confidential and proprietary information. Successful candidates for those positions will be required to sign our standard confidentiality agreement as a condition of employment." Then EEO boilerplate etc - remove. Now we need to format. We'll create sections:

    About the role

    ... description ...

    Benefits

    • Real-World Experience: Interns will work on key construction projects in Western Pennsylvania, Northwest Virginia, and West Virginia.
    • Corporate Insight: You'll also have the chance to work at our Saxonburg, PA corporate office, or a satellite office, while gaining exposure to the business side of construction.
    • Mentorship & Networking: Work alongside experienced professionals who will guide you and help you develop your skills.

    Responsibilities

    • Coordinating projects and activities
    • Preparing project reports
    • Cost computation and preparing estimates
    • Analyzing blueprints, proposals, and labor estimates
    • Following safety procedures and standards
    • Performing general labor duties

    Qualifications

    • Must be pursuing a Bachelor's Degree in Civil Engineering, Construction Management, Mechanical Engineering, Safety, or a similar

Similar jobs

Summer Internship Program

Brayman Construction CorporationWytheville, VA· 1 mo ago
Education$18–$21/hrapply on applicantpro.com