Jobs by Fastorial
Back to all jobs

AWS Cloud Devops Senior Infrastructure Lead

1 view
SopraSteria1NoidaHybrid

8-10 years

Posted 8 days ago

  • AWS
  • Docker
  • Kafka
  • Kubernetes
  • Microservices
  • PostgreSQL
  • Python
  • Terraform

The role is the technical lead for production operations within an international L1/L2/L3 organisation. They operate an existing AWS platform, understand its components and dependencies, and personally diagnose and resolve complex incidents. They work with the SDM, L1/L2, Build teams and specialist experts. The SDM organises and manages the service; L3 owns technical diagnosis and resolution. The role requires a hands-on Production/SRE profile with proven AWS expertise in production, an end-to-end view of the business application and its flows, and a high level of autonomy from the start to secure operations and prepare transitions.

Incidents and Service Restoration

  • Provide L3 support for complex incidents escalated by L2.
  • Handle P1/P2 incidents in the crisis bridge and provide technical diagnosis.
  • Investigate applications and flows end to end: front/back end, APIs, microservices, Kubernetes, middleware, networking, data and AWS services.
  • Analyse and correlate logs, metrics, events and changes to locate failures.
  • Understand business consequences and prioritise recovery actions.
  • Perform appropriate fixes or recovery operations, engage the required experts and verify service restoration.

Prevention and Operability

  • Lead RCA, document causes and define measures to prevent recurrence.
  • Define probes, metrics, thresholds and preventive checks based on component and flow knowledge.
  • Challenge Build teams on operability, configurations, observability, resilience and production risks.
  • Support the operational acceptance of new components.

Automation and Knowledge Transfer

  • Define and evolve technical standards and operating practices.
  • Standardise and automate recurring operations.
  • Structure runbooks, documentation and knowledge transfer.
  • Guide L1/L2 and strengthen their autonomy.

Technical Skills

  • Observability: direct use of Elastic/Kibana and CloudWatch for monitoring, investigation and correlation.
  • Applications: front/back end, REST APIs/API Gateway, microservices, data flows and dependencies.
  • Messaging and events: SQS, EventBridge and understanding of interactions with Kafka/Confluent.
  • AWS infrastructure: EC2, Auto Scaling, IAM, S3/EFS, VPC, Route 53, ALB/NLB, Transit Gateway and cross-account traffic.
  • Databases: PostgreSQL/Aurora investigation in a production context.
  • Automation: Terraform, GitLab CI/CD and Bash/Python scripting.
  • Containers: strong Kubernetes/EKS troubleshooting and end-to-end application understanding.
  • Data exchange: production data exchange, ideally AWS Transfer Family/SFTP, including exchange and dependency troubleshooting.
  • Lambda: hands-on Lambda operations and troubleshooting of interactions with other services.
  • Preferred: AS2, Docker/Helm, GitOps/ArgoCD. Prometheus, Grafana and OpenTelemetry can complement observability. Kafka/Confluent skills can be developed with support from the existing team.

Certifications

  • Mandatory: AWS certification, supported by significant and recent AWS production experience.
  • Preferred: Kubernetes certifications and advanced or professional AWS certifications.

Required Experience

  • Significant, recent AWS production experience.
  • Operation of business-critical applications and personal handling of major P1/P2 incidents.
  • Deep expertise in at least one core component, ideally one or two, combined with broad production support coverage and end-to-end understanding of dependencies.
  • Transfer Family and Lambda are particularly sought; strong production data exchange experience on another solution remains relevant.
  • Experience assembling, operating and troubleshooting multiple cloud services, including in startup environments. A smaller platform may be relevant if its dependencies and operational challenges are comparable.
  • Must confirm personal incident actions, architecture and flow understanding, observability tools used and preventive practices, and be able to explain decisions and ask relevant operability questions.
  • A background focused only on Build, architecture, lift and shift, infrastructure or CI/CD is insufficient.
  • A mainly Azure profile does not meet AWS requirements. AWS expertise is needed from the start; this assignment is not for learning AWS fundamentals.
  • Autonomy, production reflexes, analytical thinking, technical decision-making, clear communication and awareness of business impact.
  • Professional English is required. French is optional.
  • Total Experience Expected: 08-10 years.
  • BE/B.Tech degree.