Platform Engineering, SVP at State Street in Boston, MA

Job description

Who we are looking for The Head of Developer Platforms & Experience leads the internal product organisation that designs, builds and operates the paved road for software delivery . This is the platform, common libraries, toolchain and automated control plane through which every engineer builds, tests, releases and evidences software. The mandate is to make the compliant path the fastest path — raising engineering velocity and quality while generating security and audit evidence as a byproduct of normal work. Success is measured not in tools shipped but in delivery outcomes across the firm: faster lead times, lower change-failure rates, demonstrably stronger controls, and materially cheaper enterprise-wide change — most consequentially, create the development velocity and agility that allows XXXX able to keep our platform secure in the age of Frontier AI security models, and forthcoming quantum cryptography challenges . This is a deeply technical leadership role . The successful candidate is a credible principal-level engineer who has personally built platforms at scale, and who will lead through technical authority and product discipline rather than positional mandate. They must be equally effective writing an architecture decision record, defending a standard to s k eptical business-unit engineering leads, implementing new platforms, and presenting adoption and performance metrics to the Senior Leadership. Why this role is important to us latform as product. Developers are customers, not captive users. You run DPX with a roadmap, SLOs, adoption targets and quarterly developer feedback — and you are accountable for adoption you have earned, not mandated. Paved road, not walled garden. The golden path is the fastest, cheapest, pre-approved way to ship. Teams may deviate through a time-boxed, registered waiver — and inherit the full compliance and support burden of doing so. You make the paved road so good that deviation is rarely rational. Compliance as code. Controls, segregation of duties, change records and audit evidence are produced automatically by the platform. Regulatory strength is engineered in, not inspected after. Serve the whole estate. Mainframe, vendor-package, analytics and quant developer populations receive proportionate standards and tooling. A platform that serves only greenfield services has failed. Own the common core . Build multi-language libraries to support core functionality like logging, monitoring, service registration and discovery, event publishing, observability and telemetry, authentication, and secrets management. Consolidate before adding. You will rationalise a fragmented tooling estate before building anything new and fund the function substantially from that consolidation. What you will be responsible for Platform strategy & delivery Own the DPX strategy, roadmap and delivery across all product areas; set and hold platform SLOs, treating the developer platform as a Tier 1 production service. Design and deliver golden paths — opinionated, pre-approved templates that take a service from scaffold to production with observability, secrets management, security scanning, artefact provenance and event-streaming integration wired in by default. Define and operate the single enterprise CI/CD and release-automation capability and lead the consolidation of the existing fragmented pipeline estate on a dated migration runway. Stand up and run the internal developer portal (service catalogue, scaffolding, golden-path discovery, documentation). Standards & governance Co-chair the Technology Standards Board (owned by Enterprise Architecture) and own the engineering recommendations it decides on — approved languages, frameworks, developer tooling, CI/CD, testing and cryptographic-library standards, and their lifecycle status (Adopt / Trial / Contain / Retire). Standards are owned and ratified by EA; you are the authoritative engineering voice that shapes them. Author and maintain the Technology Radar as the