Technical Product Owner, Kubernetes
US, Canada, UK, Ireland, Estonia, Netherlands, Sweden, Israel, Mexico and Colombia. We are also open to contractors in Eastern Europe.Full-TimeMiddle
Salary not disclosed
Apply NowOpens the employer's application page
Job Details
- Experience
- 2–5 years of experience
- Required Skills
- KubernetesDevOpsNetworking
Requirements
- 2-5 years of experience in a Product Manager / Technical Product Owner role
- 2-5 years of experience with public cloud infrastructure, managed in production
- 3+ years of experience in the Kubernetes space
- Strong product sense for turning messy problems into clear scope
- Technical fluency in cloud fundamentals (identity/IAM, networking, compute, Kubernetes, observability, automation, cost/billing concepts)
- Experience building solutions leveraging cloud technologies
- Coding experience (a plus)
- Excellent communication skills
- Bias for action and continuous improvement
- Experience with developer tools, infrastructure, and SaaS platforms (bonus)
- Experience working directly with a founder or early-stage startup (bonus)
- Background in analytics, growth, or UX research (bonus)
Responsibilities
- Translate the VP’s strategy into a sequenced backlog of problems, user stories, and acceptance criteria.
- Keep work “thin-sliced” so the team can ship frequently, learn quickly, and reduce risk through iteration.
- Maintain a disciplined cadence of backlog refinement, sprint readiness, and scope negotiation.
- Leverage hands-on DevOps experience and customer conversations to identify friction, gaps, and opportunities.
- Prioritize enhancements that materially improve outcomes: speed, reliability, clarity, safety, governance, cost impact, or operational simplicity.
- Speak with customers and cross-functional DoiT stakeholders regularly to test ideas, validate assumptions, and pressure-test tradeoffs.
- Operate as a core member of the component’s Engineering team, present in daily collaboration and crisp in decision-making.
- Partner with Engineering leads on sequencing, technical tradeoffs, and delivery planning.
- Define what “success” means for the component with clear metrics (adoption, activation, workflow completion, time-to-value, retention, reliability signals, customer-reported impact).
- Ensure product requirements account for real-world cloud environments: IAM boundaries, auditability, guardrails, and safe defaults.
View Full Description & ApplyYou'll be redirected to the employer's site
