Technical Product Owner, Service of Process (SAFe)

Technical Product Owner, Service of Process (SAFe)

About ABC Legal Services

ABC Legal Services is proud to be the national leader in service of process. We are a team of 1000 and growing with offices in Los Angeles, Oklahoma City, Phoenix, Brooklyn, Chicago, Washington DC, and more. Seattle is our home and headquarters.

We've been successful in this unique business for over 30 years, and we continue to advance our technology and business processes to remain years ahead of what our competition is able to offer. Our focus is to expand our technology lead, acquire and integrate less efficient competitors, and tap into new segments through an integrated inbound marketing and sales approach.

Job overview

ABC Legal is hiring a Technical Product Owner to own the backlog and the delivery sequence for part of our Service of Process platform, and to keep work moving cleanly across a large engineering organization.

ABC Legal is a tech-forward, tech-enabled legal services business: we use technology to power a core operational service, not the other way around. Your area is one or more of our Service of Process products: the mobile app process servers use in the field, the customer-facing web portal, the enterprise APIs our largest clients integrate with, and the proprietary platform that powers job assignment, routing, task management, and evidence chain.

This is a SAFe Product Owner role with a technical program management core. Business-facing Product Managers own customer and market discovery, positioning and launch. You take their priorities and turn them into requirements, sequenced backlogs and releases that engineering can build and operations can absorb. You own the backlog, the dependencies between teams, release quality and the post-release check that what shipped works.

You will report directly to our CTO and work closely with Engineering, Operations, and the business-facing Product Managers. We will teach you the domain. We are not going to teach you the craft: we expect you already know how to write precise requirements, run a scaled agile cadence and hold a date across teams you do not manage.

Why this job is interesting

Most product roles are software all the way down. This one is not. Every job we run is a physical-world logistics problem, getting a real person to a real address at a time they will actually be there, wrapped in a legal evidentiary standard that decides whether the work counts at all.

The platform has to serve a distributed field workforce, demanding enterprise legal customers, an internal operations organization of hundreds, and a court system that changes its rules by county. A change in one system can produce a defective proof of service weeks later, in a different system, in front of a judge. Sequencing and dependencies are the job, not an afterthought.

We are also further into production AI than almost anyone in this industry: dozens of AI agents run live today across service validation, document handling, evidence review, and operational decision support. You will help decide where that belongs in the product, and where it does not.

Key responsibilities

Own the backlog

• Own the team backlog for your area of the Service of Process platform. Depending on your background, that is likely to center on the enterprise side: the APIs and integrations our largest clients build against, and the platform behind job assignment, routing, task management, and evidence chain, with surface area across the customer web portal and field mobile app.

• Take priorities from the business-facing Product Managers and turn them into crisp problem statements, requirements, success criteria and edge cases. Court rules vary by jurisdiction, and requirements must reflect that instead of discovering it in QA.

• Break features into stories that fit an iteration. Accept or reject work against acceptance criteria and the Definition of Done.

• Set and defend the priority order within your area: what gets built, what waits, and what we stop doing. Explain the reasoning to an engineer, an operations leader and the executive team in terms each cares about.

Run the program across teams

• Plan and run your area through the SAFe cadence: iteration planning, quarterly PI Planning, system demos, and Inspect & Adapt.

• Sequence work across the teams and systems it touches. A single change can touch the field mobile app, a document template and a rules store. Order the pieces so they land correctly, and hold the dependencies.

• Name prerequisites before work starts, and catch collisions between initiatives while a fix is still a conversation and not a rebuild.

• Maintain a rolling plan that survives contact with reality: sequenced, tied to business outcomes, and revised openly when the evidence changes.

• Give the executive team a clear read on status, risk and trade-offs, including the bad news, early.

Make the system picture explicit

• Work with engineering to keep current the picture of which systems a change touches, what sits upstream and downstream, and where the integration points are. Engineering supplies the truth; you make sure it is written down and kept up to date.

• Produce and maintain system and sequence diagrams, dependency maps, interface inventories and data flows jointly with engineers, because sequencing decisions get made from them.

• Understand B2B API and integration constraints: versioning, backward compatibility, developer-facing documentation and enterprise technical requirements.

Own release quality and landing

• Own release quality for your area. We have no separate QA team, so 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.

• Own release readiness end to end: rollout plan, migration and backfill, support and operations readiness, and a defined rollback path before anything ships.

• Make the go/no-go call, then confirm after release that what shipped does what the requirements said and that the outcomes you predicted show up in production.

• Partner with operations leadership on the process change that has to land alongside the software. A feature that ships without the workflow change around it has not shipped.

Ship AI into the product responsibly

• Own where AI belongs in your product area and where it does not.

• 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 outcome accountability, measured as agreement with the qualified human who would otherwise make the call.

Measure and manage risk

• Define the success metric for every initiative before it ships and name the dashboard where it will be watched. Pull your own numbers from our analytics environment.

