Systems Engineering - Integration & Test Engineering- Hardware D Security Clearance

Position: Systems Engineering - Integration & Test Engineering- Hardware D with Security Clearance
Basic Qualifications Requires a Bachelor's degree in Electrical Engineering, or a related Science, Engineering, Technology or Mathematics field. Also requires 2+ years of job-related experience, or a Master's degree and 6 months of job-related experience. Agile experience preferred, CLEARANCE REQUIREMENTS:
Department of Defense TS/SCI security clearance is preferred at time of hire. Candidates must be able to obtain a TS/SCI clearance within a reasonable amount of time from date of hire. Applicants selected will be subject to a U.S. Government security investigation and must meet eligibility requirements for access to classified information. Due to the nature of work performed within our facilities, U.S. citizenship is required.

Responsibilities for this Position ROLE AND POSITION OBJECTIVES:
As a Systems and Test Integration Engineer
- Hardware Dev Ops, on the GDMS TIDES team, you will be a core contributor within the Hardware Development Environment (HDE). The HDE is the shared engineering platform - spanning hardware, test, and software - that all spacecraft payload programs build on. The Dev Ops group owns the software platform layer: CI/CD pipelines, test automation frameworks, shared tooling, and the lab infrastructure that connects them.

You will work alongside hardware and systems engineers to build and maintain the Dev Ops Test Infrastructure (DOTI) - and your work directly enables faster hardware bring-up, more reliable regression testing, and a smoother path from development to design verification to flight readiness. You will write automation code, build and maintain pipelines, stand up testing suites, and integrate new hardware into the CI framework - all in a mission-focused environment.

Preferred

Skills & Experience:

- 3+ years of experience in Dev Ops, software integration, or test automation engineering
- Hands-on experience with CI/CD platforms (Git Lab CI, Jenkins, or equivalent) - Proficiency in Python for scripting, test automation, and tooling development

- Experience with Git-based version control workflows (branching strategies, merge requests, code review) - Familiarity with containerization tools (Docker, Podman) and basic container orchestration
- Experience working in Linux environments (RHEL, Ubuntu) - comfortable at the command line
- Experience writing and maintaining automated test frameworks (pytest, Robot Framework, or equivalent) - Familiarity with network configuration, lab infrastructure, or instrument integration

- Experience with Windows development environments (Win
10/Win
11, Power Shell) - Exposure to hardware-in-the-loop (HIL) or hardware test environments is a plus
- Familiarity with agile/scrum workflows and sprint-based delivery

Key Responsibilities
- Build, maintain, and improve CI/CD pipelines that run automated tests against hardware and software targets
- Develop and maintain test automation scripts and frameworks in Python and Bash
- Stand up and configure lab environments for hardware development and design verification activities
- Integrate new hardware platforms and instruments into the shared CI framework (DOTI) - Maintain shared tooling, package registries, and software baseline infrastructure
- Collaborate with APeX (firmware group) and STE (hardware group) ACEs to define and automate interface tests
- Document pipeline configurations, environment setups, and automation procedures
- Monitor pipeline health, triage failures, and drive continuous improvement
- Work across classification boundaries and program teams to extend the shared baseline without forking
- Support program standup activities - deploying the DOTI platform baseline to new program instances What Sets You Apart
- You think in systems - you see how the pipeline, the hardware, and the test environment connect
- You write clean, maintainable automation code that others can extend
- You're comfortable asking "why are we doing this manually?" and then fixing it
- You communicate clearly with hardware engineers who may not speak Dev Ops natively
- You treat the shared baseline as a product - with users, quality standards, and a roadmap
- Identifies opportunities to apply AI tools for continuous…