Senior Structural Engineer (Infrastructure Risk) (Ph.D. and P.E. or S.E.)

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Exponent" (company description) but we should not repeat job title heading. We need sections: maybe "About the role" (the description of role), "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to include only sections that have real specific content. Let's parse content: - About Exponent: company description. Could be "About the role"? Actually "About Exponent" is about company, not role. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading for description of role? But we have "About Exponent" which is about company. Might be okay to use "About the role" heading and put the company description there? Might be misaligned. Better to follow instruction: Use those headings if we have content. We have content for responsibilities (list of duties). We have qualifications/skills (list). We have pay (salary range). We have benefits (mention benefits page). We have schedule? Not explicit schedule info; there is mention of flexible work style, in-person unless traveling, autonomy to balance work and personal schedules. That's schedule/flexibility info. So we could include Schedule section with that content. We need to avoid boilerplate: remove EEO, navigation, legal, duplicated lines, application instructions (like "Applicants are encouraged to submit a CV...") Actually that is part of qualifications? It says "Applicants are encouraged to submit a CV (Curriculum Vitae) with publications..." That's application instruction; we should remove it. Also "Thanks for your interest..." etc. Also "Key statistics:" maybe we can keep as part of About Exponent? It's substantive. We'll keep. We need to preserve all substantive information, not invent or summarize away detail. So we need to include the list of responsibilities exactly as given, but we can format as

