Civil/Structural Design Engineer I/II – Catawba Nuclear Station

We need to output HTML fragment with sections: About the role? The posting includes summary and description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to extract content. Let's parse the posting: - Intro: "More than a career - a chance to make a difference in people's lives. Build an exciting, rewarding career with us – help us make a difference for millions of people every day. Consider joining the Duke Energy team, where you'll find a friendly work environment, opportunities for growth and development, recognition for your work, and competitive pay and benefits." That's about the role/company. Could be "About the role" or "About Duke Energy". We'll use "About the role". Provide paragraph. - Summary: "This is the entry level of the Engineering classification hierarchy. Employees at this entry level solve problems in engineering areas of specialization with close supervision. Incumbents are expected to develop skills, and the ability to work with greater independence. Duke Energy is seeking a Civil/Structural Design Engineer to support engineering design, analysis, and plant modification activities at Catawba Nuclear Station. Engineers in this role support the design, analysis, modification, and maintenance of structures, systems, and components within an operating nuclear power plant. Work may include development of design change packages, structural analyses and evaluations, pipe stress analysis, pipe hanger and support design, lifting and rigging evaluations, maintenance support, and independent review of peer-prepared engineering products." That's also description; could be part of About the role or separate "Summary". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put summary under About the role. - Responsibilities: list bullet points under "Responsibilities". The posting has a heading "Responsibilities" then a paragraph and bullet-like sentences. We need to extract each duty as

. Let's list them: 1. Provides engineering/technical expertise and guidance in the identification, analysis and resolution of routine problems in area of expertise. 2. Provide engineering and technical expertise in the identification, analysis, and resolution of routine civil/structural design problems. 3. Prepare thorough and accurate technical reports, correspondence, documentation, calculations, specifications, and sketches associated with the resolution of routine technical problems. 4. Support development and implementation of plant modification packages, including field walkdowns, design input verification, constructability considerations, and resolution of field conditions. 5. Assist with planning, organizing, estimating, scheduling, and monitoring work activities to support business goals and objectives. 6. Conduct basic engineering studies and evaluations under the guidance of higher-level engineers. 7. Apply fundamental engineering concepts, practices and procedures. 8. Develop effective working relationships, coordinate work across disciplines, communicate clearly, and maintain accurate records and files. 9. Support the company's goals and represent the company positively and professionally. Note there is some duplication: first two similar; we keep both as they appear. - Basic/Required Qualifications: This is under "Basic/Required Qualifications". It includes two levels: I and II. We need to capture qualifications. The posting includes: Civil/Structural Design Engineer I - Bachelor of Science in Civil Engineering or a closely related Structural Engineering degree from an ABET-accredited program. - A Master of Science in Civil or Structural Engineering may be considered in lieu of a Bachelor of Science in Civil Engineering, consistent with company qualification requirements. - Good written and oral communication skills. - 0-2 years of engineering experience. Civil/Structural Design Engineer II - Bachelor of Science in Civil Engineering or a closely related Structural Engineering degree from an ABET-accredited program. - A Master of Science in Civil or Structural Engineering may be considered in lieu of a Bachelor of Science in Civil Engineering, consistent with company qualification requirements. - Good written and oral communication skills. - 2-4 years of engineering experience. - Minimum of 1 year of nuclear experience. We could treat these as "Requirements" or "Qualifications". The allowed headings include Requirements and Qualifications. We need to decide. Usually "Requirements" for mandatory, "Qualifications" for desired. But we have both basic/required and desired qualifications. We'll put basic/required under "Requirements" and desired under "Qualifications". Or we could combine. Let's follow: Requirements = Basic/Required Qualifications. Qualifications = Desired Qualifications. Thus Requirements list: - Bachelor of Science in Civil Engineering or a closely related Structural Engineering degree from an ABET-accredited program. - A Master of Science in Civil or Structural Engineering may be considered in lieu of a Bachelor of Science in Civil Engineering, consistent with company qualification requirements. - Good written and oral communication skills. - 0-2 years of engineering experience. (for Engineer I) OR 2-4 years of engineering experience and minimum 1 year nuclear experience (for Engineer II). Since posting includes both levels, we need to preserve all info. Could combine as: "0-2 years of engineering experience (Engineer I) or 2-4 years of engineering experience with minimum 1 year nuclear experience (Engineer II)". But we must not invent or summarize away detail. Better to keep both bullet points separate? Could list as two sets. However we need to avoid duplication. We could list: - For Engineer I: Bachelor of Science in Civil Engineering or closely related Structural Engineering degree from an ABET-accredited program; Master's may be considered in lieu; good written and oral communication skills; 0-2 years engineering experience. - For Engineer II: same education/communication; 2-4 years engineering experience; minimum 1 year nuclear experience. But that's summarizing. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing may be considered summarizing away detail? It's ambiguous. Safer to keep each bullet as originally written, but we have duplication. We could list each bullet exactly as appears, even if duplicated. That preserves info. Let's extract the exact lines: From posting: "Civil/Structural Design Engineer I Bachelor of Science in Civil Engineering or a closely related Structural Engineering degree from an ABET-accredited program.A Master of Science in Civil or Structural Engineering may be considered in lieu of a Bachelor of Science in Civil Engineering, consistent with company qualification requirements. Good written and oral communication skills.0-2 years of engineering experience." "Civil/Structural Design Engineer II Bachelor of Science in Civil Engineering or a closely related Structural Engineering degree from an ABET-accredited program.A Master of Science in Civil or Structural Engineering may be considered in lieu of a Bachelor of Science in Civil Engineering, consistent with company qualification requirements. Good written and oral communication skills.2-4 years of engineering experience.Minimum of 1 year of nuclear experience." We could split into separate bullet points for each line, but that would be messy. Better to keep as two paragraphs under Requirements. Use

