Senior Technical Product Manager

Role Overview 

We are looking for a highly technical, impact-driven Product Manager to own and drive the evolution of our next-generation Operational Data Store and Distributed Order Fulfillment Platform. 

In this role, you will lead the strategy and execution for a high-throughput, low-latency data platform that ingests, models, and exposes critical business entities via a robust API layer. You will bridge the gap between heavy cloud infrastructure (distributed relational and graph databases) and multi-system business orchestration, ensuring that data is securely accessible, highly performant, and perfectly aligned with the needs of engineering teams across the organization. 

This is a platform product role. There may be no user interface (UI). Your products are APIs, pipelines, and orchestration engines; your customers are fellow engineers, architects, and downstream technical teams. 

Key Responsibilities 

1. Technical Strategy & Platform Engineering Drive 

• Data Pipeline & ODS Evolution: Define the roadmap for scalable, real-time, and batch data pipelines that feed a globally distributed Operational Data Store (ODS). 

• Architecture Collaboration: Partner with data engineers and architects to leverage cloud-native big data tech (e.g., Google Cloud Spanner) for relational transactional data and Graph Databases for complex entity relationship mapping. 

• Enterprise Authorization & Identity: Own the security posture of the data platform by designing and implementing the right Identity & Access Management (IAM) principles and fine-grained authorization policies at the API layer. 

2. End-to-End Execution & Order Orchestration 

• Distributed Orchestration: Drive the design and capability of engines that orchestrate stateful order fulfillment workflows smoothly across highly decoupled internal and external systems. 

• API Contract Ownership: Propose, define, and enforce robust API contracts (REST, gRPC, or GraphQL). You will ensure that both your engineering team and consuming teams strictly adhere to these interfaces to prevent breaking changes. 

• Technical Validation: Actively participate in technical verification. You must be comfortable going beyond documentation—using tools like Postman, cURL, or writing basic scripts to hit APIs, validate response payloads, and test edge-case failure scenarios. 

3. Stakeholder Management & Roadmapping 

• Cross-Functional Discovery: Act as a consultative partner to engineering leaders, product teams, and business units across the organization. Conduct deep-dive discovery to understand their technical pain points and system use cases. 

• Meaningful Roadmapping: Translate messy, fragmented cross-team operational requirements into a clean, prioritized, and logically sequenced platform product backlog that balances long-term architectural health with immediate business value. 

Required Technical Experience & Qualifications 

• Experience: 8+ years of Product Management experience, specifically managing deep technical infrastructure, backend platform services, or data engineering products. 

• Database Proficiency: Proven experience working with massive-scale distributed databases (e.g., Google Cloud Spanner, CockroachDB) and a strong conceptual grasp of Graph Databases (e.g., Neo4j, AWS Neptune) for relationship mapping. 

• API Mastery: Deep understanding of API design principles, lifecycle management, and contract testing. Proven capability to draft API specifications and validate system behavior via API endpoints directly (no UI reliance). 

• Security & Compliance Foundations: Solid architectural understanding of enterprise security protocols, including IAM, OAuth, Role-Based Access Control (RBAC), and Attribute-Based Access Control (ABAC). 

• Distributed Systems Knowledge: Familiarity with modern event-driven architectures, message brokers (e.g., Kafka, Pub/Sub), and workflow orchestration engines (e.g., Temporal, Camunda, Airflow). 

Leadership & Soft Skills 

• Elite Communication: Ability to articulate complex architectural tradeoffs to business stakeholders while simultaneously arguing technical nuances with principal engineers. 

• Empathy-Driven Discovery: Exceptional capability to ask the right questions, uncover root-cause pain points from messy user feedback, and say "no" constructively to feature requests that do not align with platform scalability. 

• Systems Thinking: A natural tendency to see how individual components intersect to form a massive, complex enterprise ecosystem. 

What Will Success Look Like in the First 6 Months? 

• 30 Days: Map out the current topology of the ODS, ingestions pipelines, and orchestration touchpoints. Build relationships with the top 3 consuming engineering teams to understand their immediate friction points. 

• 90 Days: Establish a rigorous API contract governance process within the team. Deliver a refined 2-quarter roadmap addressing critical gaps in IAM/Authorization and order fulfillment bottlenecks. 

• 180 Days: Successfully launch a new high-throughput data pipeline or orchestration flow that measurably reduces multi-system order fulfillment latency while adhering to zero-trust authorization principles.