Technical Product Owner - W2 Only

Job Title: Technical Product Owner Location: Malvern, PA (Onsite) Duration: 12 months Job Description: Data and Architecture Leadership • Understanding of enterprise data architecture, APIs and graph-based models (supergraph) • Ability to translate data and technical requirements into business impact • Ability to coordinate across CDAO, engineering and platform teams Product Strategy & Vision • Ownership of the C360 product vision and roadmap aligned to broader crew / client experience • Experience defining measurable outcomes (Adoption, data quality etc.) Strong Execution Skillset • They will need experience managing ambiguous problem spaces and evolving requirements • Can manage short term delivery pressure with long term architecture plan. Stakeholder Management & Influence • Can navigate across organization dynamics (CEI, CDAO, Engineering, business stakeholders) • Can make decisions in ambiguity and create clarity for others Although categorized as a business product manager role, it is highly technical in practice. Key Workstreams the Role Will Own • DB2 Modernization • A major and newly added responsibility. Requires working closely with technical partners and understanding: • DB2 • Mainframe environments • Beta and related systems Deadline-driven: • Expected to be completed by 12/31, though aggressive. • Requires navigating complexity across teams. C360 (Customer 360 Data Pipeline) • A pipeline syncing Dynamics CRM → AWS using agreed-upon architectural patterns. • Supports an enterprise-wide, uniform data architecture to enable insights and intelligence. • CRM holds major data responsibility, but AWS is used by other groups; requires alignment. • SuperGraph is used to unify data access and utilization. Other “Inherited” Apps • As part of modernization efforts, additional apps without clear ownership have been transferred to this team. Required Competencies Technical Competence • Not expected to be an architect or deep technical expert. • Must understand systems well enough to: • Identify roadblocks. • Communicate effectively with technical stakeholders. • Move initiatives forward quickly. • Comparable to an old school Business Systems Analyst level of system understanding. Execution Skills • Strong get-stuff-done (GSD) mindset. • Must independently push work forward under tight deadlines. • Stakeholder & Relationship Management • One of the most important skills. Requires: • Navigating a complex organization with unclear ownership structures. • Chasing down the right people. • Influencing priorities across teams. • Managing dependencies. • Managing business-side change associated with modernization. • Candidate Expectations Could be someone who: • Already has relevant experience and can jump in immediately, or • Learning extremely quickly and has adjacent domain knowledge. • Should not be someone who goes too deep technically, there are architects and engineers for that.