Physical AI Automation Engineer / Senior Engineer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We have content: description of Accenture (maybe About the role). Then "You Are The Physical AI Automation Engineer is a hands-on practitioner..." That's role description. Could be About the role.
Responsibilities: list under "Key Responsibilities" bullet points.
Requirements: "Here’s What You Need" bullet points.
Qualifications: maybe "Bonus Points If" could be Qualifications or Skills? The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content maps.
We have "Minimum 3 years of experience..." etc. That's Requirements.
"Bonus Points If ..." could be Qualifications or Skills. Could treat as Qualifications (preferred qualifications). Or Skills.
We also have Benefits section: "Benefits Accenture offers a market competitive suite of benefits ..." plus link.
Pay: we have compensation statement: "Compensation at Accenture varies depending on a wide array of factors..." plus salary ranges per location. That's Pay info.
Schedule: not mentioned (no schedule). Travel Requirements: "Travel is required for this role and could vary up to 75%" That's schedule? Not exactly schedule but travel requirement. Could be under Schedule? But schedule heading is for work schedule (e.g., full-time, part-time). Not present. Travel requirement maybe could be included under Requirements? But we should not create Schedule unless posting actually states schedule. It does not state schedule like full-time/part-time, hours. So omit Schedule.
We also have location list: many cities. That's location info, not a heading we have. Could be part of About the role or maybe not needed. We can include location in a paragraph under About the role.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out the EEO statement, accommodation request, equal employment opportunity statement, other employment statements, requesting accommodation, etc. Also remove the "Visit us at accenture.com link? That's part of About the role maybe keep? It's not boilerplate; it's a link to accenture.com. Could keep.
We must preserve all substantive information. So keep the description of Accenture, role description, responsibilities list, requirements list, bonus points, benefits, compensation/pay, travel requirement maybe under Requirements or a separate section? Travel is not schedule but could be under Requirements as a note. We'll include travel requirement in Requirements section as a bullet.
We must not repeat job title as heading. The job title is "Physical AI Automation Engineer". Not to be used as heading.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment, no /, no markdown fences.
Let's craft sections:
About the role
We Are Accenture helps the world’s leading enterprises reinvent by building their digital core and unleashing the power of AI to create value at speed for organizations across industries. Our strategy is to be the reinvention partner of choice for our clients and lead in the safe, widespread adoption of AI, and to be the most client-focused, AI-enabled, great place to work in the world. We bring together the talent of our approximately 799,000 people with proprietary assets and platforms, deep process and industry expertise, and leading ecosystem relationships to deliver end-to-end solutions and measurable outcomes at scale. Through our Reinvention Services, we offer broad expertise across Cybersecurity, Digital Core, Finance, Industry and Enterprise, Song, Supply Chain and Engineering, and Talent, with advanced capabilities in AI and Data, Industry and Process, and Technology. We serve approximately 9,000 clients and generated approximately $70 billion in FY25 revenue. Visit us at accenture.com. You Are The Physical AI Automation Engineer is a hands-on practitioner who develops and integrates digital twin, 3D, simulation and industrial-data solutions that connect virtual environments with physical operations. The role has broad Physical AI scope, with primary depth in digital twin and simulation engineering, ecosystem integration and operational use of virtual models. Robotics training and orchestration experience is valuable but complementary rather than the defining center of the role.
But we need to remove the data-cmp-data-layer attributes? They are part of the original HTML; we can keep them? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The data-cmp-data-layer is metadata for tracking; it's not substantive? It's part of the link. Might be considered boilerplate? It's not navigation/legal/EEO. It's part of the link; could keep but it's messy. Probably we can keep the link as is, but we could simplify to just href and text. However preserving all substantive information includes the link URL and maybe the attributes are not substantive. Safer to keep the link with href and maybe remove the data attributes? The instruction says preserve ALL substantive information; does not say to keep all attributes. The data attributes are likely not substantive. We could keep just href and text. I'd keep simple accenture.com. Now Responsibilities:Responsibilities
- Develop and integrate digital twins for products, equipment, production lines, factories, warehouses, engineering environments and other physical operations.
- Create and prepare 3D environments and asset pipelines using CAD/BIM/PLM inputs, 3D models, scans or reality-capture data, with appropriate asset hierarchy, semantics and configuration.
- Build solutions using NVIDIA Omniverse, OpenUSD, Nucleus, Kit-based applications or comparable 3D and virtual-world ecosystems.
- Develop or integrate discrete-event, process-flow, physics-based and virtual commissioning simulations for layout, throughput, material flow, cycle time, resource utilization and operational validation.
- Connect digital twins and simulations with industrial and enterprise systems such as IoT platforms, historians, PLC/SCADA, MES, WMS, ERP, PLM and engineering data
- Develop Python or C++ extensions, connectors, APIs, data pipelines and automation services that connect models, simulation engines, operational data and downstream applications.
- Support model calibration, scenario design, simulation experiments, validation, sensitivity analysis and interpretation of results with engineering and operations stakeholders.
- Create virtual environments for design reviews, operator training, process validation, commissioning preparation and operational decision support.
- Implement testing, version control, configuration management, CI/CD, deployment, monitoring and documentation practices for production-quality twin and simulation solutions.
- Collaborate with architects, manufacturing and warehouse SMEs, simulation specialists, data/AI teams, robotics teams and ecosystem partners.
- Contribute reusable digital-twin templates, connectors, simulation components, reference implementations and delivery standards.
Requirements
- Minimum 3 years of experience in digital twins, 3D engineering, simulation, industrial software, game engines, engineering applications or systems integration.
- Hands-on experience in at least one core area: 3D model development and integration; discrete-event or process simulation; physics-based simulation; virtual commissioning; industrial data integration.
- Experience with one or more relevant tools or ecosystems such as NVIDIA Omniverse, OpenUSD, Unity, Unreal Engine, Siemens, Dassault Systemes, PTC, Ansys, FlexSim, AnyLogic, Visual Components or comparable platforms.
- Programming or scripting capability in Python, C++, C# or a comparable language.
- Ability to translate engineering or operational requirements into models, simulation scenarios, integrations and testable outcomes.
- Understanding of software engineering, testing, documentation and structured delivery practices.
- Travel is required for this role and could vary up to 75%.
Qualifications
- NVIDIA Omniverse, OpenUSD, Nucleus, Kit SDK, Isaac Sim or related NVIDIA technologies.
- CAD/BIM/PLM integration, 3D optimization, asset conversion, reality capture, scanning or spatial-data pipelines.
- Discrete-event, process-flow, physics, controls or virtual-commissioning experience.
- Industrial ecosystem integration across IoT, historians, PLC/SCADA, MES, WMS, ERP and cloud or edge platforms.
- Robotics simulation, synthetic data, robot training, reinforcement or imitation learning, simulation-to-real transfer, fleet orchestration.
- Experience applying these capabilities in manufacturing, warehousing, logistics, engineering, capital projects, laboratories, data centers or other asset-intensive environments.
- Experience working with client engineering and operations teams in consulting, systems integration or product delivery.
Benefits
Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture
Pay:Pay
Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below. We anticipate this job posting will be posted until 10/25/2026.
- California: $30.67 to $98.94
- Colorado: $30.67 to $85.48
- Connecticut: $30.67 to $85.48
- District of Columbia: $32.69 to $91.01
- Illinois: $28.41 to $85.48
- Maine: $26.15 to $72.79
- Maryland: $30.67 to $85.48
- Massachusetts: $30.67 to $91.01
- Minnesota: $30.67 to $85.48
- New York: $28.41 to $98.94
- New Jersey: $32.69 to $98.94
- Ohio: $28.41 to $79.13
- Virginia: $28.41 to $91.01
- Washington: $32.69 to $91.01