Senior Platform Engineer — Java + GCP

• Build shared Spring Boot services and libraries with the team — auth, async tasks, replication, observability defaults — that every product team builds on top of.
• Help shape the company-wide playbook for how services get deployed, secured, monitored and rolled back.
• Work alongside the team on multi-region GCP — GKE, global load balancing, autoscaling, zero-downtime deploys with Helm and GitLab CI.
• Contribute to edge and application security — gateway policies, API key and JWT issuance, dependency hygiene, GCP IAM least-privilege.
• Take part in architectural decisions on event sourcing, Pub/Sub topology, schema design and service boundaries — and document them so the rest of engineering can follow.
• Show up for design reviews and platform RFCs alongside the rest of the team.

What you will need to be successful

• Deep production Java with Spring Boot — comfortable with transactional boundaries, connection pools, JVM behaviour under load and how things actually break in production.
• Hands-on experience building shared platform libraries or Spring Boot starters that other teams consume — this is the headline ask.
• Strong infrastructure and DevOps chops on a major public cloud (GCP preferred) — Kubernetes in production (GKE), Helm, multi-region deploys, autoscaling, rollbacks.
• Terraform as a daily tool — modules per service, IAM, networking, Pub/Sub, Cloud SQL.
• Hosting and application security ownership — gateway and edge policies, secret management, dependency scanning, IAM hygiene.
• PostgreSQL depth — schema design, indexing, query plans, migrations under load, JSONB-heavy data modelling.
• Event sourcing and asynchronous messaging — designing aggregates and events, integrating services via GCP Pub/Sub, idempotency and ordering.
• Contract-first APIs with OpenAPI — the schema is the source of truth.
• Production observability and incident response on GCP — structured logging, alerting, debugging distributed flows.
• Strong testing discipline — unit and integration tests against real Postgres and Pub/Sub as part of normal development.
  • Excellent written and spoken English.