Technical Product Owner I (Execution-Focused | CoPilot IV & Hub)

eAssist•American Fork, UT

4d•$100,000 - $100,000•Remote

About The Position

The Technical Product Owner I is an execution-focused role designed for an early-career professional (1–3 years experience) who supports product delivery through strong requirements definition, documentation, backlog readiness, and day-to-day collaboration with engineering and stakeholders. This role combines core Business Analyst responsibilities with entry-level Product Owner execution. The Technical Product Owner I does not own product strategy or architectural decisions, but is accountable for ensuring requirements are clear, documented, testable, and ready for development.

Requirements

1–3 years of experience in a Business Analyst, Product Analyst, Product Owner, or similar role
Hands-on experience writing user stories, acceptance criteria, and process documentation
Strong analytical and critical thinking skills
Excellent written and verbal communication
High attention to detail and organization
Ability to manage multiple workstreams with daily execution expectations
Familiarity with Jira and backlog management tools
Experience with documentation and diagramming tools (Google Docs, Lucidchart, Figma, or similar)
Basic understanding of the software development lifecycle (SDLC)
Ability to understand and document technical concepts provided by engineering (APIs, data flows, integrations)

Nice To Haves

Prior experience working in an Agile/Scrum environment is a plus

Responsibilities

Daily Product & Engineering Support (CoPilot IV)
Participate in standup meetings and engineering agile syncs.
Review and maintain Jira daily to ensure stories are accurate, prioritized, and actionable.
Document user journeys, workflows, and detailed requirements.
Write high-quality user stories and acceptance criteria.
Translate product requirements into clear, executable technical stories.
Answer day-to-day questions from developers and stakeholders.
Support users by reviewing GChat inquiries, bug reports, and UAT feedback.
Surface technical risks, dependencies, and trade-offs to Product Management and Engineering leads.
Support alignment of engineering output to roadmap commitments.
Requirements Gathering & Analysis (Hub)
Conduct discovery sessions with stakeholders to gather business needs, user pain points, and process gaps.
Translate business goals into functional and non-functional requirements.
Perform process mapping and gap analysis to document current-state vs future-state workflows.
Validate assumptions, scope, and dependencies with guidance from Product or Engineering leadership.
Documentation & Product Artifacts
Create and maintain clear documentation including:
User stories and acceptance criteria
Process flows and workflows
User journeys and use cases
Wireframes and interaction flows (in collaboration with UX or product leadership)
Testing and validation documentation
Ensure documentation remains current as requirements evolve.
Create training documentation and user guides to support feature adoption and operational readiness.
Product Backlog Support
Support refinement and prioritization of the technical product backlog in partnership with Product Owners or Product Managers.
Ensure stories meet the Definition of Ready before entering development.
Support backlog grooming and sprint planning by providing clarification and documentation.
Assist with validating completed work against acceptance criteria.
Testing & Validation
Define test scenarios and acceptance criteria aligned to documented requirements.
Support and coordinate user acceptance testing (UAT).
Validate that delivered functionality aligns with documented requirements and business objectives.
Capture feedback and defects and ensure they are properly documented and prioritized.
Stakeholder Communication
In collaboration with Product Management, act as a liaison between business stakeholders, users, and the technical team.
Document decisions, feedback, and requirement changes.
Help manage scope by clarifying requirements and escalating misalignment when needed.
Communicate progress, risks, and questions to Product or Engineering leadership.