Platform Engineer at GTEMAS

Confirmed open

This GTEMAS role builds the internal platform that other engineering teams use to ship software. It spans middle and senior levels, with senior ownership of architecture and reliability practices.

GTEMAS

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

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.

Role overview

This GTEMAS role builds the internal platform that other engineering teams use to ship software. It spans middle and senior levels, with senior ownership of architecture and reliability practices.

Responsibilities

Develop CI/CD, environments and self-service tools; manage AWS, Azure or GCP infrastructure as code with Terraform and operate production Kubernetes.
Provide logs, metrics and tracing through Prometheus, Grafana or OpenTelemetry, set SLOs and support incident response and postmortems.
Automate operational toil; at senior level establish platform architecture and incident processes for the organization.

Qualifications

At least three years of platform, DevOps or SRE work for middle level or six for senior level, with production Terraform and Kubernetes experience.
Ability to script tools in Python, Go or Bash and operate a major cloud platform at scale.
Understanding of IAM, network policies and secrets, fluent English for runbooks and incidents, and practical use of AI-assisted operations; senior applicants need a record of platform or SLO design.

Technology in this role

Python: Python AWS Azure GCP Kubernetes .
AWS: Python AWS Azure GCP Kubernetes .
Azure: Python AWS Azure GCP Kubernetes .
GCP: Python AWS Azure GCP Kubernetes .
Kubernetes: Python AWS Azure GCP Kubernetes .
Go: Python AWS Azure GCP Kubernetes .
Terraform: manage AWS, Azure or GCP infrastructure as code with Terraform and operate production .
Bash: Ability to script tools in Python, Go or Bash and operate a major cloud platform at .
CI/CD: Develop CI/CD, environments and self-service .
Prometheus: Provide logs, metrics and tracing through Prometheus, Grafana or OpenTelemetry, set SLOs and support incident response and .
Grafana: Provide logs, metrics and tracing through Prometheus, Grafana or OpenTelemetry, set SLOs and support incident response and .

Role-specific candidate guide

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

Understanding the scope. This Platform 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: “This GTEMAS role builds the internal platform that other engineering teams use to ship software. It spans middle and senior levels, with senior ownership of architecture and reliability practices.” 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 “Develop CI/CD, environments and self-service tools; manage AWS, Azure or GCP infrastructure as code with Terraform and operate production Kubernetes.”; “Provide logs, metrics and tracing through Prometheus, Grafana or OpenTelemetry, set SLOs and support incident response and postmortems.”; “Automate operational toil; at senior level establish platform architecture and incident processes for the organization.”. 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 three years of platform, DevOps or SRE work for middle level or six for senior level, with production Terraform and Kubernetes experience.”; “Ability to script tools in Python, Go or Bash and operate a major cloud platform at scale.”; “Understanding of IAM, network policies and secrets, fluent English for runbooks and incidents, and practical use of AI-assisted operations; senior applicants need a record of…”. 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.

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