Senior Structural Engineer (Buildings)
WSP in the U.S. · Dallas, TX · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job description.
First, there is a heading "Job Description This Opportunity". The actual content: "WSP is currently initiating a search for a Senior Structural Engineer for our Dallas, TX office. Be involved in projects with our Property and Buildings Team and be a part of a growing organization that meets our clients' objectives and solves their challenges. Provides technical assistance and guidance for multi-site/phase due diligence, investigation, remediation, improvement, and/or construction of building and infrastructure projects in the public and private sector. Tasks may include assisting with the research, design, concept development, planning, and construction of load-bearing structures. Substantiates reports and documentation regarding material, installations, and construction specifications. Ensures that responsibilities are delivered and adhered to with a level of quality that meets or exceeds acceptable industry standards for design, safety, structural soundness, and functionality."
Then "Your Impact" with many bullet-like sentences.
Then "Who You Are" with Required Qualifications list.
Then "Preferred Qualifications".
Then "About WSP" with description.
Then benefits: "WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings focused on providing health and financial stability throughout the employee’s career."
Also "At WSP, we want to give our employees the challenges they seek to grow their careers and knowledge base."
No explicit Pay or Schedule info. So we should not create Pay or Schedule sections.
We need sections: About the role (maybe from first paragraph?), Responsibilities (Your Impact), Requirements (maybe Required Qualifications?), Qualifications (maybe Preferred Qualifications?), Skills (maybe list of skills from requirements?), Benefits (benefits paragraph). Also maybe "About WSP" could be part of About the role? But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide content for each.
- About the role: could be the introductory paragraph describing the role and team.
- Responsibilities: the "Your Impact" section (list of duties). We'll convert each sentence into items.
- Requirements: maybe the "Required Qualifications" list.
- Qualifications: maybe the "Preferred Qualifications" list.
- Skills: could extract skill items from Required Qualifications (like proficiency with software, technical writing, etc.) but we might combine with Requirements? However we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one? But headings are separate; we should only include if there is real specific content. We have both Required and Preferred qualifications, so we can have Requirements (required) and Qualifications (preferred). Skills maybe we can extract from the required qualifications list (like proficiency with technical writing, office automation, discipline-specific design software, etc.) but that may be redundant. Perhaps we can skip Skills if not distinct.
But we need to include Skills only if there is real specific content. The posting does mention skills like "Proficiency with technical writing, office automation, discipline-specific design software (i.e., RAM Concept, ETABS, etc.), technology, math principles, physics, predictive models, spreadsheets, and tools." Also "Effective interpersonal and communication skills", "Highly capable self-leadership", etc. Those could be considered skills. However they are already in Required Qualifications. To avoid duplication, maybe we treat Required Qualifications as Requirements, and Preferred Qualifications as Qualifications, and we can omit Skills section (or combine some skill bullets into Skills). But the instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section called "Requirements" and include both required and preferred? But headings are fixed; we could still have both but if they are thin maybe we combine. However we have substantial content for both required and preferred, so we can keep both.
Skills: we could extract distinct skill statements not already captured. But many are overlapping. Could create a Skills section listing technical and soft skills: "Proficiency with technical writing, office automation, discipline-specific design software (RAM Concept, ETABS, etc.), technology, math principles, physics, predictive models, spreadsheets, and tools; Effective interpersonal and communication skills; Highly capable self-leadership with attention to detail, multi-tasking, and prioritization; Ability to work independently and provide guidance and leadership to junior team members; Ability to assertively direct others in the field; Ability to make technical computations and calculations; Ability to plan and conduct inspections and investigations; Project management experience with small to mid-level projects; Ability to work schedules conducive to project-specific requirements; Occasional travel may be required." But many of these are already in required qualifications. Might be okay to have Skills section summarizing.
But we must not invent or summarize away detail; we must preserve ALL substantive information. So we cannot omit any detail. If we put details in Skills section, we must ensure we still have them somewhere else (maybe in Requirements). If we duplicate, that's okay as long as we preserve all info. Duplication is not prohibited. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we can duplicate but must not lose any detail.
Thus we can create sections:
- About the role: intro paragraph.
- Responsibilities: list of duties from "Your Impact".
- Requirements: list of required qualifications (the bullet list after "Who You Are Required Qualifications").
- Qualifications: list of preferred qualifications (the bullet list after "Preferred Qualifications").
- Skills: maybe we can list skill-related items from the required qualifications that are skill-based (like proficiency with software, technical writing, etc.) but we already have them in Requirements; but we can still include them again? Might be considered duplication but okay. However we might avoid Skills to keep fewer sections. The instruction: "Prefer a few substantive sections over many thin ones." If we add Skills, that's another section; maybe we can omit Skills if we feel the content is already covered in Requirements and Qualifications. But we need to ensure we don't lose any skill-specific info that is not captured elsewhere. The required qualifications list includes many skill-like items: "Proficient knowledge of structural engineering principles, practices, process, design/build, and the application to project work-related issues." "Experience with design, and construction management; including active involvement in a variety of rehabilitation and new design projects." "Working knowledge of relevant structural and civil construction laws, codes, regulations, compliance practices, and record-keeping requirements." "Ability to make technical computations and calculations involving the application of engineering principles, understanding plans and specifications, and making factual comparisons to the appropriate regulations." "Project management experience with small to mid-level projects including tracking hours and expenses for project work." "Ability to plan and conduct inspections and investigations on various aspects of the construction and design of buildings, facilities, or structures, applying applicable regulations and policies." "Effective interpersonal and communication skills when interacting with others, expressing ideas effectively and professionally to an engineering and non-engineering audience." "Highly capable self-leadership with attention to detail, multi-tasking, and prioritization of responsibilities in a dynamic work environment." "Ability to work independently and provide guidance and leadership to junior team or project members, with strict adherence to QA/QC." "Proficiency with technical writing, office automation, discipline-specific design software (i.e., RAM Concept, ETABS, etc.), technology, math principles, physics, predictive models, spreadsheets, and tools." "Developed critical thinking and problem-solving skills required to apply technical knowledge to reach conclusions from testing results, data collation, statistical analysis and arriving at the most effective, economical, and logical solution." "Ability to assertively direct others in the field such as subcontractors and others to consistently complete tasks safely and efficiently." "Proven track record of upholding workplace safety and ability to abide by WSP’s health, safety and drug/alcohol and harassment policies." "Ability to work schedules conducive to project-specific requirements that may extend beyond the typical workweek." "Occasional travel may be required depending on project-specific requirements."
Thus many skill statements are already there. So we could omit Skills section.
Benefits: we have a paragraph about benefits.
Pay: none.
Schedule: none (though there is mention of ability to work schedules conducive to project-specific requirements that may extend beyond typical workweek, occasional travel). That's not a defined schedule; we should not create Schedule section unless posting actually states them. It does not give specific schedule like "Monday-Friday 9-5". So we omit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
Now we need to format.
About the role: use
About the role
thenwith the introductory paragraph(s). The intro includes: "WSP is currently initiating a search for a Senior Structural Engineer for our Dallas, TX office. Be involved in projects with our Property and Buildings Team and be a part of a growing organization that meets our clients' objectives and solves their challenges. Provides technical assistance and guidance for multi-site/phase due diligence, investigation, remediation, improvement, and/or construction of building and infrastructure projects in the public and private sector. Tasks may include assisting with the research, design, concept development, planning, and construction of load-bearing structures. Substantiates reports and documentation regarding material, installations, and construction specifications. Ensures that responsibilities are delivered and adhered to with a level of quality that meets or exceeds acceptable industry standards for design, safety, structural soundness, and functionality." We should keep as one paragraph. Responsibilities:
Responsibilities
then- with each duty as
- . Need to extract each sentence from "Your Impact". Let's list them: - Determine well-defined methods for collecting, compiling, and analyzing data from the physical work site, surveys, blueprints, subsurface utility information, maps, geotechnical data, and other matrices for project development, design, and construction. - Perform professional structural engineering work and conduct research and inspections of proposed and existing site conditions, resources, building and infrastructure to determine conformance with applicable rules, standards, and construction or operating permits. - Develop construction plans and specifications. - Develop or incorporate advanced modeling techniques, concept development, design requirements, and operating strategies to account for the safety and functionality of end-users, transportation vehicles/systems, and incorporate future-ready solutions with structural engineering design standards. - Work as an individual or as part of a cross-functional team of engineers, architects, planners, and scientific professionals to execute project work on multiple concurrent projects, assist with laying out installations, establishing reference points/elevations/grades to guide construction, selecting appropriate materials to ensure durability, calculating costs and quantities of material/equipment/labor, and ensuring project work conforms with specifications, permit applications, compliance documentation, and regulatory and technical analysis memos. - Verify the characteristics of a site, providing technical guidance on securing structural soundness from loads and pressures caused by environmental or human influence. - Prepare data and visualizations such as tables, charts, accurate reports, sketches, calculations, and 2D/3D illustrations for the interpretation or presentation of data, findings, or analyses. - Maintain quality control standards and procedures for accurate and precise measurements, statistical analysis, and reporting. - Assist with development and scoping of medium-sized projects. - Provide guidance and training to entry-level engineers. - Prepare technical reports and presentations that explain research, findings, and recommendations to improve, prevent, control, restore, or address design and/or construction issues or opportunities. - Assist in the analysis, evaluation, and interpretation of data obtained during site investigations, offering input with developing action plans for moderate- to high-level risk mitigation activities. - Prepare and implement site Health and Safety Plans (HASPs). - Comply with regulatory requirements pertaining to the data integrity, documentation, procedures, training, monitoring systems, and record compliance and retention. - Interact with regulatory agencies, subcontractors, and clients in a confident and professional manner. - Remain current in latest structural engineering techniques and practices. - Work collaboratively with other