Platform Engineer

Who are we?

At Finastra, we’re a global leader in financial services software, dedicated to expanding access to financial services and shaping what’s next for the industry. Our technology powers mission‑critical solutions across Lending, Payments and Universal Banking, supporting over 7,000 customers, including 80% of the world’s top 50 banks, in more than 110 countries.# Platform Engineer## About Finastra Finastra is a global leader in financial technology, providing innovative solutions that help financial institutions around the world transform their operations and deliver exceptional customer experiences.

About the Role You will build and run the platform that engineering teams deploy onto — a multi-tenant, cloud-native SaaS environment supporting the modernisation of a large-scale financial system from on-premises to Kubernetes-based microservices. This is a senior software engineering role first, and a Dev Ops/platform role second: you write production-grade code for the tooling and automation you own, not just scripts and YAML, and you understand the Spring Boot services running on top of the platform well enough to debug deployment issues at the application layer, not just the infrastructure layer.

Core Technical Requirements Software Engineering Foundation7+ years professional software engineering experience — strong general-purpose programming (Java and/or Go or Python), not solely scripting

Writes and reviews production-grade code for internal platform tooling — CLIs, operators, controllers, automation services — with the same rigour as application code: tests, code review, versioning

Comfortable extending or contributing to shared Spring Boot libraries and starter packs consumed by other engineering teams

Understands software design fundamentals — API design, concurrency, error handling, backward compatibility — well enough to be a credible reviewer on both infra and application pull requests

Can debug across the full stack — from a Kubernetes scheduling failure down to a Spring Boot stack trace or a Hibernate query plan

GitHub & Source Control Engineering Deep Git Hub Actions expertise — authoring reusable/composite workflows, matrix builds, self-hosted runners, caching strategies, and secure secret handling in CI Repository governance at scale — branch protection rules, required status checks, CODEOWNERS, merge queue strategy across many repos or a monorepo

GitHub Advanced Security — secret scanning and push protection, code scanning (CodeQL), Dependabot policy and triage

GitHub Apps and fine-grained access tokens for internal automation — building bots/integrations against the Git Hub API rather than relying on personal access tokens

GitHub Environments — deployment protection rules, required reviewers, and environment-scoped secrets as a promotion gate into staging/production

Organisation and team permission design — least-privilege access across engineering teams, audit logging, SSO/SAML integration

GitOps & Dev Ops Production  experience with Git Ops tooling — ArgoCD or Flux — managing declarative, Git-driven deployments across multiple environments and clusters

Infrastructure as Code — Terraform for cloud provisioning;
Helm charts / Kustomize for Kubernetes manifests

Progressive delivery — canary and blue-green rollout mechanics, automated rollback triggers tied to health signals

Secrets management integrated into pipelines — Vault, Sealed Secrets, or cloud-native secret stores

Kubernetes & Cloud Infrastructure Kubernetes at depth — deployments, Stateful Sets, Config Maps, Secrets, resource quotas, autoscaling (HPA/VPA), network policies

Multi-tenant cluster design — namespace isolation, per-tenant resource boundaries, workload scheduling

Cloud platform experience (AWS, Azure, or…