PLM and CAM/CAI Integration Engineer

Required Skills & Experience

REQUIRED QUALIFICATIONS

• 8 or more years implementing, configuring, and integrating Teamcenter in a production manufacturing environment, with demonstrated experience covering business object and data model definition, dataset types, relations, revision rules, status and release behavior, workflow design, and access manager rules. Teamcenter administration without configuration depth does not satisfy this requirement.
• Demonstrated NX CAM implementation experience, including environment configuration, templates, machine models and kinematics, tooling and cutting-data library management, and post-processor development and verification against physical machines.
• Demonstrated Vericut implementation experience, including machine and control configuration, integration with a CAM system and a PLM or PDM system, and verification result management.
• Demonstrated experience integrating machining process modeling or optimization software into a CAM and PLM environment. Third Wave Systems experience is the strongest signal; comparable optimization toolchain integration is considered.
• Demonstrated InnovMetric PolyWorks implementation experience, including PolyWorks data management and integration with PLM for inspection result return with item revision and characteristic identity preserved.
• Working knowledge of machining practice sufficient to verify that a post-processor output, a simulation configuration, and an optimization result are technically correct rather than merely syntactically valid. You must be able to evaluate the output, not just the process that produced it.
• Working knowledge of GD&T per ASME Y14.5 and of model-based inspection practice, sufficient to configure characteristic data paths correctly and evaluate whether the inspection data that returns to Teamcenter is the right data in the right form.
• Demonstrated experience conducting stakeholder interviews with engineering and manufacturing domain experts and translating the outputs into written, reviewable requirements and configuration design specifications.
• Demonstrated experience migrating legacy manufacturing assets into managed PLM configuration, including handling assets of uncertain provenance.
• Able to be on site in Costa Mesa regularly. This role does not work remotely.
• U.S. Person status is required, as this position needs to access export controlled data.

Nice to Have Skills & Experience

PREFERRED QUALIFICATIONS

• Experience with Teamcenter Manufacturing, Shop Floor Connect, or Teamcenter Quality, and with how manufacturing BOM, routing, and work instruction data are managed within Teamcenter rather than alongside it.
• Experience with QIF (ISO 23952) as a measurement data exchange format, including the fidelity limitations of specific tool-to-tool exchanges and how to state those limitations in architecture documentation.
• Experience integrating a Teamcenter-managed CAM and inspection environment with a manufacturing execution system such as Anduril Forge, Siemens Opcenter, or Solumina/iBase-t, specifically for work order, program delivery, and inspection result consumption.
• Experience with the Staged Modeling process or an equivalent stage-based manufacturing model practice in NX, and with how staged models are consumed as CAM source geometry.
• Familiarity with the NSE MBE Maturity Index and what practice distinguishes Level 4 (Trusted MBD) and above from lower states, applicable to Teamcenter configuration and tool integration design.
• Experience with MIL-STD-31000 Technical Data Packages and AS9102 First Article Inspection, and with how those requirements shape what must be managed and traceable in a Teamcenter configuration.
• Experience in shipbuilding, submarine construction, aerospace, or another highly regulated manufacturing environment where configuration changes require documented evidence of test and promotion.
• Experience with NX Open scripting for configuration and integration tasks, at the level of writing or modifying scripts that bind to a Teamcenter data model.
• Prior experience in a greenfield PLM and CAM environment standup, as opposed to extending or maintaining an established configuration.

Job Description

ABOUT THE TEAM

Maritime Digital Production is the software and digital systems function within Anduril's Heavy Metal division. We build and deploy the technology stack that powers Anduril's shipbuilding factories: the data infrastructure that makes every machine and sensor visible in real time, the manufacturing execution system that workers and planners use every shift, the scheduling engine that replans production in minutes instead of days, and the AI systems that remove manual toil from the shop floor and business operations. We operate at the boundary between Operational Technology and Information Technology, incubating solutions close to the production line, validating them with real operators, hardening them for reliability and security, and scaling them across sites. The environment is fast, physical, and consequential. When our systems go down, production stops. The output of our work is not a dashboard: it is a ship. We are scaling from a founding team to more than 70 engineers across multiple U.S. sites, and you will be joining early to shape how CAM, simulation, and inspection capability is built and governed as managed, traceable digital practice at Anduril.

ABOUT THE JOB

