Devops Release Manager Jobs in Arizona (NOW HIRING)

We are seeking a Senior DevOps Engineer who can take ownership of our build and release pipeline end to end, from source control through CI/CD, and containerized deployment. Our current TeamCity setup needs a strong hand; this role is as much about fixing and modernizing what exists as it is about building what comes next.

You will own our CI/CD architecture across a mixed source control environment (migrating from Bitbucket to Gitea), design and maintain TeamCity build configurations that trigger tiered validation (smoke, nightly, full regression) against our in-house test framework.

This is a hands-on technical role with direct influence over how our engineering teams ship software.

TeamCity and CI/CD

• Own and rebuild our TeamCity configuration: build chains, templates, VCS roots, build parameters, agent pools, and dependency management. Bring order to an environment that has grown without a consistent architecture.
• Lead the migration from Bitbucket to Gitea, including webhook and trigger configuration, so commits reliably kick off the correct TeamCity build chain.
• Configure commit-triggered pipelines with differentiated test tiers based on branch and event type.
• Integrate unit testing into the TeamCity build pipeline as a build and quality gate.

Containerization and Artifact Management

• Stand up and implement a container registry, such as Harbor, as our internal Docker image repository, including image lifecycle, scanning, and access policy.
• Establish artifact versioning, retention, and traceability practices across build outputs and container images.

Security and Access

• Implement Active Directory gated access controls across build, source control, and registry systems, working closely with IT on integration and permissions design.
• Manage secrets using Key Vault, or an equivalent tool.

Cross-Team and Process

• Work closely with software, firmware, QA, and tool teams to align pipeline behavior with real test and release needs.
• Document build and release architecture.
• Identify bottlenecks in build and release flow and implement scalable fixes, not workarounds.

• 5 or more years in DevOps, build engineering, or release engineering, with deep, hands-on TeamCity expertise: build chains, templates, agents, VCS integration, and troubleshooting. This is not a worked with it briefly requirement.
• Strong experience with Git and modern branching strategies, ideally across more than one source control platform (for example, Bitbucket, Gitea, or GitHub).
• Demonstrated experience building CI/CD pipelines with conditional, branch aware trigger logic, meaning different test tiers or actions based on branch or event.
• Experience with C#/.NET build environments (MSBuild, NuGet) sufficient to build, test, and containerize C# applications.
• Hands-on Docker experience: building images as part of a CI pipeline and pushing to a private registry.
• Experience implementing or administering a container registry such as Harbor, Artifactory, or equivalent.
• Working knowledge of Active Directory based access control integration for engineering tooling.
• Experience with secrets management platforms such as Azure Key Vault, HashiCorp Vault, or AWS Secrets Manager.
• Strong scripting and automation ability, using PowerShell, Python, or Bash.
• Strong documentation and cross-team communication skills, since you will be training teams on the systems you build.
• Must be a U.S. Person, per U.S. export control regulations (U.S. citizen, lawful permanent resident, or protected individual under 8 U.S.C. 1324b(a)(3)), due to the nature of our engineering environment.

• Experience supporting embedded, firmware, or hardware adjacent engineering teams.
• Infrastructure as code experience, with Terraform, Ansible, or similar tools.
• Active U.S. security clearance, clearance eligibility, or prior military service.
• Familiarity with security, compliance, and audit requirements relevant to software delivery in a regulated or export controlled environment.

Within the first few months, this person will have audited and stabilized the existing TeamCity environment, and completed or driven the repo migration with working commit triggers.

You have lived inside TeamCity. You know its quirks, its build chain patterns, and how to untangle a configuration that has grown organically over time. You are equally comfortable with source control migrations, container tooling, and working with IT to get access control right. You like owning a pipeline end to end, from the first commit trigger to a signed off container image in a private registry.