Technical Product Manager

Job Description As a Technical Product Manager (TPM) in the Platform Engineering team, you will be responsible for defining, delivering, and scaling the internal data platform capabilities that power our product and analytics infrastructure. This includes ownership of core platform capabilities around data ingestion pipelines, scalable storage systems, archival and retention workflows, lifecycle policies, and export mechanisms. You will work closely with engineering, infrastructure, compliance, and consuming product teams to ensure that the platform is robust, scalable, cost-effective, and aligned with business needs. Key Deliverables 1. Product Ownership & Strategy Define the vision, roadmap, and KPIs for data platform components such as ingestion, storage, archival, and export services. Maintain a clear articulation of how platform capabilities serve internal products and enable scale, performance, or cost optimizations. Develop a long-term platform evolution plan, identifying areas for abstraction, decoupling, and efficiency improvements. 2. Platform Capability Definition Translate requirements from internal customers (e.g., product teams, analytics, compliance) into platform features or capabilities, including: o Real-time and batch data ingestion connectors. o Multi-tiered storage architecture and capacity planning. o Time-bound archival and deletion strategies based on data classification and compliance. o Scheduled and on-demand export pipelines (to S3, Redshift, Snowflake, etc.). Define service-level expectations such as latency, throughput, durability, and retention guarantees. 3. Collaboration with Engineering Work closely with platform engineers and architects to translate product specs into technically sound solutions. Participate in architecture reviews and trade-off discussions related to scalability, availability, performance, and cost. Prioritize engineering effort across foundational improvements vs. feature asks from stakeholders. 4. Data Governance and Lifecycle Management Define and implement policies for data classification, retention, expiration, and archival across the platform. Ensure lifecycle policies are automated, audit-ready, and aligned with internal governance and external regulatory requirements. Coordinate with legal and compliance teams for ongoing review and audit support. 5. Internal Stakeholder Management Serve as the single point of contact for product teams who rely on platform data services. Create structured onboarding guides, SLAs, and usage documentation for internal consumers of the platform. Maintain a high-feedback loop from consuming teams and translate learnings into backlog items or roadmap shifts. 6. Cost & Performance Optimization Track data growth trends, storage costs, and ingestion pipeline performance across environments. Collaborate with the FinOps team to define budgets, set guardrails, and optimize for cost efficiency without degrading service. Proactively identify hotspots, cold data opportunities, and compression strategies. 7. Security & Compliance Alignment Ensure all data pipelines, storage, and exports adhere to enterprise-grade security practices, including encryption at rest, access controls, and data masking where required. Work with InfoSec to address vulnerabilities, enforce secure data export practices, and enable auditing. 8. Technical Communication & Documentation Maintain detailed internal documentation that outlines platform APIs, schemas, data models, usage guidelines, and integration steps. Communicate trade-offs, feature availability, and roadmap decisions clearly across a technical and non-technical audience. Represent the platform in internal engineering syncs, architecture forums, and quarterly business reviews. Tangible Deliverables As a TPM in the platform engineering team, your work results in measurable, reusable, and scalable assets that accelerate internal development velocity and reduce operational complexity. Key deliverables include: 1. Platform Roadmap and Backlog a. A continuously evolving 612 month roadmap aligned with business priorities, internal stakeholder needs, and engineering capacity. b. A well-groomed, prioritized backlog with clear technical specs, acceptance criteria, and linked epics/stories. 2. Product Requirements Documents (PRDs) a. Comprehensive specs for ingestion pipelines, storage tiering, archival policies, and data export services. b. Detailed edge-case handling, integration considerations, and non-functional requirements (latency, volume, compliance). 3. Cost Optimization Playbooks a. Actionable plans and dashboards co-developed with FinOps to monitor storage and pipeline usage, identify inefficiencies, and initiate cleanup/archive workflows. 4. Service SLAs & Internal Integration Guides a. SLA definitions for ingestion throughput, data availability, retention windows, and export latency. b. Onboarding documentation and how-to guides for integrating with the platform (e.g., publishing to ingestion topics, triggering data exports). 5. Cross-Team Alignment Artifacts a. Quarterly planning inputs, dependency matrices, rollout plans, and status trackers shared with infra, security, and product leads. Contribution to Delivery Management The TPM plays a key orchestration role in enabling disciplined, transparent, and dependable delivery of platform capabilities: 1. Sprint & Release Planning a. Breaks down platform epics into iterative deliverables with engineering leads. b. Sets sprint goals aligned with roadmap milestones and available team capacity. 2. Cross-Team Coordination a. Manages timelines and dependencies across infra, SRE, data engineering, and product teams. b. Facilitates decision-making on technical trade-offs and scope containment. 3. Risk & Blocker Management a. Identifies architectural or resource-related blockers early. b. Leads mitigation planning and escalation to leadership where needed. 4. Milestone Ownership a. Tracks progress across feature phases (design, development, testing, rollout). b. Owns delivery of pilot rollouts, adoption enablement, and full-scale launches. 5. Quality & Go-Live Readiness a. Partners with QA and SRE to define success criteria for new capabilities. b. Ensures operational readiness with documentation, monitoring, and rollback strategies in place. 6. Metrics-Driven Progress Tracking a. Defines delivery KPIs (e.g., lead time, backlog burn-down, adoption rate, SLA adherence). b. Builds and maintains reporting dashboards for leadership reviews.