Product Owner - Grid-scale Energy Storage System Control Software (m/f/d)

As a Product Owner at Fluence for Grid-scale Energy Storage System Control Software, your primary responsibilities involve cross-functional collaboration with engineering and product management teams to execute the Fluence OS development plan. You will lead the creation of user stories from customer requirements, manage the agile team's backlog, and ensure product compliance with regional grid codes. Your role also includes supporting technical documentation and delivering presentations to customers, ensuring that product offerings are not only compliant but also aligned with customer needs.

To be a successful Product Owner at Fluence, candidates should hold an engineering degree, preferably in Electrical or Power Systems. You need a solid 5+ years of experience in utility-scale electrical power systems and at least 2 years in a product owner role within an Agile environment. It's crucial to have a comprehensive understanding of grid following and grid forming applications and knowledge of grid interconnection agreements and technical requirements from ISOs and transmission owners.

A Product Owner at Fluence should excel in strategic thinking and problem-solving, with the ability to solve complex technical challenges. Excellent verbal and written communication skills are essential for conveying technical information clearly. Organizational competencies are also important for managing the product backlog and ensuring timely product development. You should be detail-oriented, with the ability to work collaboratively in an agile team environment while embracing change.

At Fluence, the Product Owner ensures alignment with customer needs by analyzing customer requirements (CRs) and integrating market insights into the product roadmap. By prioritizing these requirements and creating actionable user stories, the Product Owner facilitates the development process in collaboration with the agile team. Additionally, the Product Owner supports the product management and sales teams in delivering tailored technical presentations to further refine and enrich customer offerings.

Grid codes and regulations are paramount for the Product Owner role at Fluence because they shape how products must function to maintain compliance in various regions. The Product Owner's understanding of these codes allows them to guide the engineering team in developing compliant solutions that align with the company's growth strategy. This not only protects the company legally but also enhances the value of the solutions provided to customers.

To prioritize the product backlog effectively, it's essential to evaluate the impact and value of each task. I focus on customer feedback, company objectives, and compliance requirements to determine priority. I also engage with stakeholders regularly, ensuring that their insights are reflected in the backlog to align with strategic goals.

I have over 2 years of hands-on experience as a Product Owner in Agile environments where I've led cross-functional teams in iterative development. I emphasize collaboration, adaptability, and continuous improvement, organizing regular stand-ups, sprint planning sessions, and retrospectives to ensure the team is aligned and progressing towards our goals.

Handling changes in customer requirements is all about flexibility and communication. I ensure that any new requirements are assessed for impact on the current timeline and resources. I facilitate discussions with the agile team to incorporate necessary changes without derailing our development process, keeping stakeholders informed throughout.

I utilize a mix of surveys, direct interviews, and usability tests to gather customer feedback. Additionally, I keep an open line of communication with our sales teams to capture direct feedback during client interactions, ensuring that the development aligns well with customer needs and expectations.

To ensure the technical feasibility of user stories, I engage closely with engineering teams right from the requirements-gathering phase. I encourage technical discussions to assess risks and resources, ensuring that every user story is framed in a way that can be realistically delivered within our timelines.

My approach to documentation involves maintaining clear and comprehensive technical and commercial documentation throughout the product lifecycle. I document user stories, acceptance criteria, and decisions made during development to ensure transparency and provide a resource for both current and future team members.

I actively read industry publications, participate in webinars, and attend conferences related to grid systems and energy storage. Additionally, I engage with communities and professional networks to share and gather insights regarding emerging regulations and best practices.

I adapt my communication style based on the audience. For technical stakeholders, I use data-driven language and detailed explanations, while for non-technical stakeholders, I focus on high-level insights and the benefits of the product. I also encourage feedback to ensure clarity and alignment across all parties.

One major challenge I've faced is balancing competing priorities among stakeholders. I overcame this by implementing a structured prioritization framework that considered both business impact and customer needs, ensuring that decisions are made transparently and collaboratively to maintain stakeholder trust.

I am motivated by the opportunity to bridge the gap between customer needs and engineering solutions creatively. It's incredibly fulfilling to see a product evolve from concept to reality, positively impacting our clients and contributing to the advancement of sustainable energy solutions.