Senior DevOps Engineer at GTEMAS

Confirmed open

This role builds and maintains cloud infrastructure for GTEMAS clients, with responsibility for automation, scale and production security.

GTEMAS

Search jobs by company: GTEMAS

Location: Remote
Advertised region: VN / Vietnam
Employment: CONTRACTOR
Work arrangement: remote
Technologies: Python, AWS, Azure, Kubernetes, Docker

See how to apply

Save job — free account Saved jobs

Create a free application profile — Keep your skills and projects in a reusable profile. Private by default; you choose when to share. Apply for this job directly with the employer.

By continuing, you agree to processing needed to manage your account and profile. Privacy policy

Role overview

As a Senior DevOps Engineer, you will design, build, and maintain our clients' cloud infrastructure. You will focus on automation, scalability, and security of production environments using Infrastructure as Code (IaC).

Responsibilities

Manage infrastructure as code through Terraform or CloudFormation.
Build delivery pipelines with Jenkins, GitHub Actions or GitLab CI and operate Kubernetes clusters with Helm on EKS, AKS or GKE.
Implement monitoring and logs through Prometheus, Grafana or ELK; apply cloud security and compliance practices.

Qualifications

At least five years in DevOps or site reliability engineering, with substantial AWS or Azure experience.
Ability to script in Python or Bash and operate Docker containers.
Understanding of networking, load balancing and security protocols, plus monitoring and incident response.

Technology in this role

Python: Python AWS Azure Kubernetes .
AWS: Python AWS Azure Kubernetes .
Azure: Python AWS Azure Kubernetes .
Kubernetes: Python AWS Azure Kubernetes .
Docker: Python AWS Azure Kubernetes .
Terraform: Manage infrastructure as code through Terraform or .
Bash: Ability to script in Python or Bash and operate Docker .
GitHub Actions: Build delivery pipelines with Jenkins, GitHub Actions or GitLab CI and operate Kubernetes clusters with Helm on EKS, AKS or .
Jenkins: Build delivery pipelines with Jenkins, GitHub Actions or GitLab CI and operate Kubernetes clusters with Helm on EKS, AKS or .
Prometheus: Implement monitoring and logs through Prometheus, Grafana or .
Grafana: Implement monitoring and logs through Prometheus, Grafana or .

Role-specific candidate guide

Preparation notes based on the employer’s stated responsibilities and qualifications.

Understanding the scope. This Senior DevOps Engineer position at GTEMAS is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “As a Senior DevOps Engineer, you will design, build, and maintain our clients' cloud infrastructure. You will focus on automation, scalability, and security of production environments using Infrastructure as Code (IaC).” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the platform and infrastructure area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Manage infrastructure as code through Terraform or CloudFormation.”; “Build delivery pipelines with Jenkins, GitHub Actions or GitLab CI and operate Kubernetes clusters with Helm on EKS, AKS or GKE.”; “Implement monitoring and logs through Prometheus, Grafana or ELK; apply cloud security and compliance practices.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.

How to read the requirements. The listed qualifications include “At least five years in DevOps or site reliability engineering, with substantial AWS or Azure experience.”; “Ability to script in Python or Bash and operate Docker containers.”; “Understanding of networking, load balancing and security protocols, plus monitoring and incident response.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.

Technology and working evidence. The technology terms associated with this listing are Python, AWS, Azure, Kubernetes, Docker. Treat this as a set of posting-derived signals, not a guarantee that every tool is.

About GTEMAS

GTEMAS (Global Tech Masters) presents itself as a global engineering partner and talent ecosystem. It connects businesses with software professionals to build digital products, scale delivery teams and support longer-term engineering partnerships. The company describes a model that combines technical assessment, structured delivery and professional development for its engineering community.

Its public materials highlight work across software engineering, quality, cloud and security, with an emphasis on measurable delivery, learning and client collaboration. A role at GTEMAS may serve a client engagement, so the specific product, customer context and day-to-day team can differ by assignment. Candidates should ask which project this vacancy supports and how responsibilities are divided between the GTEMAS team and the client.

Employer website