Slalom-Boeing
Role #3: Platform Engineer – AWS Specialist (India – Intermediate/Senior)
Position Title
Platform Engineer – AWS / Cloud Infrastructure Engineer (India)
Location
India (Bangalore preferred)
Role Summary
This role is the
AWS-focused engineering counterpart within the platform build program, responsible for designing and delivering
AWS-based platform capabilities in parallel with the Azure/AKS track.
The AWS Platform Engineer ensures
multi-cloud consistency, builds
EKS-based infrastructure patterns, and enables reusable platform services across AWS workloads. The role operates within the same
paired engineering model and time-zone alignment, ensuring real-time collaboration with Boeing India engineers.
This role is critical in organizations where workloads span
Azure Government/EIC and AWS environments, ensuring consistent platform engineering standards, tooling parity, and operational readiness across clouds.
Key Responsibilities
1. Collaboration & Delivery Model
-
Maintain 6-hour overlap window (Mon/Tue/Thu, 6:00–11:00 AM PST)
-
Pair daily with Boeing India engineers for:
- Joint development
-
Design alignment
-
Hands-on implementation
-
Ensure real-time resolution of AWS-specific blockers
2. Phase 2 – AWS Platform Build (Primary Ownership)
Own the
AWS-based infrastructure and Kubernetes platform track, operating in parallel with the Azure-based Platform Lead.
AWS Infrastructure & Kubernetes
-
Provision and configure Amazon EKS clusters
-
Implement:
- VPC architecture (multi-AZ, private/public subnets)
-
Node groups (managed/unmanaged)
-
Networking (ALB/NLB ingress, service mesh if applicable)
Terraform Engineering
-
Develop AWS-specific Terraform modules, aligned with shared standards:
- EKS provisioning modules
-
VPC and networking modules
-
IAM role and policy modules
-
Ensure consistency with:
- Centralized state management
-
Workspace/environment isolation
-
Module versioning strategy
3. Platform Capabilities (AWS Context)
IAM & Security
-
Design and implement:
- IAM roles and policies
-
IRSA (IAM Roles for Service Accounts)
-
Enforce least-privilege access models
GitOps & Deployment
-
Extend ArgoCD/GitOps workflows to EKS environments
-
Maintain parity with AKS-based deployment patterns
Networking & DNS
-
Configure:
- Route53 DNS automation
-
Ingress and load balancing patterns
-
Integrate with enterprise DNS strategies where required
Cluster Operations
-
Define:
- Upgrade procedures
-
Backup and disaster recovery patterns
-
Drift detection strategies
4. Phase 3 – Platform Maturity & Expansion
Platform Hardening
-
Expand policy-as-code enforcement (OPA/Kyverno on EKS)
-
Ensure compliance-ready configurations
FinOps & Cost Optimization
-
Implement:
- AWS cost monitoring (Cost Explorer, CUR-based dashboards)
-
Rightsizing and autoscaling strategies
Observability
-
Enable OpenTelemetry instrumentation for EKS workloads
-
Integrate with centralized observability platforms
Knowledge Transfer
-
Co-deliver KT sessions with Boeing engineers covering:
- EKS operations
-
AWS networking patterns
-
Deployment pipelines and GitOps
-
Produce AWS-specific:
- Runbooks
-
Playbooks
-
Architecture documentation
5. Multi-Cloud Alignment
-
Ensure architectural consistency across:
- AKS (Azure) and EKS (AWS)
-
Align on:
- CI/CD pipelines
-
Security scanning integration
-
Developer onboarding flows
-
Contribute to cloud-agnostic platform patterns where applicable
Required Skills & Experience
Core Experience
-
4–7 years in cloud/platform engineering
-
Strong hands-on experience in AWS environments
AWS Expertise
-
Amazon EKS (production deployments)
-
VPC design and networking
-
IAM (roles, policies, IRSA)
-
Load balancing (ALB, NLB)
-
Route53 DNS management
Infrastructure as Code
-
Terraform (AWS-focused)
- Module design and reuse
-
State management best practices
Platform Engineering
-
GitOps tools (ArgoCD preferred)
-
CI/CD pipelines (GitLab preferred)
-
Kubernetes operations
Security & Compliance
-
AWS security best practices
-
Container and workload security fundamentals
Nice-to-Have Skills
-
Multi-cloud architecture experience (AWS + Azure)
-
Service mesh (Istio, Linkerd)
-
AWS GovCloud experience
-
Experience with centralized logging/observability platforms
Working Model
-
Operates as parallel cloud track owner (AWS) alongside:
- Platform Lead (Azure/AKS)
-
Platform Engineer (developer platform track)
-
Enables simultaneous multi-cloud delivery
-
Prevents AWS backlog accumulation during Azure-first build
Success Metrics
-
Successful provisioning and operation of EKS clusters
-
Terraform modules reusable and aligned with standards
-
GitOps pipelines functional across AWS workloads
-
Cost optimization and FinOps visibility achieved
-
Knowledge transfer completed with Boeing AWS engineers
-
AWS platform fully aligned with broader program milestones
