Job Description:

What You'll Own
Story Backlog and Sprint Delivery

Write, groom, and prioritize user stories with clear acceptance criteria across a multi-initiative platform backlog spanning catalog management, ordering, system integrations, digital asset management, identity, and more
Break epics into sprint-ready stories and flag scope that will not close within a sprint
Stay in the details, actively writing stories every sprint rather than delegating and reviewing
Maintain backlog quality and traceability across workstreams and PI targets in Jira

Technical Depth and Platform Engagement:

Understand the platform deeply enough to challenge assumptions, validate feasibility, and identify gaps across out-of-the-box capabilities, configuration requirements, and custom development areas
Engage meaningfully with architecture decisions such as API Gateway design, system integrations, schema-per-client multitenancy, and document customization engine, and surface the implications for the backlog
Partner with engineering on architecture reviews, integration sequencing, and non-functional requirement traceability
Bridge platform behavior and business requirements before stories go into a sprint

Cross-Functional Coordination:

Serve as the organizing hub for working sessions, bringing product owners, product managers, and engineering stakeholders across India and the US together for backlog reviews, story walkthroughs, and prioritization
Facilitate story-writing workshops so the team produces consistently structured, reviewable artifacts
Coordinate effectively with global vendors as part of a distributed delivery model
Maintain a shared view of epic and story status across all initiatives so nothing falls through the cracks between teams or time zones.

PI Planning and Execution:

Prepare initiative-level story maps, dependency maps, and risk flags ahead of PI planning events Keep the pipeline stocked for upcoming sprints, not just the current one
Track and communicate what is in-flight, committed, and deferred across the PI

Required Experience:

7+ years as a Product Owner or Technical Business Analyst on enterprise software platforms
Must have: proven experience on large-scale, enterprise platform development programs with multi-workstream, multi-stakeholder engagements delivered over multiple release cycles or PIs
Demonstrated track record writing user stories for platform-level and integration-heavy systems, not just UI features
Experience working in SAFe or scaled Agile environments with multiple product owners on a shared platform
Experience operating in a matrix reporting structure across globally distributed teams
Comfortable reading API specs, data models, and architecture diagrams; you do not need to write code, but you need to engage confidently with engineering
Familiarity with REST API design, multi-tenant SaaS architecture, and integration patterns such as webhooks, polling, and 
message brokers

Preferred Experience:

eCommerce platform background; understanding of catalog management, order workflows, and shopping experience patterns is directly applicable to this domain
Familiarity with dynamic document composition or CCM platforms such as Quadient Inspire, OpenText Exstream, Smart 
Communications, or similar
Experience working in regulated industries including Financial Services, Healthcare, Legal, or similar compliance-heavy 
environments
CSPO, PSPO, or SAFe PO/PM certification

Key Traits:

A detail-oriented individual contributor who leads through preparation and craft, not authority
Someone who reads the full spec, annotates the edge cases, and comes to the session with the right questions already formed
A clear, precise writer who produces stories engineers want to implement: scoped, testable, with explicit out-of-scope callouts Comfortable operating across cultures, time zones, and organizational boundaries, influencing without direct authority
Organized and methodical enough to hold a complex, multi-initiative backlog together without losing traceability
A strong communicator who can translate technical platform constraints into language business stakeholders can act on, and vice versa