Technical Product Owner

Technical Product Owner

Role description

  • Product decisions – be at the center of most major product decisions as you focus the engineering product and technical decision making to center around customer and business alignment. - Provides the vision, roadmap and strategy of the product while collaborating with different stakeholders and teams (marketing, sales, UX, development).
  • End user definitions – clear articulation of the types of our target prototypical users including their background, tools they use, how they solve the problems we’re solving today.
  • Feature specifications – written as user stories and agile feature requirements on a per sprint basis and stored in TFS – written (often with pictures/mockups/prototypes) to illustrate how users interact with our features. These don’t cover architecture, design, or implementation details that are the domain of development, but good ones will absolutely influence those things. Short, concise specifications provide the context for high quality engineering architectural design and implementation. Specs define the boundary of technology and people.
  • Product backlog - prioritizes epics/features/requirements based on product decisions, market research and business value - Clearly defines acceptance criteria for each requirement. - Ensures that the team always has an adequate number of ready requirements to work on - Facilitates the backlog refinement meeting.
  • Delivery milestones – provides the development teams with a framework for thinking about delivery pipeline. It is the definition of what needs to be done, the map to get to where we need to be. The engineering team then can work on the breakdown that best delivers.
  • Quality control - makes sure the product being built produces value to the customers – Only member of the agile team empowered to accept requirements as "done". - Participates in the team meetings and it is always available for the team providing vision and direction. – Shows produced value to stakeholders and business during iteration reviews.
  • Learn and refine – evaluate execution on previous sprints, all of which leads to better future sprint definitions, new features, and prototypes – Requirements end up in the product backlog attached to user stories.

Basic qualifications

  • English fluency.
  • Bachelor’s Degree in systems engineering, Software Engineering or similar.
  • Strong knowledge of Agile and Lean methodologies and best practices.
  • Experience managing the development of a product.
  • Strong foundations on computer science (data structures, algorithms, problem-solving, operating systems).
  • Influence to convince key leaders towards the right solution.
  • Good teamwork and communication skills.
  • 5 or more years of experience in related fields.
Apply Now