Junior Product Owner

Euna Solutions•Oakville, ON

4d•CA$60,000 - CA$80,000•Hybrid

About The Position

Public-sector procurement is a highly regulated domain, with rules touching open-records laws, vendor-fairness, accessibility standards (WCAG), audit-trail obligations, and federal data integrations. The Euna Procurement platform is where these rules intersect with financial transactions. Product Owners on this team are responsible for translating this complexity into shippable work. The role involves leveraging AI skills to produce tightly scoped, technically clear tickets for downstream AI agents and human teams, ensuring minimal rework. The ideal candidate will be able to produce work that improves team velocity.

Requirements

A technical foundation: a degree in computer science, engineering, or a closely related field, OR demonstrable equivalent experience (co-op as a developer or PO, bootcamp plus shipped work, prior SDE-to-PO transition).
Hands-on use of AI tooling for product work (story drafting, requirement analysis, summarization, ticket critique), with an informed opinion on AI's strengths and weaknesses.
Proven ability to break complex features into small, clear, testable stories with acceptance criteria (samples required).
Excellent written communication skills for tickets and async coordination.
Experience with Jira, Confluence, agile delivery.
Experience with at least one of: wireframing, technical writing, business analysis.

Nice To Haves

Prior exposure to a regulated or compliance-heavy domain (govtech, public sector, healthcare, financial services, legal tech, or similar).
Working comfort with React and SQL, with the ability to read code well enough to discuss refactors with a Tech Lead.
Experience contributing to or owning an AI-assisted development workflow (defining ticket structure for AI, grading AI output, iterating on prompts).

Responsibilities

Translate prioritized roadmap initiatives into well-scoped, technically viable user stories.
Partner daily with a Tech Lead, developers, SDETs, and UX.
Use AI tooling deliberately to accelerate ticket authoring and refinement.
Break features into stories small enough to ship inside a 2-week sprint, with clear acceptance criteria for developers or AI agents.
Author component-focused stories for AI-driven work and user-flow stories for human-driven work, understanding when each pattern applies.
Use AI tooling (Claude, internal Product Agent, or equivalent) to draft, critique, and tighten stories, and explain discrepancies in AI-generated content.
Embed compliance context (accessibility, audit-log, PII, transparency, API integration) directly into stories.
Maintain the team's backlog across the SAFe Planning, Review, and Demo cadence, ensuring stories are linked to Epics and Epics to PI Objectives.
Manage dependencies with sibling teams and surface risks early to the RTE and PM.
Present the team's work at System Demos, explaining what shipped and its significance.
Act as the first point of contact for the Tech Lead and developers regarding story ambiguity.
Accept or reject work based on acceptance criteria, providing specific reasons for rejection.
Track and own the velocity story, identifying which tickets accelerated the team and which created drag, and adjusting authoring practices accordingly.
Represent the Buyer (public-agency procurement officer) and the Vendor (supplier) in all product development.
Treat compliance constraints as first-class requirements.