AI Technical Product Owner

Pitney Bowes • Shelton, CT

5d • Onsite

About The Position

The AI CoE builds and ships agentic AI systems that sit on top of our core product APIs - a Copilot platform on Amazon Bedrock AgentCore, MCP-based tool servers, and AI advisors embedded in our shipping products. We are past the demo stage and into the part that is genuinely hard: making non-deterministic systems reliable, governed, measurable, and safe enough to put in front of customers and internal users.
This role owns the backlog and the delivery cadence for that work. You are the single throat to choke for what the team builds next and the reason the team can build it without friction. You will spend your day equally between defining outcomes with engineering, product, and security stakeholders - and clearing the path so the pod can actually deliver them.
This is a hands-on-the-details role, not a ceremony-running role. You will be expected to read an architecture diagram, argue about where the human-in-the-loop gate belongs, and write acceptance criteria for a system whose output is different every time you run it.

Requirements

• 5+ years in technical product ownership, technical program management, or engineering delivery leadership on software platforms - with at least 2 years directly accountable for a backlog.
• Demonstrated experience delivering AI/ML or LLM-based features to production. Prototypes and pilots count only if you can describe what broke when real users arrived.
• Working fluency with modern AI application patterns: prompting, RAG, tool/function calling, agent orchestration, evaluation, and guardrails. You do not need to write the code; you need to reason about the design.
• Strong API literacy - you can read an OpenAPI spec, understand auth models, and reason about latency, idempotency, and error handling.
• Proven Scrum or Kanban facilitation with distributed teams, including offshore or multi-timezone pods.
• Excellent written communication. This role produces a lot of writing that executives read.
• Comfort with ambiguity and with saying "not this sprint" to senior stakeholders.

Nice To Haves

• Hands-on exposure to a managed agent platform (Amazon Bedrock / AgentCore, Azure AI Foundry, Vertex AI Agent Builder) and to MCP or a comparable tool-integration protocol.
• Experience defining evaluation frameworks for LLM systems - golden sets, LLM-as-judge, human review loops, regression gating.
• Familiarity with enterprise data platforms (Snowflake or equivalent) and with data governance constraints on AI systems.
• Experience operating inside an AI governance or model risk process in a regulated or enterprise environment.
• Background in logistics, shipping, supply chain, or B2B SaaS.
• CSPO, PSPO, CSM, PSM, or SAFe certification - useful, not a substitute for judgment.

Responsibilities

• Own and groom the backlog for one or more AI pods (agent platform, AI advisor products, or AI productivity tooling). Set sprint goals that ladder to quarterly outcomes, not activity.
• Translate ambiguous executive intent ("we need an agent that helps SMBs ship smarter") into epics, stories, and acceptance criteria engineers can start on Monday.
• Write acceptance criteria for probabilistic systems: define what "good" means for an agent response, what the eval set is, what the pass threshold is, and what the failure mode is when it misses.
• Own the definition of done for agent capabilities - including evals, guardrails, observability, cost per interaction, and rollback path, not just "the happy path works."
• Prioritize ruthlessly across competing stakeholders: product management, engineering leadership, security, architecture, and the business units consuming the platform.
• Maintain the tool and capability catalog for the agent platform - which APIs are exposed as agent tools, which are approval-gated, which are read-only, and why.
• Run sprint planning, standup, review, and retrospective for the pod. Keep them short and keep them useful.
• Track and report delivery health: velocity, cycle time, spillover, blocked-time. Bring problems forward early rather than explaining them in hindsight.
• Remove impediments - cross-team dependencies, environment access, security review queues, vendor bottlenecks. Escalate with a proposed resolution, not just a flag.
• Facilitate estimation and scope negotiation in a domain where estimates are genuinely uncertain, without letting uncertainty become an excuse.
• Coordinate across pods and with partner teams (platform engineering, data, security, product) so integration work is planned rather than discovered.
• Partner with the architecture lead on target-state decisions and carry those decisions into the backlog with enough fidelity that they survive contact with implementation.
• Maintain requirement traceability from product requirements through to delivered agent behavior, including where a requirement was deliberately descoped and why.
• Own the AI governance checkpoints in the delivery flow: model approval, data handling review, human-in-the-loop placement, prompt and tool change control, and audit evidence.
• Keep a live view of platform economics - token spend, model selection, inference cost per use case - and treat cost regressions as defects.
• Run POCs as time-boxed experiments with a written decision at the end, not as open-ended projects.

Benefits

• Provide the opportunity to grow and develop your career
• Offer an inclusive environment that encourages diverse perspectives and ideas
• Deliver challenging and unique opportunities to contribute to the success of a transforming organization
• Offer comprehensive benefits globally (PB Benefits and Wellbeing Programs)

What This Job Offers

• Job Type: Full-time
• Career Level: Senior
• Education Level: No Education Listed