> Markdown version of [/jobs/ext/2011184-remote-incident-commander](https://www.wearedevelopers.com/jobs/ext/2011184-remote-incident-commander). 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). --- # remote Incident Commander - **Company:** One Inc - **Location:** Tacoma, WA, United States - **Contract:** Permanent contract - **Skills:** Linux, Reliability Engineering, Ansible, Containerization, Information Technology, Terraform, Docker, Programming Languages - **Published:** August 10, 2026 - **Apply:** https://careersingovernment.com/job/2424887/incident-commander-38/ ## About the Role As a key member of the site reliability team, the remote Incident Commander will manage incident response across various organizations, ensuring effective classification, documentation, and resolution of incidents while collaborating with cross-functional teams to enhance service delivery and prevent future disruptions.Key responsibilitiesLead real-time incident management and enhance collaboration with Incident Commanders, Customer Support, and Engineering teamsDevelop and improve practices, frameworks, and processes for incident management and service deliveryManage Root Cause Analysis documentation and communicate effectively with stakeholders regarding incident status and resolutionsRequired qualificationsExperience in incident management or a similar roleUnderstanding of containerization technologies, preferably Docker and KubernetesFamiliarity with automation tools such as Terraform, Ansible, and HelmExperience with programming languages and comfortable working in Linux environmentsA degree in computer science, engineering, or equivalent experience As a key member of the site reliability team, the remote Incident Commander will manage incident response across various organizations, ensuring effective classification, documentation, and resolution of incidents while collaborating with cross-functional teams to enhance service delivery and prevent future disruptions.Key responsibilitiesLead real-time incident management and enhance collaboration with Incident Commanders, Customer Support, and Engineering teamsDevelop and improve practices, frameworks, and processes for incident management and service deliveryManage Root Cause Analysis documentation and communicate effectively with stakeholders regarding incident status and resolutionsRequired qualificationsExperience in incident management or a similar roleUnderstanding of containerization technologies, preferably Docker and KubernetesFamiliarity with automation tools such as Terraform, Ansible, and HelmExperience with programming languages and comfortable working in Linux environmentsA degree in computer science, engineering, or equivalent experience ## Related Videos - [Docker network without Docker](https://www.wearedevelopers.com/videos/1418-docker-network-without-docker) - [Applying Agile Principles to Incident Management ](https://www.wearedevelopers.com/videos/101-applying-agile-principles-to-incident-management) - [Dev & Test in the Cloud? Deploy your cloud environments with Ansible & Terraform](https://www.wearedevelopers.com/videos/1607-dev-test-in-the-cloud-deploy-your-cloud-environments-with-ansible-terraform) - [Docker Compose: Rediscovered](https://www.wearedevelopers.com/videos/1978-docker-compose-rediscovered) - [Docker exec without Docker](https://www.wearedevelopers.com/videos/1094-docker-exec-without-docker) - [Docker build without Docker](https://www.wearedevelopers.com/videos/100114-docker-build-without-docker) ## Related Articles - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs) - [Mastering Remote Work: Tips for Developers](https://www.wearedevelopers.com/magazine/558-mastering-remote-work-tips-for-developers) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Remote Work: Best Practices for Developers](https://www.wearedevelopers.com/magazine/315-remote-work-best-practices-for-developers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Walking Into The Era of Supply Chain Risks](https://www.wearedevelopers.com/magazine/106-walking-into-the-era-of-supply-chain-risks)