AWSCloudKubernetesTerraformGoCommunicationRemote Work
About this role
Role Overview
Platform Tooling & Automation (25%) — Contribute to and maintain internal Go services, CLIs, and automation pipelines that reduce manual toil and eliminate support dependencies
Self-Service Enablement (25%) — Create documentation, runbooks, and knowledge bases that allow feature teams to operate independently; identify gaps in existing materials and close them
Incident Response (20%) — Participate in on-call rotations, execute and refine incident response procedures, contribute to postmortems, and help improve escalation playbooks
Standards & Architecture (20%) — Learn and apply technical standards and operational frameworks; contribute to RFC and PRD reviews as you develop architectural instincts
Service Ownership Coaching (10%) — Support feature teams in building operational maturity, scorecard compliance, and self-service capability
Requirements
3–5 years in DevOps/SRE or related cloud infrastructure engineering roles
Go proficiency: you've written Go in a professional or serious project context, understand the language well enough to own and debug production code, and are actively developing your skills
Kubernetes fundamentals: hands-on experience deploying, troubleshooting, and operating workloads in Kubernetes; comfortable with manifests, RBAC, networking basics, and cluster observability
Cloud & Infrastructure: solid AWS experience and working knowledge of Terraform; exposure to multi-cloud environments is a plus
Operational instincts: experience with incident response, on-call, and postmortem processes; you know what good looks like even if you're still building toward it
Software engineering fundamentals: you write code to solve operational problems, not just to script one-offs; you care about testability, readability, and maintainability
Communication & documentation: strong written communication; able to translate operational complexity into clear runbooks and team-facing guidance
Collaborative mindset: you ask good questions, seek feedback, and default toward enabling others over owning work yourself