Engineer II - Electrical Studies

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: description of company (maybe About the role?), responsibilities (What You'll Do), qualifications (What You Bring To Us), competencies, What You'll Need To Be Successful (skills), Travel, Working Conditions, Benefits, Pay Range. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. Also remove duplicated lines. We need to preserve all substantive info. We need to decide sections: - About the role: maybe the introductory paragraph about Rosendin and the Engineer II description. Could be "About the role" heading. - Responsibilities: "What You’ll Do" list. - Requirements: maybe "What You Bring To Us" (education, experience) and "What You’ll Need To Be Successful" (skills). Could combine into Requirements and Skills sections. - Qualifications: maybe same as Requirements? But we can have separate sections: Requirements (education/experience) and Skills (technical competencies). The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content. - Benefits: list of benefits. - Pay: pay range. - Schedule: maybe Travel up to 25% and Working Conditions? Schedule not explicitly given. Could include Travel as part of Schedule? But schedule is not given. We could omit Schedule if no specific schedule info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. So we can include Pay and Benefits. Schedule not present, so omit. We also have Working Conditions and Travel; maybe could be part of Responsibilities? Not exactly. Could be a separate section like "Working Conditions" but not in allowed headings list. The allowed headings list includes those specific ones; we should only use those headings. So we should not create a heading like Working Conditions. We could fold that info into Responsibilities or Requirements? Probably better to include under Responsibilities as additional duties? But it's not a duty. Could include under Responsibilities as bullet points? Might be okay to include under Responsibilities as extra bullet: "Travel up to 25% (excluding local field visits)" and "Working conditions: ...". However the instruction: Use

• for any list of duties/requirements/benefits. So we can list those as list items under Responsibilities? Might be okay. But we need to preserve all substantive information. So we need to include travel and working conditions somewhere. Could create a section "Responsibilities" that includes duties plus travel and working conditions as list items. That might be acceptable. Alternatively we could create a section "Requirements" for education/experience, "Skills" for technical competencies, "Benefits", "Pay". And put travel/working conditions under Responsibilities. Let's extract content: About the role: The first paragraphs about Rosendin, Engineer II description: "Whether you’re a recent grad... Your Next Opportunity The Engineer II is a mid-level engineering position responsible for providing technical engineering information and support to the senior engineers to ensure that projects comply with the project requirements and all engineering standards, applicable codes, and specifications. Knowledge of various electrical engineering concepts, including power distribution, lighting, grounding, energy conservation, and value engineering related to designing state-of-the-art, constructible projects." We can put that as prose under About the role. Responsibilities: list from "What You’ll Do": bullet points (each sentence). Also include Travel up to 25% (Does not include local field visits) and Working Conditions paragraph. We need to ensure we don't duplicate lines. The posting repeats some EEO lines; we remove. Requirements: "What You Bring To Us": Bachelor’s degree in engineering, architectural engineering, construction sciences, or equivalent experience. Typically requires a minimum of 2 years of Engineering Experience. This candidate may have completed the Engineer-In-Training and is encouraged to pursue registration as a Professional Engineer. LEED AP® is desired for this position. Can be a combination of education, training, and relevant experience. Also maybe "What You’ll Need To Be Successful" includes many skill requirements; but those could go under Skills. Skills: list of competencies: Teamwork, Productivity, Strategic thinking (under Competencies). Also the bullet list under "What You’ll Need To Be Successful": requires working electrical engineering knowledge..., fully competent in majority of Engineer I skills, high-rise residential, Commercial, Data Center experience a plus, proficiency in analytics programs..., fluency with the codes, working knowledge of energy efficiency requirements, proficient in Autodesk, Microsoft Office, illumination software, ability to prioritize..., ability to work to meet deadlines..., effective oral and written communication skills, ability to be self-motivated..., ability to interact effectively..., travel up to 25% (but we already placed travel), working conditions. We need to avoid duplication: travel and working conditions we already placed maybe under Responsibilities; but they also appear under Skills. To avoid duplication, we could keep them only once. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include travel and working conditions somewhere. If we put them under Responsibilities, we still need to include them under Skills? That would be duplication. Better to keep them under Skills (as they are skill requirements) and not duplicate under Responsibilities. But Responsibilities list does not include travel/working conditions originally; they are separate sections after skills. So we should keep them under Skills (or maybe a separate section like Working Conditions but not allowed). Since we cannot create a new heading, we could fold them into Skills as list items. Thus Skills section will include both the competency list and the technical requirements plus travel and working conditions. Responsibilities will be just the "What You’ll Do" list. Requirements will be education/experience. Benefits list. Pay range. Now we need to format. We must not include boilerplate like EEO, duplicated lines, cookie/navigation/legal etc. Also remove duplicated lines like "Rosendin is committed to creating a diverse environment..." appears twice; we keep only once maybe but we are removing EEO entirely, so we can drop those lines. Also remove "Our success is rooted in our people..." etc maybe not needed? That's generic fluff but still substantive? It's more like marketing; but we might keep as part of About the role? It's not essential but could be considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Our success is rooted..." is not EEO but could be considered boilerplate fluff. Might be okay to keep? It's not a specific job detail. Safer to omit generic fluff that doesn't add specific info about role. However the instruction says preserve ALL substantive information; generic fluff may not be substantive. I'd lean to keep only specifics about role, responsibilities, requirements, skills, benefits, pay. So we can omit the fluff paragraphs about success, shared ownership, etc. Thus About the role will include the initial paragraph about Rosendin and Engineer II description. Possibly also the "Why Rosendin?" bullet points? Those are values: Committed. Innovative. Engaged. Could be considered substantive? Might be okay to keep as part of About the role. But they are short adjectives; could be considered fluff. I'd keep them as part of About the role as they describe culture. Let's craft HTML. Structure:

  About the role

  ... paragraphs ...

  Responsibilities

  • Oversee junior engineers, designers, and staff assigned to your work or team. In this instance, an Engineer II should be comfortable leading projects of limited scope.
  • Review, comment on, and process equipment and system submittals in coordination with the Engineer of Record.
  • Generate electrical specifications appropriate for the project.
  • Develop complete and accurate sequences of operation for electrical systems.
  • Support equipment and system testing, startup, and commissioning activities.
  • Perform coordination between architectural, structural, mechanical, plumbing, and electrical disciplines.
  • Prepare and review power distribution system designs, including power, lighting, grounding, and auxiliary systems.
  • Prepare power system single-line diagrams, including feeder sizing, overcurrent protection device selection, and equipment layouts.
  • Perform electrical system modeling and conduct: Short Circuit Studies, Protective Device Coordination Studies, Arc Flash Hazard Analyses, Equipment Rating Evaluations.
  • Develop and maintain SCCAF models using ETAP, SKM Power Tools, EasyPower, or equivalent power system analysis software.
  • Produce technical reports and recommendations related to system protection, selective coordination, equipment adequacy, and arc flash mitigation.
  • Perform engineering calculations related to: Voltage drop, Voltage regulation, Conductor sizing, Distribution capacity, Underground heat effects (Neher-McGrath), Fault current calculations.
  • Coordinate study results with project specifications, equipment procurement, and construction requirements.
  • Visit jobsites to perform field surveys, collect electrical system data, and verify existing conditions.
  • Utilize engineering analysis programs and professional judgment to evaluate system performance, fault currents, loading conditions, and protective device operation.
  • Conduct value engineering evaluations and recommend practical, cost-effective solutions.
  • Attend project design meetings and coordinate with clients, architects, engineers, contractors, commissioning teams, and utility representatives.
  • Research and resolve technical issues, drawing discrepancies, interference conditions, and constructability concerns.
  • Represent the engineering group during construction and commissioning activities to ensure timely resolution of field issues and proper implementation of study recommendations.

  Requirements

  • Bachelor’s degree in engineering, architectural engineering, construction sciences, or equivalent experience.
  • Typically requires a minimum of 2 years of Engineering Experience.
  • This candidate may have completed the Engineer-In-Training and is encouraged to pursue registration as a Professional Engineer.
  • LEED AP® is desired for this position.
  • Can be a combination of education, training, and relevant experience.

  Skills

  • Teamwork
  • Productivity
  • Strategic thinking
  • Working electrical engineering knowledge, including power distribution, lighting, grounding, energy conservation, and value engineering related to designing state-of-the-art constructible projects.
  • Fully competent in the majority of Engineer I skills.
  • High‑rise residential, Commercial, and Data Center experience is a plus.
  • Proficiency in analytics programs for short circuit and over‑current coordination and arc flash analysis programs.
  • Fluency with the Codes.
  • Working knowledge of the energy efficiency requirements.
  • Proficient in Autodesk, Microsoft Office (Outlook, Word, Excel, etc.); illumination software.
  • Ability to prioritize and manage multiple tasks, changing priorities as necessary.
  • Ability to work to meet deadlines and adapt to changing requirements with a positive attitude.
  • Effective oral and written communication skills as required for the position.
  • Ability to be self‑motivated, proactive, and an effective team player.
  • Ability to interact effectively and professionally with all levels of employees, both management and staff alike, vendors, clients, and others.
  • Travel up to 25% (does not include local field visits).
  • Working conditions: general work environment – sitting for long periods, standing, walking, typing, carrying, pushing, bending; work conducted primarily indoors with varying environmental conditions such as fluorescent lighting and air conditioning; noise level usually low to medium; occasional lifting of up to 40 lbs.