Technical Product Owner

TEKsystems•Dayton, OH

12d•$55 - $65•Hybrid

About The Position

We are seeking a Sr. Technical Product Owner to own the EDB end-to-end data platform, which includes Vault ETL and KEL's Cosmos-backed customer APIs. The ideal candidate will be technically fluent to effectively question requirements without owning architecture or implementation. This role's primary value lies in disciplined requirements discovery, integrated prioritization, cross-team coordination, customer-facing accountability, and shielding engineering teams from unstructured operational and stakeholder noise. EDB is a combined platform that handles incoming data processing (Vault: ETL, orchestration, processing, validation, and delivery) and data normalization into customer-facing entities (KEL: Normalization into customer-facing entities exposed through Cosmos-backed APIs/shells). The Product Owner will be responsible for the end-to-end product outcome, from upstream data requirements through delivery to downstream customers.

Requirements

Sr-level experience owning a technical platform, data product, API product, or integration platform.
Strong requirements discovery and stakeholder-management skills.
Ability to turn ambiguous requests into clear outcomes, acceptance criteria, dependencies, and measurable expectations.
Experience coordinating delivery across multiple engineering and external stakeholder teams.
Sufficient technical fluency to understand and question: ETL and distributed data-processing workflows; Data schemas, contracts, quality, freshness, volume, and lineage; APIs and downstream consumer compatibility; Cosmos DB concepts such as throughput, partitioning, indexing, throttling, consistency, scale, and cost; Operational and reliability implications of customer requirements.
Ability to identify when a seemingly simple request needs technical review.
Confident, diplomatic, and persistent—capable of building relationships first, but driving accountability and escalating when necessary.
Strong customer-facing communication, including the ability to explain trade-offs and deliver a well-supported “no” or alternative proposal.

Nice To Haves

Experience/exposure to Azure Cosmos DB.

Responsibilities

Serve as the primary product contact for upstream data teams, downstream consumers, Vault, and KEL.
Solicit, clarify, challenge, and mature requirements before bringing them into refinement.
Own and order the integrated EDB backlog across Vault and KEL.
Coordinate dependencies, sequencing, milestones, and customer expectations across all involved teams.
Ensure requirements cover data quality, schema changes, volume, freshness, compatibility, security, migration, and operational needs.
Own customer-facing intake and triage: understand impact, route issues to the correct technical team, communicate status, and confirm closure.
Act as a buffer for engineering so technical teams are not constantly interrupted by unstructured external requests.
Ensure external documentation, release communication, and onboarding material exist and are business-friendly.
Establish accountability around repeatedly delayed specifications, dependencies, and customer inputs.
Validate that delivered work achieves the complete EDB customer outcome—not merely that Vault or KEL completed its individual component.