Platform Engineer

We need to output HTML fragment with sections: About the role, Responsibilities? The posting includes "About The Role", then description. There's also "Core Technical Requirements" which could be Requirements. There's "Nice to Have". There's "What We Look For At This Level". There's "Benefits". There's no explicit Pay or Schedule. So we should include sections for which there is real content: About the role, Responsibilities (maybe not explicit), Requirements (Core Technical Requirements), Nice to Have (maybe as part of Requirements? but we can include as a subsection? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings: About the role, Requirements, Nice to Have (maybe under Skills?), What We Look For (maybe as Skills?), Benefits. We need to avoid filler. Ensure we preserve all substantive info. We need to remove boilerplate like "Who are we? At Finastra..." etc. Also remove duplicated lines. The posting includes "# Platform Engineer ## About Finastra". We should not repeat job title as heading. So we start with About the role. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to parse the content. Let's extract sections: - About The Role: paragraph(s) describing role. - Core Technical Requirements: list of bullet points (each line starting with bold?). We'll turn each bullet into

• . - GitHub & Source Control Engineering: seems part of Core Technical Requirements? Actually it's a subcategory. Could be part of Requirements. - GitOps & DevOps: also part. - Kubernetes & Cloud Infrastructure: also part. - Observability & Reliability: also part. - Nice to Have: list. - What We Look For At This Level: list (or paragraph). It's bullet-like sentences. - Benefits: list of bullet points (Flexibility, Well‑being, Health & Financial Security, Sustainability, Inclusion, Career Development, Recognition). Each has sub-bullets. We need to output HTML fragment only. We'll structure:

  About the role

  ...

  Requirements

  • Software Engineering Foundation ...
  • GitHub & Source Control Engineering ...
  • GitOps & DevOps ...
  • Kubernetes & Cloud Infrastructure ...
  • Observability & Reliability ...
  Maybe also include "Nice to Have" as separate section? Could be under Requirements but we can make a separate

  Nice to Have

  with list. Similarly "What We Look For At This Level" could be

  What we look for

  with list. Benefits:

  Benefits

  with list. We must not include Pay or Schedule. We need to ensure we preserve all substantive info, not invent. Let's extract exact text. From posting: "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 DevOps/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." That's the paragraph. Now Core Technical Requirements bullet list: - Software Engineering Foundation 7+ 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 GitHub 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 GitHub 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 & DevOps Production experience with GitOps 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, StatefulSets, ConfigMaps, 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 GCP) — networking, IAM, managed Kubernetes (EKS/AKS/GKE), managed databases Container image strategy — multi-stage Docker builds, base image hardening, registry and vulnerability scanning - Observability & Reliability Builds and maintains observability stack — structured logging, distributed tracing, metrics (Prometheus/Grafana or equivalent) Defines SLIs/SLOs and alerting thresholds in partnership with engineering teams Incident response — on-call practices, runbooks, postmortems that lead to platform-level fixes, not just fire-fighting Nice to Have: - Experience migrating workloads from on-premises / JBoss-style deployments into Kubernetes - Kafka or RabbitMQ operations — cluster management, topic/queue scaling, consumer lag monitoring - Policy-as-code experience — OPA/Gatekeeper, admission controllers, compliance-as-code for regulated environments - Exposure to the financial services domain — awareness of the audit, resiliency, and change-control expectations that come with banking customers What We Look For At This Level: - You treat the platform as a product — self-service, documented, and reliable enough that application teams rarely need to escalate to you - You write platform tooling as real software — tested, versioned, code-reviewed — not one-off scripts that only you can maintain - You can move fluidly between a Terraform module, a GitHub Actions workflow, a Kubernetes manifest, and a Spring Boot stack trace without losing context - You design deployment and rollback paths that reduce customer-facing risk by default, not as an afterthought - You partner with engineering teams during design, flagging operability, security, and scaling concerns before code is written - You mentor other engineers on CI/CD and platform practices, and you're a credible voice in architecture discussions beyond just infrastructure Benefits: - Flexibility: Enjoy unlimited vacation, subject to local regulations and business priorities. Benefit from hybrid working arrangements and inclusive policies such as paid time off for voting, bereavement, and sick leave. - Well‑being: Access confidential one‑to‑one support through our Employee Assistance Program, connect with our network of Wellbeing Champions and Gather Groups, and take part in monthly events and initiatives designed to help you thrive—inside and outside of work. - Health & Financial Security: Medical, life and disability insurance, retirement plans, lifestyle, and other benefits.* - Sustainability: Paid time off for volunteering and donation‑matching opportunities to support causes that matter to you. - Inclusion: Get involved in our inclusion communities, such as Count Me In, Culture@Finastra, Proud@Finastra, Disabilities@Finastra, and Women@Finastra—open to everyone who wants to participate and contribute. - Career Development: Access online learning and accredited courses through our Skills & Career Navigator tool. - Recognition: Take part in our global recognition program, Finastra Celebrates, and share your voice through regular employee surveys that help shape our culture and ways of working. - Specific benefits may vary by location. At Finastra, each individual is unique—bringing their own ideas, perspectives, cultural backgrounds, and experiences. We learn from one another, value what makes us different, and create an environment where everyone feels included, supported, and able to be their authentic selves. Be unique. Be exceptional. Help us make a difference at Finastra. We need to preserve all substantive info. The last paragraph about uniqueness etc is part of Benefits? It's after the bullet list but still part of benefits section. We'll include as a

  after the list. Now we need to output HTML fragment. We'll wrap each section in

  and then content. For Requirements, we have sub-bullets; we can just make each bullet as

  containing the whole block (including sub-points). Could also nest

  but instruction says use
  • for any list. It doesn't forbid nested lists. We'll keep simple: each main bullet as
  • with line breaks using
    or separate

    inside? Simpler: keep as plain text with line breaks. We'll output:

    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 DevOps/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.

    Requirements

    • Software Engineering Foundation
      7+ 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 GitHub 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 GitHub API rather than relying on personal access tokens
      GitHub Environments — deployment protection rules