Northwood Space
Infrastructure Engineer
About this role
Northwood seeks an Infrastructure Engineer to own and operate critical components of their space communications infrastructure stack, including CI/CD, cloud platforms, networking, and security systems. You'll work independently on a defined scope, handle on-call responsibilities, and drive automation to reduce operational toil across a globally distributed satellite ground station network.
What you'll do
- Own and operate infrastructure components (CI/CD, app platform, cloud/IaC, networking, observability, security tooling)
- Build and maintain infrastructure as code using Terraform, Helm, and GitOps patterns
- Carry on-call rotation and resolve majority of incidents independently
- Partner with security and compliance teams on controls implementation and policy management
- Automate repetitive manual work and address underlying system design issues
- Create and maintain runbooks, design documentation, and component guides
What they're looking for
- Linux and networking fundamentals
- AWS or equivalent cloud platform
- Infrastructure as code (Terraform)
- Kubernetes and containerization
- CI/CD pipeline design and implementation
- Observability and monitoring tools
- Python, Go, or similar scripting languages
- Technical writing (design docs, post-mortems, runbooks)
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Northwood Space
Northwood Space builds advanced ground station infrastructure for satellite communications, including phased array antennas and high-speed digital systems deployed globally. The company is hiring engineers across mechanical design, electrical systems, tooling, testing, and infrastructure to support the development and deployment of scalable satellite ground networks.
View all jobs at Northwood SpaceLikely interview questions
- Walk us through a production system you've owned end-to-end—from design through operation. What went wrong, and how did you handle the incident?
- Describe your experience with infrastructure as code. How do you approach keeping Terraform/Helm code maintainable and in sync with actual deployed state?