Platform Engineer

Job Overview

You will work on a cloud-native SaaS platform serving financial institutions globally, built on a modern Java + Angular stack. The team is modernising a large-scale enterprise system from a JBoss monolith to a multi-tenant Spring Boot microservices architecture, with a strong emphasis on configuration-driven extensibility over code generation.

Core Technical Requirements

Backend - Java / Spring Boot

• 3+ years building production REST APIs with Spring Boot
• Strong understanding of layered architecture - controller, service, domain, persistence
• Hibernate ORM - entity mapping, relationship management, query optimisation
• Oracle or equivalent relational database - schema design, SQL, indexing
• Experience with event-driven or pipeline-based processing (validation chains, pre/post-save hooks, deserialisation pipelines)
• Unit and integration testing with JUnit 5, Mockito, Spring Test

Frontend - Angular / TypeScript

• Angular reactive forms, component architecture, HTTP client
• TypeScript - interfaces, generics, strict mode
• Schema-driven / configuration-driven UI rendering
• Experience integrating with REST APIs and handling async state

Platform Infrastructure

• Docker - containerisation, multi-stage builds
• Kubernetes - deployments, ConfigMaps, Secrets, volume mounts
• CI/CD pipelines - build, test, deploy automation
• Git - branching strategy, code review practice

Architecture Design

• Understands multi-tenant SaaS patterns - per-tenant data isolation, JWT-based tenant resolution, path-scoped configuration
• Comfortable with configuration-over-code design - building systems where runtime behaviour is driven by YAML/JSON config rather than compiled logic
• Familiar with extension/plugin architectures - hook registration, dynamic dispatch, runtime resolution of behaviour
• Can reason about API contract design - what crosses a service boundary, what must be a plain DTO vs a domain object, versioning

What We Look For at This Level

• You can own a feature end-to-end: backend API persistence frontend rendering - without requiring architecture sign-off on every step
• You recognise when a configuration-driven approach saves a code change per customer, and you build for that
• You write tests that cover the contract, not just the happy path
• You flag security and data-isolation risks during design, not after deployment
• You contribute to code review and leave the codebase cleaner than you found it

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.