Product Manager – Enterprise Orchestration (Banking Workflow Platform)

Job Description

About the Role

A newly acquired startup inside FIS is building an AI-enabled, autonomous banking platform aimed at Tier-1 financial institutions — and this role owns one of its most important pieces. As Product Manager for Enterprise Orchestration, you'll be the single-threaded owner of the workflow engine that keeps long-running banking processes intact even when systems fail, restart, or change mid-stream. Think of it as the connective tissue that lets a modern platform sit on top of decades-old core banking systems without ripping any of them out.

This isn't a delivery or client-program management role — that work sits with a separate Forward Deployed team. This is product ownership: defining what gets built, why it matters, and how it scales across every banking journey that runs through it.

What You'll Actually Be Doing

• Set the vision and roadmap for the orchestration platform — the reusable workflow primitives, connectors, and templates that let banking operations teams automate complex, multi-step processes without a bespoke build every time.
• Sit between engineering, banking-operations leaders, and clients, translating messy operational reality (payments, settlement, onboarding, KYC, approvals, exceptions) into governed, platform-level capabilities rather than one-off fixes.
• Own the hard technical decisions that make a workflow platform trustworthy: execution semantics, versioning, retry and recovery behavior, idempotency, and audit trails at the scale a Tier-1 bank actually needs.
• Push adoption of no-code/low-code authoring tools so operations teams — not just engineers — can build and modify workflows themselves.
• Turn recurring, one-off client requests into reusable product features instead of letting the backlog fill up with bespoke work.
• Coordinate product contracts across ledger, customer, compliance, and servicing domains so the orchestration layer doesn't become its own silo.
• Use telemetry, experimentation, and AI-assisted analysis to decide what to build next and prove it worked.

What You Need to Bring

• A track record of owning a workflow, orchestration, BPM, or process-automation product end-to-end — not just contributing to one.
• Real fluency in banking middle-office operations: payments, settlement, onboarding, KYC, approvals, exception handling.
• Comfort defining execution models, business rules, and audit requirements for systems that can't afford to silently drop a step.
• Technical depth across APIs, event-driven architecture, and distributed systems — you don't need to write production code, but you need to hold your own in an architecture conversation.
• A bachelor's degree in Computer Science, Engineering, Information Systems, Business, or equivalent hands-on experience.

Nice to Have

• Direct experience with Temporal, Cadence, or comparable durable-execution/BPM frameworks.
• An engineering background — someone who's actually built or operated production systems, not just managed them.
• Experience designing no-code/low-code tools for non-technical enterprise users.
• Familiarity with core banking platforms, regulatory controls, Kafka, SFTP integrations, and workflow DSLs.
• Hands-on use of AI tools for product discovery, documentation, or decision-making — this team expects you to use them, not just talk about them.