• . Similarly for qualifications/skills. We need to not repeat job title as heading. So no heading for "Senior Structural Engineer (Infrastructure Risk)". We'll not include. We need to not put Job ID/requisition numbers as headings; none present. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  About Exponent Exponent is the only premium engineering and scientific consulting firm ... (the paragraph about company vision, etc.) plus maybe key statistics.

  But "About the role" maybe should be about the role, not company. However we have no explicit "About the role" paragraph besides the company description. Could we instead use "About Exponent" as heading? Not in allowed list but we could still use

  with that text? 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 those for those sections. Safer to stick to those headings. So we will put company description under "About the role". Might be okay. Then responsibilities: we have a list after "Our Opportunity We are currently seeking...". Actually after that paragraph, there is "You will be responsible for" then a list of items separated by line breaks. We'll extract each bullet. List: - Developing and implementing analytical tools and frameworks to characterize and assess critical infrastructure risks and support decision-making - Performing quantitative and probabilistic risk analysis to determine the impacts of hazards on infrastructure - Performing engineering analyses related to project work in the energy sector - Collaborating with multidisciplinary teams of engineers, statisticians, and data scientists to develop and implement engineering risk analyses - Preparing clear, technically rigorous reports, presentations, calculations, and exhibits that communicate engineering findings, conclusions, and recommendations to clients and stakeholders in the energy sector - Gathering, reviewing, analyzing, and synthesizing diverse sources of data and information – including structural drawings and specifications, inspection data, photographs, test results, codes and standards, meteorological and other environmental data, and relevant technical literature – for use in engineering analyses - Enhancing professional profile and expertise through participation and service in professional societies, continued professional development, technical publications, and conference presentations - Supporting practice recruiting efforts by identifying and recruiting exceptional and diversely experienced talent We'll put each as

  . Then qualifications/skills: The section "You Will Have The Following Skills And Qualifications" then list: - Ph.D. in Civil/Structural Engineering - Presently legally authorized to work in the United States. No immigration sponsorship or processing required. - Professional Engineer (P.E.) and/or Structural Engineer (S.E.) license in at least one state is required - 4+ years of relevant post-PhD work experience - Technical background in the theory and implementation of probabilistic risk analysis - Graduate coursework in probabilistic methods or risk analysis in civil engineering applications - Excellent written and verbal communication skills (writes and speaks clearly and concisely; work product is thorough and technically accurate) - Able to work independently and in multidisciplinary teams - Able to gather and interpret information from diverse sources in engineering, infrastructure, energy, and related contexts - Able to convey technical conclusions to individuals in engineering, business, and related industries - Applies technical knowledge, creativity, and innovation in completing work - Efficient and poised under stress; receptive to changes and new ideas; able to prioritize tasks - Able to support multiple concurrent group projects We could split into Requirements, Qualifications, Skills sections. But we can combine into one "Qualifications" or "Skills". The instruction allows multiple sections. We need to decide how to split logically. Maybe:

  Requirements

  list of mandatory items: Ph.D., work authorization, PE/SE license, 4+ years experience, technical background in probabilistic risk analysis, graduate coursework.

  Skills

  list of soft skills: communication, teamwork, etc. But we also have "You Will Have The Following Skills And Qualifications" heading; we could treat that as Qualifications. Let's create:

  Qualifications

  includes Ph.D., work auth, PE/SE license, 4+ years, technical background, graduate coursework.

  Skills

  includes communication, work independently, gather info, convey conclusions, applies knowledge, efficient under stress, support multiple projects. We also have "Benefits" section: The posting says "Benefits You Will Enjoy Access benefits information on our Life@Exponent page: https://www.exponent.com/careers/life-exponent". That's the only benefit info. So we can include Benefits section with that sentence as

  . Pay: "Salary Range USD $130,000.00 - USD $155,000.00 /Yr." Also mention base salary range dependent on experience etc. We'll include that. Schedule: The posting includes flexible work style: "Consultants have the autonomy to balance their work and personal schedules so you can meet with clients, visit inspection sites, attend conferences, and make time for priorities outside of work, too. It is this flexible, agile work style and working hours that allow our teams to drive innovation and results in their own ways, while meeting the needs of clients." Also earlier: "Our consultants engage in-person in the office unless they are traveling for client work or other business activities." We'll capture that. We need to ensure we don't include boilerplate like EEO, navigation, legal, duplicated lines, application instructions (CV submission). Also remove "Thanks for your interest..." etc. Also remove "Life @ Exponent" links? Actually we kept benefits link. The "Life @ Exponent" section includes links to life-exponent and our-impact; we might keep only the benefits link. The "Life @ Exponent" heading is not part of allowed headings; we can ignore that section, but we need to preserve substantive info: the links to life-exponent and our-impact are maybe not essential? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The links are substantive? They are pointers to more info. Might be considered substantive. However they are under "Life @ Exponent" which is not a required heading; we could still include a

  with those links under Benefits or maybe under About the role? But we already have benefits link. The life-exponent link is same as benefits link. The our-impact link is extra. We could include a

  under About the role: "Learn more about life at Exponent and our impact: https://www.exponent.com/careers/life-exponent https://www.exponent.com/company/our-impact". That seems substantive. We also need to remove duplicated lines: there may be duplicate of "Exponent is a proud equal opportunity employer." We'll drop that. Now construct HTML. We'll start with

  About the role

  then

  containing company description and key statistics and maybe life-exponent links. Let's write company description paragraph: "Exponent is the only premium engineering and scientific consulting firm with the depth and breadth of expertise to solve our clients’ most profoundly unique, unprecedented, and urgent challenges. Our vision is to engage multidisciplinary teams of science, engineering, and regulatory experts to empower clients with solutions that create a safer, healthier, more sustainable world. For over five decades, we've connected the lessons of past failures with tomorrow's solutions to advise clients as they innovate technologically complex products and processes, ensure the safety and health of their users, and address the challenges of sustainability. Join our team of experts with degrees from top programs at over 500 universities and extensive experience spanning a variety of industries. At Exponent, you’ll contribute to the diverse pool of ideas, talents, backgrounds, and experiences that drives our collaborative teamwork and breakthrough insights. Plus, we help you grow your career through mentoring, sponsorship, and a culture of learning." Then key statistics: "Key statistics: 950+ Consultants 640+ Ph.D.s 90+ Disciplines 30+ Offices globally". We'll include as part of same paragraph or separate

  . Probably separate

  . Then life-exponent links: "Learn more about life at Exponent and our impact: https://www.exponent.com/careers/life-exponent https://www.exponent.com/company/our-impact". We'll put as

  . Now responsibilities section. Then qualifications section. Then skills section. Then benefits section:

  Access benefits information on our Life@Exponent page: https://www.exponent.com/careers/life-exponent

  Pay section:

  The base salary range for this position is dependent on experience and capabilities which will be assessed during the interview process. Salary Range USD $130,000.00 - USD $155,000.00 /Yr.

  Schedule section:

  Our consultants engage in-person in the office unless they are traveling for client work or other business activities. Consultants have the autonomy to balance their work and personal schedules so you can meet with clients, visit inspection sites, attend conferences, and make time for priorities outside of work, too. It is this flexible, agile work style and working hours that allow our teams to drive innovation and results in their own ways, while meeting the needs of clients.

  Check for any duplicated content: we have not included EEO etc. Now ensure we didn't miss any substantive info: The "Opportunity" paragraph: "We are currently seeking a Senior Structural Engineer (Infrastructure Risk) for our Civil & Structural Engineering Practice in New York, NY; Menlo Park, CA; Oakland, CA; Irvine, CA; Atlanta, GA; or Houston TX." That's location info. Should we include location? It's substantive. Where to put? Could be under About the role or maybe a separate "Locations" but not in