> Markdown version of [/jobs/ext/4440158-senior-devops-engineer](https://www.wearedevelopers.com/jobs/ext/4440158-senior-devops-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior DevOps Engineer

- **Company:** Manufacturing llc
- **Location:** St. Louis, MO, United States
- **Experience:** Expert
- **Salary:** $100,000.0 - $140,000.0
- **Contract:** Permanent contract
- **Skills:** Microsoft Azure, Cloud Computing, DevOps, Github, Bicep, Terraform
- **Published:** October 21, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=3121aa542a9e09ee

## About the Role

* 6+ years in DevOps, platform, or cloud infrastructure engineering.
 * Deep hands-on Azure experience (compute, networking, identity, storage, security).
 * A track record of building and owning CI/CD pipelines (Azure DevOps, GitHub Actions, or similar)., * Bachelor's (Required)

Experience:

 * DevOps: 6 years (Required)
 * Cloud computing: 6 years (Required)

## Description

* Own and evolve our CI/CD pipelines, making releases faster, safer, and more automated.
 * Drive Infrastructure as Code adoption (Terraform/Bicep) and environment consistency from dev to production.
 * Partner with developers to remove friction in builds, testing, and deployment.
 * Stand up visibility into build, release, and deployment metrics (e.g., DORA).

Azure Platform & Infrastructure

 * Operate our Azure environment across networking, identity, access control, and security.
 * Lead reliability, performance, and scalability improvements, including readiness for seasonal peak demand.
 * Drive cost optimization, right-sizing, and capacity planning.

Reliability & Operations

 * Serve as the technical lead with our managed service provider (NOC/SOC) on monitoring, alerting, and incident response.
 * Shape escalation paths and lead incident reviews, root-cause analysis, and preventive fixes.
 * Document platform standards, configurations, and runbooks.

Goals for Position:

 * Releases are routine and low risk, with measurably fewer deployment and environment issues.
 * Infrastructure is defined in code and reproducible.
 * The platform handles peak periods without issue.
 * Incidents are caught early, escalated cleanly, and don't repeat.