Technical Product Manager

Campus Connect Group; Miami, Northern (FL, KY); Hybrid; USD 90,000 - 130,000; Full time

Job summary

Campus Connect Group in Miami, FL seeks a results-driven Product Owner to lead a backlog for a B2B SaaS platform serving higher education institutions. You own triage, set priorities, and collaborate with client-facing teams and developers to keep work flowing.

You will define release cadence, maintain clear acceptance criteria, and push for measurable improvements in cycle time and client satisfaction.

Qualifications

• Five or more years owning a product backlog in B2B SaaS or enterprise software.
• Experience clearing a neglected or distressed backlog and describing tradeoffs.
• Hands-on configuration of a ticketing system with workflow states, SLAs, automation, and reporting.

Responsibilities

• Own the ranked backlog and decide sequencing based on severity, client revenue, and effort.
• Perform triage of incoming requests within one business day.
• Maintain work intake standards with concrete examples, expected behavior, steps to reproduce, and acceptance criteria.
• Lead release planning with the development lead and define deployment cadence.
• Make clear decisions on items we will not do and provide justified reasons.
• Generate weekly reports on items created vs. closed, aging, cycle time, and SLA breaches.

Skills

Product backlog ownership

Backlog triage

Release planning

Stakeholder communication

SQL querying

Reading stack traces

Legacy systems familiarity

Tools

Zoho

Jira

Zendesk

ServiceNow

Azure DevOps

Job description

About the role

Campus Connect Group operates a portfolio of software businesses serving the private post-secondary education sector. One of our operating companies runs a mature platform used daily by career colleges and training institutes across North America.

What you will own

• The ranked backlog. You decide sequencing based on severity, client revenue, and effort, and you can explain that order to an executive team or to a client.
• Triage. Every incoming request classified within one business day: account management work, developer work, needs more information, or declined.
• Work intake standards. No item reaches a developer without a concrete example, expected versus actual behavior, steps to reproduce, and acceptance criteria.
• Release planning with the development lead, including deployment cadence.
• Clear decisions on what we will not do. Declining a request with a stated reason is better for the client than an open item that never moves.
• Weekly reporting on items created versus closed, aging, cycle time, and SLA breaches, and acting on what it shows.

Technical skills

• This role works closely with developers on a legacy codebase, so we are looking for genuine technical comfort:
• You can read a stack trace and form a view on what is happening.
• You can write SQL well enough to query a database and check something yourself.
• You can distinguish a display issue from a data issue from a permissions issue.
• You can discuss a developer's estimate on its merits.
• You are comfortable with legacy technology: classic ASP.NET WebForms, Visual Basic, on-premise deployment, and a codebase with years of accumulated decisions.

Experience required

• Five or more years owning a product backlog in B2B SaaS or enterprise software.
• Experience clearing a neglected or distressed backlog, and the ability to describe how you did it and what tradeoffs you made.
• Hands-on configuration of a ticketing system, not just use of one: workflow states, SLAs, automation, and reporting. Zoho experience is helpful. Jira, Zendesk, ServiceNow, or Azure DevOps all transfer well.
• Direct experience working with client-facing teams and with clients, including conversations about scope and timing.

Nice to have

• Education technology, student information systems, or another sector selling to institutions with procurement cycles and compliance requirements.
• Experience through a version control or CI/CD modernization. We are migrating to GitHub and adopting AI-assisted development tooling.
• Enough comfort with data to build your own reports.

What success looks like

• At 3 months: you own triage, every open item has a severity, an owner, and a clear rank, and weekly metrics are published.
• At 6 months: requests for clarification are down significantly and delivery is predictable enough that clients stop chasing.
• At 12 months: we close more than we open on a sustained basis, and aged items are a fraction of what you inherited.

Interview process

Mostly practical and mostly live. Expect a timed triage exercise using real anonymized items, a technical conversation with a developer present, and a discussion of a backlog you have turned around. You are welcome to use AI tools on any written stage; we will discuss the substance in conversation. About two and a half hours across two sessions.