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 questions with you in year one and gives you more room as you earn it.

What You Bring

Product work you have actually done, in one of two shapes. Either 2 or more years as an Associate Product Manager, Product Owner or Product Manager at a B2B software company, owning a backlog and running discovery with a senior PM above you.

Or 3 or more years in solutions engineering, implementation, customer success or support leadership at a software company serving schools, universities, facilities teams or public agencies, where you wrote requirements that shipped, ran customer conversations, and made at least one call about what got built next.

A prioritization decision you made, or helped make, with incomplete evidence: how you gathered what you could, who disagreed, what was decided, and what happened. A story about turning a sales or customer success ask into something a developer could build, and what you learned about the difference between the ask and the problem.

Enough technical depth to hold your own with engineers on APIs, integrations, data models and multi-tenant SaaS; experience inside Jira, Azure DevOps or equivalents. Evidence that you care what happened after something shipped, including at least one thing that did not land. Daily, practical use of AI tools in product work and a grounded view of where they help and where they do not.

Clear writing. Clear speaking. The ability to present to an executive and to a two-person development team in the same week.

The appetite to be the product manager for two products, and the honesty to want help with the hardest calls while you grow into them. If you have been the only product manager somewhere already and built a feedback loop that outlived you, we want to hear from you too; tell us about it in your note.

Preferred Skills Experience in higher education operations (media services, libraries, campus IT, makerspaces) or public-sector facilities and maintenance (K-12, municipalities, airports), or with CMMS, asset management or scheduling software. Time in a buy-and-hold software portfolio (Volaris, Constellation or similar) or another small, durable software company. Exposure to pricing and packaging decisions.

HubSpot or other CRM literacy for mining deal and churn data; basic SQL or comfort with exports. Familiarity with accessibility requirements (ADA Title II, WCAG, VPATs) as they apply to public-institution procurement. Experience running or sitting in on win/loss interviews.

Why This Role The title and the seat, together. If you have been doing product work as an associate, a product owner or a solutions lead, this is the product manager seat for two products with paying customers, and the backlogs are yours from day one. A team that asked for you.

The developers at both companies want a product partner. You will not be selling the idea of product management; you will be doing it. Two kinds of problem.

Inherit and improve a working function at one company; build one from nothing at the other. Few product roles offer both at once. Real coaching.

A Director who has done the work frames the strategic questions with you weekly in year one, and a peer product manager is a standing call away. Few first PM seats come with that. A written path forward.

We will tell you in the first interview what the next level looks like and how you get there. Durability. We hire for the third year of a product line, not the first quarter, and our products do not get shut down.

Modern tooling. Enterprise AI tools, AI-native development teams, and a manager who wants to see how you use them.