Product Data Manager

Job Title: Product Manager - Data Applications Duration: 12+ Months (Possible extension) Location: Washington, DC 20005 Onsite Role (4 days a week) Responsibilities: • Looking for one senior person who operates simultaneously as a Product Owner for a data-intensive application, a Data Insights practitioner who can build and communicate what the data means, and a Testing leader who understands how every layer of the system fits together. • These three dimensions are not separate jobs that happen to sit on the same org chart line. • The person is embedded directly with a government client stakeholder and is the primary product and quality voice on the delivery. Product Owner: • This person is the one writing epics and user stories from a deep understanding of a data-intensive pipeline - not from templates. • Understand how data flows through the system, what business events trigger what processing steps, and how operations and engineering teams actually use the product. • Run a backlog grooming session in the morning, walk a government client through a new screen in the afternoon, and write the acceptance criteria that locks the story that evening. • Comfortable facilitating requirements sessions with program stakeholders who are not technical, translating what they hear into stories that engineering can build against and that testing can verify. • A client says "I need to know why that account is unclaimed" and this person turns it into a defined data requirement, a dashboard feature, and a test scenario — without involving three other people to make that translation. Data Insights and Data Science practitioner: • Build when the situation requires it — writing SQL, using LLMs and AI assistance, building a dashboard view, or producing an analysis artifact that answers a specific program question. • But their primary value is not raw technical output. • Ability to look at a pipeline that moves millions of records, identify what the data is actually telling the program, and communicate that story in a way a government client can act on. • They know what a meaningful metric looks like versus a vanity number. Testing: • Understands the full quality picture from the inside out. • They can read a batch execution log, write a database-level assertion, evaluate whether a security test is producing real evidence or just passing by coincidence, and hold a release gate when engineering wants to ship and the evidence is not there.