Cloud Infrastructure Engineer

What we're looking for?

We need someone with 2-5 years of hands-on experience in cloud infrastructure, DevOps, platform engineering, or SRE who has designed, built, and owned AWS build and deployment pipelines in production. Ideally they built them from scratch at an early-stage startup or on a small team. You should be comfortable working as the only infrastructure engineer on a small, fast team. Expect to own the work end to end and have engineers relying on you every day. You should have a track record of cutting manual deployments and incidents, securing cloud architecture, and helping engineers ship faster. Bonus points if you like breaking systems: hacking side projects, pen testing, or fixing vulnerabilities. Experience with AWS GovCloud or with aerospace and defense customers is also a plus.

What you'll do:

• Own all of Vendra's build and deployment pipelines (CI/CD), and refactor them where needed. They cover our customer platform, supplier portal, internal ERP, and AI/ML workflows, across both commercial AWS and AWS GovCloud.
• Own cloud architecture and security: least-privilege IAM, network isolation, encryption, secrets management, audit logging, and automated vulnerability detection and patching.
• Work directly with the CTO and a lean 3-person product engineering team. You'll give them repeatable, observable, easy-to-roll-back deployments so they don't need manual infrastructure help for every change.
• Build and manage infrastructure as code (GitHub Actions today; Pulumi, CDK, or CloudFormation). You'll also set up useful monitoring, alerting, backups, and incident-response runbooks across dev, staging, and production.
• Run the networking and access setup for Vendra's new in-house GPU training rigs from start to finish, so the technical team can reserve compute and test their own models.
• Improve system performance, availability, and cloud cost efficiency. Support customer security reviews and compliance work with documented controls and evidence.

Who this is for: This is a hands-on individual contributor (IC) role, not a team lead role. Senior candidates are welcome, but they must still be doing the work themselves. Cloud should be the main focus of their experience, not a side task next to backend or full-stack work. We'd rather see someone who built the build pipelines than someone who used systems running on the cloud. AWS is a must. Terraform-heavy, process-heavy profiles are less of a fit than scrappy builders who move fast.