# Technical Product Owner, DevOps Platform - US

OneView Commerce

29d•$120,000 - $135,000•Remote

About The Position

OneView Commerce is seeking a Technical Product Owner with a DevOps engineering background to own and prioritize work entering its DevSecOps team. The team builds and secures the platform used by the rest of the company. Demand comes from internal stakeholders and from the Platform Engineering roadmap, including the internal developer platform (IDP). The Product Owner qualifies requests, decides their priority, and makes trade-offs transparent, including declining or deferring work when appropriate. The role reports to the Sr. Director of Platform Engineering, who leads the DevSecOps pillar and owns product vision, strategy, the roadmap, and technical execution. The Product Owner works closely with the Sr. Director and is responsible for priority, supported by evidence and open to revising decisions when stronger cases are presented. Hands-on DevOps knowledge is essential to understand the risks associated with platform changes. This is an individual contributor role with no direct reports. OneView is remote-first and uses AI in its work, while expecting the role to remain effective without AI.

Requirements

At least 2 years as a Product Owner, Technical Product Owner, or in an equivalent backlog-owning role.
At least 3 years of hands-on experience in DevOps, security operations, platform engineering, or site reliability engineering.
Working experience in most of the following areas, using the listed or comparable tools: Git; CircleCI, GitLab CI/CD, or GitHub Actions; AWS or Google Cloud; Docker and Kubernetes; Terraform, CloudFormation, or Ansible; Python, Bash, or JavaScript; Datadog, AppDynamics, CloudWatch, or Splunk; Linux or UNIX.
Working knowledge of cloud infrastructure and delivery-pipeline security practices, including access control, secrets handling, and pipeline guardrails.
Ability to conduct intake conversations with engineers and produce complete requirements, identifying omissions and downstream impacts.
Ability to write acceptance criteria that account for adjacent systems, integrations, and existing platform behavior.
Ability to translate business requirements into actionable technical language and technical constraints into terms business stakeholders can use to make decisions.
Experience ranking infrastructure or platform work against visible feature or customer work and defending the ranking to stakeholders.
Experience declining a request from a senior stakeholder, explaining the reasoning, and maintaining the relationship.
Experience coordinating dependencies across multiple internal teams and external parties, including operating a dependency tracker used by other program teams.

Nice To Haves

Point-of-sale experience.
Experience in a shared-services or internal-platform team serving internal customers with competing priorities, and the ability to describe how its queue was managed.
On-call experience and an understanding of how unplanned work affects delivery.
Knowledge of DevSecOps principles, including shifting security left and zero trust.
Experience with platform engineering and GitOps, including internal developer and monitoring platforms, self-service infrastructure, and declarative deployment.
Experience with reliability and resilience practices such as chaos engineering, penetration-testing requirements, and disaster-recovery drills.
FinOps awareness and cloud-cost accountability.
AI and AIOps fluency, including AI-assisted automation, predictive monitoring, self-healing pipelines, and AI use for story generation, acceptance-criteria drafting, and requirements traceability.
Experience implementing a measurable operational improvement that improved a delivery team's speed or quality, and ability to explain the change and its measured effect.
AWS, Google, or Microsoft DevOps credentials.

Responsibilities

Own the DevSecOps intake process and qualify requests by identifying desired outcomes, affected parties, impact, dependencies, and hard due dates.
Clarify the underlying problem before committing to a solution proposed by a requester.
Rank inbound requests and Platform Engineering roadmap items on a shared backlog, publish and refine the ranking, make trade-offs explicit, and explain decisions to stakeholders whose work is displaced.
Bring team improvement ideas to the Sr. Director as roadmap proposals, with problems, scope, and effort worked out with engineers and architects.
Translate the Platform Engineering roadmap, including the IDP build-out, into deliverable backlog items and keep status current and visible to dependent teams.
Report IDP adoption and user feedback to the Sr. Director.
Limit work in progress, resist mid-sprint additions, and make the cost of unavoidable interruptions visible.
Translate requester needs into platform, automation, tooling, and security requirements, with stories and testable acceptance criteria covering failure impact, rollback, access control, auditability, cost, and functional outcomes.
Own intake and prioritization of unplanned and obligation-driven demand, including post-incident remediation and work generated by compliance, audit, and customer security commitments.
Coordinate dependencies across internal teams and third-party vendors, surfacing them early enough to avoid queue delays.
Report on request-to-delivery lead time, work in progress, throughput, queue depth, unplanned work, and the balance between inbound requests and platform initiatives.
Use flow metrics to make the case for additional capacity or automation.