CAM programs, simulation results, cutting parameters, and inspection outputs currently live on file shares and local disks - not as controlled objects tied to an item revision. A CAM program cannot be reliably linked to the model revision it was cut from. Inspection results return to quality by hand. You will change that. You will design the Teamcenter data model and integration architecture, build it, and deploy it into production - integrating NX CAM, Vericut, Third Wave Systems, and InnovMetric PolyWorks as managed, governed capabilities rather than desktop applications operating beside the digital thread. You will also define the integration architecture for non-NX CAM and CAI platforms against the same data model, with the same traceability and release behavior. The scope is everything from NX CAM environment standup and post-processor development to tooling and machine library governance, CAM-to-model associativity, DNC delivery configuration, and inspection result return. This role requires deep Teamcenter configuration experience combined with genuine CAM and machining knowledge. You will not hand the design to another team to build. If you have spent your career on the PLM side without meaningful CAM or machining exposure, the gap will show in the data model you design. If you have spent it on the CAM side without PLM configuration depth, the integrations will bypass managed configuration rather than implement it. The role requires both.

WHAT SUCCESS LOOKS LIKE

Three outcomes, in priority order. These are how the role is measured. Anduril engineers create, manage, and lifecycle CAM and CAI programs inside Teamcenter. CAM programmers author programs in NX CAM against released model data. CAI programs are authored and managed in the same managed environment. Every program - CAM or CAI, NX or non-NX - exists as a controlled Teamcenter object tied to a specific item revision, progresses through a defined review and release workflow, and is revised under change control. Nothing lives on a file share. An engineer can determine the current released program for any part in one step, without asking anyone. Tools, fixtures, and machines are managed as reusable library assets, not rebuilt per programmer. Tooling, fixturing, and machine definitions exist as managed Teamcenter objects that CAM and CAI programmers select from a governed library rather than re-create from scratch. Machine models, kinematics, and post-processors are versioned, validated against the physical machines, and updated through a defined governance path. A new programmer inherits a complete, current set of assets on day one. Programs are post-processed and delivered to the machine within the system, without leaving Teamcenter. Post-processing runs against the released program and the validated post-processor within the managed environment. The NC output is a controlled object tied to the program revision and the machine it was generated for. DNC delivery to the machine controller runs from Teamcenter, not from a file share or a programmer's desktop. A machinist loads the correct, current, released program because the system enforces it - not because they checked manually.

WHAT YOU'LL DO

• Configuring the NX CAM environment: customer defaults, templates, operation and geometry templates, and the configuration that makes programming from a released MBD source model the default path
• Building and governing the tooling, fixturing, and machine library as managed Teamcenter objects - versioned, validated against physical assets, and updatable through a defined governance path - so programmers select from a current library rather than re-create assets per program
• Developing and verifying post-processors for the machine tools in scope against the physical machines, with a verification record per post-processor covering motion types, cycles, and controller behavior
• Configuring CAM-to-model associativity in Teamcenter, binding CAM programs to specific item revisions and defining the action raised when a source model revises
• Configuring post-processing and DNC delivery within Teamcenter so NC output is a controlled object tied to the program revision and machine, and delivery to the machine controller runs from the system rather than from a file share or programmer desktop
• Implementing Vericut integration with NX CAM and Teamcenter, including simulation result management and verification gating
• Implementing Third Wave Systems integration, including the feedback path that returns optimized parameters to the CAM program and cutting-data library without manual re-entry
• Implementing InnovMetric PolyWorks integration, including the model and characteristic data path into PolyWorks and the result return path into Teamcenter with characteristic identity and item revision preserved
• Defining and implementing integration architecture for non-NX CAM and non-PolyWorks CAI platforms against the same Teamcenter data model, with the same traceability and release behavior
• Implementing Teamcenter business objects, item types, dataset types, relations, revision rules, status behavior, workflows, and access rules per the approved configuration design
• Executing migration of existing CAM programs, post-processors, machine models, tooling libraries, simulation assets, and inspection assets into managed Teamcenter configuration
• Interviewing CAM programmers, manufacturing engineers, machinists, metrology engineers, and quality engineers to elicit requirements, and translating those into Teamcenter configuration designs and integration architecture specifications before configuration work begins
• Delivering configuration documentation sufficient for an Anduril administrator to perform a defined configuration change unaided
• Authoring and delivering user documentation, work instructions, and training curricula for CAM programmers, manufacturing engineers, machinists, and metrology staff
• Maintaining the residual-gap register identifying every capability the delivered environment does not yet support, with a recommended closure path for each item

WHAT THIS ROLE DOES NOT OWN

Stated explicitly, because the scope is broad.

• Production CAM programming of Anduril parts. Programs produced under this role are validation and reference cases, not production release deliverables.
• Authorship of manufacturing methods and process definitions. The configured environment supports methods defined elsewhere; this role builds the environment.
• NX Open custom tooling development beyond the configuration and integration scripting required by the tool standup. Bespoke automation is a separate scope.
• Procurement of software licenses, hardware, or metrology equipment.
• Authorship of general MBE standards, style guides, or cross-program MBE training curricula. Tool-specific documentation and training remain in scope.
• Engineering management. You will have no direct reports.