About The Position

The Product Engineer builds internal software for ZURU teams and works within a business unit rather than a central engineering office. The role owns a business problem end to end, from speaking with the person who has the problem through validation, development, production use, and eventual graduation or retirement. Business owners define the desired outcome alongside the engineer; there is no specification handoff. This role is for internal products, separate from the organization responsible for external product engineering. The engineer is expected to reach a Go/No-Go decision with the business within five days of assignment, ship applications that reach their target users, and maintain no more than three ungraduated applications. Over time, the work should shorten the Group’s median time from an accepted business request to a live solution. Applications should demonstrate weekly active adoption among their target users and have a clear exit to the supported estate, retirement, or a team responsible for packaged systems.

Requirements

  • Able to work with finance, sales, or operations teams to understand how they work.
  • Able to direct coding agents effectively and identify incorrect output.
  • Able to read and reason about code.
  • Able to ship working software rather than prototypes.
  • Has built something that another person went on to use.

Nice To Haves

  • Background in a business unit such as finance, sales, or operations is welcome.

Responsibilities

  • Work within business units to discover undocumented context, processes, spreadsheets, manual data joins, and workarounds.
  • Drive a Go/No-Go decision with the business within five days of assignment.
  • Start builds using internal tooling that applies current standards and automated checks to the repository.
  • Own applications from validation and development through production use and graduation.
  • Direct coding agents using established patterns and judge whether their output is correct.
  • Use governed data and paved-path platforms as products owned by other teams, and raise gaps rather than working around them.
  • Make each application reproducible from a clean clone, with a pinned capability version, repository runbook, telemetry, defined SLO, and alerts routed to a rote.
  • Maintain no more than three ungraduated applications at any time.
  • Ensure applications reach their target users and have a defined exit through graduation, retirement, or transfer to the team that runs packaged systems.

Benefits

  • Opportunity to relocate to Auckland, New Zealand
  • Health benefits
  • Competitive remuneration
  • Fresh fruit, coffee, and a pals fridge
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service