Staff Structural Engineer

Arcadis · New York, NY · 1 mo ago

HybridOTHR$85k–$125k/yrFull-time

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, etc. Must preserve all substantive info. Let's parse the posting. Content: - Intro about Arcadis (company description) maybe part of About the role? The role description: "Arcadis is seeking an experienced Structural Engineer with 6 or more years of project experience to join our growing team. If you’re motivated by tackling complex structural challenges, working with a wide range of materials, leading technical efforts, and collaborating within multidisciplinary teams, this role is an excellent fit. You’ll also have clear opportunities to grow into senior technical or project leadership roles as your career progresses. In this position, you will lead key project components, mentor junior engineers, and contribute to innovative, high‑quality design solutions for projects across sectors such as manufacturing, automotive, aerospace, technology, utilities, and rail. Our team welcomes either a licensed Professional Engineer (PE) or an experienced EIT preparing to sit for the PE exam within the next six months. Some travel may be required for project work and client visits within the United States. Apply, and come join Arcadis!" - Role accountabilities: bullet list (but not bullet in text). We'll need to convert to

. - Required Qualifications & Experience: list. - Why Arcadis? (maybe About the role? Could be Benefits? Actually it's about company culture; could be part of About the role or separate section like "About Arcadis". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Arcadis?" could be considered About the role or maybe Benefits? It's more about company culture; but we can put under About the role. - Our Commitment to Equality, Diversity, Inclusion & Belonging: boilerplate EEO, should be removed. - Arcadis offers benefits...: that's Benefits section. - Salary range: Pay section. - No schedule info given (like work schedule). So we should not create Schedule section. - No explicit Skills section separate from qualifications; but we have technical software skills etc. Could be Skills. We need to avoid filler like "commensurate with experience". Not present. We must not invent or summarize away detail. Must preserve all substantive info. Thus we need sections: - About the role: include company intro? Actually "About the role" maybe includes role description and why Arcadis? We'll include role description paragraph(s) and maybe the "Why Arcadis?" paragraph. - Responsibilities: from Role accountabilities bullet list. - Requirements: maybe from Required Qualifications & Experience? But we also have Qualifications heading separate. The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need both Requirements and Qualifications sections. Likely Requirements = mandatory experience/education; Qualifications = maybe preferred? But we have only one list. We could split: Requirements = 6+ years experience, PE or Senior EIT, Bachelor's degree. Qualifications = problem-solving skills, knowledge of codes, software skills, communication skills. Or we could treat Required Qualifications & Experience as Qualifications, and maybe Requirements could be something else? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we need to decide what content goes under Requirements vs Qualifications. The posting has "Required Qualifications & Experience:" then list items: 6+ years experience, PE or Senior EIT, Bachelor's degree, Strong problem-solving skills..., Excellent working knowledge of codes..., Strong technical software skills..., Effective communication skills. Thus we could put all under Qualifications (since it's titled Required Qualifications & Experience). But we also need a Requirements section; maybe we can put the experience/education under Requirements, and the skills/knowledge under Qualifications. That seems reasonable. Thus: - Requirements: 6 or more years of relevant structural engineering project experience; Professional Engineer (PE) License or Senior EIT candidate looking to write their PE exam in the next 6 months; Bachelor’s degree in Structural or Civil Engineering. - Qualifications: Strong problem-solving skills with critical thinking and initiative; Excellent working knowledge of all USA National codes and standards, such as IBC, ACI, AISC, etc.; Strong technical software skills related to: RISA, ETABS, BIM tools, Revit, AutoCAD; Effective communication skills - oral and written. - Skills: maybe we could also have a Skills section for technical software skills? But we already placed them under Qualifications. Could also separate: Skills = technical software skills (RISA, ETABS, BIM tools, Revit, AutoCAD) and maybe communication skills. But we already used communication under Qualifications. To avoid duplication, we need to decide. Better: Use Skills for technical software skills and maybe communication; Qualifications for problem-solving, knowledge of codes, etc. But the posting lumps them together. However we can split as we see fit as long as we preserve all info and not invent. We must not create thin sections; prefer few substantive sections over many thin ones. So maybe better to have only Qualifications (includes all) and not Skills. But we need to follow allowed headings; we can omit Skills if no specific content. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills if we can fit its content elsewhere. Thus we could have: - About the role - Responsibilities - Requirements - Qualifications - Benefits - Pay No Skills, Schedule. Now we need to extract content for each. About the role: Should include the role description paragraph(s) and maybe the "Why Arcadis?" paragraph. Also maybe the introductory company description? The posting starts with "STAFF STRUCTURAL ENGINEER (PE OR SENIOR EIT) LOCATION - USA - HYBRID ROLE Arcadis is the world's leading company delivering sustainable design, engineering, and consultancy solutions for natural and built assets. We are more than 34,000 people, in over 30 countries, dedicated to improving quality of life. Everyone has an important role to play. With the power of many curious minds, together we can solve the world’s most complex challenges and deliver more impact together." That's company overview; could be part of About the role. It's substantive. We'll include it. Thus About the role will contain: - Company overview paragraph. - Role description paragraph(s) (starting "Arcadis is seeking an experienced Structural Engineer..."). - Why Arcadis? paragraph(s) (starting "We can only achieve our goals when everyone is empowered to be their best..."). We must not include boilerplate like EEO etc. Now Responsibilities: from Role accountabilities bullet list. We'll convert each sentence to
. List items: - Work with the Engineer of Record (EOR) to establish codes, loads, analysis methods, and tools; seismic analysis experience is a plus. - Perform technical work with an increased level of complexity with senior review - Work directly with a variety of engineering disciplines, office/project staff, client, and subcontractors, throughout the project life cycle, and have clear and concise, oral and written communication skills - Develop calculations, plans, specifications, and other contract documents. - Exercise judgment on details of work and in making preliminary selections and adaptations of engineering alternatives. - Perform Construction Administration duties, including completing field observation reports, responding to RFIs, submittal reviews. - Traveling, as needed, for project-related activities such as client meetings and site visits. Note: Some sentences have line breaks; we keep as is. Now Requirements: as defined. - 6 or more years of relevant structural engineering project experience - Professional Engineer (PE) License or Senior EIT candidate looking to write their PE exam in the next 6 months - Bachelor’s degree in Structural or Civil Engineering Now Qualifications: (the rest) - Strong problem-solving skills with critical thinking and initiative - Excellent working knowledge of all USA National codes and standards, such as IBC, ACI, AISC, etc. - Strong technical software skills related to: RISA, ETABS, BIM tools, Revit, AutoCAD - Effective communication skills - oral and written Now Benefits: from "Arcadis offers benefits for full time and part time positions..." paragraph. We need to preserve all substantive info: list of benefits: medical, dental, and vision, EAP, 401K, STD, LTD, AD&D, life insurance, paid parental leave, reward & recognition program and optional benefits including wellbeing benefits, adoption assistance and tuition reimbursement. Also nine paid holidays and 15 days PTO that accrue per year. We should not include boilerplate like "We are an equal opportunity employer." Already removed. Thus Benefits section will contain a paragraph describing benefits and maybe a ul list? The instruction: Use
- for any list of duties/requirements/benefits. So we should list benefits as
  - . Could also include the PTO and holidays as list items. Thus Benefits:
    - medical, dental, and vision
    - EAP
    - 401K
    - STD
    - LTD
    - AD&D
    - life insurance
    - paid parental leave
    - reward & recognition program
    - optional benefits including wellbeing benefits, adoption assistance, and tuition reimbursement
    - nine paid holidays
    - 15 days PTO that accrue per year
    But we need to preserve the phrase "Arcadis offers benefits for full time and part time positions." Could be a
    before list. Now Pay: from "The salary range for this position is $85,000-$125,000. Actual salaries will vary and are based on several factors, such as experience, education, budget, internal equity, project and location." We should keep that as a
    . Not include filler like "varies". It's actual statement; it's okay. Now we must not include Schedule section because no info. Now ensure we don't repeat job title as heading. Not include Job ID. Now output only HTML fragment, no /, no markdown. Thus final HTML:
    About the role
    
    ...company overview...
    
    ...role description...
    
    ...Why Arcadis?...
    Then
    Responsibilities

Staff Structural Engineer

About the role

Responsibilities

Requirements

Qualifications

Benefits

Pay

Similar jobs