Technical Product Manager (Systems)

Description Local to Plano, TX Job Summary The Technical Product Manager (TPM) partners with Marketing Product Management and cross-functional stakeholders to translate customer and stakeholder needs into clear, testable system and sub-system requirements across hardware, firmware/software, connectivity, and cloud components. The TPM drives technical clarity and alignment from requirements through delivery for a defined product and/or system scope. This role focuses on one primary product and owns intake and prioritization for that product’s R&D Engineering pipeline, ensuring work is triaged, clarified, sequenced, and delivered predictably using objective criteria and transparent backlog practices. Responsibilities (Essential Functions) A. Product Definition Partnership (Shared with Marketing) Co-own product definition with Marketing PM (e.g., PRD/TPP, user needs, use cases, target outcomes), ensuring feasibility and testability. Translate PRD/user needs into system/sub-system requirements and technical acceptance criteria; drive shared understanding across engineering domains. B. System & Sub-system Requirements Ownership Author and maintain system and sub-system requirements that are unambiguous, feasible, verifiable, and traceable, with clear acceptance criteria. Decompose requirements across mechanical, electrical, firmware, software, connectivity, and cloud; ensure constraints and assumptions are explicit. Own requirements change control for the assigned product: impact analysis, review/approval facilitation, and controlled updates through the lifecycle. C. Traceability & Verification Alignment (Design Controls Support) Maintain bidirectional traceability from user needs → system requirements → design outputs → verification evidence (trace links, trace matrix, and rationale). Partner with Verification & Validation to ensure verification plans/protocols align with requirement intent and acceptance criteria; resolve ambiguity and gaps early. Manage requirements + traceability artifacts through PLM to support lifecycle governance, controlled changes, and auditable history. D. Technical Tradeoffs, Risks & Delivery Enablement Lead technical tradeoff discussions (architecture, scalability, performance, reliability, security, serviceability) for the assigned product, documenting decisions and rationale. Identify risks and dependencies; drive mitigation plans and timely decision escalation. E. Tools Jira: Manage   Knowledge, Skills, and Abilities    Strong systems thinking across HW/FW/SW/cloud; ability to translate needs into engineered requirements and interface definitions.    Requirements engineering discipline: decomposition, acceptance criteria, traceability, and change impact analysis.    Strong facilitation and communication skills; lead through influence across Engineering, Marketing, Quality/Regulatory, and IT.    Operational excellence in intake and backlog governance using Jira;…