Product Manager (Software Services): remote role at RaftLabs
Product Manager (Software Services)
Remote · Full Time · Position closed
Application policy
Apply only through the “Apply now” button on each job posting.
Applications via email, contact form, direct messages, or reaching out to team members will result in immediate rejection. We review applications submitted through our careers portal only.
This position is currently closed. We are not accepting applications at this time. Check our open positions for current opportunities.
Remote position.
We build custom software for founders and product teams across the UK, EU, and North America. You will take ambiguous client briefs, define what should actually get built, and make sure delivery doesn't drift from that definition.
This role is 80% product thinking, 20% delivery discipline. If your default mode is tracking tasks rather than shaping outcomes, this isn't the role for you.
What you own
Discovery: run structured sessions with non-technical clients, challenge assumptions, and define what's worth building and what isn't.
Specification: produce BRDs, user stories, and acceptance criteria that engineering can build from without a follow-up call. Your spec is your reputation.
Scope: set it, defend it, and catch creep before it becomes a conversation about budget.
Prioritization: make hard calls when time, money, or tech forces a trade-off. You have a point of view and you can back it.
Translation: bridge client intent and engineering reality without losing either side.
Delivery ownership: timelines, risks, and blockers are yours to surface early, not explain later.
Requirements
3-5 years in a product or BA role inside a software services or consulting company - not in-house product, not pure coordination.
Has produced real discovery outputs: BRDs, user stories, feature specs - not Jira hygiene.
Client-facing by default: comfortable running discovery calls, pushing back on scope, and writing directly to clients without a filter.
Written English that's client-grade: every doc, update, and message you send represents RaftLabs.
Async-first discipline: you move work forward without meetings and don't need to be chased.
Actively uses Claude, ChatGPT, or equivalent AI tools as part of daily workflow - for drafting specs, structuring discovery notes, stress-testing requirements, or accelerating research. Not theoretical. Show us how.
Delivery layer (secondary but real)
Sprint planning, timeline management, client updates.
Cross-functional coordination across dev, design, and QA.
Change request handling with scope and budget awareness.
Pre-sales scoping and effort estimation support.
Hard filters - don't apply if
Your PM experience is entirely internal with no external client delivery.
You're waiting for requirements to be handed to you before you start thinking.
You have never written a spec or BRD from scratch.
AI tools are something you plan to use more, rather than something already in your stack.
You need daily check-ins to stay on track.
How we work
Fully remote. Async-first: your specs, client updates, and decision logs move through written documentation, not meetings. We measure whether delivery stays true to the scope you defined, not hours online.
As a PM here, you are client-facing by default. Every document you send, every update you write, every scope decision you make represents RaftLabs directly. Clear writing is not a soft skill - it is the job.
Annual offsite: the full team meets in person once a year.
What success looks like
In the first 90 days: you have run discovery on at least two active client projects independently, produced BRDs and user stories that engineering built from without revisiting you, and caught at least one scope issue before it became a budget conversation.
Over time: clients trust your word. Delivery does not drift from spec. Engineers do not need a second meeting to understand what they are building.
Benefits
5-day work week: healthy work-life balance, not just a talking point.
Fully remote: work from wherever suits you.
Your setup, your call: no office, no commute.
Flexible hours: we care about what ships, not when you log in.
Annual offsites: the whole team meets in person once a year.
Questions about this role
- RaftLabs PMs work in a software services context: you take ambiguous client briefs, define what should actually get built, and ensure delivery stays true to that definition. Unlike in-house roles, every project has a paying external client and a measurable outcome to hit. The spec you write is what gets built, so it has to be right.
- RaftLabs PMs own discovery (client sessions, requirements), specification (BRDs, user stories, acceptance criteria), scope management, prioritization, and delivery oversight. The role is 80% product thinking and 20% delivery discipline.
- Yes. The PM position is fully remote. RaftLabs is async-first, meaning work moves forward through documentation and clear specs, not constant meetings. You move things without needing to be chased.
- Yes. RaftLabs expects PMs to actively use Claude, ChatGPT, or equivalent AI tools in their daily workflow for drafting specs, structuring discovery notes, stress-testing requirements, and accelerating research. This is not theoretical - you should be able to show how you already use these tools.
- To apply, use only the Apply Now button on the job posting. Applications via email, contact form, direct messages, or reaching out to team members will result in immediate rejection. We review applications submitted through our careers portal only.
This role is filled, but we keep hiring.
Check our open positions or send us what you're great at. We hire for fit when the right person shows up.