Platform Engineering Manager - Platform Shared Services

• Management experience: minimum 4 + years directly managing engineering teams, in addition to prior hands-on software engineering experience.
• Delivery track record: proven delivery of backend, platform, or infrastructure services; experience managing teams responsible for shared/platform services (authentication, messaging, APIs) strongly preferred.
• Technical depth (to steer, not to code daily): solid background in backend engineering and distributed systems - enough to guide decisions on authentication and messaging infrastructure and review design proposals with senior engineers.
• Reliability & delivery practices: working knowledge of cloud infrastructure, CI/CD, and service reliability (SLAs/SLOs, incident management).
• Platform / shared-services understanding: how internal engineering teams operate as service providers to the rest of the org.
• People & delivery balance: organised and outcome-driven, comfortable balancing people management (~60%) with technical/business activities (~40%).
• Planning: budget/resource planning experience for a team.
• Communication & judgement: clear communicator across technical and non-technical stakeholders; sound decision-making and comfort resolving ambiguity.
• Language: Professional-level English (spoken and written).

• Hands-on background with authentication/identity (OAuth 2.0, OIDC, JWT) and/or messaging/event-driven systems (Kafka, RabbitMQ).
• Experience with Microsoft Azure, Kubernetes (AKS), and.NET/C# environments.
• Familiarity with GDPR / consent and security/compliance as part of the delivery bar.
• Experience leading a team through a CI/CD or platform migration.
• Interest in Spec-Driven Development and enabling an AI-First delivery workflow for the team (Cursor, MCP, the Technology Framework).
• Background in Scientific Publishing.

• We prioritise office presence and emphasise in-person collaboration, but also offer appropriate adjustments where needed, in line with company policy
• Extra wellbeing days on top of your annual leave allowance
• Up to 3 paid volunteering days each year
• 24/7 confidential Employee Assistance Programme (wellbeing, mental health, legal & financial support)
• Learning & development support via the Frontiers Learning Hub

At Frontiers, we are rewriting the rules of scientific publishing. Behind every product team sit the shared technical services the whole publishing platform depends on. Today these are Identity & Access Management (IAM) and Messaging (transactional email and GDPR-compliant consent) - examples of this kind of shared service, with more likely over time - owned by our Platform Shared Services team. We are looking for a Platform Engineering Manager to lead the team that builds and runs them.

You will own team delivery, technical direction (in partnership with your Senior Engineers), and the people development of a team of [5-8] engineers. These are high-blast-radius services consumed org-wide, so you'll balance shipping new capability with reliability, security and backward compatibility - treating the services as products for internal engineering customers. You'll form a delivery triad with the team's Platform Product Manager (who owns the What/Why) and your Senior Engineers (who drive the How).

You'll lead the team behind two of Frontiers' highest-leverage capabilities: get identity and messaging right, and every product team ships faster and safer. It's a rare mix of real people leadership, technical direction on interesting distributed systems, and platform-as-a-product thinking - all in service of a mission that matters: making science open for everyone.

• Lead the team day to day - oversee operations, resource allocation and task assignment across the IAM and Messaging portfolio.
• Turn roadmap into execution - translate the shared-services roadmap and portfolio objectives (owned with the Platform PM) into actionable engineering plans; ensure delivery aligns with department and wider engineering goals.
• Own team delivery - for authentication, messaging and related infrastructure: coordinate resources, manage risk, and deliver outcomes for the many teams that depend on these services.
• Partner with the Platform Product Manager - align roadmap priorities with technical feasibility, reliability and platform health; push back with technical reality where needed.
• Guide technical direction with your Senior Engineers - you don't need to be hands-on daily, but you provide enough depth to steer decisions on authentication and messaging infrastructure and to review architecture and design proposals.
• Develop people - set clear expectations, give regular feedback, support career growth, and run performance management for the team.
• Own reliability & operational excellence at the team level - SLAs/SLOs, incident management, and blameless post-incident follow-through; protect the team from unbounded toil.
• Improve process - identify and implement improvements that increase delivery efficiency and reliability across the team and portfolio.
• Represent the team cross-functionally - drive alignment with the engineering teams that consume shared services; escalate and manage significant technical/delivery risks to senior leadership.

You will lead delivery across the team's shared-service lines - today IAM and Messaging.

• IAM: OAuth 2.0 / OIDC (Ory Hydra), JWT authorization, fine-grained authz via a Permission API (Ory Keto), Azure APIM, OAuth client tooling, shared.NET libraries.
• Messaging: transactional/outreach email at scale (SendGrid, Mailgun), templating and A/B testing, deliverability tooling, and a central GDPR consent authority (Subscription Management).
• Core stack: C#/.NET services on Microsoft Azure + Kubernetes (AKS); event-driven with RabbitMQ and Kafka; SQL Server, PostgreSQL, Redis, Elasticsearch.
• Delivery & reliability: CI/CD, observability (New Relic, Grafana), SLAs/SLOs and incident management.
• Ways of working: Spec-Driven / AI-First Delivery (PRDs/SDDs in git, the Technology Framework as executable context, Cursor, MCP) - available to help the team deliver faster and more safely.

• Delivery: predictable, healthy throughput against the shared-services roadmap; risks surfaced and managed early.
• Reliability: SLAs/SLOs met for owned services; incident trend and quality of post-incident follow-through.
• People: team health, retention, growth and clear performance management.
• Consumer outcomes: satisfaction/adoption from the engineering teams that depend on IAM and Messaging.
• Security & compliance: the team's output meets the Technology Framework bar (OAuth/JWT, GDPR consent).