Product Owner/ Business Analyst

College HUNKS Hauling Junk & Moving runs its franchise network on HunkWare, our in-house platform for booking, pricing, dispatch, crews, customer messaging, and franchise reporting. We ship to production several times a week with an offshore engineering team.

We are hiring a Product Owner to own each feature from first request to real-world adoption. You will turn requests from franchise and corporate teams into clear, testable stories. You will work with our UI/UX design team on the experience, set priorities, and do the final acceptance check before anything goes live. After launch, you will turn on the feature flags, announce what changed, and make sure people actually use it.
 

·         Be the single front door for product requests from all stakeholders.

·         Triage each request: clarify the problem, find duplicates, and decide whether it is a bug, an enhancement, or a new feature.

·         Keep requesters informed on status and expected timing.

·         Interview stakeholders and write epics and stories with clear acceptance criteria, edge cases, and permission rules.

·         Write product requirements documents (PRDs) for larger initiatives: the problem, goals, scope, user flows, success metrics, and open questions.

·         Document current behavior before a change.

·         Answer developer questions quickly so work is not blocked across time zones.

·         Review designs with UI/UX for business logic, copy, and edge cases before development starts.

·         Bring user feedback and usage data into design decisions.

·         Keep a ranked backlog against company goals, franchise impact, and engineering capacity.

·         Plan quarterly themes and release scope.

·         Break large projects into phases, each with its own scope, release, and success check, so value ships early and later phases can adjust.

·         Run the last functional and regression pass on our training environment after engineering QA.

·         Check calculations against expected results.

·         Make the go/no-go call for each release and log any defects you find.

·         Plan the rollout of each feature behind a flag: who gets it first, the default setting, and the rollback plan.

·         Turn flags on and off in our feature-flag tool for pilot locations, then everyone.

·         Create tickets to remove flags once a feature is fully live.

Feature announcement

·         Review and edit the in-app release notes before they publish; decide which items to highlight.

·         Write short announcements, how-to guides, and FAQs for users, and give support teams a heads-up at least a day before changes that affect them.

·         Define a success metric for each launch and check it after launch.

·         Collect feedback from pilot users and turn it into follow-up work.

·         Retire legacy screens once adoption targets are met.