Cloud & Hosting - Senior Product Owner - Observability
GSK (company site, opens in a new tab)5+ yrsBengaluruOn-siteDirect career pageEst. 25–45 LPA
Posted 9h ago
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Reach people at GSK
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at GSK you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own and prioritise the product backlog and roadmap for the Observability platform, linking backlog items to strategy and OKRs with measurable outcomes.
- Work closely with engineering teams to deliver, review, and accept increments, balancing new features with reliability bar and SLOs.
- Measure product adoption and value delivered using flow metrics and data-driven insights to iterate the roadmap and manage stakeholder expectations.
Minimum Requirements
- At least 5 years in technology with minimum 2 years owning a backlog in a platform or infrastructure context specifically.
- Hands-on expertise in modern observability tools (e.g., Grafana, Google Cloud Observability) and proven domain knowledge in metrics, logs, traces, telemetry pipelines, dashboards, alerting, reliability, and cost.
- Experience with agile backlog prioritisation by value and risk, working to OKRs, steering with flow metrics, managing stakeholders, and AI tooling for backlog refinement.
- Work Experience Required: 5+ years in technology including 2+ years as product owner in platform/infrastructure context.
Ideal Candidate Profile
- Experienced product owner comfortable making backlog sequencing decisions based on value over requester seniority with strong technical literacy to understand and challenge engineering estimates and reliability trade-offs.
- Data-driven decision maker focused on measurable outcomes such as adoption, throughput, cycle time, and error budgets rather than feature delivery volume.
- Collaborative in working with architects and reliability engineers, adhering to product boundaries and standards in a complex, regulated enterprise environment.