JOBSEARCHER

Technical Product Owner - W2 only

BeaconfireMalvern, PAMay 11th, 2026
Job Title: Technical Product OwnerLocation: Malvern, PA (Onsite)Duration: 12 monthsJob Description:Data and Architecture LeadershipUnderstanding of enterprise data architecture, APIs and graph-based models (supergraph)Ability to translate data and technical requirements into business impactAbility to coordinate across CDAO, engineering and platform teamsProduct Strategy & VisionOwnership of the C360 product vision and roadmap aligned to broader crew / client experienceExperience defining measurable outcomes (Adoption, data quality etc.)Strong Execution SkillsetThey will need experience managing ambiguous problem spaces and evolving requirementsCan manage short term delivery pressure with long term architecture plan.Stakeholder Management & InfluenceCan navigate across organization dynamics (CEI, CDAO, Engineering, business stakeholders)Can make decisions in ambiguity and create clarity for othersAlthough categorized as a business product manager role, it is highly technical in practice.Key Workstreams the Role Will OwnDB2 ModernizationA major and newly added responsibility.Requires working closely with technical partners and understanding:DB2Mainframe environmentsBeta and related systemsDeadline-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” AppsAs part of modernization efforts, additional apps without clear ownership have been transferred to this team.Required CompetenciesTechnical CompetenceNot 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 SkillsStrong get-stuff-done (GSD) mindset.Must independently push work forward under tight deadlines.Stakeholder & Relationship ManagementOne 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 ExpectationsCould be someone who:Already has relevant experience and can jump in immediately, orLearning extremely quickly and has adjacent domain knowledge.Should not be someone who goes too deep technically, there are architects and engineers for that.