The role
Make infrastructure understandable, reproducible, and observable. Help the team ship changes with clear verification, controlled access, and a practical recovery path.
What you’ll do
- Design and maintain reproducible development, test, and deployment environments.
- Improve CI/CD workflows, release checks, and rollback procedures.
- Implement observability for reliability, performance, and infrastructure cost.
- Manage infrastructure changes through code, reviews, and documented access boundaries.
- Investigate operational incidents and turn findings into durable improvements.
- Collaborate with engineering on isolated execution, secrets handling, and dependency maintenance.
What you bring
- Hands-on experience operating cloud infrastructure and Linux systems.
- Experience with containers, networking, CI/CD, and infrastructure as code.
- Practical scripting skills and a methodical approach to debugging distributed systems.
- Understanding of least privilege, secret management, backups, and recovery.
- Ability to balance reliability, delivery speed, and operational complexity.
- Clear runbooks and effective communication during remote incident response.
Nice to have
- Experience with Kubernetes, Terraform, or comparable orchestration and provisioning tools.
- Familiarity with sandboxed execution or multi-tenant systems.
- Experience setting service objectives and improving cost visibility.
Your first priorities
- Map the environment and identify the largest operational risks.
- Improve a deployment or recovery workflow with reproducible checks.
- Deliver useful observability and a prioritized reliability roadmap.
Working remotely
This is a remote role. Eligible hiring locations, working hours, collaboration overlap, and engagement terms will be discussed during the hiring process. We value clear writing, reliable follow-through, and making work visible to teammates.
How to apply
Share your relevant experience, a CV or professional-profile link, and a short example of work that shows how you approach problems. You do not need to match every nice-to-have to introduce yourself.
Read the Privacy Policy before providing personal information. Please do not include sensitive personal information or confidential work from a current or previous employer.