Product Manager




London, UK

last month

Team, product and stakeholders

Saberr started with a product called Base that focuses on hiring. It asks people in a team to answer questions about their values and personality. This establishes the team’s “profile” which is then used to compare candidates against.

We have since pivoted to focus more on team coaching. For that we have an early stage product called CoachBot that is now our flagship offering. We want you to be the product owner for CoachBot. Its aim is to democratise team coaching, by bringing a lot of what human coaches do with fortunate teams to all teams through an affordable digital service. At the moment a lot of our offering is done out of product with the aim or productising it as we learn what does and doesn’t work. That’s it in a nutshell but we will explain more during the interview. It is currently a classic SaaS web app.

The team consists of 4 developers (2 frontend, 2 backend), 1 data scientist (who also does other development), 2 UX designers and a visual designer who we work with on a freelance part/time basis.

The product team’s external stakeholders are:

  • The customers and users in our flagship pilots - to succeed we need to expand them from pilots into the rest of their company.
  • The wider Saberr team - commercial, customer support and management.There is a lot of domain knowledge acquired in the company so whilst you are on your way to being the customer and user expert you will rely a lot on them. Managing different opinions and biases will be key here.
  • Investors and board. Some of them are coaches that we frequently work with, others have a lot of experience in other types of businesses. They are friendly and hands off but do like infrequent short updates on direction.

Your goals for the first 3-6 months

  • TL;DR Take ownership of the CoachBot product and do all those good product owner things. Below is how things will likely pan out in the beginning, but it may of course change with your input/new information.
  • Get to grips with our domain. Team coaching is our field and will probably be new to you. It is however not rocket science since most people have worked in teams and a lot of the principles are well known: agile, goals, psychological safety etc. Books, the current Saberr employees and coaches will be key to this.
  • Integrate into the product team. Understand how product work happens at the moment and what does and doesn’t work for our team. (We tried many things, from JIRA to Trello, from strict sprints to more Kanbanny sprints, from daily to weekly standups etc).
  • Get to grips with our current go-to-market strategy. Interacting with the business development team will be important here.
  • Develop and own the 3-6 month roadmap. By this we don’t mean features, rather prioritising hypotheses, experiments and areas to explore that should get us to validated revenue the soonest. Agreeing on what metrics we want to impact.
  • Begin to own the near term work. Discuss work/backlog, doing regular product reviews to inform people outside the product team and so on.
  • Understand where our product can add value. What is worth us competing with and defining where our product should start and end.

After the first 6 months (and on top of owning the CoachBot product)

  • Start to shape the longer term product(s) strategy. For example we know that one branch of product would be focusing on engaging interactive team sessions, another might be dashboards for central administrators, third might be integrations into chat systems like Slack, fourth a community of flesh and blood coaches, fifth how to do team based hiring with integrations into applicant tracking systems… we can keep going on.
  • Help with splitting/growing the team into more than one cross functional product unit (revenue dependent). There will be a lot of scope for growth here, whether into a head of product role, or to pick which product to focus on as more product owners are brought onboard. Helping with product manager hiring.
  • By this point you should know customers and users better than anyone else on the team so will depend less on internal opinions for product strategy and more on customer and user demands. You would have established a good direct relationship with important clients and users.


  • You have more than 3 years of real-life digital product management experience. Big plus: having developed a SaaS product from “not quite product market fit with users” through to commercial traction.
  • Our space is B2B2C (sorry, we are not fans of acronyms either), i.e. different people are users and buyers. What we mean by this is that our main users are teams and employees. However the buyers are typically a central HR function and they often have different needs and may think they know what their employees need but those employees often disagree. This means you either have similar experience to this or you have a strong understanding of how different this is to pure consumer products.
  • You have a keen eye for UX and are a passionate user advocate. (We have 2 UX designers on the team.) We do not want our products to be yet another boring HR tool that only pretends to be ‘engaging’ and ‘fun’.
  • You have an interest in modern technology and trends, especially machine learning and AI.
  • You are highly skilled at critical decision-making; ability to evaluate business issues and resolve problems with multiple constraints.
  • You are an advocate for focussed product development using frameworks such as jobs to be done, cost of delay, lean etc. Our product is early stage to doing a lot of experimentation will be important.
  • You must be able to thrive in a highly dynamic, flexible work environment and switch rapidly from strategy to execution and everything in between.
  • You have an excellent ability to communicate with stakeholders and know how to say no in different ways to different people. There are often side channel conversations to try and influence opinions. Building consensus will be important.
  • We do not expect you to be very technical as user and customer value is our key focus. However, being able to understand tech limitations and constraints is a plus (we currently have a web app that uses React, Python REST API, Postgres database; and having an early product our unique dataset is still small).
  • You are comfortable working in a cross functional team (described above). Some of our dev team are in Serbia so you should be ok with frequent travel (3-4 times a year, usually for a week).
  • You can communicate well in English and have the full right to work in the UK. Our current office is in Angel, London.


  • Competitive salary
  • Flexible working hours and locations
  • Generous paid holiday policy
  • Collaborative culture with a supportive team
  • Training and conferences budget with no strings attached
  • Office with safe bike storage and showers (if that's how you roll)
  • A new MacBook Pro if they are still en vogue