Technical Product Owner - DoiT Cloud Intelligence - Core Services

The Opportunity

We’re hiring a Technical Product Owner to drive rapid delivery and iteration for the Core Services team of DoiT Cloud Intelligence, our platform that helps DevOps , Cloud Infrastructure , and FinOps teams manage public cloud environments effectively and efficiently. Core Services builds and operates foundational platform capabilities used across DoiT’s products and engineering teams. Its responsibilities include identity and access management , authentication and authorization , customer and tenant services , shared APIs , platform integrations , and other cross-cutting capabilities.

This role is designed for someone with a technical product mindset who is comfortable working deep within platform architecture , distributed systems , APIs , cloud infrastructure , and internal engineering workflows. You will help turn broad platform needs into clear technical product direction, sequenced investments, and reliably delivered capabilities.

You will report to a VP of Product and work as an embedded member of the Core Services Engineering team. You will collaborate closely with engineering leadership, architects, security, product teams, and internal platform consumers to determine what the team should build next and why.

Role clarity: VP of Product vs. Technical Product Owner

VP of Product (what they own)

• Sets the overall vision, strategy, positioning, and long-range roadmap for the platform area.
• Makes the highest-level prioritization calls across multiple components and investment themes.
• Aligns stakeholders across the company (executive leadership, GTM, partners) on direction and tradeoffs.
• Defines success at the portfolio/area level and ensures the area’s outcomes ladder up to company goals.

Technical Product Owner (what you own)

• Owns delivery, iteration, and learning velocity for the Core Services.
• Turns VP-level direction into clear problems to solve, a prioritized backlog, and incrementally shippable scope.
• Runs the feedback loop: discover → define → build → release → measure → iterate, repeatedly.
• Works within the Engineering teams to ensure they are always building the highest-value next increment with clarity, quality.
• Review technical designs, reason about tradeoffs and constraints, and understand their impact on delivery timelines and system behavior, without being the primary implementer.
• Leverages deep, hands-on DevOps experience and public cloud understanding to ensure that solution implementations are done correctly.

This distinction matters: the VP creates the “why” and “where”; the Product Owner ensures the “what next” is always sharp, validated, and shipping.

Responsibilities

Fast iteration and backlog leadership

• 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.
• Maintain a disciplined cadence of backlog refinement, sprint readiness, and scope negotiation to keep delivery predictable without slowing innovation.

Deep user and workflow understanding

• 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.
• Use firsthand domain knowledge and ongoing customer conversations to identify friction, gaps, and opportunities for differentiation.
• Prioritize enhancements that materially improve outcomes: speed , reliability , clarity , safety , governance , cost impact , or operational simplicity .

Customer validation and external communication

• 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.
• Communicate clearly and confidently: share concepts early, take feedback openly, synthesize input into decisions, and explain “why” in a way that builds trust.
• Rely on your hands-on, DevOps experience to go deep with stakeholders (internal/external) into the technical details of the problem, our solution, and the contexts and environments in which both of these exist.
• Support beta/design-partner motions where appropriate by shaping hypotheses, success criteria, and rollout plans.

Engineering-embedded technical product ownership

• Operate as a core member of the Core Services’ 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 - ensuring product intent survives implementation realities.
• Ensure Core Services are cohesive across UX , APIs , data , and operational behavior - and that it meets a high bar for reliability and customer trust.

Quality, outcomes, and measurement

• Define what “success” means for Core Services with clear metrics ( adoption , activation , workflow completion , time-to-value , retention , reliability signals , customer-reported impact ).
• Instrument learning: make sure releases are measurable and that insights reliably flow back into prioritization.
• Own release readiness for Core Services: documentation, enablement inputs, and clear communication of what’s new and why it matters.

Safety, governance, and trust by design

• 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 Core Services earns trust over time.

Qualifications

• 7–10 years of hands-on experience as a Platform Engineer , DevOps Engineer , SRE , Cloud Engineer , Solutions Architect , or a similar roles working with or building products for public cloud infrastructure ( AWS , GCP , and/or Azure ).
• A strong product sense for turning messy problems into clear scope and shipped value - without waiting for perfect information.
• Systems thinking: Ability to reason about complex distributed systems , architectural tradeoffs, and long-term platform evolution.
• Prioritization: Demonstrated ability to balance customer needs, engineering constraints, and platform investments when making prioritization decisions.
• Deep curiosity and technical fluency in cloud fundamentals ( cost/billing concepts , identity/IAM , networking , compute , Kubernetes , observability , automation ), and experience building solutions that leverage or focus on these technologies.
• Coding experience is a plus - enough to collaborate effectively with engineers, reason about feasibility, and understand system behaviors.
• Excellent communication skills: you can explain complex ideas simply, facilitate alignment, and confidently engage with customers and experts.
• A bias for action and continuous improvement: you ship, measure, learn, and iterate - building capabilities that become a meaningful competitive differentiator.

How success will be measured

• The Core Services’ roadmap advances through frequent, high-quality releases with clear customer value.
• Customer feedback loops are strong: you can show how insights translated into shipped improvements.
• Adoption and outcomes improve measurably ( usage , engagement , workflow completion , reliability , and customer impact ).
• The Engineering team consistently has clarity on the next most valuable increment to build - and why.