Technical Product Owner

The Technical Product Owner is responsible for requirements gathering and close collaboration with engineering, infrastructure and product teams. This role involves ongoing interaction with a variety of end-users and internal stakeholders. The Technical Product Owner will create a vision for development projects, manage the product backlog, and prioritize scope. This role requires deep domain knowledge with strong experience in weighing priorities according to the needs and objectives of stakeholders and be accountable for each stage of the development process and the final product. Key Areas of Responsibilities •The Product Owner spends effort to manage the backlog and ensure requirements are complete for features and stories as well as definition of 'ready' and 'done' is clearly defined. •The Product Owner works through approved Demand Idea Intake process and subsequently adds the Idea to the Product backlog. •Collaborates with Business and Technology stakeholders to understand the business requirements and translate them to product requirements. The product owner also works on grooming the product backlog. •Analyzes processes and systems in detail and works closely with the development team to understand product development requirements, help identify areas for automation, improvement. •The Product Owner builds user stories according to the business requirements, review with the Development, QA and other team members, making sure everyone on the team understands the scope and how it can be tested. •The Product Owner defines the acceptance criteria of the user stories and review with Product Owner to make sure it meets the objective of the story. •Understanding the technical concepts, systems, and architectures to be able to write clear and concise stories for technical audiences and communicate with development teams. •The Product Owner should possess technical competencies to understand architecture and integration across multiple systems e.g. type of Integration, type of record, record structure, etc. •The Product Owner should have experience with any middleware solutions like MuleSoft, ESB, ASB to be able to write technical stories with proper description and acceptance criteria, along with technical documentation. •Analyze existing software applications to understand and document functionality, business rules, and data flows. •Develop user stories from solution architect's design and customer requirements including details of the data interfaces within the different layers of the data platform. •Translate high level requirements into products and product features. •Create work items in stories in backlog. Work closely with engineering and QA to validate that the work item meets acceptance criteria. •Prioritize stories, epics and themes to ensure work focuses on those with maximum value that are aligned with product strategy. Collaboration •Works with team members and stakeholders to help the team contribute towards improving the overall development Value Stream. Facilitates preparation and readiness for PI Planning •Collaborates with scrum master in preparation for ART activities, including PI Planning, System Demos, and the Inspect and Adapt, supports estimating. Required Qualification •Bachelor's degree or equivalent combination of education and experience with a preferred area of study in technology, business, or project management. •5 years experience as a product owner or technical product owner. •Demonstrates a strong understanding of SAFe Agile portfolio practices. •Working understanding of Azure Service Bus and MongoDb or similar middleware and repositories •Demonstrated strong analytical and problem-solving skills to understand complex business processes and systems. •Experienced with creating technical specs. •Experienced with Azure DevOps •Excellent communication and interpersonal skills to interact with both technical and non-technical stakeholders and translate business needs into technical requirements. •Basic project management skills to assist in the planning and execution of projects. •Good understanding of Workday or Salesforce CRM and CPQ.