Who we are looking for
This engineer supports deployments and keeps production running in Cadonix’s controlled AWS environment, including AWS GovCloud (US), where only US Persons are permitted under ITAR. ProduCt teams manage their own continuous integration and delivery workflows and publish artifacts. This role moves those artifacts into the restricted production environment. It verifies them and resolves infrastructure problems from new deployments or spontaneous issues in running systems.
Beca or equivalent experience required.use access to this environment is limited, the role is often the only person able to see what is actually happening in production.
What you bring to the Team
- A bachelor’s degree or equivalent experience in Computer Science, Software Engineering, or a related field. Minimum of 5 years’ experience in DevOps, cloud infrastructure or production operations, including at least 3 years supporting production workloads on AWS.
- AWS Fixing – Practical, hands-on experience diagnosing real production problems on AWS: EC2, ECS or EKS, VPC network architecture and security configurations, ALB/NLB, Route 53, ACM, IAM policy evaluation, S3, RDS, and CloudWatch. Capable of reading CloudTrail and CloudWatch logs to reconstruct what happened. AWS GovCloud experience is a plus but not required; equivalent experience in isolated or regulated environments is equally relevant.
- Deployment and Release Mechanics – Understands container images, artifact versioning, environment configuration and secrets injection, and rollback. Comfortable working with CI/CD pipelines owned by other teams and diagnosing where a handoff has gone wrong.
- Infrastructure defined through code – Able to read, modify, and safely apply existing Terraform, CDK, or CloudFormation. Understands state, drift, and why manual console changes cause problems later. Does not need to have designed a large estate from scratch.
- Linux and Networking – Solid Linux administration and fixing. Working understanding of TCP/IP, DNS, TLS, routing, and firewall behaviour — enough to tell a network problem from an application problem.
- Scripting – Proficient in Bash and Python (or Go) for automation, diagnostics, and small tooling.
- Monitoring and Observability – CloudWatch, Prometheus, Grafana, or similar. Able to build a dashboard or alert that answers a real operational question.
- Closed System Problem Solving – Comfortable supporting software they did not write and may not have source access to, working from telemetry, timing, and behaviour rather than code. Persistent and methodical when the obvious answer is not available.
- Data Field – Good judgement about what constitutes sensitive or client-related information, including inside logs, stack traces, configuration, and crash artifacts. Holds the boundary under production pressure and advances rather than improvising. Familiarity with ITAR, CUI, FedRAMP, PCI-DSS, or HIPAA environments is an advantage.
- Communication and Ownership – Keeps collaborators informed during an incident without being asked. Works effectively alongside product groups across time zones, and with external vendors under support contracts. Reliable and self-directed, since much of the environment cannot be observed by anyone else.
The BIG payoff
We are a company who is going to make a difference in the industries and the communities in which we choose to operate. Every employee of Re:Build will share ownership in the company and will share in the financial rewards of the success we achieve together, at all levels of the company!
We want to work with people that reflect the communities in which we operate