for prose. But we need to use

• for any list of duties/requirements/benefits. Requirements is a list, so we should use
  • . Each requirement could be a bullet. We could break into logical items: education, master's alternative, communication skills, experience (with variants). But that may be summarizing. Given the instruction to prefer a few substantive sections over many thin ones, we could keep Requirements as a

    containing the text. However the rule says: "Use

    • for any list of duties/requirements/benefits, and

      for prose." So if we treat Requirements as a list, we need

      • . If we treat it as prose, we use

        . The requirement list is indeed a list of qualifications. So we should use

        • . We'll break into sensible items without losing info. Let's list: - Bachelor of Science in Civil Engineering or a closely related Structural Engineering degree from an ABET-accredited program. - A Master of Science in Civil or Structural Engineering may be considered in lieu of a Bachelor of Science in Civil Engineering, consistent with company qualification requirements. - Good written and oral communication skills. - 0-2 years of engineering experience (Engineer I) OR 2-4 years of engineering experience with minimum 1 year nuclear experience (Engineer II). But that's summarizing the experience. Could we instead list two separate bullets for experience: "0-2 years of engineering experience (Engineer I)" and "2-4 years of engineering experience with minimum 1 year nuclear experience (Engineer II)". That preserves detail. Thus Requirements bullets: - Bachelor of Science in Civil Engineering or a closely related Structural Engineering degree from an ABET-accredited program. - A Master of Science in Civil or Structural Engineering may be considered in lieu of a Bachelor of Science in Civil Engineering, consistent with company qualification requirements. - Good written and oral communication skills. - 0-2 years of engineering experience (Engineer I). - 2-4 years of engineering experience with minimum 1 year nuclear experience (Engineer II). That seems to preserve all info. Now Desired Qualifications: list bullet points. From posting: "Desired Qualifications Successful completion of the Fundamentals of Engineering (FE) examination or active pursuit of Engineer Intern certification.Interest in continued professional development and obtaining Professional Engineer (PE) licensure. Background in pipe stress analysis with a willingness to perform and learn ASME B31.1 and ASME Section III pipe stress analysis.Coursework or experience in structural analysis, steel design, reinforced concrete design, foundations, anchorage, seismic design, or structural dynamics. Familiarity with engineering analysis or design software used for structural, piping, or finite element analysis. Understanding of basic engineering theories, principles, and practices used to research engineering design issues, evaluate alternatives, develop sound recommendations, and present results.Ability to deal with a variety of individuals from various socio-economic, cultural and ethnic backgrounds.Experience in the utility, industrial, power generation, or nuclear industry. Understanding of basic principles of project management." We need to split into separate bullets. Let's parse: - Successful completion of the Fundamentals of Engineering (FE) examination or active pursuit of Engineer Intern certification. - Interest in continued professional development and obtaining Professional Engineer (PE) licensure. - Background in pipe stress analysis with a willingness to perform and learn ASME B31.1 and ASME Section III pipe stress analysis. - Coursework or experience in structural analysis, steel design, reinforced concrete design, foundations, anchorage, seismic design, or structural dynamics. - Familiarity with engineering analysis or design software used for structural, piping, or finite element analysis. - Understanding of basic engineering theories, principles, and practices used to research engineering design issues, evaluate alternatives, develop sound recommendations, and present results. - Ability to deal with a variety of individuals from various socio-economic, cultural and ethnic backgrounds. - Experience in the utility, industrial, power generation, or nuclear industry. - Understanding of basic principles of project management. Now Benefits: The posting mentions "competitive pay and benefits" in intro, but no specific benefits listed. There's also "Relocation Assistance Provided (as applicable) Yes". That's a benefit. Also "Represented/Union Position No", "Visa Sponsored Position No". Those are not benefits. Also "Travel Requirements 5-15%". That's not benefit. There's also "Occasional overnight travel." That's not benefit. There's also "Additional hours expected as workload/business need requires." Not benefit. We have "Relocation Assistance Provided (as applicable) Yes". That's a benefit. Also maybe "competitive pay and benefits" is generic but not specific. We should only include sections when posting has real specific content. Relocation assistance is specific. So we can have a Benefits section with that. Pay: The posting mentions "competitive pay" but no specific numbers. Not specific enough to include Pay section (should not include if not specific). So we omit Pay. Schedule: Not specific; we have "Additional hours expected as workload/business need requires." Not a schedule. So omit Schedule. Now we also have "Working Conditions" etc. Not in allowed headings, so we ignore. We also have "Travel Requirements 5-15%" maybe could be under Schedule? But schedule is about work