Senior Platform Engineer - Kubernetes - FinTech

Senior Platform Engineer - Kubernetes - FinTech

Excellent opportunity for Senior Platform Engineer to own and evolve the internal platform that all application services run on.

This role sits between application engineering and core cloud infrastructure. You will design, build, and operate the Kubernetes platform on AWS as a product, providing secure defaults, reliable delivery paths, and strong operational guarantees.

You are expected to be hands-on, opinionated, and comfortable taking ownership of production systems.

Kubernetes platform ownership

• Own the EKS platform end to end: cluster design, upgrades, node life cycle, scaling strategy, and reliability.
• Define and maintain cluster baselines: namespaces, RBAC, resource limits, pod security, network policies.
• Design safe patterns for running stateless and stateful workloads on Kubernetes.
• Ensure predictable behaviour under load, failure, and partial outages.

AWS platform foundations

• Design and maintain AWS infrastructure supporting EKS: VPCs, subnets, routing, load balancing, IAM, KMS.
• Implement least-privilege IAM using IRSA and strong role separation.
• Manage AWS integrations such as ALB/NLB, Route 53, ECR, S3, CloudWatch.
• Balance cost efficiency with reliability and regulatory expectations.

Infrastructure as Code

• Treat Terraform as the source of truth for AWS and Kubernetes infrastructure.
• Build reusable, auditable modules rather than one-off stacks.
• Own change control, reviews, and drift management.

CI/CD and delivery guardrails

• Own the delivery foundations used by application teams.
• Define standard build and deploy paths for Kubernetes workloads.
• Improve deployment safety through automated checks, rollbacks, and promotion models.
• Reduce manual steps and operational risk without slowing delivery.

Security and compliance by design

• Embed security controls into the platform, not as after-the-fact reviews.
• Implement secrets management patterns aligned with AWS and Kubernetes best practice.
• Introduce policy-as-code to prevent unsafe configurations reaching production.
• Support auditability, access control, and operational evidence expected in regulated environments.

Observability and operations

• Define standard observability across services: metrics, logs, tracing, alerts.
• Build actionable alerting with clear ownership and low noise.
• Participate in on-call and incident response.
• Run post-incident reviews and drive systemic improvements.