As the Product Owner II at M&T Bank, your main responsibilities include developing and evolving the product vision and roadmap for APIs, prioritizing the API feature backlog, and translating complex business use cases into clear, actionable product requirements. You will work closely with engineering and architecture teams to ensure APIs are scalable and secure, while also actively participating in Agile ceremonies to ensure alignment on delivery.

To qualify for the Product Owner II position at M&T Bank, candidates should have a Bachelor's degree and a minimum of 6 years of experience in business, analytical, technical, or product roles. Alternatively, a combination of a minimum of 10 years of higher education and/or relevant work experience can be accepted. Strong communication skills and an understanding of Agile and Lean principles are also important for this role.

Preferred experience for the Product Owner II position at M&T Bank includes prior experience in prioritizing competing tasks, employing Design Thinking principles, and collaborating with user experience teams on product design. Familiarity with product design best practices and working in digital capabilities management will also enhance your candidacy.

M&T Bank supports work-life balance for its Product Owner II employees by offering flexible work arrangements along with generous PTO policies. Our Banking Officers receive 25 days of paid time off plus 12 paid holidays, along with 40 hours of paid volunteer time each year to support community involvement.

M&T Bank offers a competitive compensation package including health, welfare, and retirement benefits, a 401(k) match of 5%, generous PTO, and additional paid volunteer hours. These benefits reflect our commitment to fostering a positive and supportive work environment for our employees.

When defining the product roadmap as a Product Owner II, it’s essential to align the roadmap with business objectives and user feedback. Start by gathering insights from stakeholders, analyzing market trends, and identifying key opportunities that drive the product vision forward. Prioritize features based on customer needs and technical feasibility while ensuring transparency with your team for collaborative understanding.

To translate business use cases into API product requirements, I first engage with stakeholders to understand their needs fully. For example, if a user indicates a need for secure data sharing, I’d define specific API functionalities that cater to this need, while drafting clear user stories and acceptance criteria that the engineering team can use to build effective solutions.

I ensure APIs are designed with technical integrity and user value by involving both technical teams and end users throughout the development process. Conducting user feedback sessions and usability testing helps in refining your APIs. Pairing this with rigorous technical reviews ensures that the APIs are both robust and user-friendly.

For backlog prioritization, I employ a combination of value assessment, technical feasibility, and stakeholder input. Utilizing a prioritization framework such as MoSCoW helps me categorize tasks effectively, ensuring that we focus on delivering features that align with the overall product vision and yield the highest business value.

My experience with Agile methodologies has involved embracing continuous improvement and adaptive planning. I actively participate in Agile ceremonies like sprint planning and retrospectives, which provide opportunities to adapt our approach based on team feedback. This iterative process enables the team to remain focused on delivering value while promoting collaboration and transparency.

I gather and integrate feedback through structured feedback loops such as regular check-ins with internal users, surveys for external users, and usability testing sessions. Consistently analyzing this feedback allows me to adjust the API roadmap and ensure that we meet the evolving needs of our users effectively.

I have significant experience in creating and maintaining API documentation. To make it developer-friendly, I ensure the documentation is clear, comprehensive, and includes examples and use cases. Collaborating with developers during the documentation process helps identify potential gaps and improve on existing materials.

When handling competing priorities, I rely on open communication with all stakeholders to gather insights on their needs. Emphasizing a collaborative approach allows for alignment on objectives. I prioritize tasks based on urgency and business impact while remaining flexible to adjust as new information or priorities emerge.

Staying updated on industry trends involves a combination of continuous learning through online courses, attending relevant conferences, and engaging with thought leaders in the field via webinars. I also subscribe to industry publications and follow key blogs to ensure I’m informed of best practices and emerging technologies related to API design and management.

A notable instance was when I had to independently decide on the prioritization of a critical API feature amidst conflicting priorities. Understanding the strategic importance of this feature for user engagement, I advocated for its development, ultimately leading to increased user satisfaction and engagement metrics.