Product Owner

**Position Summary**
- Driving Simulation Software-In-the-Loop (SIL) testing solutions for virtual validation
- Data Processing tools for data visualization, extraction, insights, and analysis
- The Simulation and Tools’ ready-to-use products are derived from shared foundations and components called Platforms.
- In the Simulation and Tools Organization all managers and senior managers are also Software Project Owners and either Platform Owners or Platform Architects.
- A Simulation and Tools Product Owner is assigned to one or more products that are derived from a Platform under the leadership of the Platform Owner. Though it is not always the case, for this specific Product Owner role the people leader at the Aptiv offices in Wuppertal Germany is also the Platform Owner of the Digital Twin Platform.
- A Simulation and Tools Product Owner is an Engineer involved in Software Development whose typical daily duties are associated with the Software Development Leadership activities of being a Product Owner rather than direct Software Development ‘coding’. However, it is expected that a Simulation and Tools Product Owner is able to also contribute as a software developer (a ‘coder’) for the products owned by the Product Owner and the Platform from which the products are derived.

**Your Role as a Product Owner**
- Own and maintain the Product Backlog. A Backlog of work including and derived from Change Requests, Risks, and Problems associated with the assigned Products.
- Responsible for the internal stakeholder & customer communication for the assigned product including the documentation of stakeholder and customer requirements.
- A Product Owner is cheerful, optimistic, honest, pleasant, outgoing, compassionate, rigorous, attentive, respectful, clear, and persistent. They are excellent communicators who convey confidence and eager supportiveness.
- Accept or reject stories. Accepting a story includes validation that the story meets acceptance criteria and has the appropriate acceptance tests, and that it meets its Definition of Done (DoD).
- The Product Owner writes the stories for the software developers to implement. The Product Owner determines if the stories are implemented per the acceptance and definition of done criteria.
- Participate in the development of acceptance criteria for features and draft them when feasible.
- The Product Owner documents the feature creation and feature change details that flow from change requests and oversees the work of software developers as they document the software requirements and software requirements changes, and the work of product architects and they document the product architectures and product architecture changes that flow from the feature creation and feature change details.
- Review and reprioritize the backlog as part of the preparatory work for Iteration including coordination of content dependencies with other POs and all relevant stakeholders.
- Protect the long term technical integrity of the feature/product.
- Involve the team in backlog refinement to achieve minimum handover and maximum joint understanding.
- Understand the scope and need for architectural roadmaps and collaborate with Architects and Engineering to assist with decision-making and sequencing of the key technological infrastructures.
- Define the team’s specific objectives for the upcoming Project/Program Increment.
- Play an essential role in Sprint Team Demos as well as Project/Program Increment demos to ensure that it will show the most critical aspects of the solution to the stakeholders.
- Coordinate content dependencies with other POs and all relevant stakeholders.
- Participate as a member of the extended Project Management team and review and contribute to the project-level vision, roadmap, and content presentations.
- Has a total responsibility for the Quality of the feature/product/ component.
- Ensuring every story, every test, and every release process step is executed to deliver software products that flawlessly achieve the stakeholder/customer.

**Your Background**
- Master’s degree in engineering, computer science, or physics (master’s degree in software engineering preferred or computer science with concentration in software development preferred).
- Ability to code/script in C++ and Python 3 [you will be tested during the evaluation process] (2+ years of job assignment experience preferred)
- 2+ years of combined education and on-the-job experience in modeling and simulation (5+ years of job assignment experience preferred)
- 1+ years of project management experience (2+ years of job assignment experience and a professional project management certification or MBA preferred)
- Understanding of the SPICE (ISO 15504) standard (2+ years of job assignment experience involving SPICE compliant software development preferred)
- Understanding of Agile software development (2+ years of job assignment experience involving work in the agile scrum working model prefe