Job Description & Details
This is a heavy-duty infrastructure and release management role focused on modernizing the NC FAST platform. You'll be the person bridging the gap between development and operations by building bulletproof automation pipelines and wrangling complex AWS environments. If you enjoy untangling deployment bottlenecks and scaling up automation rather than clicking around consoles, this gig is right up your alley.
What You'll Actually Be Doing
You'll spend your days writing and refining automation workflows, mostly centered around Ansible playbooks and keeping Ansible Tower/AWX running smoothly. Your core mission is to make infrastructure provisioning and application builds completely repeatable so that releases are boring and predictable. You'll be coordinating across dev, DBA, and architecture teams to troubleshoot configuration drift, optimize CI/CD pipelines, and occasionally jumping on-call when a production deployment goes sideways.
The Core Tech Stack
You absolutely must know your way around AWS cloud services, Linux administration, and deep automation tooling. Ansible and Ansible Tower/AWX are non-negotiable here, alongside a strong grasp of YAML and Infrastructure as Code principles. If you've also touched Terraform, Docker, Kubernetes, or Jenkins, you'll easily stand out, but your bread and butter needs to be master-level configuration management and deployment automation.
Interview Expectations
The hiring manager is going to test how you handle failure in production. Expect them to ask you to walk through a time an Ansible deployment failed midway through a massive release, and exactly how you safely rolled it back without corrupting the state. They want to see how you troubleshoot under pressure, so don't just talk about success—be ready to explain your debugging methodology for complex Linux and cloud networking bottlenecks.
Application Advice
To get past the automated screeners and land an interview, make sure your resume explicitly calls out your years of experience with Ansible, AWS, and Linux administration right near the top. Don't just list buzzwords like CI/CD and DevOps; describe the actual scale of the pipelines you built and how much you reduced deployment times by using Infrastructure as Code.