Simulation Engineer: FEA & Multi body simulation
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting: It includes About Us, Who We're Looking For, This Role, What We Offer, plus some EEO boilerplate at end (which we need to remove). Also there is mention of location: based in NYC, working 2-3 days per week in our central office. Traveling domestically and globally up to 2–3 weeks per quarter. That's schedule info? It's about travel and hybrid schedule. Could be considered Schedule? The instruction says only create Schedule section if posting actually states them. It does mention "working 2-3 days per week in our central office" and traveling up to 2-3 weeks per quarter. That's schedule info. So we could include a Schedule section with that detail.
Pay: Not mentioned. So no Pay section.
Benefits: The "What We Offer" section lists many benefits: equity options, pension contribution, free office lunches, enhanced parental leave, YellowNest nursery scheme, 25 days annual leave (+ public holidays), private medical insurance, Wellhub Subscription, eye tests, personal development, Employee Assistance Programme, Bike2Work scheme, Season ticket loan, Octopus EV salary sacrifice. Also mention "Build what actually matters", "Learn alongside exceptional people", "Influence over hierarchy", "Sustainable pace, long-term ambition". Those are more cultural aspects but could be considered Benefits? The instruction: Use
- for any list of duties/requirements/benefits. So we should list the tangible benefits as
- . The cultural statements could be prose
. We'll need to decide.
Also "About Us" section: description of company. Could be "About the role"? Actually "About Us" is company overview. Could be placed under a section like "About the company" but headings limited to given list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". But we could put company overview under "About the role"? Not exactly. Perhaps we treat "About Us" as part of the role description (maybe under a
without heading). The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should use those headings when appropriate. If we don't have content for a heading, we shouldn't create it. So we need to decide which sections we have substantive content for.
We have:
- Responsibilities: The "This Role" bullet list of duties: owning technical delivery, partner with customers, working at intersection, leveraging data sampling, accelerate high-fidelity modelling, document work, traveling. That's responsibilities.
- Requirements/Qualifications/Skills: The "Who We're Looking For" includes expertise across FEA and MBS, hands-on expertise, proficiency in solvers, Python, parametric CAD, exposure to open source, 2+ years experience, owning workflow end to end. Those could be requirements/qualifications/skills. We need to decide how to split. Could combine into Requirements (or Qualifications) and Skills. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section? But we have headings for Requirements, Qualifications, Skills. We could choose one heading that best fits: maybe "Requirements" for the experience and expertise, and "Skills" for technical proficiencies. However we need to avoid thin sections. Could combine into "Requirements" covering both experience and skills. Or we could have "Qualifications" for education/experience and "Skills" for technical proficiencies. Let's see content: "Who We're Looking For" includes: expertise across FEA and MBS, grasp and apply advanced engineering concepts, excel at working directly with customers, hands-on expertise in structural dynamics and vibration, highly proficient in at least one FEA solver and at least one MBS solver, working knowledge of pre/post tool chain, proficiency in Python for pipeline scripting, proficiency in parametric CAD modelling (NX or CATIA) as well as exposure to open source tools (Calculix, OpenRadioss) is an advantage. With 2+ years of industry experience (post Masters or PhD) delivering FEA, MBS, or structural dynamics analysis in a commercial engineering environment, you're comfortable owning a workflow end to end: model build, solver setup, run management, and results interpretation, and making engineering judgment calls independently.
Thus we can treat "Requirements" as the experience and education (2+ years, post Masters/PhD). "Skills" as the technical proficiencies (FEA/MBS solvers, Python, CAD, etc.). Could also include "Qualifications" similar to Requirements. But to avoid thin sections, maybe we just have one "Requirements" section that includes both experience and skills. However the instruction says use headings like Requirements, Qualifications, Skills. It doesn't forbid using only one of them. So we could use "Requirements" for the experience and "Skills" for the technical proficiencies. That's two sections, each substantive.
Alternatively we could use "Qualifications" for education/experience and "Skills" for technical proficiencies. Let's decide: We'll have:
- About the role
maybe not needed; we could start with a
containing the company overview (About Us). But we need a heading for that? Not required; we can just have a
without heading. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must have a heading for company overview. So we can start with a
containing the About Us paragraph.
Then we have Responsibilities (
Responsibilities
) with - list.
Then Requirements (
Requirements
) with - list (maybe includes experience and education).
Then Skills (
Skills
) with - list (technical proficiencies).
Then Benefits (
Benefits
) with - list of benefits.
Then Schedule (
Schedule
) with containing hybrid work and travel details.
We must not include Pay section.
We must remove EEO boilerplate at end.
We must preserve all substantive information: ensure we don't lose any details.
Let's extract details.
About Us paragraph: "Re-architecting Engineering for the Age of Intelligence PhysicsX is the physics AI company for industrials. The company’s mission is to accelerate hardware innovation by overhauling what industrial engineering and manufacturing look like today. PhysicsX is building a new simulation software stack to deliver deep physics AI enablement across the entire engineering lifecycle. The company partners with leading organisations in aerospace & defence, automotive, semiconductors, materials, and energy & renewables, supporting them on some of their most critical and complex challenges. PhysicsX is headquartered in the United Kingdom, with offices in London, New York, and Singapore and an expanding presence in the Bay Area."
We'll put that as a
.
Responsibilities: from "This Role In this role, you’ll work closely with our Data Scientists, Machine Learning Engineers, and customers to understand and define the engineering challenges we are solving. You'll play a crucial role in delivering these workflows by:" then bullet list:
- Owning the technical delivery of building complex structural and multi-physics models from geometry clean-up and meshing, to simulating and post-processing complex real-world phenomena, integrating experimental data for model validation.
- Partner with customers to address their most complex engineering challenges through advanced FEA & AI solutions; communicate results clearly
- Working at the intersection of CAE and Data Science to generate high-quality simulation datasets for training Machine/Deep Learning models.
- Leveraging data sampling techniques to efficiently capture the design space, reduce computational cost, and enhance model accuracy.
- Accelerate high-fidelity modelling by using Flux (our cloud platform) and on-premise HPC resources, going beyond smart meshing and model setup to achieve real performance gains.
- Document your work through clear technical reports and process notes, contributing to the team's shared knowledge base.
- Traveling domestically and globally (North America, Europe, Asia, Oceania) up to 2–3 weeks per quarter to work side-by-side with customers in building solutions on-site.
Note: The last bullet about travel could also go to Schedule, but it's also a responsibility. We'll keep it under Responsibilities as it's a duty. However we also have schedule info about hybrid work (2-3 days per week in NYC office). That's separate.
We'll keep travel bullet under Responsibilities.
Now Requirements: from "Who We're Looking For" we need to capture experience/education: "With 2+ years of industry experience (post Masters or PhD) delivering FEA, MBS, or structural dynamics analysis in a commercial engineering environment, you're comfortable owning a workflow end to end: model build, solver setup, run management, and results interpretation, and making engineering judgment calls independently."
Also earlier: "You are someone who can grasp and apply advanced engineering concepts across multiple industries, and you excel at working directly with customers (often directly on-site) to build CAE models that are integrated into AI-tools that are both useful and used." That's more skill/experience but could be part of Requirements.
We'll put Requirements as: 2+ years industry experience (post Masters or PhD) delivering FEA, MBS, or structural dynamics analysis in a commercial engineering environment; able to grasp and apply advanced engineering concepts across multiple industries; excel at working directly with customers (often on-site) to build CAE models integrated into AI-tools; comfortable owning workflow end to end (model build, solver setup, run management, results interpretation) and making independent engineering judgment calls.
We'll list as
- .
Now Skills: technical proficiencies: "Highly proficient in at least one FEA solver (Nastran, Abaqus, or ANSYS) and at least one MBS solver (e.g., Adams, SIMPACK, Virtual Dynamics, or Excite M), with working knowledge of the surrounding pre/post tool chain (SimLab, HyperMesh, OptiStruct, Hypergraph or equivalents). Proficiency in Python for pipeline scripting and automation is expected. Proficiency in parametric CAD modelling (NX or CATIA) as well as exposure to open source tools (Calculix, OpenRadioss) is an advantage."
Also maybe "hands-on expertise in structural dynamics and vibration with a solid ability to apply fundamental knowledge to real-world phenomena across a wide range of engineering applications." That's also skill.
We'll list those.
Now Benefits: from "What We Offer" we need to list each benefit as
- . Also include the cultural statements as prose maybe before list.
The "What We Offer" section includes
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting: It includes About Us, Who We're Looking For, This Role, What We Offer, plus some EEO boilerplate at end (which we need to remove). Also there is mention of location: based in NYC, working 2-3 days per week in our central office. Traveling domestically and globally up to 2–3 weeks per quarter. That's schedule info? It's about travel and hybrid schedule. Could be considered Schedule? The instruction says only create Schedule section if posting actually states them. It does mention "working 2-3 days per week in our central office" and traveling up to 2-3 weeks per quarter. That's schedule info. So we could include a Schedule section with that detail. Pay: Not mentioned. So no Pay section. Benefits: The "What We Offer" section lists many benefits: equity options, pension contribution, free office lunches, enhanced parental leave, YellowNest nursery scheme, 25 days annual leave (+ public holidays), private medical insurance, Wellhub Subscription, eye tests, personal development, Employee Assistance Programme, Bike2Work scheme, Season ticket loan, Octopus EV salary sacrifice. Also mention "Build what actually matters", "Learn alongside exceptional people", "Influence over hierarchy", "Sustainable pace, long-term ambition". Those are more cultural aspects but could be considered Benefits? The instruction: Use
- for any list of duties/requirements/benefits. So we should list the tangible benefits as
- . The cultural statements could be prose
. We'll need to decide. Also "About Us" section: description of company. Could be "About the role"? Actually "About Us" is company overview. Could be placed under a section like "About the company" but headings limited to given list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". But we could put company overview under "About the role"? Not exactly. Perhaps we treat "About Us" as part of the role description (maybe under a
without heading). The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should use those headings when appropriate. If we don't have content for a heading, we shouldn't create it. So we need to decide which sections we have substantive content for. We have: - Responsibilities: The "This Role" bullet list of duties: owning technical delivery, partner with customers, working at intersection, leveraging data sampling, accelerate high-fidelity modelling, document work, traveling. That's responsibilities. - Requirements/Qualifications/Skills: The "Who We're Looking For" includes expertise across FEA and MBS, hands-on expertise, proficiency in solvers, Python, parametric CAD, exposure to open source, 2+ years experience, owning workflow end to end. Those could be requirements/qualifications/skills. We need to decide how to split. Could combine into Requirements (or Qualifications) and Skills. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section? But we have headings for Requirements, Qualifications, Skills. We could choose one heading that best fits: maybe "Requirements" for the experience and expertise, and "Skills" for technical proficiencies. However we need to avoid thin sections. Could combine into "Requirements" covering both experience and skills. Or we could have "Qualifications" for education/experience and "Skills" for technical proficiencies. Let's see content: "Who We're Looking For" includes: expertise across FEA and MBS, grasp and apply advanced engineering concepts, excel at working directly with customers, hands-on expertise in structural dynamics and vibration, highly proficient in at least one FEA solver and at least one MBS solver, working knowledge of pre/post tool chain, proficiency in Python for pipeline scripting, proficiency in parametric CAD modelling (NX or CATIA) as well as exposure to open source tools (Calculix, OpenRadioss) is an advantage. With 2+ years of industry experience (post Masters or PhD) delivering FEA, MBS, or structural dynamics analysis in a commercial engineering environment, you're comfortable owning a workflow end to end: model build, solver setup, run management, and results interpretation, and making engineering judgment calls independently. Thus we can treat "Requirements" as the experience and education (2+ years, post Masters/PhD). "Skills" as the technical proficiencies (FEA/MBS solvers, Python, CAD, etc.). Could also include "Qualifications" similar to Requirements. But to avoid thin sections, maybe we just have one "Requirements" section that includes both experience and skills. However the instruction says use headings like Requirements, Qualifications, Skills. It doesn't forbid using only one of them. So we could use "Requirements" for the experience and "Skills" for the technical proficiencies. That's two sections, each substantive. Alternatively we could use "Qualifications" for education/experience and "Skills" for technical proficiencies. Let's decide: We'll have: -
About the role
maybe not needed; we could start with acontaining the company overview (About Us). But we need a heading for that? Not required; we can just have a
without heading. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must have a heading for company overview. So we can start with a
containing the About Us paragraph. Then we have Responsibilities (
Responsibilities
) with- list.
Then Requirements (
Requirements
) with- list (maybe includes experience and education).
Then Skills (
Skills
) with- list (technical proficiencies).
Then Benefits (
Benefits
) with- list of benefits.
Then Schedule (
Schedule
) withcontaining hybrid work and travel details. We must not include Pay section. We must remove EEO boilerplate at end. We must preserve all substantive information: ensure we don't lose any details. Let's extract details. About Us paragraph: "Re-architecting Engineering for the Age of Intelligence PhysicsX is the physics AI company for industrials. The company’s mission is to accelerate hardware innovation by overhauling what industrial engineering and manufacturing look like today. PhysicsX is building a new simulation software stack to deliver deep physics AI enablement across the entire engineering lifecycle. The company partners with leading organisations in aerospace & defence, automotive, semiconductors, materials, and energy & renewables, supporting them on some of their most critical and complex challenges. PhysicsX is headquartered in the United Kingdom, with offices in London, New York, and Singapore and an expanding presence in the Bay Area." We'll put that as a
. Responsibilities: from "This Role In this role, you’ll work closely with our Data Scientists, Machine Learning Engineers, and customers to understand and define the engineering challenges we are solving. You'll play a crucial role in delivering these workflows by:" then bullet list: - Owning the technical delivery of building complex structural and multi-physics models from geometry clean-up and meshing, to simulating and post-processing complex real-world phenomena, integrating experimental data for model validation. - Partner with customers to address their most complex engineering challenges through advanced FEA & AI solutions; communicate results clearly - Working at the intersection of CAE and Data Science to generate high-quality simulation datasets for training Machine/Deep Learning models. - Leveraging data sampling techniques to efficiently capture the design space, reduce computational cost, and enhance model accuracy. - Accelerate high-fidelity modelling by using Flux (our cloud platform) and on-premise HPC resources, going beyond smart meshing and model setup to achieve real performance gains. - Document your work through clear technical reports and process notes, contributing to the team's shared knowledge base. - Traveling domestically and globally (North America, Europe, Asia, Oceania) up to 2–3 weeks per quarter to work side-by-side with customers in building solutions on-site. Note: The last bullet about travel could also go to Schedule, but it's also a responsibility. We'll keep it under Responsibilities as it's a duty. However we also have schedule info about hybrid work (2-3 days per week in NYC office). That's separate. We'll keep travel bullet under Responsibilities. Now Requirements: from "Who We're Looking For" we need to capture experience/education: "With 2+ years of industry experience (post Masters or PhD) delivering FEA, MBS, or structural dynamics analysis in a commercial engineering environment, you're comfortable owning a workflow end to end: model build, solver setup, run management, and results interpretation, and making engineering judgment calls independently." Also earlier: "You are someone who can grasp and apply advanced engineering concepts across multiple industries, and you excel at working directly with customers (often directly on-site) to build CAE models that are integrated into AI-tools that are both useful and used." That's more skill/experience but could be part of Requirements. We'll put Requirements as: 2+ years industry experience (post Masters or PhD) delivering FEA, MBS, or structural dynamics analysis in a commercial engineering environment; able to grasp and apply advanced engineering concepts across multiple industries; excel at working directly with customers (often on-site) to build CAE models integrated into AI-tools; comfortable owning workflow end to end (model build, solver setup, run management, results interpretation) and making independent engineering judgment calls. We'll list as
- . Now Skills: technical proficiencies: "Highly proficient in at least one FEA solver (Nastran, Abaqus, or ANSYS) and at least one MBS solver (e.g., Adams, SIMPACK, Virtual Dynamics, or Excite M), with working knowledge of the surrounding pre/post tool chain (SimLab, HyperMesh, OptiStruct, Hypergraph or equivalents). Proficiency in Python for pipeline scripting and automation is expected. Proficiency in parametric CAD modelling (NX or CATIA) as well as exposure to open source tools (Calculix, OpenRadioss) is an advantage." Also maybe "hands-on expertise in structural dynamics and vibration with a solid ability to apply fundamental knowledge to real-world phenomena across a wide range of engineering applications." That's also skill. We'll list those. Now Benefits: from "What We Offer" we need to list each benefit as
- . Also include the cultural statements as prose maybe before list. The "What We Offer" section includes
- list of benefits.
Then Schedule (
- list (technical proficiencies).
Then Benefits (
- list (maybe includes experience and education).
Then Skills (
- list.
Then Requirements (
- . The cultural statements could be prose