Product Owner - Technical # 26-25391
Product Owner - Technical # 26-25391
Posted today
SENIORITY
Lead
About the role
- Support and contribute to the product roadmap for internal developer platforms (CI/CD (Continuous Integration/Continuous Deployment), infrastructure, observability, automation tools) supporting client.
- Own and manage the product backlog, translating customer needs into clear epics, user stories, and acceptance criteria.
- Track and report on product metrics such as adoption, user satisfaction, operational efficiency, and productivity indicators.
- Communicate product updates, prioritization decisions, and progress to cross-functional stakeholders.
- Support planning, intake, and capacity management activities for platform initiatives.
- Stakeholder Engagement:
- Gather and represent feedback from internal engineering teams through interviews, surveys, office hours, and ongoing engagement.
- Partner closely with engineering teams (SRE (Site Reliability Engineering), DevOps, Solutions Architecture) to balance product priorities with technical execution.
- Collaborate with brand product teams, the brand SRE team, Byte platform engineering, and enterprise cloud and security teams.
- Platform Adoption & Automation:
- Support adoption of platform capabilities through customer-focused prioritization and clear communication.
- Contribute to self-service and automation initiatives that reduce manual support work and improve developer efficiency.
- People Grower: You share knowledge freely, create learning opportunities, and make the team around you better.
- Influencer: You earn credibility through consistent delivery and clear communication. You bring people along rather than going it alone, and you build trusted relationships across teams.
- Results-Focused: You take ownership of outcomes, not just tasks. You define what success looks like, execute with urgency, and follow through.
- In addition, this role requires:
- Service orientation: treating engineering teams as customers of the platform and holding a high bar for their experience.
- Clear prioritization communication: stakeholders always understand what is being built, what is not, and why.
- What Does Success Look Like:
- Platform features and improvements are clearly defined, well prioritized, and delivered with high quality.
- Engineering teams adopt platform capabilities and provide positive feedback on usability and value.
- Backlog items are consistently ready for development with clear acceptance criteria.
- Stakeholders understand prioritization decisions and feel informed and aligned.
- Self-service and automation initiatives measurably reduce manual support effort.
- Product metrics are tracked and actively used to inform decisions and improvements.
- The Technical Product Owner III is viewed as a reliable, collaborative partner by engineering teams and stakeholders.
- About US Tech Solutions:
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
