# Technical Product Owner, DevOps Platform - US

About OneView Commerce

For retailers with thousands of shops, commerce platforms have historically fallen into two categories, each with significant drawbacks. Web-native platforms move fast but were never built for a shop floor. Legacy store systems were built for the shop floor but take a year to change anything. OneView Commerce is the third option: a headless commerce platform for physical retail that lets the world’s largest retailers innovate just as quickly as the smaller ones. We ship store experiences that deploy fast out of the box, and we give retailers the freedom to build their own on top of a headless transaction engine engineered for the physical store rather than the browser.

Our customers are global retailers who build on OneView because it lets them keep moving: new journeys, new channels, and new store formats ship continuously rather than waiting on the next multi-year program.

Founded in 2010 to close the gap between fast-moving e-commerce and slow-moving in-store systems, OneView’s founding principle is a single view of customers, orders, and inventory throughout the shopping journey. That remains our mission as we enable retailers to deliver exceptional store experiences that build loyalty.

We are a remote-first team with Viewers working across the globe, and we operate as a trusted provider of digital commerce systems for leading retailers.

Position summary

OneView is looking for a Technical Product Owner with a DevOps engineering background to own the flow of work into our DevSecOps team. The team builds and secures the platform every other team here depends on, which makes it the most contended team in the company. Work reaches the team from two sources: requests from software engineering, QA, agile delivery, product support, customer implementation, security, and leadership; and the Platform Engineering roadmap, which includes building our internal developer platform (IDP). You decide what the team takes on, in what order, and what it declines, and you will say “no” and “not yet” more often than “yes”.

You report to the Sr. Director of Platform Engineering, who leads the DevSecOps pillar and sets product vision, strategy, and the roadmap, with input from the VP of Engineering, the Chief Architect, and the team’s engineers. You work closely with the Sr. Director while it is drafted. The Sr. Director owns how the work gets done (technical approach, standards, assignment, and quality), and you own priority. Expect the Sr. Director and others more senior than you to challenge your ranking. You are expected to defend it with evidence and make adjustments when a stronger case is made.

The role needs hands-on DevOps knowledge. You cannot specify a pipeline change, a cluster upgrade, a secrets rotation, or a new set of guardrails without understanding what each one puts at risk.

We use AI throughout our work and want you to find uses for it we have not thought of. We also expect you to do this job well if it were switched off tomorrow, because the priority calls and the stakeholder relationships depend on you.

This is an individual contributor role with no direct reports.

Responsibilities

• Own the intake path into the DevSecOps team, and qualify every request at the point of arrival: the desired outcome, affected parties, impact, dependencies, and any hard due dates. Where a request specifies its own solution, establish the problem it is meant to solve before the team commits to that solution.
• Rank inbound requests and Platform Engineering roadmap items on one backlog by urgency and value, publish the ranking, and keep it refined far enough ahead that an engineer can start without waiting on you for clarification. Make the trade-offs explicit, and answer to the teams whose work a ranking displaces. A stakeholder should be able to see what their request is weighed against and where it sits without escalating.
• Bring the team’s improvement ideas to the Sr. Director as roadmap proposals, with the problem, scope, and effort worked out with the team’s engineers and architects.
• Turn the Platform Engineering roadmap, including the IDP build-out, into backlog items the team can deliver, and keep their status current and published for the teams that depend on them. Report IDP adoption and user feedback to the Sr. Director.
• Limit work in progress to what the team can finish, resist mid-sprint insertion, and make the cost of an interruption visible when one is unavoidable.
• Translate r…