Senior Middleware & EKS Workload Engineer

Job Description

• Skill Set :

  Kubernetes,AWS EKS,Container Platform Operations,Middleware Support & Modernization

• Total Experience :

  10.00 to 15.00 Years

• No of Openings :

  1

• Job Post Date :

  25/08/2026

• Job Expiry Date :

  30/11/2026

• Domain :

  IT

• Location :

  PUNE [India]

• Job Reference No :

  4103581

Job Summary

We have an exciting opportunity with one of our prestigious clients for a Senior Middleware & EKS Workload Engineer position based in Pune (Sharada Location).

Role Highlights:

• Experience: 8-15 Years
• Location: Pune (Sharada)
• Shift Window: Between 9:00 AM and 9:00 PM
• Focus Area: AWS EKS, Kubernetes, Container Platform Operations, Middleware Support & Modernization

Key Skills Required:

• Strong hands-on experience with Amazon EKS/Kubernetes
• Expertise in Docker, Helm, YAML, GitOps/ArgoCD, CI/CD
• Production support and troubleshooting experience in cloud/container environments
• AWS knowledge including IAM, RBAC, VPC, CloudWatch
• Hands-on experience with middleware technologies such as:
  • WebSphere
  • WebLogic
  • Liberty
  • BPM
  • API Gateway / Apigee
• Experience in incident management, RCA, automation, patching and operational support

What We Are Looking For:

Professionals who have worked on both:

• Modern container platforms (EKS/Kubernetes)
• Traditional middleware environments (WebSphere/WebLogic/Liberty)

Senior Middleware & EKS Workload Engineer

Experience: 8-15 years

Role focus: 80% EKS / Containers / Kubernetes Workload Operations; 20% Legacy Middleware Upkeep, Maintenance & Future Transition

Role Summary

We are seeking a senior hands-on engineer with 10-12 years of experience across middleware, application hosting, infrastructure operations, and modern container platforms. The primary delivery focus is Amazon EKS, Kubernetes, container workload operations, automation, observability, and production reliability, while continuing to support legacy middleware platforms during migration and modernization.

The ideal candidate should have strong real-world EKS/Kubernetes administration and troubleshooting experience, along with sufficient hands-on WebSphere, Liberty, WebLogic, BPM, and/or API Gateway experience to maintain current platforms and support the transition toward modern hosting patterns.

Must-Have: EKS / Containers / Kubernetes

• Hands-on Kubernetes administration: Pods, Deployments, StatefulSets, DaemonSets, Services, Ingress, DNS, ConfigMaps, Secrets, PV/PVC, StorageClass, Network Policies, and Autoscaling.
• Amazon EKS workload operations: namespaces, access controls, IAM/RBAC, node health, workload placement, scaling, deployments, upgrades, rollbacks, and day-2 support.
• Container image lifecycle using Docker or equivalent tooling, including build, tagging, scanning, deployment, and troubleshooting.
• Practical Helm, Kubernetes YAML, GitOps/ArgoCD, and CI/CD integration experience.
• Strong troubleshooting across pod crashes, image pulls, service discovery, ingress/routing, DNS, networking, storage, scheduling failures, failed rollouts, and application availability.
• AWS operating knowledge covering VPC networking, routing, IAM, CloudWatch/observability, security groups/firewall coordination, and production support practices.

Must-Have: Automation, Reliability & Operations

• Automation using Shell scripting, Python basics, YAML, Helm, Ansible, Terraform, and CI/CD pipeline hooks.
• Production operations experience covering incident, change and problem management, patching, vulnerability remediation, audit evidence, service requests, and runbooks.
• Strong observability mindset covering logs, metrics, alerts, dashboards, health checks, capacity, error patterns, and incident-learning actions.
• Ability to provide on-call support and drive L3 troubleshooting through RCA and corrective/preventive actions.

Legacy Middleware / Transition Skills

