Technical Product Owner, Kubernetes
US, Canada, UK, Ireland, Estonia, Netherlands, Sweden, Israel, Mexico, ColombiaFull-TimeMiddle
Salary not disclosed
Apply NowOpens the employer's application page
Job Details
- Experience
- 2-5 years
- Required Skills
- KubernetesDevOpsNetworking
Requirements
- Experience working in a similar role of a Product Manager / Technical Product Owner
- 2–5 years of experience working closely with public cloud infrastructure, with a strong understanding of how it is operated and managed in production environments
- 3+ years of experience in the Kubernetes space
- A strong product sense for turning messy problems into clear scope and shipped value
- Deep curiosity and technical fluency in cloud fundamentals (identity/IAM, networking, compute, Kubernetes, observability, automation, and cost/billing concepts)
- Experience building solutions that leverage or focus on cloud technologies
- Excellent communication skills
- A bias for action and continuous improvement
- Coding experience is a plus
- 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” for frequent shipping, quick learning, and risk reduction.
- Maintain a disciplined cadence of backlog refinement, sprint readiness, and scope negotiation.
- Leverage hands-on DevOps experience and expertise in real-world workflows of cloud operators and practitioners.
- Use firsthand domain knowledge and ongoing 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 (aiming for 3-5 calls a week) and cross-functional DoiT stakeholders regularly to test ideas, validate assumptions, and pressure-test tradeoffs.
- Communicate clearly and confidently: share concepts early, take feedback openly, synthesize input into decisions, and explain “why” to build trust.
- Rely on hands-on DevOps experience to go deep with stakeholders into technical details of problems, solutions, and contexts.
- Support beta/design-partner motions by shaping hypotheses, success criteria, and rollout plans.
- Operate as a core member of the component’s Engineering team - present in daily collaboration, crisp in decision-making, and pragmatic about constraints.
- Partner with Engineering leads on sequencing, technical tradeoffs, and delivery planning.
- Ensure the component is cohesive across UX, APIs, data, and operational behavior, meeting a high bar for reliability and customer trust.
- Define “success” for the component with clear metrics (adoption, activation, workflow completion, time-to-value, retention, reliability signals, customer-reported impact).
- Instrument learning: make sure releases are measurable and insights reliably flow back into prioritization.
- Own release readiness for your component: documentation, enablement inputs, and clear communication of what’s new and why it matters.
- Ensure product requirements account for real-world cloud environments: IAM boundaries, auditability, guardrails, and safe defaults.
- Partner with security, support, and customer teams to anticipate edge cases and ensure the component earns trust over time.
View Full Description & ApplyYou'll be redirected to the employer's site
