2027 Summer Internship - Construction Management (Northern California)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. From posting: It's an internship. We have: - About The Program (maybe "About the role" heading). We'll use

About the Program

with prose. - What You'll Gain (maybe "Responsibilities" or "What You'll Gain"? Could be "What You'll Gain" but we need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate. We have sections: About The Program, What You'll Gain, What We Look For (Qualifications/Requirements), What You Bring To Us (maybe Requirements/Qualifications), What You'll Need To Be Successful (Skills), Working Conditions (maybe not a standard heading; could be omitted or put under Responsibilities? But we should only include sections with real content and allowed headings. Working Conditions not in list; maybe we can omit or incorporate into Responsibilities? But we must preserve all substantive information; we cannot drop details. However we can embed details under appropriate headings like Responsibilities or Requirements. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but we should use those headings when appropriate. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create sections for any of those headings if we have content. If we have content that doesn't fit those headings, we could still use a heading like "About the Program" which is similar to "About the role". That's acceptable. We need to avoid repeating job title as heading. No Job ID etc. We need to remove boilerplate: EEO etc. Remove duplicated lines (Pay Range appears twice). Keep one. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: Intro paragraph: "Whether you're a recent grad or a seasoned professional, you can experience meaningful career growth at Rosendin. Enjoy a true sense of ownership as you work with a proven industry leader on some of the most exciting and high-profile projects in the nation. We offer a wide range of job opportunities, competitive compensation, full benefits, an Employee Stock Ownership Plan and more. Why Rosendin? Committed. Innovative. Engaged. Come build your experience with us! At Rosendin, our interns are more than participants; they are contributors. Our internship program is designed to give you meaningful, hands-on experience in the electrical construction industry while helping you build the foundation for a successful career." That's prose; could be under About the role. Then "About The Program Rosendin's Summer Internship Program is a paid 12 week hands-on experience designed for students ready to take the next step in their professional journey. You'll gain exposure to the electrical construction industry by working on real projects alongside experienced professionals across areas such as: Project ManagementEngineeringBIM (Building Information Modeling)Estimating & PreconstructionProcurement & Supply Chain Apply classroom learning while exploring career paths and taking on meaningful responsibilities alongside industry leaders." We can put that under About the role or maybe a separate "About the Program". We'll use

About the Program

