Back to Jobs

Jr. Site Reliability Automation and Orchestration Engineer

Everforth Apex

Job Description & Details

This is a solid entry-to-mid level infrastructure role focused on automating networks and virtualized environments for a large-scale government IT program. If you like digging into Windows automation, writing playbooks, and figuring out how to make rigid release cycles smoother, this gig gives you plenty of hands-on technical ownership.

What You'll Actually Be Doing

You will spend your days bridging the gap between development and operations by building and maintaining Ansible playbooks, writing automation scripts, and managing release schedules. Expect to troubleshoot non-production environments, migrate configurations to production networks safely, and set up automated acceptance testing. It is a mix of heavy scripting, documentation, and coordination with a distributed team to ensure updates do not break the network.

The Core Tech Stack

Ansible and Windows automation are non-negotiable here; you must know how to build roles and handle configurations in a mixed environment. You will also need solid scripting skills in PowerShell or Python to automate routine tasks and manage CI/CD pipelines using tools like Jenkins or GitLab. Familiarity with Azure DevOps workflows and an understanding of Infrastructure as Code principles will keep you from drowning in manual updates.

Interview Expectations

Expect the hiring team to test your practical knowledge of Ansible by asking you to walk through how you would structure a playbook for a complex Windows software deployment and handle error rollback. They will also likely drill down into your scripting abilities, asking how you parse logs or automate a repetitive administrative task in PowerShell or Python, looking for clean code and a methodical approach to debugging.

Application Advice

Make sure your resume explicitly highlights any hands-on experience with Ansible, Windows system administration, and automation scripting using PowerShell or Python. Do not just list tools; briefly mention how you used CI/CD pipelines or CI tools like Jenkins to speed up deployments. Drop in keywords like 'release management', 'Infrastructure as Code', and 'CI/CD' naturally to clear the ATS filters and show you understand the full engineering lifecycle.