Technical Product Manager

Job Description

Job Description

Job Title: Technical Product Manager
Location: Fully Remote for Minneapolis MN, Atlanta GA, and Chicago IL locations, and hybrid in Milwaukee WI for 3 days onsite
Duration: 4 Months contract with high possibility of extension

Top Requirements:

• Product Management
• Wealth Management & investment services background (Preferred)
• Business Analysis and Requirement gathering (5 years)

Work with product, design, and operations teams to deliver innovative ways to serve our learners.
• Supports what products to make, ensuring those products get made and reporting back on how users respond to products.
• Works with partners like engineering and design teams to strategically plan products and their development
• Works with external third parties to assess partnerships and licensing opportunities runs beta and pilot programs with early-stage products and samples and becomes an expert with respect to the competition.
• Demonstrated ability as a technical product manager, product owner, or solutions architect.
• Proven experience as a software engineer, data engineer or SDET.
• Technical fluency - Ability to understand, discuss, and challenge architectural concepts, trade offs, and new opportunities with technical team members. Understand technical issues well enough to make the right decisions about prioritizing not only new product features but also reducing technical debt or improving resiliency.
• Excellent written and verbal communication of ideas, narratives and complex technical information to a broad audience including, but not limited to: executives, stakeholders and engineers.

Responsibilities:
• Work with engineering and key teams to deliver scalable and extensible software solutions to support business needs.
• Coordinate with business line product managers and other component teams to define your team's roadmap and delivery of product features.
• Translates business needs, user needs and technological capabilities into user stories and product specifications that will lead to successful implementations.
• Document detailed acceptance criteria that developers and QA can rely upon to complete their tasks.
• Drive Agile principles and methodologies, including owning the team backlogs, defining and prioritizing epics, features, user stories and other artifacts to support development goals.
• Define objective requirements with success criteria.