• Working hands-on knowledge of WebSphere Application Server, WebSphere Liberty, WebLogic, BPM, and API Gateway platforms such as Apigee or equivalent.
• JVM monitoring/tuning, heap and thread dump collection/analysis, certificate lifecycle, CSR generation, certificate deployment, and validation.
• Middleware patching, upgrades, vulnerability remediation, OS/DB maintenance coordination, service requests, and production support.
• Understanding of REST, SOAP, APIs, JSON, XML, OAuth/token concepts, Postman-based validation, and API troubleshooting.

Key Responsibilities

• Own day-2 operations for EKS/Kubernetes workloads, including deployment support, access, namespace management, health checks, scaling, configuration, troubleshooting, and controlled releases.
• Build, deploy, upgrade, rollback, and troubleshoot workloads using container images, Kubernetes manifests, Helm, ArgoCD/GitOps, kubectl, AWS CLI, and CI/CD pipelines.
• Perform L3 troubleshooting across pods, services, ingress, DNS, networking, secrets, storage, nodes, scheduling, releases, and workload performance.
• Partner with application and platform teams to modernize VM/middleware-hosted workloads into containerized deployment models.
• Maintain legacy middleware during transition, including runtime support, JVM analysis, certificate management, patch/upgrade coordination, vulnerability remediation, and production issue support.
• Apply secure practices across IAM, RBAC, secrets, TLS/certificates, patching, vulnerabilities, audit controls, and least-privilege access.
• Drive automation and standardization through reusable scripts, Helm patterns, runbooks, GitOps workflows, dashboards, and reduced manual intervention.
• Maintain runbooks, SOPs, RCA documents, KT material, migration notes, and support documentation.

Expected Profile

• 8-15 years in infrastructure, middleware, application hosting, platform engineering, or production operations.
• Strong hands-on experience with Kubernetes/EKS, containers, automation, and cloud-based workload operations.
• Proven production support experience with incident/change discipline, service ownership, vulnerability remediation, patching, audit support, and operational controls.
• Comfortable supporting a hybrid transition model where legacy platforms remain operational while future delivery centers on EKS, containers, automation, and modern platform engineering.
• Ideal background: a middleware or infrastructure engineer who has successfully expanded into Kubernetes/EKS operations and can support modernization at scale without losing control of existing production platforms.

Tools & Ways of Working

• Kubernetes/EKS: kubectl, eksctl, AWS CLI, Helm, ArgoCD, GitOps, YAML, Docker/container runtime.
• Cloud/Security: AWS, IAM, RBAC, VPC networking, DNS/routing, CloudWatch, secrets, certificates, vulnerability remediation.
• Automation/IaC: Shell, Python basics, Ansible, Terraform, Helm templates, CI/CD integration.
• Operations: JIRA, Confluence, ServiceNow, Agile, ITIL, Incident/Change/Problem Management, RCA, audit evidence.
• Legacy Middleware: WebSphere, Liberty, WebLogic, BPM, Apigee/API Gateway, JVM dumps, certificates, Postman, REST/SOAP/XML/JSON/OAuth.

Behavioural Expectations

• Strong ownership and ability to independently drive technical issues to closure.
• Clear technical communication with application teams, peers, service owners, and leadership.
• Ability to guide peers, document learnings, and support cross-skilling from legacy middleware to containers.
• Process-oriented approach to change discipline, incident response, RCA quality, audit controls, and production stability.
• Self-driven learning across Kubernetes, AWS, automation, middleware, and API platforms.

Hiring Emphasis

Please prioritize genuine hands-on EKS/Kubernetes workload operations, production troubleshooting, automation, GitOps/Helm exposure, observability, and secure operational practices. Legacy middleware experience remains required as transition value, but it is not the primary hiring focus. Candidates who are only traditional middleware administrators without practical container/EKS depth should not be considered a strong fit. Likewise, candidates with Kubernetes/EKS experience but no hands-on middleware experience should not proceed.