Technical Product Manager (26-02145) -

Role: Technical Product Manager

Summary

We're looking for a Technical Product Manager to own requirements and interface design for strategic initiatives. The role bridges business requirements and engineering. You'll translate business needs into well-defined technical stories, lead payload-level and API contract discussions, and keep engineering aligned on what gets built and why. This is a technical role, not a functional one: you should be comfortable reading schemas, reviewing API specs, and reasoning about data flow across services.

Responsibilities

• Translate business requirements from Finance, Sales, Deal Desk, and Legal stakeholders into technical requirements and user stories with clear acceptance criteria.
• Lead payload-level design discussions covering event structures, field definitions, validation rules, and versioning.
• Own API contracts across UDS services (Ingestion, Processing, Extraction, Reconciliation) and integrations with CI, BRIM, Sales CRM, and CSP, including schema governance and change management.
• Partner with the engineering team on data model decisions, including partitioning and access patterns in Cosmos DB and event flows in Kafka.
• Define and prioritize the backlog, and manage dependencies with upstream and downstream system owners.
• Validate delivered work against requirements, including reconciliation logic and Snowflake/EDP extract outputs.

Required qualifications

• Hands-on technical background, such as software engineering, QA/SDET, data engineering, or solution architecture, with a strong grasp of how systems communicate.
• Experience writing or reviewing API specifications (REST, GraphQL, or event schemas such as JSON Schema or Avro).
• Comfort with JSON payloads, data modeling, and reasoning about data consistency and reconciliation.
• Experience writing user stories and acceptance criteria for backend or platform work.
• Ability to work directly with engineers in technical depth and to challenge assumptions when a requirement has hidden implications.
• Experience working across multiple stakeholder groups on complex, cross-functional programs.