ZUS COFFEE Hiring! Full Time Regional DevOps Engineer in - Ricebowl

Experience Requirements

• 4–7+ years of experience in Site Reliability Engineering, DevOps, or Production Engineering
• Demonstrated experience supporting a distributed microservices architecture in production
• Experience operating high-traffic production systems — and owning what happens when they fail
• Experience participating in on-call rotations and leading incidents through to resolution and RCA

Nice to Have

• Experience managing multi-region infrastructure
• Experience operating high-scale microservices systems
• Knowledge of service mesh architectures
• Experience with AWS ECR, Lambda, or event-driven architecture
• Experience with AWS cost optimisation
• Background in F&B, retail, or operational-heavy consumer businesses with peak-hour traffic patterns

Position Responsibilities

We are looking for a DevOps Engineer to own the reliability, availability, and operational health of our production platform — the AWS infrastructure and Go and Node.js microservices that our customers and stores depend on every day.

This is not a "keep the servers running" role. This is a reliability ownership role responsible for how our services are deployed, observed, scaled, and recovered across multiple regions.You will be the person who makes production predictable — defining what "healthy" means through SLOs, building the systems that detect problems before customers do, and eliminating the classes of incidents that keep coming back.

What You Will Own

• Production reliability and availability of services across multiple regions: uptime, latency, and performance under high traffic
• Service Level Objectives (SLOs), Service Level Indicators (SLIs), and error budgets — defining them, tracking them, and using them to drive engineering decisions
• Incident response and root cause analysis (RCA) for production issues, including blameless postmortems and the preventive actions that follow
• AWS infrastructure for containerised services: ECS, Application Load Balancers, Auto Scaling, CloudWatch, and VPC networking
• CI/CD pipelines for microservices — deployment reliability, infrastructure consistency, and the reduction of manual intervention
• Infrastructure as Code (Terraform / CloudFormation) and the automation of recurring operational tasks
• Observability across the platform: metrics, logging, distributed tracing, dashboards, and alerting
• Service resilience patterns in partnership with development teams: health checks, circuit breakers, retry strategies, fault tolerance, redundancy, and graceful degradation
• Operational runbooks and on-call response processes

Required Technical Skills

• Extensive hands-on experience managing production workloads on AWS
• Hands-on expertise with AWS ECS (Fargate and EC2 launch types) and Docker containerisation
• Proficiency in VPC configuration, Application Load Balancers (ALB), and Network Load Balancers (NLB)
• Experience managing Auto Scaling to sustain high-traffic production environments
• Proven ability to support and optimise distributed microservices written in Go and Node.js
• Experience automating infrastructure with Terraform or CloudFormation
• Skilled in building internal tools and automation scripts using Go, Python, and Bash
• Hands-on experience building and maintaining CI/CD pipelines for microservices
• Strong working knowledge of observability tooling: Prometheus / Grafana, AWS CloudWatch, and OpenTelemetry
• Practical understanding of SLOs, SLIs, error budgets, and resilience patterns (circuit breakers, retries, health checks, graceful degradation)

Required Engineering Collaboration Skills

• Ability to work with development teams to improve service architecture — influencing how services are built, not just how they are deployed
• Comfort leading incident response under pressure and communicating clearly to both engineers and non-technical stakeholders
• Ability to run blameless postmortems that produce real preventive actions, not just a document
• Strong written communication — runbooks, RCAs, and infrastructure decisions should be legible to the next engineer on call
• Self-directed: able to spot reliability risks, prioritise them, and drive fixes without being told where to look.