Product Owner/ Business Analyst

College Hunks Hauling Junk and Moving - Corp Office

1d•Remote

About The Position

College HUNKS Hauling Junk & Moving runs its franchise network on HunkWare, an in-house platform for booking, pricing, dispatch, crews, customer messaging, and franchise reporting. The company ships to production several times a week with an offshore engineering team. The Product Owner owns each feature from the initial request through real-world adoption. The role turns requests from franchise and corporate teams into clear, testable stories; works with the UI/UX design team on user experience; sets priorities; and performs final acceptance checks before releases. After launch, the Product Owner activates feature flags, communicates changes, and monitors adoption.

Requirements

At least 3 years of experience as a Product Owner, Business Analyst, or Product Manager on a B2B or internal SaaS product.
Track record of writing user stories and acceptance criteria that engineers can build from without rework.
Hands-on testing experience, including user acceptance testing or regression testing and writing clear bug reports.
Comfort with number-heavy business logic such as pricing, quoting, discounts, taxes, or invoicing.
Daily use of Jira or a similar tracker for backlog and sprint management.
Experience working with a remote or offshore engineering team across time zones.
Clear written English for specifications, comments, and announcements.
Comfort saying no to stakeholders and explaining trade-offs.

Nice To Haves

Experience rolling out features with flags such as Split.io, LaunchDarkly, or similar, including staged rollouts and rollbacks.
Experience with field-service, home-services, logistics, or franchise software.
Product analytics experience with tools such as Metabase, GA4, or RudderStack to measure adoption.
Ability to read SQL or write simple queries to check data during testing.
Experience reviewing Figma designs and writing in-product copy.
Experience writing release notes, training materials, or change-management communications.

Responsibilities

Serve as the single intake point for product requests from stakeholders; clarify problems, identify duplicates, classify requests as bugs, enhancements, or new features, and keep requesters informed about status and timing.
Interview stakeholders and write epics and stories with clear acceptance criteria, edge cases, and permission rules.
Create product requirements documents for larger initiatives, covering the problem, goals, scope, user flows, success metrics, and open questions.
Document current behavior before changes and answer developer questions promptly to avoid blocking work across time zones.
Review designs with the UI/UX team for business logic, copy, and edge cases before development, incorporating user feedback and usage data into design decisions.
Maintain a ranked backlog based on company goals, franchise impact, and engineering capacity; plan quarterly themes and release scope; and divide large projects into phases with defined scope, releases, and success checks.
Perform the final functional and regression pass in the training environment after engineering QA, verify calculations, make go/no-go release decisions, and log defects.
Plan feature-flag rollouts, including initial audiences, default settings, and rollback plans; activate or deactivate flags for pilot locations and then broader users; and create tickets to remove flags after full release.
Review and edit in-app release notes, choose items to highlight, prepare announcements, how-to guides, and FAQs, and notify support teams at least a day before changes that affect them.
Define a success metric for each launch, check it after release, collect pilot-user feedback and turn it into follow-up work, and retire legacy screens once adoption targets are met.