- Translate the VP’s strategy into a sequenced backlog of problems, user stories, and acceptance criteria that the Engineering team can deliver continuously.
- Keep work “thin-sliced” so the team can ship frequently, learn quickly, and reduce risk through iteration.
- Leverage your hands-on DevOps experience and expertise in the real-world workflows of the professionals you’re building for - especially cloud operators and practitioners.
- Often 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.
- Operate as a core member of the component’s Engineering team - present in daily collaboration, crisp in decision-making, and pragmatic about constraints.
- 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.
KubernetesProduct ManagementDevOps+1 more