Software Engineer, Infrastructure & Platform

Aalyria

1d•$135,000 - $165,000•Hybrid

About The Position

We are seeking a highly motivated and experienced Software Engineer to join our core Spacetime engineering team. We value engineers who are adaptable, proactive, and eager to tackle new challenges as we advance our technology. The ideal candidate will bring a solid technical background and a proven track record in solving complex engineering challenges. As a software engineer, you will play an integral role in developing and optimizing systems critical to our business, with the flexibility to contribute to and take ownership of various projects as both you and the company grow. You will be working alongside a team of seasoned engineers from top-tier tech companies, managing project priorities, timelines, and deliverables while designing, developing, testing, and maintaining core software. Aalyria builds multicloud, Kubernetes-based systems. They run in environments we operate and in environments our customers operate themselves: commercial cloud, government cloud, and secure, classified, or disconnected deployments. The same product has to install, upgrade, and stay observable in all of them. Every other engineering team at Aalyria builds on what we provide: cloud accounts and projects, networking, identity, cluster lifecycle, and infrastructure provisioning. We make this self-service and repeatable, so engineering teams can ship without having to be experts in each cloud provider.

Requirements

Bachelor's degree in Computer Science or a related technical field, or equivalent practical experience.
5+ years of experience with production infrastructure or distributed systems.
Strong software engineering fundamentals. You automate infrastructure in code instead of orchestrating it by hand.
Experience with AWS or GCP, infrastructure-as-code, cloud networking, and Kubernetes infrastructure.
Experience packaging and delivering software onto Kubernetes, with a good understanding of the tradeoffs between templating, rendering, and controller-based approaches.

Nice To Haves

Experience supporting classified, air-gapped, regulated, or otherwise constrained environments.
Experience with cloud landing zones, account and project vending, network architecture, DNS/IPAM, IAM foundations, workload identity, organizational policy, or quota management.
Experience with GitOps delivery and continuous reconciliation at scale – Argo CD, Flux, or comparable – including drift, promotion, and multi-environment rollouts.
Experience with Terraform or OpenTofu, including reusable modules and self-service provisioning.
Experience designing infrastructure platforms used by multiple internal engineering teams.

Responsibilities

Build the foundations every Aalyria environment starts from: accounts and projects, networking, DNS and IPAM, identity and RBAC, quotas and policy.
Own Kubernetes cluster lifecycle end to end – provisioning, upgrades, addons – and the networking layer on top of it: Gateway API, service mesh, and zero-trust connectivity.
Keep patterns consistent across environments, and make the differences that cloud providers, security domains, and customers force on us deliberate.
Make disconnected deployment a first-class path: registry and artifact mirroring, hermetic builds, artifact sourcing with no egress, bootstrapping with no upstream, and out-of-band promotion.
Define how Spacetime is packaged and configured for Kubernetes, and decide where Helm, rendering, or custom controllers each belong.
Build the delivery path: GitOps reconciliation with Argo CD, IaC run orchestration, drift detection, OPA policy gates, and promotion between environments.
Own fleet-scale change mechanics – module and chart versioning, staged rollouts, migration paths, deprecation – so one change reaches every environment without breaking any of them.
Run what you build: availability, upgrades, capacity, observability, backup/recovery, security maintenance, and incident response.
Work with product and domain engineers, and turn their requirements into primitives other teams use on their own.