Kubernetes/Linux Engineer for support on testing
Budget: ₹750 – ₹1,250 INR
We are looking for a highly experienced Kubernetes/Linux engineer to test a confidential technical environment involving Kubernetes ingress and production-style troubleshooting.
You must be very comfortable with Linux, Kubernetes, kubectl, and understand what realistic command outputs, remediation paths, and incident workflows should look like inside a large engineering organisation. We are specifically looking for someone who has worked in real production environments and has previous on-call or incident-response experience.
This is not an implementation or support role. Your job will be to act as an experienced engineer, work through a technical setup, and give direct feedback on and whether the workflow reflects how things are actually handled. We especially want someone confident enough to say, “this is not how an engineer/team would do this,” and explain why.
Full details, access, and commercial context will only be shared after NDA signature.
This is a short-term role: we expect either 0.5–1 day initially, then a further 0.5 day the following week. Weekend work is fine. If the engagement goes well, this may become an ongoing arrangement for a couple of days per month across multiple projects.
Ideal background
• Strong Linux command-line skills
• Strong Kubernetes production experience
• Experience debugging ingress / service / endpoint / readiness / DNS issues
• Prior on-call or incident-response experience
• Able to provide clear written feedback and practical suggestions
To apply, please include
• Your years of Kubernetes production experience
• A short note on your on-call/incident background
• Which Kubernetes environments/controllers you’ve used
• One example of a relevant production incident you’ve worked on
You must be very comfortable with Linux, Kubernetes, kubectl, and understand what realistic command outputs, remediation paths, and incident workflows should look like inside a large engineering organisation. We are specifically looking for someone who has worked in real production environments and has previous on-call or incident-response experience.
This is not an implementation or support role. Your job will be to act as an experienced engineer, work through a technical setup, and give direct feedback on and whether the workflow reflects how things are actually handled. We especially want someone confident enough to say, “this is not how an engineer/team would do this,” and explain why.
Full details, access, and commercial context will only be shared after NDA signature.
This is a short-term role: we expect either 0.5–1 day initially, then a further 0.5 day the following week. Weekend work is fine. If the engagement goes well, this may become an ongoing arrangement for a couple of days per month across multiple projects.
Ideal background
• Strong Linux command-line skills
• Strong Kubernetes production experience
• Experience debugging ingress / service / endpoint / readiness / DNS issues
• Prior on-call or incident-response experience
• Able to provide clear written feedback and practical suggestions
To apply, please include
• Your years of Kubernetes production experience
• A short note on your on-call/incident background
• Which Kubernetes environments/controllers you’ve used
• One example of a relevant production incident you’ve worked on