. Then "What You'll Gain Hands-on experience contributing to active projectsOpportunities to take ownership of meaningful work and make an impactMentorship and guidance from industry expertsExposure to electrical construction systems, processes, and technologiesDevelopment of technical, professional, and leadership skillsNetworking opportunities across teams and business functions" That's like benefits or what you'll gain; could be under Benefits? But Benefits usually refers to compensation/benefits like health, 401k. This is more like learning outcomes. Could be under "What You'll Gain" but not in allowed list. Could treat as "Responsibilities"? Not exactly. Could treat as "Skills"? Not exactly. Maybe we can create a section "What You'll Gain" as heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. ...)" implying we should use those headings for sections. It might be okay to use other headings if they match content, but safer to map to allowed ones. "What You'll Gain" could be considered "Benefits" (benefits of the internship). But Benefits usually refers to employee benefits like health insurance. However we have no explicit benefits listed besides "competitive compensation, full benefits, an Employee Stock Ownership Plan". That's in intro. So we could have a Benefits section with that content. Thus we can put the "What You'll Gain" list under Benefits? Might be odd but okay. Alternatively we could create a section "What You'll Gain" as heading, but risk deviating from spec. The spec 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, but the examples are given. I'd stick to those. Thus we need to map content: - About the role / About the Program: combine intro and About The Program. - Responsibilities: maybe "Apply classroom learning while exploring career paths and taking on meaningful responsibilities alongside industry leaders." plus maybe "Hands-on experience contributing to active projects" etc. But those are more gains. - Requirements: "What We Look For" (coachability, accountability, learning agility, collaboration). - Qualifications: "What You Bring To Us" (currently pursuing bachelor's degree, graduation date Dec 2027 or later, rising junior/senior, fields, etc.) - Skills: "What You'll Need To Be Successful" (interest in applying technical knowledge, organizational skills, analytical, communication, collaboration, proficiency in MS Office, positive attitude). - Benefits: "competitive compensation, full benefits, an Employee Stock Ownership Plan" plus maybe "paid 12 week hands-on experience". Also Pay Range. - Pay: Pay Range $25.00-$28.00 Hourly. - Schedule: maybe not specified; we have no schedule info besides 12 week summer internship (implies schedule). Could mention "12 week" as schedule? But schedule heading expects maybe full-time, hours. We have no explicit schedule; we could omit Schedule section. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated. Benefits is stated (competitive compensation, full benefits, ESOP). So we can include Benefits and Pay. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive information. Let's list all substantive points: Intro paragraphs: - Meaningful career growth at Rosendin. - Sense of ownership, work with proven industry leader on exciting high-profile projects. - Wide range of job opportunities, competitive compensation, full benefits, ESOP. - Why Rosendin? Committed. Innovative. Engaged. - Interns are contributors; internship program gives meaningful hands-on experience in electrical construction industry while building foundation for successful career. About The Program: - Paid 12 week hands-on experience for students ready to take next step. - Gain exposure to electrical construction industry by working on real projects alongside experienced professionals across areas: Project Management, Engineering, BIM, Estimating & Preconstruction, Procurement & Supply Chain. - Apply classroom learning while exploring career paths and taking on meaningful responsibilities alongside industry leaders. What You'll Gain: - Hands-on experience contributing to active projects. - Opportunities to take ownership of meaningful work and make an impact. - Mentorship and guidance from industry experts. - Exposure to electrical construction systems, processes, and technologies. - Development of technical, professional, and leadership skills. - Networking opportunities across teams and business functions. What We Look For: - Motivated students aligning with commitment to excellence, integrity, growth. - Successful candidates demonstrate: - Coachability & Curiosity: eager to learn, seek feedback, take initiative. - Accountability & Work Ethic: takes ownership, follows through, delivers high-quality work. - Learning Agility & Adaptability: thrives in fast-paced environments, quickly applies new knowledge. - Collaboration & Communication: works effectively with others, communicates clearly and professionally. What You Bring To Us: - Currently pursuing bachelor's degree with graduation date Dec 2027 or later in field aligned with Rosendin's work including but not limited to: - Rising junior or rising senior status preferred. - Construction Management or Construction Engineering. - Engineering disciplines (Architectural, Electrical, Civil, Mechanical, Construction, etc.). - BIM. - Estimating & Preconstruction. - Procurement & Supply Chain. - Previous construction internship experience is a plus. What You'll Need To Be Successful: - Interest in applying technical knowledge to real-world projects and challenges. - Strong organizational skills with attention to detail and accuracy. - Ability to manage multiple tasks and adapt to changing priorities. - Strong analytical and problem-solving skills. - Professional verbal and written communication skills. - Ability to collaborate effectively with diverse teams and stakeholders. - Proficiency in, or willingness to learn, Microsoft Office applications (Outlook, Word, Excel) and other industry-related technologies. - Positive attitude and commitment to continuous learning. Working Conditions: - General work environment: performed primarily on active construction sites. - Activities include sitting for extended periods, standing, walking, typing, carrying, pushing, bending. - Work conducted primarily indoors with varying environmental conditions, such as fluorescent lighting and air conditioning. - Noise level typically low to medium. - Occasional lifting of up to 30 lbs. Pay Range: - $25.00-$28.00 Hourly. - Pay range for this role is what we expect to pay for candidates that meet the specified qualifications and requirements listed on this job description. - Candidate's pay can vary based on location, job-related experience, skills, and education. (Note duplicate removed.) We also have statement about success rooted in people, long-term vision, shared ownership, etc. That's more fluff; could be included in About the role or maybe omitted as boilerplate? It's not EEO but still generic. Might be considered boilerplate? It's not navigation/legal/EEO. It's about company culture. Might be okay to keep. We also have EEO statement at end: "Rosendin is committed to creating a diverse environment and is proud to be an Equal Opportunity Employer..." That's EEO boilerplate; we should remove. Also "Our success is rooted in our people..." maybe not boilerplate but could be kept under About the role. We need to ensure we don't repeat duplicated lines. The Pay Range appears twice; we keep one. Now craft HTML. We'll have sections:

About the Program

(or About the role). We'll include intro and About The Program content. Maybe better:

About the Role

with intro + About The Program. But we have also "What You'll Gain" which could be under Benefits? But we have separate Benefits section for compensation/benefits. Could put "What You'll Gain" under "What You'll Gain" heading but not allowed. Could treat as "Responsibilities"? Not exactly. Could treat as "Skills"? Not exactly. Maybe we can create a section "What You'll Gain" as heading, but risk deviating. However the instruction 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. I'd try to map to those. What You'll