Infrastructure Engineer at Deliverect
Jakarta
—
Jun 28, 2026
Jakarta
Jul 21, 2026
What this job asks for AI summary
A DevOps/platform engineering role focused on maintaining and scaling cloud infrastructure for a global microservices platform. Day-to-day work spans Kubernetes and Docker operations, Terraform-based infrastructure automation, CI/CD pipeline development, observability tooling, database management, and disaster recovery — with participation in on-call incident response. Suited to engineers with solid hands-on experience across AWS or GCP, container orchestration, and GitOps practices.
Mid level · 4+ years · Remote
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 14,300 people nationally plausibly meet what this posting asks for (software developers). range 8,600–21,400
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $135,980 (middle half $105,210–$171,980).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (11)
SOC classification is Medium confidence: the role is titled as a Cloud Platform / DevOps engineer and the day-to-day work spans both writing infrastructure-as-code / automation (pointing to 15-1252 Software Developers) and operating/maintaining infrastructure (pointing to 15-1244). The balance of responsibilities — Terraform, GitOps, CI/CD pipeline development, Python development, and building monitoring tooling — tips toward 15-1252, but 15-1244 is a credible runner-up.
Seniority is assessed as Mid despite the 4+ year overall requirement: the role carries no explicit 'Senior' title or framing, the Kubernetes/Docker gate is only 2+ years, and the scope (team contributor, on-call rotation, collaboration with engineering) is consistent with a mid-level individual contributor rather than a senior owner of a domain.
AWS and GCP are presented as alternatives ('specifically AWS or GCP'); AWS is listed first and is the primary name, with GCP in alternatives.
GitHub Actions, CircleCI, and ArgoCD are listed as interchangeable CI/CD tool examples ('such as'); GitHub Actions is named first.
New Relic, Grafana, and Datadog are listed as interchangeable monitoring tool examples ('like'); all three appear only in the requirements section but are framed with 'like', indicating substitutability — captured as one preferred skill with alternatives.
MongoDB is explicitly called out as 'a plus' within the database requirement sentence, so it is marked preferred.
Postman and Insomnia are listed as API client examples under the requirements section with 'like'; treated as a single preferred skill (they are tooling aids, not core platform gates).
The degree requirement accepts 'equivalent work experience', so the degree requirement is set to None.
No compensation figures are provided in the posting.
The posting does not specify a country or region for this remote role; the US-based flag defaults to true per caller instruction, and no metro is inferred.
Caller marked this a fully-remote role — scored against the national candidate pool.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.