Product Manager

Product Manager, WebCheckout and QWare

About Us

WebCheckout and QWare are two software companies in the Volaris Group family, part of Constellation Software. WebCheckout runs equipment checkout, asset lending and resource scheduling for university media centers, libraries, film schools, makerspaces and labs. QWare is a maintenance management system for the people who keep school districts, municipal buildings and other public facilities running: work orders, assets, preventive maintenance, inventory, event scheduling, and a mobile app for the field. Both are led from AssetWorks’ product and development organization. We are a buy-and-hold software group, which means we build for the long term and invest in products our customers will still be running a decade from now.

About the Role

Two products. Two small development teams that have asked for a product manager. No product manager yet. That is the opening.

At WebCheckout you inherit a real product function: an AI-assisted discovery and feedback program with structured customer sessions before every release, a decision tracker for every ask, and competitive research. What it lacks is a person who owns it, consistent input from sales and customer success, and any measurement of what happened after a feature shipped. At QWare you build the function from scratch: the lead developer has been writing most of the backlog himself and has said plainly he would rather someone with product judgment decide what comes next.

You will be the one product manager across both companies, reporting to the Director of Product and Development. You will own both backlogs, write every requirement, run every customer conversation and write the memos that end debates. In your first year you will not do the hardest parts alone: your manager will sit down with you every week to frame the big strategic questions, the WebCheckout development lead will run one full feedback cycle alongside you before handing it over, and you will have a peer product manager to think with. We are telling you this up front because it is the design of the seat, not a lack of trust. If you have been doing product work and want to be the one who decides, with someone experienced in the room while you learn to, this is that job.

What You Will Do

• Own product direction, discovery, requirements and outcome measurement for WebCheckout and QWare.
• Take over WebCheckout’s customer feedback program and make it whole: add the sales and customer success inputs it is missing, and close the loop on what happened after each release.
• Stand up product discovery and feedback intake at QWare where none exists today: find the customers with the richest signal, talk to them, and turn what you hear into a roadmap.
• Make the calls the teams cannot make on their own, with evidence, in writing, framed with your manager in year one. QWare’s backlog holds a good example: invest in event and facility-use scheduling, or in building automation integration? Someone has to decide.
• Write PRDs, stories and acceptance criteria that two-person development teams can build from without a second meeting; groom both backlogs; own the trade-offs.
• Measure outcomes. Every major feature gets a named success metric before it is built and a check-in 90 days after it ships. One of your first jobs is to find out what became of a module that shipped a year ago on a customer success recommendation.
• Build the enablement kit for sales, support and implementation at each company, and start a regular win/loss review with the account executives.
• Use AI tooling as a daily part of the work, including owning WebCheckout’s AI “product manager” agent profile: what it does well, where a human decision is required, how its output is reviewed.

How We Work

• Small teams, direct access. You will talk to the developers who build the product and the people who sell and support it, every week, at both companies.
• Two rhythms. WebCheckout ships two named releases a year (June and December) and tracks work in Jira and Confluence. QWare runs two-week sprints in Azure DevOps. You will be comfortable in both.
• AI-native by default. Both teams use agentic tooling in development, and you will have enterprise AI tools for discovery synthesis, drafting and analysis. We care how you use them and how you check them.
• Written decisions. A one-page memo that ends a debate is worth more here than a deck.
• Remote, with a manager who frames the hard…