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 act on 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.

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 you don't need to be chased

Actively and efficiently 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.

Sprint planning, timeline management, stakeholder updates

Cross-functional coordination — dev, design, QA

Change request handling with scope and budget awareness

Pre-sales scoping and effort estimation support

Your PM experience is entirely internal — no external client delivery

You're waiting for requirements to be handed to you before you start thinking

You've 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