🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
About the Role : We are seeking a highly experienced Senior Platform Engineer to lead a complex infrastructure modernization initiative involving on-premises Kubernetes, Enterprise Linux, and GitLab CI/CD migration. This role requires strong hands-on expertise in on-prem environments, deep technical ownership, and the ability to independently drive large-scale migrations end-to-end. Key Responsibilities : - Lead and execute RKE1 to RKE2 Kubernetes migration, including cluster setup, workload migration, and networking reconfiguration. - Drive GitLab migration from on-prem to gitlab.com, including repositories, CI/CD pipelines, runners, and container registry transition. - Design and implement end-to-end GitLab CI/CD pipelines (build, test, security scans, deployment, and rollback strategies). - Manage and harden SUSE Linux Enterprise Server (SLES) environments. - Act as a technical escalation point for post-migration issues, including application-level debugging inside containers. - Deploy and manage Kubernetes components including Rancher, Longhorn, MetalLB, and Nginx Ingress. - Implement observability solutions using Prometheus, Grafana, and Loki. - Establish Infrastructure as Code (IaC) practices using Terraform/Ansible. - Create migration plans, documentation, and runbooks. Must-Have Skills (Non-Negotiable) : - Hands-on experience with RKE1 to RKE2 migration (mandatory). - Strong experience with on-prem Kubernetes (VMware-based environments). - Deep expertise in GitLab CI/CD pipeline design and GitLab administration. - Proven experience in migrating GitLab from on-prem to gitlab.com. - Production experience with SUSE Linux Enterprise Server (SLES). - Ability to debug issues beyond Kubernetes (container/application-level troubleshooting). Core Technical Skills : - Kubernetes (RKE1, RKE2), Rancher Manager. - GitLab CI/CD, GitLab Runner, Container Registry. - SLES (zypper, systemd, security hardening). - Networking & Storage : MetalLB, Nginx Ingress, Longhorn. - Observability : Prometheus, Grafana, Loki. - IaC : Terraform / Ansible. - Scripting : Bash, Python. - CI/CD practices, branching strategies, and deployment patterns (blue-green, canary). Good to Have : - Experience with air-gapped/on-prem Kubernetes environments. - Exposure to AWS services (EKS, EC2, S3, IAM, etc. - GitOps tools such as Argo CD. - Experience with JFrog Artifactory migration. - Knowledge of OpenShift migrations (OCP3 OCP4). What Were Not Looking For : - Candidates with only cloud-managed Kubernetes (EKS/AKS/GKE) experience. - Limited exposure to GitLab (only deployment, not full CI pipeline design). - No hands-on experience with SLES. - Superficial or UI-level experience with Kubernetes upgrades. Work Details : - Type : Full-time Contract. - Duration : 6 months+ (extendable). - Location : Remote. - Availability : Overlap with EST hours required. - Joining : Immediate / Short notice preferred. .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.