Manufacturing Test Automation EngineerActive

Anduril Industries is a defense technology company with a mission to transform U. S.

What you'll do

• The manufacturing-line console. Pre-programmed for PCBA bring-up and bottle: bring-up. Technicians execute curated, version-controlled tests through a GUI. They do not author command-line.

• The vehicle-level test base. A pre-programmed console for vehicle Factory: Acceptance Test and system check-out. Same as manufacturing-line console.

• Design and build a production utility suite of tools. From requirements: through architecture, through GUI development, through deployment to the floor. These are the two consoles that the production team will live in.

• Test framework architecture. The shared substrate underneath both consoles —: test runners, instrumentation drivers, data logging, traceability hooks, error-code library, configuration management.

• Toolchain standardisation. NixOS-based, declarative, reproducible. Drive the: move off mixed Linux/ Windows/ Mac/ NixOS dev environments to a single config-managed target.

• CI/CD for test code. Test software ships through pipelines, not over USB: sticks. Stand it up, maintain it, hold the line on review and version control.

What they're looking for

• Integration with Anduril's factory systems: MES (work instructions, routings, defect capture), Oracle ERP, Teamcenter PLM where relevant. Test results should land in the systems where they're traced and acted on, not in spreadsheets.
• Technician-facing usability. GUIs that lower the entry-skill bar. Curated,: version-controlled tests. Clear pass/fail. Helpful error codes that point at the actual problem, not at a stack trace.
• Cross-site codebase convergence with other Anduril production sites. You're: part of converging the AU and US Manufacturing Test stacks — shared framework, shared XL Utility code, common error-code library. You'll work with the US team to make that real.
• Floor support. When a test fails and it's not clear whether it's the product,: the tester, or the test code — you debug it. You're the one called when the GUI throws an unexpected error and the build's stopped.