Product Manager — Service of Process

ABC Legal Services

10h•$110,000 - $120,000•Remote

About The Position

ABC Legal is a tech-forward, tech-enabled legal services business that uses technology to power its core operational service. This role involves owning one or more of the Service of Process product lines, including the mobile app for process servers, the customer-facing web portal, enterprise APIs, and the proprietary platform for job assignment, routing, task management, and evidence chain. The Product Manager will report directly to the CTO and will be responsible for discovery, requirements, cross-functional coordination, launch readiness, and outcome accountability, rather than backlog grooming and engineering coordination. The role requires working directly with process servers, the operations team, enterprise customers, and engineering. A key aspect of this role is to model upstream product work, focusing on discovery, market insight, and outcome ownership, as the current product team is stronger on delivery.

Requirements

4–7 years of product management experience, including at least one product spanning multiple technical surfaces (e.g. mobile + web, or a field/consumer app backed by a core platform).
Demonstrated track record of running your own discovery and turning it into shipped requirements — not just executing a spec you were handed.
Comfortable working directly with engineering across mobile, web, and backend teams simultaneously.
Hands-on backlog ownership in a scaled agile environment — writing and accepting work, running iteration planning, and participating in quarterly planning. SAFe specifically is a plus; scaled agile of some kind is expected.
Experience with B2B APIs, integrations, or platform products — versioning, developer-facing documentation, integration partners, enterprise technical requirements. This is where the role is most likely to center.
Comfortable with data. You can pull your own numbers and build your own view rather than waiting on an analyst. SQL is a plus, not a requirement.
Evidence that you've raised the product bar around you — introduced a discovery practice, moved a team from output to outcomes, or influenced peers and leaders who don't report to you. This role carries a change mandate, not just a delivery mandate.
Experience owning release quality without a dedicated QA team behind you — scoping what to test, running UAT with business stakeholders, and holding people who don't report to you to a testing commitment. If you've only shipped with a QA org catching things downstream of you, this part of the job will be a real adjustment.
Some go-to-market experience — comfortable partnering on launch messaging, sales enablement, or customer rollout, not just handing off a shipped feature and moving on.
Experience navigating a cross-functional sign-off or impact-review process before release, or a clear point of view on why one matters.
Bachelor's degree or equivalent practical experience.

Nice To Haves

Native mobile product experience (iOS/Android), especially apps used by a field workforce in real working conditions.
Experience building for internal operators — where the product's users are colleagues and their throughput is the business.
Experience shipping AI-assisted features, and a clear point of view on where automation should and shouldn't replace human judgment.
Legal services, legal tech, process serving, litigation support, courts, or another regulated / compliance-heavy industry background. Genuinely a plus, genuinely not required — we'll teach you this domain.

Responsibilities

Own your product area end to end.
Own outcomes, not just output, for your area of the Service of Process product line like the APIs and integrations our largest clients build against, and the proprietary platform behind job assignment, routing, task management, and evidence chain, as well as the customer web portal and our field mobile app.
Set and defend the priority order. Decide what gets built, what waits, and what we stop doing.
Maintain a rolling roadmap that survives contact with reality: sequenced, tied to business outcomes, revised openly when the evidence changes.
Run your own discovery.
Get into the field. Ride along with process servers, sit with the operations teams who work jobs all day, and watch customers use the product.
Run structured discovery with customers — interviews, win/loss input, support themes, usage data — and turn it into a written point of view about what to build and why.
Serve two distinct user populations: external customers who want speed, price, and certainty, and internal operators whose throughput determines whether we can deliver it.
Turn insight into shipped software.
Write the requirements: crisp problem statements, success criteria, edge cases, and the operational and legal constraints that apply by jurisdiction.
Own the backlog for your team(s) within our SAFe cadence: features and stories, acceptance, iteration planning, and PI planning.
Work directly and daily with mobile, web, and backend engineering. Break work into releasable increments, unblock decisions fast, and make tradeoff calls.
Own launch readiness end to end: rollout plan, internal enablement, support readiness, migration and backfill, and a defined rollback path.
Own release quality for your area. We have no separate QA team: you decide what needs testing and to what depth, shape the test approach, and coordinate the business owners and operations partners who validate the work in their own domain.
Make the go/no-go call, and confirm after release that what shipped does what the requirements said and that the customer and operational outcomes you predicted show up in production.
Partner with Operations as a first-class customer.
Treat internal operations as a product surface with real users and real cost. Tooling that saves an ops team minutes per job compounds across hundreds of thousands of jobs.
Find where automation, better routing, or better decision support removes manual work — and quantify what that work is worth before committing to it.
Ship AI into the product responsibly.
Define the accuracy bar, the human-review path, and the failure behavior for every AI-assisted feature before it ships. Default to advisory; earn the right to automate by clearing a threshold you set in advance.
Hold AI features to the same outcome accountability as everything else: measured agreement with the qualified human who would otherwise make the call.
Measure, and be accountable to the measurement.
Define the success metric for every initiative before it ships, and name the dashboard where it will be watched.
Pull your own numbers. You'll have direct access to our analytics environment and reporting to decide what worked and what didn’t and act on it.
Manage risk and compliance.
Understand the regulatory and evidentiary texture of this business: jurisdiction- specific service and filing requirements, chain-of-evidence integrity, proof of service standards, and the handling of sensitive case and party data.
Identify compliance and operational risk early and design around it — a product decision that creates a defect in a proof of service is a legal problem, not a bug.
Ensure changes clear the appropriate cross-functional review before release.