Structural Engineer SME - AI Data Centers
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections are present.
We have content: "Your impact" paragraph describing role. Could be "About the role". Then responsibilities: list of duties (Provide quality reviews..., Leading complex..., Developing..., Overseeing...). Then requirements/qualifications: list of needed abilities (Ability to quickly identify..., Understand..., Experience..., Bachelor..., 15+ years..., Registered Professional Engineer..., Knowledge of CAD..., Proficiency with structural analysis..., Knowledge and application of ACI..., Knowledge and application of Building Codes..., Proficiency with MS Office..., Ability for travel..., Proficiency reviewing...). Also "Ideally, you’ll also have..." list: Master of Science, Registered SE License, Experience with hyperscale facility design, Ability to lead teams... Those could be "Preferred qualifications" but we can include under Requirements or Skills.
Benefits: described: health and welfare benefits, medical, dental, vision, basic life insurance, 401(k), ability to purchase stock at discount, deferred compensation plan, Executive Deferral Plan, unlimited U.S. Personalized Paid Time Off (PPTO), seven paid holidays, caregiver leave, possible additional rewards (merit increases, performance discretionary bonus, stock). Also hybrid working policy.
Pay: base salary range $169,500 to $233,000.
Schedule: not explicitly given besides travel percentage; no schedule like full-time, part-time. Not given, so we should not create Schedule section.
We must not include boilerplate like EEO, etc. Remove duplicated lines, cookie/navigation/legal/EEO etc. Also remove application instructions, job posted date, etc.
We need to preserve all substantive information. So include all details.
Structure: Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide sections: About the role (Your impact paragraph). Responsibilities (list of duties). Requirements (maybe combine qualifications and skills). Benefits. Pay.
We could also have Skills section for technical skills (CAD, analysis software, codes, MS Office, Bluebeam). But we can incorporate into Requirements.
Better to follow typical: About the role (overview), Responsibilities, Requirements, Benefits, Pay.
Let's extract prose for About the role: The paragraphs starting from "At Jacobs, we're challenging today..." through "Your guidance will not only help shape the design delivery of the team but will guide the delivery of our Design-Build delivery methodology." That's a block. We'll put that in
.
Responsibilities: list items: "Provide quality reviews of complex projects.", "Leading complex structural analyses and guiding the selection of appropriate methodologies to ensure robust, code compliant, and constructible design solutions.", "Developing and validating advanced structural computer models, establishing modeling standards, and mentoring team members in best practice simulation techniques.", "Overseeing critical calculations for member design and foundations, directing material take offs and estimating inputs, and providing technical governance for schedules, design documentation, and interdisciplinary coordination."
Also earlier: "As a senior subject matter expert within our Data Center team, you’ll lead structural engineering efforts across a portfolio of data center projects, including new builds and retrofits. As part of the vision of the Department Manager, you’ll drive the technical direction, and ensure structural solutions meet the highest standards of performance, and constructability. This role is heavily client‑ and contractor‑facing, blending technical authority with the ability to communicate and collaborate across diverse teams. The ideal candidate thrives at the intersection of deep mission‑critical engineering expertise and relationship‑driven leadership—confidently navigating design, construction, and stakeholder challenges while delivering solutions that inspire trust and keep our clients at the center. You’ll serve as a key technical leader, guiding a portfolio of projects and coordinating closely with the structural engineering teams. You will mentor structural leads and support the projects by meeting with clients and upper management as required and be able to speak directly to the status of various projects. Your expertise will shape project execution, influence design strategy, and strengthen our delivery excellence. This role offers significant opportunity to expand your technical authority, mentor emerging talent, and grow your leadership presence as you help define the next generation of high-performance data center infrastructure."
These could be considered responsibilities as well. Might be better to include them in About the role or Responsibilities. The instruction: Use
- for any list of duties/requirements/benefits. So we should turn duties into list. The paragraphs describing duties could be turned into list items. But we also have a separate explicit list after "Other key contributions include". That list is clearly duties. We'll combine all duty statements into a list.
Let's extract duty statements:
- Lead structural engineering efforts across a portfolio of data center projects, including new builds and retrofits.
- Drive the technical direction (as part of the vision of the Department Manager) and ensure structural solutions meet the highest standards of performance and constructability.
- Role is heavily client‑ and contractor‑facing, blending technical authority with the ability to communicate and collaborate across diverse teams.
- Serve as a key technical leader, guiding a portfolio of projects and coordinating closely with the structural engineering teams.
- Mentor structural leads and support the projects by meeting with clients and upper management as required and be able to speak directly to the status of various projects.
- Shape project execution, influence design strategy, and strengthen delivery excellence.
- Expand technical authority, mentor emerging talent, and grow leadership presence to help define the next generation of high-performance data center infrastructure.
- Guide the delivery of our Design-Build delivery methodology.
- Provide quality reviews of complex projects.
- Lead complex structural analyses and guide the selection of appropriate methodologies to ensure robust, code compliant, and constructible design solutions.
- Develop and validate advanced structural computer models, establish modeling standards, and mentor team members in best practice simulation techniques.
- Oversee critical calculations for member design and foundations, direct material take offs and estimating inputs, and provide technical governance for schedules, design documentation, and interdisciplinary coordination.
That seems comprehensive.
Now Requirements: list of needed abilities and qualifications.
From "Here's what you'll need" list:
- Ability to quickly identify complex challenges, solve problems, communicate solutions and direct junior and senior staff on best practices
- Understand the complexities of large contracts and different contract structures and be able to manage change orders, and be able to stand up for the engineering team against the liabilities of contractors
- Experience with almost every building material and type, and have the ability to speak to the executive level about any subject without advance notice
- Bachelor of Science in Civil or Structural Engineering
- 15+ or more years of professional experience in structural engineering
- Registered Professional Engineer with the ability to become registered in additional states
- Knowledge of CAD software, such as AutoCad, Revit, MicroStation and S3D
- Proficiency with structural analysis software such as RISA, RamSS or STAAD
- Knowledge and application of ACI, AISC, ASCE 7, AIST Technical Report 13, and other industry relevant design code and standards
- Knowledge and application of Building Codes
- Proficiency with MS Office suite software including MS Teams for remote coordination
- Ability for travel to various client’s sites (approx. 10% to 40% travel)
- Proficiency reviewing and commenting on drawings in Bluebeam
Then "Ideally, you’ll also have":
- Master of Science in Engineering
- Registered SE License
- Experience with hyperscale facility design with key global clients
- Ability to lead teams to deliver commitments on schedule and on budget while meeting quality and client expectations
These could be "Preferred qualifications". We could include them under Requirements as well, maybe separate section "Preferred qualifications". But instruction says only include sections when posting has real specific content. It does have that content, so we could add a section "Preferred qualifications". However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use "Qualifications" for the required qualifications, and "Skills" for technical skills, and "Preferred qualifications" not in list. But we could incorporate into Requirements or Qualifications.
Better to follow: Use "Requirements" for mandatory requirements, and "Preferred qualifications" maybe not allowed. Could put them under "Qualifications". The list includes "Qualifications" as a possible heading. So we can have a section "Qualifications" for the required qualifications (Bachelor, 15+ years, PE, etc.) and maybe "Skills" for technical skills (CAD, analysis software, codes, MS Office, Bluebeam, travel). And "Preferred qualifications" could be included under "Qualifications" as well, but we could add a separate "Preferred qualifications" not in allowed list; better to avoid.
Thus we can have sections: About the role, Responsibilities, Requirements (maybe combine mandatory and preferred), Benefits, Pay.
But we need to avoid thin sections. Let's decide:
- About the role: overview paragraph (Your impact).
- Responsibilities: list of duties (the combined list).
- Requirements: list of mandatory requirements (the "Here's what you'll need" list).
- Benefits: list of benefits.
- Pay: salary range.
We could also include a "Skills" section for technical skills (CAD, analysis software, codes, MS Office, Bluebeam). But those are already in Requirements list; we could keep them there.
Thus we will output:
About the role
... (the overview paragraph)
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
The base salary range for this position is $169,500.00 to $233,000.00. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training.
We must not include fluff like "commensurate with experience". Not present.
Now we need to ensure we preserve all substantive information. Let's capture overview paragraph exactly as in text, but we may need to trim to avoid duplication. The overview includes multiple sentences. We'll copy the block from "At Jacobs, we're challenging today..." to "...Design-Build delivery methodology." Let's extract that block.
Original text:
"At Jacobs, we're challenging today to reinvent tomorrow by solving the world's most critical problems for thriving cities, resilient environments, mission-critical outcomes, operational advancement, scientific discovery and cutting-edge manufacturing, turning abstract ideas into realities that transform the world for good. Your impact This job opportunity is available at ANY location in the United States. Ideally, selected candidates will be near a JACOBS U.S. based office, but we intend to hire the "best" candidates. At Jacobs, we never settle — we push boundaries, elevate standards, and deliver with purpose. As a senior subject matter expert within our Data Center team, you’ll lead structural engineering efforts across a portfolio of data center projects, including new builds and retrofits. As part of the vision of the Department Manager, you’ll drive the technical direction, and ensure structural solutions meet the highest standards of performance, and constructability. This role is heavily client‑ and contractor‑facing, blending technical authority with the ability to communicate and collaborate across diverse teams. The ideal candidate thrives at the intersection of deep mission‑critical engineering expertise and relationship‑driven leadership—confidently navigating design, construction, and stakeholder challenges while delivering solutions that inspire trust and keep our clients at the center. You’ll serve as a key technical leader, guiding a portfolio of projects and coordinating closely with the structural engineering teams. You will mentor structural leads and support the projects by meeting with clients and upper management
- for any list of duties/requirements/benefits. Use
for prose. We need to decide sections: About the role (Your impact paragraph). Responsibilities (list of duties). Requirements (maybe combine qualifications and skills). Benefits. Pay. We could also have Skills section for technical skills (CAD, analysis software, codes, MS Office, Bluebeam). But we can incorporate into Requirements. Better to follow typical: About the role (overview), Responsibilities, Requirements, Benefits, Pay. Let's extract prose for About the role: The paragraphs starting from "At Jacobs, we're challenging today..." through "Your guidance will not only help shape the design delivery of the team but will guide the delivery of our Design-Build delivery methodology." That's a block. We'll put that in
. Responsibilities: list items: "Provide quality reviews of complex projects.", "Leading complex structural analyses and guiding the selection of appropriate methodologies to ensure robust, code compliant, and constructible design solutions.", "Developing and validating advanced structural computer models, establishing modeling standards, and mentoring team members in best practice simulation techniques.", "Overseeing critical calculations for member design and foundations, directing material take offs and estimating inputs, and providing technical governance for schedules, design documentation, and interdisciplinary coordination." Also earlier: "As a senior subject matter expert within our Data Center team, you’ll lead structural engineering efforts across a portfolio of data center projects, including new builds and retrofits. As part of the vision of the Department Manager, you’ll drive the technical direction, and ensure structural solutions meet the highest standards of performance, and constructability. This role is heavily client‑ and contractor‑facing, blending technical authority with the ability to communicate and collaborate across diverse teams. The ideal candidate thrives at the intersection of deep mission‑critical engineering expertise and relationship‑driven leadership—confidently navigating design, construction, and stakeholder challenges while delivering solutions that inspire trust and keep our clients at the center. You’ll serve as a key technical leader, guiding a portfolio of projects and coordinating closely with the structural engineering teams. You will mentor structural leads and support the projects by meeting with clients and upper management as required and be able to speak directly to the status of various projects. Your expertise will shape project execution, influence design strategy, and strengthen our delivery excellence. This role offers significant opportunity to expand your technical authority, mentor emerging talent, and grow your leadership presence as you help define the next generation of high-performance data center infrastructure." These could be considered responsibilities as well. Might be better to include them in About the role or Responsibilities. The instruction: Use
- for any list of duties/requirements/benefits. So we should turn duties into list. The paragraphs describing duties could be turned into list items. But we also have a separate explicit list after "Other key contributions include". That list is clearly duties. We'll combine all duty statements into a list.
Let's extract duty statements:
- Lead structural engineering efforts across a portfolio of data center projects, including new builds and retrofits.
- Drive the technical direction (as part of the vision of the Department Manager) and ensure structural solutions meet the highest standards of performance and constructability.
- Role is heavily client‑ and contractor‑facing, blending technical authority with the ability to communicate and collaborate across diverse teams.
- Serve as a key technical leader, guiding a portfolio of projects and coordinating closely with the structural engineering teams.
- Mentor structural leads and support the projects by meeting with clients and upper management as required and be able to speak directly to the status of various projects.
- Shape project execution, influence design strategy, and strengthen delivery excellence.
- Expand technical authority, mentor emerging talent, and grow leadership presence to help define the next generation of high-performance data center infrastructure.
- Guide the delivery of our Design-Build delivery methodology.
- Provide quality reviews of complex projects.
- Lead complex structural analyses and guide the selection of appropriate methodologies to ensure robust, code compliant, and constructible design solutions.
- Develop and validate advanced structural computer models, establish modeling standards, and mentor team members in best practice simulation techniques.
- Oversee critical calculations for member design and foundations, direct material take offs and estimating inputs, and provide technical governance for schedules, design documentation, and interdisciplinary coordination.
That seems comprehensive.
Now Requirements: list of needed abilities and qualifications.
From "Here's what you'll need" list:
- Ability to quickly identify complex challenges, solve problems, communicate solutions and direct junior and senior staff on best practices
- Understand the complexities of large contracts and different contract structures and be able to manage change orders, and be able to stand up for the engineering team against the liabilities of contractors
- Experience with almost every building material and type, and have the ability to speak to the executive level about any subject without advance notice
- Bachelor of Science in Civil or Structural Engineering
- 15+ or more years of professional experience in structural engineering
- Registered Professional Engineer with the ability to become registered in additional states
- Knowledge of CAD software, such as AutoCad, Revit, MicroStation and S3D
- Proficiency with structural analysis software such as RISA, RamSS or STAAD
- Knowledge and application of ACI, AISC, ASCE 7, AIST Technical Report 13, and other industry relevant design code and standards
- Knowledge and application of Building Codes
- Proficiency with MS Office suite software including MS Teams for remote coordination
- Ability for travel to various client’s sites (approx. 10% to 40% travel)
- Proficiency reviewing and commenting on drawings in Bluebeam
Then "Ideally, you’ll also have":
- Master of Science in Engineering
- Registered SE License
- Experience with hyperscale facility design with key global clients
- Ability to lead teams to deliver commitments on schedule and on budget while meeting quality and client expectations
These could be "Preferred qualifications". We could include them under Requirements as well, maybe separate section "Preferred qualifications". But instruction says only include sections when posting has real specific content. It does have that content, so we could add a section "Preferred qualifications". However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use "Qualifications" for the required qualifications, and "Skills" for technical skills, and "Preferred qualifications" not in list. But we could incorporate into Requirements or Qualifications.
Better to follow: Use "Requirements" for mandatory requirements, and "Preferred qualifications" maybe not allowed. Could put them under "Qualifications". The list includes "Qualifications" as a possible heading. So we can have a section "Qualifications" for the required qualifications (Bachelor, 15+ years, PE, etc.) and maybe "Skills" for technical skills (CAD, analysis software, codes, MS Office, Bluebeam, travel). And "Preferred qualifications" could be included under "Qualifications" as well, but we could add a separate "Preferred qualifications" not in allowed list; better to avoid.
Thus we can have sections: About the role, Responsibilities, Requirements (maybe combine mandatory and preferred), Benefits, Pay.
But we need to avoid thin sections. Let's decide:
- About the role: overview paragraph (Your impact).
- Responsibilities: list of duties (the combined list).
- Requirements: list of mandatory requirements (the "Here's what you'll need" list).
- Benefits: list of benefits.
- Pay: salary range.
We could also include a "Skills" section for technical skills (CAD, analysis software, codes, MS Office, Bluebeam). But those are already in Requirements list; we could keep them there.
Thus we will output:
About the role
... (the overview paragraph)
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
The base salary range for this position is $169,500.00 to $233,000.00. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training.
We must not include fluff like "commensurate with experience". Not present. Now we need to ensure we preserve all substantive information. Let's capture overview paragraph exactly as in text, but we may need to trim to avoid duplication. The overview includes multiple sentences. We'll copy the block from "At Jacobs, we're challenging today..." to "...Design-Build delivery methodology." Let's extract that block. Original text: "At Jacobs, we're challenging today to reinvent tomorrow by solving the world's most critical problems for thriving cities, resilient environments, mission-critical outcomes, operational advancement, scientific discovery and cutting-edge manufacturing, turning abstract ideas into realities that transform the world for good. Your impact This job opportunity is available at ANY location in the United States. Ideally, selected candidates will be near a JACOBS U.S. based office, but we intend to hire the "best" candidates. At Jacobs, we never settle — we push boundaries, elevate standards, and deliver with purpose. As a senior subject matter expert within our Data Center team, you’ll lead structural engineering efforts across a portfolio of data center projects, including new builds and retrofits. As part of the vision of the Department Manager, you’ll drive the technical direction, and ensure structural solutions meet the highest standards of performance, and constructability. This role is heavily client‑ and contractor‑facing, blending technical authority with the ability to communicate and collaborate across diverse teams. The ideal candidate thrives at the intersection of deep mission‑critical engineering expertise and relationship‑driven leadership—confidently navigating design, construction, and stakeholder challenges while delivering solutions that inspire trust and keep our clients at the center. You’ll serve as a key technical leader, guiding a portfolio of projects and coordinating closely with the structural engineering teams. You will mentor structural leads and support the projects by meeting with clients and upper management
- for any list of duties/requirements/benefits. So we should turn duties into list. The paragraphs describing duties could be turned into list items. But we also have a separate explicit list after "Other key contributions include". That list is clearly duties. We'll combine all duty statements into a list.
Let's extract duty statements:
- Lead structural engineering efforts across a portfolio of data center projects, including new builds and retrofits.
- Drive the technical direction (as part of the vision of the Department Manager) and ensure structural solutions meet the highest standards of performance and constructability.
- Role is heavily client‑ and contractor‑facing, blending technical authority with the ability to communicate and collaborate across diverse teams.
- Serve as a key technical leader, guiding a portfolio of projects and coordinating closely with the structural engineering teams.
- Mentor structural leads and support the projects by meeting with clients and upper management as required and be able to speak directly to the status of various projects.
- Shape project execution, influence design strategy, and strengthen delivery excellence.
- Expand technical authority, mentor emerging talent, and grow leadership presence to help define the next generation of high-performance data center infrastructure.
- Guide the delivery of our Design-Build delivery methodology.
- Provide quality reviews of complex projects.
- Lead complex structural analyses and guide the selection of appropriate methodologies to ensure robust, code compliant, and constructible design solutions.
- Develop and validate advanced structural computer models, establish modeling standards, and mentor team members in best practice simulation techniques.
- Oversee critical calculations for member design and foundations, direct material take offs and estimating inputs, and provide technical governance for schedules, design documentation, and interdisciplinary coordination.
That seems comprehensive.
Now Requirements: list of needed abilities and qualifications.
From "Here's what you'll need" list:
- Ability to quickly identify complex challenges, solve problems, communicate solutions and direct junior and senior staff on best practices
- Understand the complexities of large contracts and different contract structures and be able to manage change orders, and be able to stand up for the engineering team against the liabilities of contractors
- Experience with almost every building material and type, and have the ability to speak to the executive level about any subject without advance notice
- Bachelor of Science in Civil or Structural Engineering
- 15+ or more years of professional experience in structural engineering
- Registered Professional Engineer with the ability to become registered in additional states
- Knowledge of CAD software, such as AutoCad, Revit, MicroStation and S3D
- Proficiency with structural analysis software such as RISA, RamSS or STAAD
- Knowledge and application of ACI, AISC, ASCE 7, AIST Technical Report 13, and other industry relevant design code and standards
- Knowledge and application of Building Codes
- Proficiency with MS Office suite software including MS Teams for remote coordination
- Ability for travel to various client’s sites (approx. 10% to 40% travel)
- Proficiency reviewing and commenting on drawings in Bluebeam
Then "Ideally, you’ll also have":
- Master of Science in Engineering
- Registered SE License
- Experience with hyperscale facility design with key global clients
- Ability to lead teams to deliver commitments on schedule and on budget while meeting quality and client expectations
These could be "Preferred qualifications". We could include them under Requirements as well, maybe separate section "Preferred qualifications". But instruction says only include sections when posting has real specific content. It does have that content, so we could add a section "Preferred qualifications". However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use "Qualifications" for the required qualifications, and "Skills" for technical skills, and "Preferred qualifications" not in list. But we could incorporate into Requirements or Qualifications.
Better to follow: Use "Requirements" for mandatory requirements, and "Preferred qualifications" maybe not allowed. Could put them under "Qualifications". The list includes "Qualifications" as a possible heading. So we can have a section "Qualifications" for the required qualifications (Bachelor, 15+ years, PE, etc.) and maybe "Skills" for technical skills (CAD, analysis software, codes, MS Office, Bluebeam, travel). And "Preferred qualifications" could be included under "Qualifications" as well, but we could add a separate "Preferred qualifications" not in allowed list; better to avoid.
Thus we can have sections: About the role, Responsibilities, Requirements (maybe combine mandatory and preferred), Benefits, Pay.
But we need to avoid thin sections. Let's decide:
- About the role: overview paragraph (Your impact).
- Responsibilities: list of duties (the combined list).
- Requirements: list of mandatory requirements (the "Here's what you'll need" list).
- Benefits: list of benefits.
- Pay: salary range.
We could also include a "Skills" section for technical skills (CAD, analysis software, codes, MS Office, Bluebeam). But those are already in Requirements list; we could keep them there.
Thus we will output: