Product Manager - B2B SaaS
Description
Designation: Product Manager
As a Product Manager, you will own multiple modules defining what to build, why it matters and what to prioritise. You will work closely with engineering, design, QA, business and customer-facing teams to turn institutional needs into simple, scalable product solutions, and make sure what we ship delivers measurable value to universities and colleges.
About the Role:
You are accountable for outcomes across your modules, not just delivery. You own their roadmap, make the scope and trade-off calls, frame ambiguous problems, and decide when a release is ready. You are the product voice for your modules with customers, you set workflow direction with design, and you coordinate with other PODs whenever your work affects theirs.
Roles & Responsibilities:
- Own the roadmap and priorities for assigned modules across new features, enhancements, redesigns and defects, using customer impact, adoption data, product health and prioritisation frameworks such as RICE.
- Evaluate customer requests and determine whether they should become core product capabilities, configuration options or institution-specific settings, while maintaining product consistency.
- Understand dependencies across modules and the broader platform, and collaborate with other Product Managers to align cross-functional changes.
- Make scope, priority and trade-off decisions for assigned modules, escalating decisions with wider POD impact to the Senior Product Manager.
- Lead discovery with institutional stakeholders, including administrators, department heads, faculty and students, to understand workflows, pain points and the underlying problem before defining solutions.
- Translate ambiguous problems into clear problem statements by identifying the root cause, impacted users and desired outcomes or success measures.
- Convert institutional policies, processes and business rules into clear, scalable and testable product behaviour.
- Own PRDs for assigned modules, covering problem statement, requirements, workflows, roles and permissions, configurations, defaults, validations, edge cases and impact on existing data.
- Set workflow direction in partnership with Design and ensure the overall experience addresses the underlying user and business needs.
- Review specifications and acceptance criteria created by Associate Product Managers and Product Associates before they move to Engineering.
- Partner with Engineering to define the right approach, scope and trade-offs, ensuring system and data fixes are addressed through appropriate engineering solutions.
- Set the quality bar for assigned modules by ensuring QA has clear business rules, configuration variations, acceptance criteria and regression risks before testing begins.
- Personally verify critical issues and ensure lower-severity bugs are appropriately prioritised, resolved and validated by the team.
- Own release readiness for assigned modules and manage controlled rollouts using feature flags and appropriate release practices.
- Track adoption, product health and customer feedback after launch, and use these insights to determine follow-up actions, improvements and priorities.
- Act as the product voice for assigned modules across customers, Customer Success and Business, ensuring product behaviour and decisions are clearly understood.
- Mentor and guide Associate Product Managers and Product Associates, review their work and progressively increase their ownership and accountability.
- Build towards independently leading a full POD and taking end-to-end ownership as a Senior Product Manager.
Requirements:
Must Haves:
- 2 to 3 years of product management experience, ideally in B2B or enterprise SaaS, owning multiple modules or major features from discovery through release and adoption.
- A track record of roadmap ownership: you have made prioritisation and trade-off decisions and can explain the reasoning behind them.
- Strong requirements writing for complex, rule-heavy products. You specify permissions, configuration, validation and edge cases instead of leaving those gaps for engineering.
- Structured problem-solving: you separate symptoms from root causes and trace the upstream and downstream effects of a change.
- Enough technical fluency to discuss APIs, data relationships and feature flags with engineers, and to investigate system behaviour alongside them.
- Confidence representing the product with customers and guiding junior team members.
Good to Have:
- Experience with ERP, student information systems, LMS or other workflow-heavy enterprise products, or with higher education.
- Experience building configurable products used by many customers with different rules.
- Comfort with data, such as SQL or product analytics tools like Mixpanel or Amplitude.
- Working knowledge of ClickUp or Jira, and Figma.
- Experience mentoring junior product managers or product associates.
- You use AI tools to speed up analysis and documentation, and you check their output against how the product actually behaves.
- A genuine interest in education.
- Opportunity to make a dent in higher education globally.
- An open culture that thrives on passion, ownership, and engineering excellence.
- A true sense of satisfaction where your work helps millions of students have a better campus experience.
- Opportunity to work on production-level, complex infrastructure.
- Mentorship from dedicated DevOps consultants and DevOps Leads from leading companies.
- Strong learning environment with exposure to modern cloud and DevOps practices.
- Your workplace and duration of work hours do not matter, as long as you are able to deliver and perform at your best potential and are available to the team whenever required.
Skills
Sign in to read and join the discussion.