> Markdown version of [/jobs/ext/4787483-test-automation-engineer-project-sunrise-orbital-data-centers](https://www.wearedevelopers.com/jobs/ext/4787483-test-automation-engineer-project-sunrise-orbital-data-centers). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Test Automation Engineer, Project Sunrise - Orbital Data Centers - **Company:** Blue Origin - **Location:** Denver, CO, United States - **Experience:** Expert - **Salary:** $121,023 - $169,432 - **Contract:** Permanent contract - **Skills:** Abstraction Layers, Automation of Tests, Biometrics, Code Review, Databases, Data Centers, Data Systems, Hardware-In-The-Loop Simulation, Python (Programming Language), LabVIEW, Regression Testing, Software Engineering, System Testing, Test Data, Test Execution Engine, Data Logging, Hardware Testing, Information Technology, Software Version Control - **Published:** November 19, 2026 - **Apply:** https://blueorigin.wd5.myworkdayjobs.com/BlueOrigin/job/Denver-CO/Test-Automation-Engineer--Project-Sunrise---Orbital-Data-Centers_R75910 ## About the Role · Bachelor's degree in engineering, computer science, physics, or a related technical field · 5+ years of test automation experience on hardware test systems, such as hardware-in-the-loop, automated test equipment, EGSE, or production or lab validation · Python proficiency at the level of maintainable, version-controlled, tested software, not one-off scripts · Experience building or substantially extending an automated test framework, including test sequencing, instrument control, and results logging · Experience controlling instruments and hardware programmatically, such as programmable power supplies, electronic loads, data acquisition, and communication buses, and designing abstractions so that hardware can be swapped · Software engineering discipline applied to test code: version control, code review, automated regression testing of the test system, and release control · Experience storing test results so they trace to unit serial number, configuration, and procedure revision, and can be queried later · Clear written and verbal communication, and the ability to treat test engineers as customers of your framework Preferred Qualifications · Experience with LabVIEW · Experience in hardware-in-the-loop, semiconductor or electronics ATE, or data center and server validation, running high volumes of units through automated test · Experience with spacecraft EGSE, including telemetry and command interfaces and simulators for flight computers or power systems · Experience validating a test system, including measurement system analysis, instrument calibration management, and demonstrating that automated results can be trusted · Experience testing high-power electronics, high-voltage DC power systems, or GPU or HPC hardware · Experience with relational or time-series databases and dashboarding tools for test results · Experience on commercial or rapid-development hardware programs, including moving from a first article to repeatable production acceptance ## Description Project Sunrise intends to test every unit the same way every time, with more than 80% of acceptance test execution running fully automated and without operator judgment, and the evidence from each run has to be trustworthy enough to release flight hardware on. You will build the framework that makes that possible: the test sequencing layer, the instrument and ground support equipment abstraction, the results capture, and the run orchestration that sit underneath every automated acceptance test. This is a software and test-infrastructure role. The test engineers for the spacecraft and for the compute system write the procedures and the automated test content. You own the framework they run on and the tools they use to author that content. The framework has to run on both the spacecraft electrical ground support equipment (EGSE) and the compute system test bench, so a test written once behaves the same way on either. You will work closely with the test engineers, the test data analyst who consumes the data your framework captures., · Architect the automated test framework for production acceptance testing, with a target of more than 80% of test execution running fully automated and without operator judgment · Build the test sequencing layer (the test executive): step ordering, limit checking, branching, retries, safe abort, and recovery of the hardware to a known safe state when a run is interrupted · Build an abstraction layer for instruments and EGSE, so test content does not depend on a specific power supply, electronic load, data acquisition unit, or simulator and bench hardware can be replaced without rewriting tests · Make one framework run on both the spacecraft EGSE and the Compute System test bench, with shared services and bench-specific drivers, so test content moves between them with minimal change · Capture results and logs for every run with full traceability: requirement, procedure revision, unit serial number, hardware configuration, bench, and instrument calibration state · Build run orchestration and scheduling: queuing, bench resource arbitration, unattended and overnight runs, remote monitoring, and alerts when a run needs a human · Provide the tools test engineers use to author automated content: templates, shared libraries, simulated hardware for dry runs, and static checks that catch errors before a test touches a real unit · Validate the automation itself: version and release the framework under change control, run regression suites and known-good and known-bad reference runs, and prove that an automated pass or fail means what it says · Work with the test engineers to convert manual first-article procedures into automated tests, and report automation coverage and the steps that still need a person, with the reason for each · Define data schemas and export interfaces with the test data analyst and the program's data systems, so results flow into analysis and the configuration record without manual handling · Support anomaly investigation by making every run reproducible from its logs, and keep framework documentation current for the engineers who build on it, Applicants for employment at Blue Origin must be a U.S. citizen or national, U.S. permanent resident (i.e. current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum. Background Check * Required for all positions: Blue's Standard Background Check * Required for Certain Job Profiles: Defense Biometric Identification System (DBIDS) background check if at any time the role requires one to be on a military installation * Required for Certain Job Profiles: Drivers who operate Commercial Motor Vehicles with a Gross Vehicle Weight (GVW), Gross Vehicle Weight Rating (GVWR) or combination of power unit and trailer that meets or exceeds 10,001 lbs. and/or transports placardable amounts of hazardous materials by ground in any vehicle on a public road while in commerce, may be subject to additional Federal Motor Carrier Safety Regulations including: Driver Qualification Files, Medical Certification (obtained before onboarding), Road Test, Hours of Service, Drug and Alcohol Testing, vehicle inspection requirements, CDL requirements (if applicable) and hazardous materials transportation/shipping training. * Required for certain Job Profiles: Ability to obtain and maintain Merchant Mariner Credential, which includes pre-employment and random drug testing as well as DOT physical