Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Unisongroup

Cloud Engineer ( Google Cloud Engineer)

  • Seen live on Unisongroup's site today
  • Mid level
Pay
Not stated
Location
Singapore, Singapore, Singapore
Open for
5 days
First seen
Oct 30, 2026
Apply on Unisongroup's site (opens in a new tab)

Posting record

No flags

Open 5 days

The posting's record, oldest first
  1. Ghostless first sees this listing
  2. Last checked: still up
How we know

It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.

Ghostless records the day it first sees a posting, so a repost can't reset its age.

Last checked Nov 4, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What the posting discloses

Not stated: Pay, real vacancy, AI screening.

Why these three

Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the role

Job Summary

We are seeking a skilled and proactive GCP Cloud Engineer with strong expertise in Google Kubernetes Engine (GKE) and Google Cloud Dataproc . The ideal candidate will be responsible for designing, implementing, and managing cloud infrastructure and data processing pipelines on Google Cloud Platform. This role will support scalable deployment of applications and big data workflows, ensuring high availability, security, and performance.

Key Responsibilities

  • Design, deploy, and manage containerized applications using Google Kubernetes Engine (GKE) .
  • Implement and optimize Dataproc clusters for batch and stream data processing.
  • Develop and maintain CI/CD pipelines for container-based workloads.
  • Collaborate with development and data engineering teams to design scalable, cloud-native solutions.
  • Monitor and troubleshoot cloud infrastructure, ensuring high availability and reliability.
  • Automate infrastructure provisioning using tools like Terraform , Deployment Manager , or Ansible .
  • Ensure security and compliance standards are met across all GCP environments.
  • Optimize performance and cost-efficiency of cloud resources.
  • Participate in incident response and root cause analysis.

Requirements

Required Skills and Qualifications

  • Hands-on experience in cloud engineering with GCP.
  • Strong experience with GKE (setup, maintenance, monitoring, scaling).
  • Proficiency in Google Cloud Dataproc , including Spark and Hadoop job management.
  • Solid understanding of Kubernetes concepts , Helm, and container orchestration.
  • Familiarity with CI/CD tools (e.g., Jenkins, GitLab CI/CD, Cloud Build).
  • Scripting and automation skills in Python , Shell , or similar.
  • Experience with Infrastructure as Code (IaC) tools like Terraform.
  • Strong knowledge of cloud networking, IAM, monitoring (Stackdriver/Cloud Monitoring), and logging.

Preferred Qualifications

  • GCP Professional Cloud Architect or GCP DevOps Engineer certification.
  • Experience with other GCP services like BigQuery, Cloud Functions, Pub/Sub, etc.
  • Background in data engineering or DevOps practices.

Something wrong with this posting?