Senior Principal Product Delivery Lead

SimCorp•New York, NY

2d•$185,840 - $278,760•Hybrid

About The Position

The Senior Principal Product Delivery Lead is a critical leadership role responsible for holding complex, multi-product client programs together end to end. Large client engagements at SimCorp span multiple product domains, engineering teams, and commercial stakeholders — and delivering on them requires more than great individual contributors. It requires someone who can orchestrate the full program: keeping teams aligned, clients informed, and momentum building even as complexity grows. This role is that connective force. This role ensures that: Internal stakeholders across product, engineering, and commercial functions know what they own, when, and why. Client stakeholders feel heard, informed, and comfortable with the cadence of communication. Risks and dependencies are visible early so internal teams and clients are never caught off guard. Complex tradeoffs are framed with clarity, enabling confident decisions at pace. The outcome is predictable, repeatable, well-coordinated delivery against complex multi-product client programs with internal teams aligned on scope and sequence, and clients confident in progress, tradeoffs, and timelines.

Requirements

5+ years coordinating complex software delivery programs, it's beneficial if you have experience from a enterprise B2B environments.
Experience running client-facing programs with multiple internal teams involved, and delivering predictable outcomes in ambiguous conditions.
Working knowledge of financial services, enough to engage credibly with clients and internal stakeholders from day one.
Familiarity with how modern software development works: agile, release cycles, and engineering tradeoffs.
Effective written and verbal communicator who can translate between technical and commercial audiences.
Systems thinker who maps dependencies, sequences work, and cuts through complexity to keep the program focused on what drives outcomes.
Runs effective program cadences that keep teams moving and accountable, with the right level of structure for the complexity at hand.
Exercises judgment in tense situations: knows when to escalate, when to absorb, and how to keep stakeholders confident without overpromising.
Navigates ambiguity in scope and resourcing without losing momentum.

Responsibilities

Serve as the single point of accountability for end-to-end coordination across product, engineering, and commercial workstreams on major client programs.
Ensure all internal stakeholders have clear ownership of their scope, timelines, and dependencies and maintain that clarity as programs evolve.
Identify and actively manage cross-team dependencies, sequencing work and resolving conflicts before they compound.
Run program cadences including working groups and status reporting with the right level of structure to drive accountability without overhead.
Act as the primary orchestrator of client-facing communication, ensuring the client has a consistent, credible view of program status, tradeoffs, and timelines.
Translate between technical and commercial audiences, making complex delivery realities legible to client stakeholders without oversimplifying or overpromising.
Build and sustain trust with client stakeholders through reliable cadences, proactive transparency, and disciplined expectation-setting in difficult situations.
Surface risks and dependencies early, with enough context and framing for stakeholders to make informed decisions rather than deferring them.
Exercise sound judgment on when to escalate and when to resolve, protecting team focus while ensuring leadership has visibility on what matters.
Frame tradeoffs clearly and lead decision-making forums that drive alignment and produce actionable outcomes.
Own the program’s operational infrastructure: status reporting, dependency tracking, risk logs, and decision records.
Maintain a single, credible picture of program health that is accessible to both internal leadership and client stakeholders.
Continuously improve delivery practices and coordination patterns based on what is actually happening in the program.