• Report honestly on what worked and what did not, then act: kill, iterate or double down.

• Understand the regulatory and evidentiary texture of this business: jurisdiction-specific service and filing requirements, chain-of-evidence integrity, proof of service standards, and sensitive case and party data.

• Identify compliance and operational risk early. A product decision that creates a defect in a proof of service is a legal problem, not a bug. Make sure changes clear cross-functional review before release.

How we work

• Framework: We run SAFe (Scaled Agile Framework). This is a Product Owner role: features and stories, acceptance, iteration planning, and quarterly PI Planning, which is a synchronous, multi-day commitment.

• No dedicated QA function, and you should know that going in. Product owns release quality here. That does not mean you personally click through every test case. It means you decide what needs testing and how much, design the approach, pull in the business owners who own the affected process to validate it, and hold the go/no-go call.

• Where the business-facing work sits: Business-facing Product Managers own customer and market discovery, positioning, pricing and launch. You are their technical counterpart, and you will not be asked to run that work.

• Scope is flexible. We recently reorganized how product responsibility is divided across mobile, enterprise, and platform. We would rather hire the right person and shape the area around their strengths than force a great candidate into a fixed box. We will be direct about the realistic options during the process.

• Tools: Jira and Confluence for planning and documentation, Bitbucket for source, Metabase for analytics, Intercom for customer conversations, Miro for collaboration, Slack for everything else.

• AI: We are unusually far along here. Claude is in daily use across the company, including product, engineering, operations and support, and we run dozens of AI agents in production. We expect you to use these tools well and to have a point of view on where they belong in the product.

• Team: You will work with 30+ engineers across 7+ teams spanning mobile, web, and backend, alongside design, Scrum Masters, and a product peer.

Qualifications

What we are looking for

• 3-5 years of product ownership, product management or technical program management experience, including at least one product spanning multiple technical surfaces (for example mobile plus web, or a field or consumer app backed by a core platform).

• Hands-on backlog ownership in a scaled agile environment: writing and accepting work, running iteration planning, participating in quarterly planning, and managing dependencies across teams. SAFe specifically is a plus; scaled agile of some kind is expected. SAFe Product Owner/Product Manager (POPM) certification, or willingness to earn it within your first 90 days.

• Comfortable working directly with engineering across mobile, web and backend teams at the same time.

• Technical fluency: you can read an architecture diagram, follow a data flow across services, and ask useful questions about an integration, a migration or a rollback.

• Experience producing engineering artifacts alongside engineers, such as system and sequence diagrams, dependency maps and interface inventories, and keeping them current.

• Experience with B2B APIs, integrations or platform products: versioning, developer-facing documentation, integration partners and enterprise technical requirements. This is where the role is most likely to center.

• A track record of holding a date you did not set, across people you did not manage.

• Experience owning release quality without a dedicated QA team behind you: scoping what to test, running UAT with business stakeholders, and holding people who do not report to you to a testing commitment. If you have only shipped with a QA org catching things downstream, this part of the job will be a real adjustment.

• 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.

• 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 have

• 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 should not replace human judgment.

• Legal services, legal tech, process serving, litigation support, courts, or another regulated or compliance-heavy industry background. Genuinely a plus, genuinely not required: we will teach you this domain.

What success looks like

In your first 90 days

• Your backlog is refined, with about two iterations of ready stories ahead of the teams.

• You have mapped the systems your area touches, with a current dependency map and interface inventory agreed with engineering.

• You have run at least one PI Planning cycle for your area with dependencies named and owned.

• You have shipped at least one meaningful improvement with a rollout plan and a rollback path.

In your first year

• Your plan is sequenced, understood and trusted across engineering, operations and leadership.

• Two or three initiatives you owned have shipped and moved a metric you named in advance.

• Every release in your area has a named test approach, a go/no-go decision on record, and a post-release check against the requirements.

• Collisions between initiatives are caught in the plan, not in production.

Compensation and location

• Salary range: $90,000-$110,000 annually. Actual compensation depends on experience, skills, and location.

• Location: Remote, anywhere in the United States. Our product and engineering teams work out of Seattle and Longmont, Colorado. Being near either is a nice-to-have, not a requirement. The CTO you would report to is based in Longmont.

• Overlap hours: Expect meaningful daily overlap with US Pacific through Central. Quarterly PI Planning is a synchronous, multi-day commitment.

• Travel: Up to 10% for periodic in-person time with the product and engineering group and time at our operations centers.

Benefits

We know that a company's success starts with its employees, and that an individual's success starts with the right career opportunity. Join our team today!

• Health, Dental, Vision insurance

• 401(k) with company matching

• Paid time off

• 7 paid company holidays

• 4 floating holidays per year

• Life Insurance and AD&D Insurance

• Long Term Disability

• Health Care Reimbursement Flexible Spending Account

• Dependent Care Flexible Spending Account

• EAP (Employee Assistance Program)

• Pet Insurance