Senior DevOps Engineer — AWS, Terraform & ECS/Fargate

EthBerry; Tangerang; Hybride; IDR 650 000 000 - 1 000 000 000; Plein temps

Avantages offerts par ce poste

14 vacation days

7 sick days

Public holidays in residence

Laptop provided

Paid software licences

Flexible schedule

Résumé du poste

EthBerry is seeking a senior infrastructure engineer to design, provision, deploy, and operate production cloud environments for client applications. You will own infrastructure changes from architecture through delivery, observability, recovery, and operational documentation.

The role balances security, reliability, delivery speed, and cost relative to client scale and risk. Responsibilities include designing secure AWS environments, building Terraform modules, packaging services with Docker

Qualifications

• 5+ years in DevOps, platform engineering, cloud engineering, or SRE with ownership of production AWS
• Strong Terraform experience including modules, remote state, drift and failed-change recovery
• Production experience with Docker and ECS/Fargate
• Strong AWS networking and security fundamentals across VPC, ALB, IAM, SSO, and secrets
• Experience with RDS backups, upgrades, failover, observability

Responsabilités

• Design and evolve secure AWS environments for client products
• Build reusable Terraform modules and maintain safe planning and drift workflows
• Package services with Docker and operate on ECS/Fargate behind ALBs
• Operate RDS with backup and recovery procedures
• Establish CloudWatch logs, metrics, dashboards, alarms, and runbooks
• Build CI/CD with GitHub Actions and OIDC
• Explain infrastructure trade-offs and document decisions
• Participate in production support under agreed terms

Connaissances

Strong English communication

Cloud infrastructure design

CI/CD design

Observability & incident response

Cost optimization

Outils

Terraform

Docker

ECS/Fargate

AWS networking & security

GitHub Actions

CloudWatch

Description du poste

We are looking for a senior infrastructure engineer to design, provision, deploy, and operate production cloud environments for client applications. You will own infrastructure changes from architecture and review through delivery, observability, recovery, and operational documentation. The role requires balancing security, reliability, delivery speed, and cost while keeping each solution proportionate to the client's scale, operational needs, and risk.

What you will do

• Design and evolve secure AWS environments for client products.
• Build reusable Terraform modules and maintain safe planning, review, remote-state, and drift workflows.
• Package services with Docker and operate them on ECS/Fargate behind ALBs, with images stored in ECR.
• Operate RDS with appropriate backup, upgrade, failover, observability, and recovery procedures.
• Design VPC boundaries, routing, security groups, IAM roles, workforce SSO, and secrets management with least privilege.
• Build GitHub Actions pipelines using OIDC, environment approvals, immutable artefacts, and reliable rollback.
• Establish CloudWatch logs, metrics, dashboards, alarms, and actionable runbooks.
• Improve reliability, security, and AWS cost without introducing unnecessary platform complexity.
• Explain infrastructure trade-offs to engineers and clients and document decisions clearly.
• Participate in production support under explicitly agreed engagement terms; no unstated 24/7 availability is assumed.

Required experience

• 5+ years in DevOps, platform engineering, cloud engineering, or SRE, including ownership of production AWS systems.
• Strong Terraform experience including reusable modules, remote state, review workflows, drift, and failed-change recovery.
• Production experience with Docker and ECS/Fargate.
• Strong AWS networking and security fundamentals across VPC, ALB, IAM, SSO or federation, and secrets.
• Experience operating relational databases on RDS and designing backup and recovery procedures.
• Ability to build secure CI/CD with GitHub Actions and short-lived AWS credentials through OIDC.
• Practical observability and incident-response experience using CloudWatch or equivalent tools.
• Strong written and spoken English for engineering and client communication.

Useful, not required

• AWS Organizations, Control Tower, multi-account landing zones, or IAM Identity Center.
• Blue/green ECS deployments, OpenTelemetry, or practical FinOps.
• Bash, Python, or TypeScript for operational tooling.
• EKS or Kubernetes for client engagements where Fargate is not appropriate.
• Previous consultancy, outsourcing, or direct client-facing delivery.

What we offer

• Full-remote work with a flexible schedule outside agreed client and team overlap.
• 14 paid vacation days and 7 paid sick days per year.
• Official public holidays in your country of residence in addition to the paid days above.
• Work from your own laptop; EthBerry provides the project accounts and paid software licences required for the engagement.
• Compensation agreed individually based on relevant experience.
• Authority to reject unsafe access practices, including shared accounts and long-lived cloud credentials.
• No assumed 24/7 availability; any on-call scope and response expectations are agreed separately for the engagement.
• The contract does not include health insurance, company hardware, or office-based benefits.

Hiring process

• Application review.
• HR screening — 30 minutes.
• Technical interview — 75 minutes. We discuss one production platform, one incident, one infrastructure decision, and the operational trade-offs involved.
• Unpaid take-home assignment — strictly capped at 4–6 hours. Produce a written design for a NestJS API on ECS/Fargate with Terraform and GitHub Actions OIDC, including RDS, IAM boundaries, secrets, deployment and rollback, observability, backups, reliability risks, and one cost trade-off. No AWS account, real deployment, or candidate-funded resource is required.
• Assignment review — 75 minutes. You walk through the design and adapt it to one changed client requirement.
• Final cultural-fit interview — 30 minutes.

AI tools are allowed. Their use must be disclosed briefly, and you must be able to explain and defend every submitted decision. The assignment is not used in production.