Salford · St Helens
£44,000 · Full-time
We are a pharmacy group that builds its own software. Not one tool, a full ecosystem covering what a pharmacy actually needs to run: stock management, ordering, payroll, reporting and everything in between. It is built in-house and used in real pharmacies every day.
We need a pharmacist on the product team. Not to dispense — to tell us what the software should do, and to tell us when it is wrong.
You will be the person who knows what actually happens behind the counter and can turn that into a product. When an engineer asks “what does a pharmacy actually do when the shelf does not match the system?”, you are the answer.
What you will do
- Sit between our pharmacies and our engineers, turning real workflow problems into clear requirements.
- Work across the whole platform, not one corner of it — dispensary through to back office.
- Test new features against how a pharmacy actually runs — and block the ones that do not survive contact with a Saturday afternoon.
- Be the authority on the clinical and regulatory detail the software has to get right: the things that are obvious to a pharmacist and invisible to an engineer.
- Triage what comes in from branches — work out whether the system is wrong, the process is wrong, or the person is.
- Help pharmacy teams get up and running on it, and be the voice they trust on a call.
- Dig into the data yourself: pull the numbers, spot the pattern, bring evidence instead of anecdote.
What we are looking for
- MPharm. Recently qualified pharmacist are welcome to apply
- Real pharmacy floor experience. Placements and foundation training count.
- Genuinely technical. Not a coder — but the person in your pharmacy who fixed the PMR when it broke, who built the rota spreadsheet everyone still uses, who automated something because doing it by hand annoyed you.
- Comfortable with data. Pivot tables, filters, a bit of SQL or at least an appetite to learn it fast.
- Able to write clearly. Most of this job is explaining something precisely to someone who is not a pharmacist.
- Opinionated about bad software. You have used systems that made your job harder and you can say exactly why.
Nice to have
- Strong opinions about the PMR and stock systems you have worked with.
- You have written any code at all, even badly.
- You have worked in a pharmacy that ran badly, and you know why.
What you get
- Direct influence over software real pharmacies use — you will see your decisions live in a branch in weeks, not quarters.
- Breadth. You will touch the whole pharmacy, not one narrow feature, and understand the business end to end.
- Support for GPhC revalidation.
- Small team, direct founder access, no product-committee theatre.
To apply
Send your CV plus : a process in a pharmacy you have worked in that was slower or more error-prone than it should have been — what was actually going wrong, and how you would fix it.
