Netomi DevOps Engineer I: remote role with Kubernetes, ECS and Terraform

Netomi is advertising a remote DevOps position connected with Gurugram. At least two years of related experience is required, and the employer specifically makes Amazon ECS and Terraform experience mandatory.

Recruitment overview

OrganisationNetomi
Post / roleDevOps Engineer I
Notification / job IDffe81537-5d1b-437e-a5e8-43546aa8c655
Job locationGurugram, India — remote
Work arrangementRemote
Educational qualificationNo specific degree requirement stated
Experience requiredAt least 2 years in DevOps or a related field
Salary / stipendNot disclosed for India
Last date to applySee official notice

About the remote DevOps position

Netomi’s DevOps Engineer I role is associated with Gurugram and marked full-time remote. The engineer collaborates with software-development teams to deploy, run and continuously monitor systems. The notice requests at least two years in DevOps or a related field. This is an operational engineering opportunity requiring hands-on infrastructure experience rather than a general cloud-certification training placement.

Kubernetes administration and access control

The work includes designing, deploying and managing Kubernetes clusters, improving their scalability and enforcing role-based access control. The engineer is expected to understand how access policies and cluster operations affect a running service. Helm charts are another named responsibility, including their maintenance, versioning and use in deployment strategies. These are practical production tasks, not only familiarity with container terminology.

Deployment pipelines and service meshes

Netomi names Jenkins, ArgoCD and Spinnaker as examples of CI/CD tooling for building and improving delivery pipelines. Service-mesh work may use Istio, Linkerd or a similar system for discovery, traffic management, observability and secure communication. The engineer also automates infrastructure and debugging tasks using scripting languages such as Python, Ruby or Go.

Mandatory experience and tools

At least two years of relevant experience is specified. Crucially, hands-on Amazon ECS and Terraform experience is expressly mandatory in the requirements; it should not be overlooked because Kubernetes occupies much of the description. The notice also expects cloud familiarity, networking, infrastructure management and system-design understanding. A particular degree is not specified in the reviewed advert.

Additional resilience-engineering skills

Chaos and resilience engineering are described as bonus areas. The notice gives tools such as Chaos Monkey, LitmusChaos and Gremlin as examples, with an emphasis on testing how systems behave under failure. This is an additional advantage rather than a replacement for the core deployment, cluster and infrastructure experience. Candidates should label laboratory experiments separately from production incident or operational work.

Compensation and working arrangements to confirm

The employer does not publish an India salary range, closing date or fixed interview-round sequence for this role. Although continuous monitoring is part of the work, the advert does not specify an on-call rota or shift allowance. Ask about incident coverage, escalation, working hours and any office expectations directly rather than treating an assumption about DevOps work as an announced employment condition.

Applying on the official Lever form

Use the Netomi application for requisition ffe81537-5d1b-437e-a5e8-43546aa8c655. Make relevant production experience easy to identify, especially ECS, Terraform, Kubernetes and deployment automation. Include accurate employment dates and describe what you owned within a team. The official employer form determines whether submissions are still being accepted; no third-party closing date has been inferred.

Practical preparation: explain a safe deployment

A useful experience example can explain what changed, how it was tested, the rollback path and what monitoring confirmed afterwards. For infrastructure as code, discuss state handling and review controls only where you have actually worked with them. This is application guidance, not an announced Netomi assessment. Avoid disclosing access keys, internal network details or confidential operational records in an example.

Questions about the engineering environment

Clarify how ECS and Kubernetes divide the workload, which cloud resources Terraform manages and who owns incident response. Ask how cluster access is approved and reviewed, and how service-mesh changes reach production. Those questions help establish the actual environment and responsibility level without presuming that every example tool in the advert is deployed together in one stack.

Relevant skills

  • Kubernetes
  • Amazon ECS
  • Terraform
  • Helm
  • CI/CD
  • Scripting

Important links

Official notification / job descriptionOpen official page
Official application / recruitment pageOpen official page

Read the complete official notice before applying. Availability and requirements can change.

For corrections, see our editorial policy and contact information.