Infrastructure Engineer

Responsibilities

• Own and operate one or more components of the Northwood infrastructure stack (CI/CD, app platform, cloud/IaC, networking, observability, security tooling).
• Take a defined scope and execute without ongoing oversight.
• Build and maintain infrastructure as code. Default to Terraform, Helm, and GitOps.
• Carry on-call for the infra stack. Handle the majority of incidents to resolution independently.
• Run post-incident reviews for incidents you owned.
• Partner with security engineering and compliance on controls implementation (Vault policies, IAM boundaries, SIEM coverage, evidence collection).
• Treat toil as a design signal. When manual work repeats, automate it or fix the underlying system.
• Write and maintain runbooks, design docs, and component documentation. Keep them current with the system.
• Collaborate across infra, product engineering, and ground station operations on cross-cutting work.

Basic Qualifications

• 3-5 years of production infrastructure experience (SRE, DevOps, platform, network, or systems engineering).
• Working competence across: Linux, networking fundamentals, AWS or equivalent cloud, infrastructure as code (Terraform), containers and Kubernetes, CI/CD pipelines, observability tooling.
• Demonstrated ownership of a production system end-to-end: design, implementation, operation.
• On-call experience in a production environment with measurable reliability outcomes.
• Comfortable in code (Python, Go, or similar) for automation, tooling, and integration work.
• Strong technical writing — design docs, runbooks, post-mortems.

Preferred Qualifications

• Strong background in one or more of the following: Networking (FortiGate, switching, TGW, WireGuard, BGP, IPsec), Security engineering (Vault, Okta, IAM, SIEM), Compliance (CMMC, FedRAMP, NIST 800-171, ITAR), Observability (VictoriaMetrics, Prometheus, Grafana, Vector, Loki), App platform (EKS, k3s, ArgoCD), CI/CD and developer experience, Cloud architecture (multi-account AWS, GovCloud, Cloudflare), On-prem and hardware-adjacent ops.